I don't know if I am talking about the same problem. But the CTDs when time-warping transfers between Earth and Moon still happen
That sounds very similar to what I'm currently chasing, except I don't get any stuttering. But the rest of the symptoms are identical: Doesn't happen in inline, doesn't happen if I take other vessels out of the scenario. I'm still looking for a waterproof repro, so far no luck. I have one at 100%, but that's with one of my own vessels, so technically there's the possibility that my code bugs out... Though the access violation isn't triggered anywhere near my code, and the ctd doesn't happen if I have the same vessel in a scenario but fly to the moon with a DG instead. I'll try to narrow it down further.
---------- Post added 07-21-16 at 09:02 PM ---------- Previous post was 07-20-16 at 10:43 PM ----------
Boom, headshot!
I have a 100% repro on my ctd with a minimal scenario. Well, at least on my machine. Since the CTD is caused by an access violation, your lineage may vary, but I hope not.
It is important to note however that I was only able to reproduce running in D3D9 client!
So there is a chance that it is a client-side issue. The reason why I'm posting it here is because of a dependency of the crash on the presence (and apparently state) of GL-01 in the scenario (see below for circumstances under which the crash will not happen).
So here's the scenario:
Code:
BEGIN_DESC
END_DESC
BEGIN_ENVIRONMENT
System Sol
Date MJD 51982.6414158006
Help CurrentState_img
END_ENVIRONMENT
BEGIN_FOCUS
Ship ProjectAlpha_ISS
END_FOCUS
BEGIN_CAMERA
TARGET ProjectAlpha_ISS
MODE Extern
POS 34.269927 171.965869 162.003817
TRACKMODE TargetRelative
FOV 34.00
END_CAMERA
BEGIN_SHIPS
ISS:ProjectAlpha_ISS
STATUS Orbiting Earth
RPOS -10873977.777 16.436 -804218.703
RVEL -4502.1663 0.1564 -7158.3635
AROT 156.154 33.561 25.304
AFCMODE 7
IDS 0:588 100 1:586 100 2:584 100 3:582 100 4:580 100
NAVFREQ 0 0
XPDR 466
END
GL-01:DeltaGlider
STATUS Orbiting Earth
RPOS -5543461.122 2938905.831 -2274724.174
RVEL 4503.7488 5004.5322 -3862.4400
AROT -55.968 -29.940 94.891
AFCMODE 7
PRPLEVEL 0:0.553000 1:0.900000
NAVFREQ 0 0 0 0
XPDR 0
HOVERHOLD 0 1 0.0000e+000 0.0000e+000
AAP 0:0 0:0 0:0
END
END_SHIPS
Reproduction:
IMPORTANT: run in windowed mode, not fullscreen (fullscreen window is ok). When the thing crashed in fullscreen with the debugger hooked in the system couldn't get posession of the screen back, shooting down the task didn't have any effect and I had to reboot.
Start scenario. You'll see the ISS, it's on its way to the moon (don't even ask).
Turn time-accel up to 10,000 (press t 4 times).
At MJD 51985.8, turn time acceleration down to 1000 (press r once).
CTD should occur shortly thereafter. If you make it all the way around the moon, it probably won't happen ever.
CTD will NOT happen when:
You fly by the moon with timeaccel at 10'000
You remove GL-01 from the scenario
You switch the state vectors of ISS and GL-01, taking the glider insted of the ISS to the moon, but preserving the gliders state vectors on the ISS.
Things I found had no influence:
Any kind of graphical settings (terrain- and texture resolution, mipmap settings etc) had no impact on the behavior.