#111 EMS initialisation causes wacky screen corruption

7.0 beta
closed
nobody
None
9
2008-01-24
2008-01-18
Mark Grant
No

If I load any scenario which is missing the 'DVINITIALIZED' line in the EMS entries, then switch to the main control panel with F1, my monitor goes black... even if Orbiter is just running in a window.

I'm guessing this is a combination of an Nvidia DirectX bug with something weird that the EMS is doing when that variable isn't set in the scenario. Either way, the default configuration of the EMS should be checked to ensure that it's in a sensible state if the scenario doesn't contain this line.

This happens, for example, with the standard historical scenarios in CVS. Add EMS_BEGIN, DVINITISALIZED 1 and EMS_END, and it stops.

Discussion

  • Mark Grant

    Mark Grant - 2008-01-18

    Logged In: YES
    user_id=1209252
    Originator: YES

    OK, the problem appears to be that the code doesn't set sensible values for all class variables in the constructor. If DVINITIALIZED isn't set to true, then it skips most of the timestep function and just sets the LastWeight; other code later must look at variables like xacc and do something horribly wrong!

    I can stop the bug occuring by setting xacc to zero if !DVInitialized, but I'm not sure whether that's the correct fix. Hopefully someone else can figure out what the code should be doing there.

     
  • Mark Grant

    Mark Grant - 2008-01-24
    • status: open --> closed
     
  • Mark Grant

    Mark Grant - 2008-01-24

    Logged In: YES
    user_id=1209252
    Originator: YES

    Now fixed!

     

Get latest updates about Open Source Projects, Conferences and News.

Sign up for the SourceForge newsletter:

JavaScript is required for this form.





No, thanks