|
2005-03-19 18:49
|
screen0000.jpg (27,895 bytes) |
|
|
It's, uuuhhh... uummmm.... eeehhh, yeah. That's pretty friggin weird :) Does this happen on other builds too? If it's not happening in newer builds then whatever was causing it may be fixed. I'll take a look anyway though, pretty interested to know where that's coming from. |
|
|
it happened in his P4 build, and the one for not p4's... i haven't seen it anywhere else though... |
|
|
Wait, wasn't that my build? The cmdline shows my exec name. |
|
|
no, i had switched over builds, since his p4 one didn't let me view me ships exterior (it gave me a CTD on the death screen, warpout, and pressing . or *)... I just copied that for the lines... |
|
|
WMC perhaps? |
|
|
Yeah, I'm betting that this is more a product of optimization that an actual code error. I want to try and track it down a little first before passing it along though. If it's optimization related then it's possible that it could affect Linux builds too at some point so I'd like to head it off early. |
|
|
I'm seeing the same thing (and accidentally posted that duplicate bug - missed this somehow) in fs2_open_C20050318.exe (both normal and p4 optimized). I'll bet that's the build in question. And yeah, it's weird. It also may be something that WMC's playing with interface-related; the first thing I thought when I saw it was that someone was trying to impliment a label system for ships in-mission. Sort of like the "FRED Replacement" (but not really, more like a mission timing and physics simulator) he mentioned a while back. |
|
|
Ok, moving the WMC then. I still haven't been able to have this happen in any of my builds, on Windows or Linux. Since it only appears to happen on this one build set then it should be considered build related until proven otherwise. I tried going with full optimizations on the Linux builds without this problem so I'm not really worried about it for the future at this point. |
|
|
Ahh, this again. I *think* this is caused by some code I put in to test out my dynamic clipping distance stuff; I left the numbers in there for awhile, and forgot about them, until I ran into this same problem - probably caused by the Zbuffer being dynamically changed before/after I rendered the text. I'm pretty sure when I #ifdef'd the code out, I made sure I removed the code to draw the numbers (Basically what it is is the distance to the closest object; unfortunately, it didn't work well with beams or particles and I couldn't work around those by clearing the zbuffer for obvious reasons.) Summary: It shouldn't occur with any new builds. I'm going to leave this bug open for now, if no one notices by a week after the next build is posted, I'll either close this entry, or have forgotten about it. :P |
|
|
http://mgo.maxgaming.net/mantis/bug_view_advanced_page.php?bug_id=0000365 |
|
|
I'm pretty sure this is fixed, if it pops up again, PM me mor something and I'll reopen this bug. |
- Anonymous
