|
2004-11-08 02:37
|
|
|
|
What build are you using? What are your system's specs? D3D or OGL? What version of D3D are you using? What version of Windows? |
|
|
Build: fs2_open_r.exe dated 11/6/04 System Specs: 2600+ XP 512 RAM Radeon 9600 256MB Using D3D, by version are you referring to something like DirectX8 or 9? In any case DX9.0b Using Windows98SE |
|
|
The comm animations aren't supposed to show up when the hud is disabled. I'm not sure if showing them was the intent though so Goober5000 will have to clarify that. The hud-disable-except-messages sexp does look like it is supposed to show the anims but they just aren't turned on if the rest of the hud is off. Without more than a quick look at the code it just appears that the hud_disabled_except_messages() check wasn't ever added to HUD_render_3d() so only the 2D gauges would be turned off by the sexp. Adding it there would turn off the offscreen target triagles, message sender brackets, etc. so I don't know if that is what's really wanted. For your observation specifically it needs to be in hud_show_radar() and hud_show_target_model() since they are called separately from normal hud rendering. hud_disable_except_messages(0) probably needs to be called in HUD_init() to make sure it doesn't stay disabled on the next mission. If Goober5000 doesn't get the chance to fix this before me I'll make the changes when I next can. |
|
|
Fixered. Test it in the next build somebody releases and if it's not just what you were looking for please reopen this bug. |
|
|
I just tried it with the 20041215 build. The radar, enemy box, and the center of the hud gauges go away when I want, but the the orientation indicator, enemy hull strength, speed and distance and shield diagram still appear. I just put up a screen of what it looks like so you can see exactly what doesn't go away. edited on: 12-21-04 20:13 |
|
2004-12-22 01:13
|
screen00.jpg (13,713 bytes) |
|
|
Aw, munch. Taylor, I'm not sure I like the idea of putting the "everything at once" code inside hud_disabled_except_messages(). For one thing, it's supposed to be an accessor that just returns a value, not something with a side-effect. For another thing, since it's called from several different parts in the code, it ends up drawing the message stuff more than once per frame, which is wasteful. What was wrong with the original code? I might be able to roll it back and fix it properly. |
|
|
Your right, what I changed it to is wrong. I've got to update it anyway to fix the other things Axem mentioned so I'll fix it. Don't roll it back since I know exactly what to change to render it once. I did have code in there is disable at the start of a mission though. Guess I forgot to commit that or something. |
|
|
The only thing needed to reset the HUD at the begining of a mission is an initializer in hud_init, which I committed just now. As for the rest, I'll comment after I see what you come up with. edited on: 12-26-04 16:51 |
|
|
Alright Goober check it out and tell me what you think. @Axem: Using your mission as a test all of the hud stuff except the messages, talking head, and message indicator (offscreen indicator for ship talking, grey outline of talking ship) are off. If builds after this moment don't work let me know. I'll leave this bug open for a day or two and try to get you a new build to test. |
|
|
@Axem, forgot to tell you to try either of my newer builds (20041230 / 20050103) since both have this fix. Please update if it's really fixed. |
|
|
Yay, it works, it works! Me and my ingame cutscenes salute you sir. :-) |
|
|
Fixered. Properly this time. |
- Anonymous
