In my next MFD, I'm getting sometimes (sometimes none after 15+min of tests) an exception raised by ddraw.dll, according to the C++ debugger. My MFD switches automatically from a view to another, from a vessel to another, and moves the camera based on some computation. It doesn't look like other errors with ddraw reported by @moonheart , @TheDarkDecidueye or earlier. Here it is:
"Exception raised at 0x7A96A999 (ddraw.dll) in orbiter.exe: 0xC0000005: Access violation when reading from location 0x00000004."
Precisions: at the time of crash, no overload of GPU (<80%), CPU (ca. 50%) nor Memory (<500MB), no use of orbiter_ng, no optimization in compilation (debug flavour).
Any suggestion? Possible relevant question(?): if it is a memory problem (ram/vram), is there a way to force Orbiter to purge unused memory?
"Exception raised at 0x7A96A999 (ddraw.dll) in orbiter.exe: 0xC0000005: Access violation when reading from location 0x00000004."
Precisions: at the time of crash, no overload of GPU (<80%), CPU (ca. 50%) nor Memory (<500MB), no use of orbiter_ng, no optimization in compilation (debug flavour).
Any suggestion? Possible relevant question(?): if it is a memory problem (ram/vram), is there a way to force Orbiter to purge unused memory?