Aeadar
Lurker Representitive
- Joined
- Apr 30, 2009
- Messages
- 456
- Reaction score
- 3
- Points
- 18
Ya know, I truly love Orbiter and I'm not quite sure what to do anymore. With 2006P1 virtually everything I downloaded went into my single installation, and while not every add-on worked, I was still able to maintain an evolving scenario with nearly a dozen different add-on ships, including 8 or 9 DGIVs, 3 to 6 Prelude bases, Heinlein, Niven ,and DunOrbitin lunar bases, Celestium Station, Bond-Vaga (if I remember the name correctly), the Big Wheel, Energia, 4 or 5 add-on MFDs, WIN, and large numbers of assorted Greg Burch Space Station modules, a couple of which being used to stick multiple stock wheel stations together (with the hi-res 'shiny' skin, of course), multiple, attached ISSs, hi-res textures for Earth, Moon and Mars. And that's just the add-ons that come to mind at the moment. I was able to maintain this scenario over almost a year of 'sim-time', involving hundreds of scenario saves.
Now comes Orbiter 2010, which I love even more. So much nicer visually. The exponential stars in 2010 are so much nicer than 2006, which always kind of reminded me of the old 'flying through stars' screensaver. But with 2010(100606) I've run into problems with doing multiple saves. Other than with AMSO, that's worked great. But after a few AMSO missions, I got to thinking of doing a Deepstar mission. So I created a new install, downloaded Deepstar and started a scenario beginning with a shakedown cruise to the moon and back to LEO. Now, I don't really like that much time acceleration, so I can easily save a scenario 10 times or more doing a lunar mission. And so, after 10 or 12 saves I'm back at LEO but I'm starting to get instances of the simulation session not closing when I exit Orbiter. So, I started using quicksave instead but after a few of those suddenly Orbiter would close when reloading the scenario. About this time I was starting to get into the idea of the same type mission with UMMU. So...new install, downloaded latest version of Hispas Longshot and DanStephs UMMU ShuttleA along with the latest DGIV. UMMU ShuttleA docked to Longshot and crew transffered, no problem. Then launch DGIV, rendezvous and dock with Longshot, transfer crew, save the scenario after which trying to reload the scenario resulted in Orbiter closing every time I tried.
I'm not very good at interpreting the orbiter.log, but I never found any instances of the word, 'error'. So I get on the forum to see if any others have had similar problems and I see talk of 2010P1. Needless to say, I forget about my problem and download P1, set up an install, add Longshot, UMMU ShuttleA and the latest XR-2 since it has the local lights. Again, after I dock the XR-2 to Longshot and transfer the crew, I save the scenario. This time it does reload, but the sim runs for exactly 99 seconds and then closes. I've tried this 4 times now and every time it's the same. At some point I realize that I have a couple of add-ons in this install as well; Aurora lunar base and DGIV, so over the weekend I try another new install, this time just 2010P1, OrbiterSound3.5, and again the UMMU ShuttleA and latest XR-2, and Wideawake International.
This time, I start with the XR-2 scenario, "Prototype", in the, "SKINS" folder, use scenario editor to locate the XR-2 at Wideawake, and add Longshot to orbit, thinking to launch, rendezvous, and dock, then transfer the crew, exiting and saving at each stage, checking at each reload to see the the sim goes past 99 seconds. And all goes well. Scenario reloads and continues past 99 seconds after crew transfer. So I then add the UMMU ShuttleA, place in also at Wideawake, add a crew. Same process, launch, rendezvous, dock, again checking at each stage. This time the scenario save just after docking doesn't load and at first I got no errors in the orbiter.log. Today though, I saw a post from Izack about Orbiter shutdown options > Respawn Orbiter process, so I tried that and the senario loaded...once, but the shuttleA was invisible. Subsequent attempts to reload the scenario resulted in Orbiter closing, but now the .log shows an error;
I realize this points to the UMMU ShuttleA, but I seem to have had problems with continuing ANY scenarios in 2010 or 2010P1 that have multiple add-on vessels in the scenario. No matter what the vessels are. Only AMSO saves and reloads time after time without trouble. I'm getting pretty desperate. Running add-ons in Orbiter has always carried a certain level of frustration for some, who, like me know nothing really about coding. A bit of tinkering with BASIC back in the Timex/Sinclair and Commodore 64 days, but that's it. Still, the frustration level was acceptable with 2006P1. Since going to 2010 and 2010P1 though, it seems as though I can barely get a scenario off the ground, as it were.
And the truly frustrating part is that I've now been completely seduced by P1s 'visible light' celestial sphere (Dammit Martin!
). Absolutely gorgeous. Of course, that means the stars in 2006P1 now look even more like an old video game. I suppose I could turn them off, but I'm also hooked on the local lights after one docking using them.:lol:
EDIT: Just got my, "HAIL PROBE' shirt today and looking forward to debuting it at work next week.
:hail:
Now comes Orbiter 2010, which I love even more. So much nicer visually. The exponential stars in 2010 are so much nicer than 2006, which always kind of reminded me of the old 'flying through stars' screensaver. But with 2010(100606) I've run into problems with doing multiple saves. Other than with AMSO, that's worked great. But after a few AMSO missions, I got to thinking of doing a Deepstar mission. So I created a new install, downloaded Deepstar and started a scenario beginning with a shakedown cruise to the moon and back to LEO. Now, I don't really like that much time acceleration, so I can easily save a scenario 10 times or more doing a lunar mission. And so, after 10 or 12 saves I'm back at LEO but I'm starting to get instances of the simulation session not closing when I exit Orbiter. So, I started using quicksave instead but after a few of those suddenly Orbiter would close when reloading the scenario. About this time I was starting to get into the idea of the same type mission with UMMU. So...new install, downloaded latest version of Hispas Longshot and DanStephs UMMU ShuttleA along with the latest DGIV. UMMU ShuttleA docked to Longshot and crew transffered, no problem. Then launch DGIV, rendezvous and dock with Longshot, transfer crew, save the scenario after which trying to reload the scenario resulted in Orbiter closing every time I tried.
I'm not very good at interpreting the orbiter.log, but I never found any instances of the word, 'error'. So I get on the forum to see if any others have had similar problems and I see talk of 2010P1. Needless to say, I forget about my problem and download P1, set up an install, add Longshot, UMMU ShuttleA and the latest XR-2 since it has the local lights. Again, after I dock the XR-2 to Longshot and transfer the crew, I save the scenario. This time it does reload, but the sim runs for exactly 99 seconds and then closes. I've tried this 4 times now and every time it's the same. At some point I realize that I have a couple of add-ons in this install as well; Aurora lunar base and DGIV, so over the weekend I try another new install, this time just 2010P1, OrbiterSound3.5, and again the UMMU ShuttleA and latest XR-2, and Wideawake International.
This time, I start with the XR-2 scenario, "Prototype", in the, "SKINS" folder, use scenario editor to locate the XR-2 at Wideawake, and add Longshot to orbit, thinking to launch, rendezvous, and dock, then transfer the crew, exiting and saving at each stage, checking at each reload to see the the sim goes past 99 seconds. And all goes well. Scenario reloads and continues past 99 seconds after crew transfer. So I then add the UMMU ShuttleA, place in also at Wideawake, add a crew. Same process, launch, rendezvous, dock, again checking at each stage. This time the scenario save just after docking doesn't load and at first I got no errors in the orbiter.log. Today though, I saw a post from Izack about Orbiter shutdown options > Respawn Orbiter process, so I tried that and the senario loaded...once, but the shuttleA was invisible. Subsequent attempts to reload the scenario resulted in Orbiter closing, but now the .log shows an error;
Code:
**** Orbiter.log
Build Aug 30 2010 [v.100830]
Timer precision: 3.39776e-007 sec
Found 0 joystick(s)
Devices enumerated: 3
Devices accepted: 3
==> RGB Emulation
==> Direct3D HAL
==> Direct3D T&L HAL
Module AtlantisConfig.dll .... [Build 100830, API 100830]
Module AtmConfig.dll ......... [Build 100830, API 100830]
Module DGConfigurator.dll .... [Build 100830, API 100830]
Module Meshdebug.dll ......... [Build 100830, API 100830]
Module TrackIR.dll ........... [Build 100830, API 100830]
TrackIR module not found.
Module CustomMFD.dll ......... [Build 100830, API 100830]
Module LuaMFD.dll ............ [Build 100830, API 100830]
Module transx.dll ............ [Build 100824, API 100823]
Module OrbiterSound.dll ...... [Build ******, API 060425]
---------------------------------------------------------------
>>> WARNING: Obsolete API function used: oapiRegisterMFDMode
At least one active module is accessing an obsolete interface function.
Addons which rely on obsolete functions may not be compatible with
future versions of Orbiter.
---------------------------------------------------------------
Module LuaConsole.dll ........ [Build 100830, API 100830]
Module ScriptMFD.dll ......... [Build 100830, API 100830]
Module ExtMFD.dll ............ [Build 100830, API 100830]
Module FlightData.dll ........ [Build 100830, API 100830]
Module Framerate.dll ......... [Build 100830, API 100830]
Module Rcontrol.dll .......... [Build 100830, API 100830]
Module ScnEditor.dll ......... [Build 100830, API 100830]
**** Creating simulation session
DirectDraw interface OK
Direct3D interface OK
Graphics: Viewport: Fullscreen 1280 x 1024 x 32
Graphics: Hardware T&L capability: Yes
Graphics: Z-buffer depth: 32 bit
Graphics: Active lights supported: 8
Loading 15382 records from star database
Module Sun.dll ............... [Build 100830, API 100830]
VSOP87(E) Sun: Precision 1e-006, Terms 554/6634
Module Mercury.dll ........... [Build 100830, API 100830]
VSOP87(B) Mercury: Precision 1e-005, Terms 167/7123
Module Venus.dll ............. [Build 100830, API 100830]
Module VenusAtm2006.dll ...... [Build 100830, API 100830]
VSOP87(B) Venus: Precision 1e-005, Terms 79/1710
Module Earth.dll ............. [Build 100830, API 100830]
Module EarthAtmJ71G.dll ...... [Build 100830, API 100830]
VSOP87(B) Earth: Precision 1e-008, Terms 2564/2564
Module Moon.dll .............. [Build 100830, API 100830]
ELP82: Precision 1e-005, Terms 116/829
Module Mars.dll .............. [Build 100830, API 100830]
Module MarsAtm2006.dll ....... [Build 100830, API 100830]
VSOP87(B) Mars: Precision 1e-005, Terms 405/6400
Module Phobos.dll ............ [Build ******, API 060425]
Module Deimos.dll ............ [Build ******, API 060425]
Module Galsat.dll ............ [Build 100217, API 100215]
Module Jupiter.dll ........... [Build 100830, API 100830]
VSOP87(B) Jupiter: Precision 1e-006, Terms 1624/3625
Module Io.dll ................ [Build 100217, API 100215]
Module Europa.dll ............ [Build 100217, API 100215]
Module Ganymede.dll .......... [Build 100217, API 100215]
Module Callisto.dll .......... [Build 100217, API 100215]
Module Satsat.dll ............ [Build 100215, API 100212]
Module Saturn.dll ............ [Build 100830, API 100830]
VSOP87(B) Saturn: Precision 1e-006, Terms 2904/6365
Module Mimas.dll ............. [Build 100215, API 100212]
SATSAT Mimas: Terms 113
Module Enceladus.dll ......... [Build 100215, API 100212]
SATSAT Enceladus: Terms 33
Module Tethys.dll ............ [Build 100215, API 100212]
SATSAT Tethys: Terms 101
Module Dione.dll ............. [Build 100215, API 100212]
SATSAT Dione: Terms 59
Module Rhea.dll .............. [Build 100215, API 100212]
SATSAT Rhea: Terms 68
Module Titan.dll ............. [Build 100215, API 100212]
SATSAT Titan: Terms 100
Module Iapetus.dll ........... [Build 100215, API 100212]
SATSAT Iapetus: Terms 605
Module Uranus.dll ............ [Build 100830, API 100830]
VSOP87(B) Uranus: Precision 1e-006, Terms 1827/5269
Module Miranda.dll ........... [Build ******, API 060425]
Module Ariel.dll ............. [Build ******, API 060425]
Module Umbriel.dll ........... [Build ******, API 060425]
Module Titania.dll ........... [Build ******, API 060425]
Module Oberon.dll ............ [Build ******, API 060425]
Module Neptune.dll ........... [Build 100830, API 100830]
VSOP87(B) Neptune: Precision 1e-006, Terms 391/2024
Finished initialising world
Module XR2Ravenstar.dll ...... [Build 100830, API 100830]
Module LongShot.dll .......... [Build ******, API 060425]
---------------------------------------------------------------
>>> WARNING: Obsolete API function used: VESSEL::SetBankMomentScale
At least one active module is accessing an obsolete interface function.
Addons which rely on obsolete functions may not be compatible with
future versions of Orbiter.
---------------------------------------------------------------
Module UCGOShuttleA.dll ...... [Build ******, API 060425]
---------------------------------------------------------------
>>> ERROR: Could not load vessel module: UCGOShuttleA
>>> [Vessel::LoadModule | .\Vessel.cpp | 5442]
---------------------------------------------------------------I realize this points to the UMMU ShuttleA, but I seem to have had problems with continuing ANY scenarios in 2010 or 2010P1 that have multiple add-on vessels in the scenario. No matter what the vessels are. Only AMSO saves and reloads time after time without trouble. I'm getting pretty desperate. Running add-ons in Orbiter has always carried a certain level of frustration for some, who, like me know nothing really about coding. A bit of tinkering with BASIC back in the Timex/Sinclair and Commodore 64 days, but that's it. Still, the frustration level was acceptable with 2006P1. Since going to 2010 and 2010P1 though, it seems as though I can barely get a scenario off the ground, as it were.
And the truly frustrating part is that I've now been completely seduced by P1s 'visible light' celestial sphere (Dammit Martin!
). Absolutely gorgeous. Of course, that means the stars in 2006P1 now look even more like an old video game. I suppose I could turn them off, but I'm also hooked on the local lights after one docking using them.:lol:EDIT: Just got my, "HAIL PROBE' shirt today and looking forward to debuting it at work next week.
:hail:
