How the heck did I die? (Destiny)

by Claude Errera @, Saturday, January 09, 2016, 05:35 (3336 days ago)

Fresh health, no enemies in sight... how did I die?

http://xboxdvr.com/gamer/Louis%20Wu/video/13775489

Avatar

weak ankles apparently

by unoudid @, Somewhere over the rainbow, Saturday, January 09, 2016, 05:41 (3336 days ago) @ Claude Errera

- No text -

Avatar

Brain Hemmorhage.

by BeardFade ⌂, Portland, OR, Saturday, January 09, 2016, 05:49 (3336 days ago) @ Claude Errera

- No text -

Avatar

Beats me

by Kahzgul, Saturday, January 09, 2016, 08:49 (3336 days ago) @ Claude Errera

That's a new one to me. If I had to guess, you found a microscopic seam in the geometry and got stuck in it so the game killed you as a means of freeing you? Except we already know Destiny doesn't do that. It looked like maybe falling damage... are you running a weird absolute minimum armor build?

Avatar

IDK, he took a half a step.

by Funkmon @, Saturday, January 09, 2016, 13:24 (3336 days ago) @ Kahzgul

Must be undiagnosed aneurysm.

Beats me

by Claude Errera @, Saturday, January 09, 2016, 16:57 (3336 days ago) @ Kahzgul

That's a new one to me. If I had to guess, you found a microscopic seam in the geometry and got stuck in it so the game killed you as a means of freeing you? Except we already know Destiny doesn't do that. It looked like maybe falling damage... are you running a weird absolute minimum armor build?

Nope, actually spec'd for toughness.

Please take care of yourself

by General Battuta, Saturday, January 09, 2016, 12:23 (3336 days ago) @ Claude Errera

Louis Wu is down

