[0957] CTD on acquiring bomb lock-on
Posted: 2011-07-01 14:25
Description:
The protagonists: [NEW] Rag3 in the F-16 and me in the A-10.
What happened:
1. Our spotter lased a tank. Rag3 approaches it and CTDs at about the time when he felt he should have acquired a lock-on
2. Rag3 rejoins the server.
3. Our spotter lases a tank in the same area as before, unfortunately i can't remember if it was actually the same one. I approach and CTD right whe i felt i should have gotten a lock-on.
4. I rejoin the server only to find out that Rag3 had gotten a second CTD simultaneously with me. He was doing infantry at that time, the F-16 hadn't respawned yet.
So, if it wasn't for Rag3s second CTD, one could argue that those were just computing-power-related CTDs, i.e. our computers failed to keep up with rendering etc. while quickly diving below the clouds.
But this only happened when going for a lase, not for instance in a dogfight that took place earlier.
Also, to preempt that response, if we had problems like that frequently, we wouldn't fly jets.
And Rag3s second CTD seems to suggest that whatever was wrong, "stuck" with him even after rejoining the server and when not flying.
Unfortunately i can't remember if we had any successful bomb-runs before or after that or if the round was bugged all the time.
Steps to Reproduce:
???
Screenshots / Video:
none
Tested On:
New Era Warfare, some time last weekend
Kashan Desert AAS 64
The protagonists: [NEW] Rag3 in the F-16 and me in the A-10.
What happened:
1. Our spotter lased a tank. Rag3 approaches it and CTDs at about the time when he felt he should have acquired a lock-on
2. Rag3 rejoins the server.
3. Our spotter lases a tank in the same area as before, unfortunately i can't remember if it was actually the same one. I approach and CTD right whe i felt i should have gotten a lock-on.
4. I rejoin the server only to find out that Rag3 had gotten a second CTD simultaneously with me. He was doing infantry at that time, the F-16 hadn't respawned yet.
So, if it wasn't for Rag3s second CTD, one could argue that those were just computing-power-related CTDs, i.e. our computers failed to keep up with rendering etc. while quickly diving below the clouds.
But this only happened when going for a lase, not for instance in a dogfight that took place earlier.
Also, to preempt that response, if we had problems like that frequently, we wouldn't fly jets.
And Rag3s second CTD seems to suggest that whatever was wrong, "stuck" with him even after rejoining the server and when not flying.
Unfortunately i can't remember if we had any successful bomb-runs before or after that or if the round was bugged all the time.
Steps to Reproduce:
???
Screenshots / Video:
none
Tested On:
New Era Warfare, some time last weekend
Kashan Desert AAS 64