[IceFire]

I've got a very small but very annoying bug that I can replicate over and over and over again.  To the point of driving me insane.  I cannot use any of the 3.5's without this happening.

Here is the bug.

Fly around, have a nice battle like normal.  If you press 'Y' for targeting in quick succession (your searching for that specific fighter infront of you) and you happen to target a piece of debris, an asteroid field, or a debris field, the game crashes to desktop.  No errors, no messages, just crash.

Yes I have submitted a bug report but I haven't heard word.  Thought I would remind everyone

And I thought I would ask if others have the same problem.  TO be sure.

[Bobboau]

could you run a debug build and see if it spews anything

[Goober5000]

Refer back to your bugzilla entry... I replied.
http://fs2source.warpcore.org/bugzilla/show_bug.cgi?id=65

I looked through the code and could find no place where this might occur.  Then I ran latestrelease.exe and did not get the bug.  I assume it is fixed.  (Yes, I did notice the bug in earlier versions.)  Can you try latestrelease.exe?

[IceFire]

My appologies...I seemed to have missed your reply.  I shall test the new exe for the problem.  Thanks!

[IceFire]

Well done...the bug has indeed been fixed.  Thank you!

[Hippo]

is this in any way related to why the hud changes olors hen you target debris? or was tht fived in 3.5?

[IceFire]

Originally posted by Hippo
is this in any way related to why the hud changes olors hen you target debris? or was tht fived in 3.5?

Thats from FS2 and I forget what the cause was, but it has something to do with drawing polys.

[Goober5000]

I believe that was fixed as well.

[Goober5000]

*bump*, because this bug has reared its ugly head again.  Can anyone figure out what's going on?

[Flipside]

Yes, I seem to be getting this bug from time to time. No real rhyme or reason to it apparently, just when you target a ship ( I was using 'target ship in reticle', on occasion,  it crashes out without error

Flipside

[diamondgeezer]

I quite happily targeted some debris the other day under 355... I used a joystick button bound to the function rather than Y, but I wouldn't have thought that would have made a difference.

[StratComm]

I got this when targeting in a nebula... the first nebula mission actually, and I pressed 'y' while the shivans were still out of sensor range.  It targeted them, then crashed.

[CP5670]

I have run into this problem countless times in the past with the retail 1.2 version, but it seemed to have gone away with the open versions. However, I did see it again about three days ago with 3.55; I was cycling through a bunch of enemy fighters (I use q for hostile targeting) in an asteroid belt and an asteroid somehow got targeted for like half a second, after which it dumped me to windows. I was not able to reproduce the bug with the same general actions, and it seems to be pretty random.

[CP5670]

gah...sorry for bumping this but I just got this problem like four times in a row and it's really starting to piss me off now. Once it happened when I was not changing targets but launching bombs instead, although as usual it screwed up right when I pressed the key. Also, windows then behaved as if I was holding down the key; I use ctrl for secondary firing, and IE was acting strange (e.g. pressing f would bring up the find menu and using the mouse scroll wheel would change the font size) until I hit ctrl again. There might be some problem with the input system.