Feel better soon :(

Avatar

Heh.

by Ragashingo ⌂, Official DBO Cryptarch, Saturday, January 09, 2016, 14:31 (3336 days ago) @ General Battuta

- No text -

Misadventure

by petetheduck, Saturday, January 09, 2016, 16:26 (3336 days ago) @ Claude Errera

- No text -

Avatar

Used a Hunter.

by ProbablyLast, Saturday, January 09, 2016, 17:20 (3336 days ago) @ Claude Errera

- No text -

Avatar

+1. Obvious cause. Y'all should know this by now

by ZackDark @, Not behind you. NO! Don't look., Saturday, January 09, 2016, 17:48 (3336 days ago) @ ProbablyLast

- No text -

-1 (:

by Oholiab @, Saturday, January 09, 2016, 19:15 (3336 days ago) @ ZackDark

- No text -

Avatar

There's some raging on reddit about similar things happening

by unoudid @, Somewhere over the rainbow, Saturday, January 09, 2016, 22:57 (3336 days ago) @ Claude Errera

- No text -

Avatar

There's some raging on reddit about similar things happening

by Ragashingo ⌂, Official DBO Cryptarch, Sunday, January 10, 2016, 01:21 (3335 days ago) @ unoudid

I've been dying to Fist of Havocs a lot recently... My Fist of Havocs... :/

Avatar

There's raging on Reddit for everything.

by Funkmon @, Sunday, January 10, 2016, 01:57 (3335 days ago) @ unoudid

For example, the anger at Xur.

Xur hasn't sold an engram in 6 weeks!

6 weeks earlier

FFS IDK why Bungie thinks it can give us engrams and not guns. Why do they force RNG on us?

Avatar

There's raging on Reddit for everything.

by Xenos @, Shores of Time, Sunday, January 10, 2016, 03:19 (3335 days ago) @ Funkmon

For example, the anger at Xur.

Xur hasn't sold an engram in 6 weeks!

6 weeks earlier

FFS IDK why Bungie thinks it can give us engrams and not guns. Why do they force RNG on us?

Yeah my favorite reaction to this glitch is someone saying "A glitch like this SHOULD not be happening for more than a few days." (that's a direct quote). Someone doesn't know much about programming and debugging...

Rofl

by Raflection, Sunday, January 10, 2016, 16:39 (3335 days ago) @ Xenos

Maybe they would prefer bungie put destiny servers offline for a few days to test it and fix it?

live world

How easy do they think this shit is? It took them a year to nerf ghorn xD

Avatar

From my professional experience

by Kahzgul, Monday, January 11, 2016, 01:43 (3334 days ago) @ Raflection

The problem isn't fixing the bug. Good coders (and Bungie has loads of them, though apparently not in the "tools" department) can fix scores of bugs in a day. The problem is figuring out what the bug really is. Anything that's not 100% reproducible is nearly impossible to just go in and fix, because you don't really know what's causing the bug. Anything that is 100% reproducible still needs to be pared down to the absolute minimum number of steps in order to really figure out what's going on.

Let's take the Birth of History ship's glaring graphics bug, for example. Obvious bug, 100% reproducible. There's a giant hole in the middle of the ship; it's clearly unintentional since it lets you see out through the back of other textures on the ship. Obvious obvious obvious.

I'm assuming (based on comparison to other ships' graphics with similar components) that the problem is actually that the back part of the ship is too far away from the middle of the ship, leaving a gap. Seems like a really simple change to a z-coordinate value would solve the issue (or y coord or x coord depending on how they have things arranged).

BUT it could be that there is actually geometry at that position, and instead the texture is flipped (textures in Destiny are 1-way, as we've observed when we see through objects). They can't magically make all textures 2-way because then things like the pumpkin on your head would suddenly occlude your vision. So they have to figure out if the problem is the texture was created with the wrong side up (unlikely, since ship art is re-used and we'd see this problem on other ships), or added to this particular ship component facing the wrong way (again, unlikely, same reason), or if there's something special with this particular ship where the component was added in a unique way that messed up all the art (like the y axis values were inverted, which someone thought would make the component upside down, but actually made it inside out).

OR maybe all of the art assets are totally fine on the ship. If you load the ship up on its own using the dev tools that take overnight just to load a map because god damn stupid tools design that makes patching the game take forever UGH BUNGIE YOU KNOW BETTER, the ship is just fine. Like totally fine. Which means the missing art has to do with some kind of weird interaction with other elements in the game. Probably the UI, like they share texture memory space, and the UI code guarantees that it always wins when there's a conflict. This would be a problem for that texture with that particular color pallette (which is, afaik, unique), but would not necessarily be easy to fix because artists don't generally dictate how texture memory allocation occurs, but - rather - the core engine figures it out on its own. So you'd need to figure out why the core engine is making this mistake and then re-write the whole core engine and hope nothing else broke in the process. This is also unlikely, because bad gfx engine code tends to cause far more problems than one single isolated missing texture.

So if I'm being totally honest, it really does seem like the only reason there's a hole in that ship is that Bungie is being lazy as hell fixing a pretty basic art issue of misplaced assets. Seriously guys, you only have to change one number.

--

But I digress. Sometimes the bug is really difficult to parse. You have to capture the event live, using a dev kit that you can then interrupt and go back to look at what procedures called what other procedures and where the decision to do the buggy thing came from. So really really really rare bugs like this one are pretty tough to figure out. It's actually easier to do since the game is live and you get more instances of the bugs occurring, but still very hard.

Avatar

What He said

by MacAddictXIV @, Seattle WA, Monday, January 11, 2016, 12:20 (3334 days ago) @ Kahzgul

As someone who works on a live system and influence by data from other people. I agree that reproduction is essential to fixing a bug. Mainly because there are way to many unknowns with data you can't directly control.

Avatar

I have an alternate view...

by slycrel ⌂, Monday, January 11, 2016, 16:10 (3334 days ago) @ Kahzgul

I think it's listed as a valid bug in their DB. I strongly suspect that they have a "will not fix" category. See also dancing on a sparrow. it's likely that this isn't a high enough priority to get attention. They're to busy fixing other things that are more meaningful.

Anything can be fixed given the time and effort. I strongly suspect this one doesn't make that tradeoff of resources spent vs result achieved.

Back to the forum index
RSS Feed of thread