Closed chhhrrriiisss closed 8 years ago
Watching replays of footage seems to indicate at least one of these errors is a result of rocket pods exploding nearby the client.
GW_HUD_NORMAL_ACTIVE = true; GW_HUD_VEHICLE_ACTIVE = false; GW_HUD_REFRESH = false; GW_INVEHICLE = false; GW_ISDRIVER = false;
States after a rocket pod explodes nearby (not every time, just some times). Seems to indicate GW_INDRIVER and GW_ISDRIVER get reset and cause the HUD to default to "normal" mode.
This is a tricky and very difficult to replicate bug. It seems to occur more frequently in populated battles and under a specific climate of weapon/module combinations.
Symptoms include a sudden loss of visible weapon/module timers on the right hand side of the HUD and an inability to shoot weapons or activate modules (despite no debuff preventing it). Fix is to exit and re-enter said vehicle which causes a HUD reset and a vehicle re-compile to correct the error.
The times it has happened frequently have distinctly occurred fighting against specific vehicles and in quick succession (sometimes several failures inside of a minute), so there's a good chance it is an offensive module or combination of modules that's causing a corrupted or unhandled status on the receiving client's HUD.
If there is anyone who can replicate this bug consistently, i'd be really interested to hear about it!