Meadville Space Center
Welcome, Guest. Please login or register.
September 23, 2020, 11:18:13 PM

Login with username, password and session length
Search:     Advanced search
Welcome to the new Meadville Space Center forums!
25068 Posts in 2094 Topics by 2266 Members
Latest Member: twa517
* Home Help Search Login Register
+  Meadville Space Center
|-+  Project Apollo - NASSP
| |-+  Project Apollo - NASSP Development
| | |-+  Programming (Moderators: movieman, dseagrav, Swatch, lassombra)
| | | |-+  Initialisation
« previous next »
Pages: [1] Print
Author Topic: Initialisation  (Read 891 times)
movieman
Moderator
Hero Member
****
Posts: 1710



View Profile
« on: June 10, 2006, 08:56:57 AM »

BTW, we should initalise all floating point values to zero or some other sensible value in the constructor for our classes. I've just been fixing a bunch of bugs where Orbiter explodes on saving the scenario because there's some random value in a double which makes the oapiWriteScenario_float() function crash.

Worst of all it leaves you with a corrupt scenario file that you can't load.

This often wasn't a problem before when we started up the scenarios with the buses powered, because the timestep code would load sane values into the variables. But now we start unpowered, those values don't get loaded and if you save then Orbiter blows away.
Logged
Pages: [1] Print 
« previous next »
Jump to:  

Powered by MySQL Powered by PHP Powered by SMF 1.1.10 | SMF © 2006-2009, Simple Machines LLC Valid XHTML 1.0! Valid CSS!