I am using Orbiter 2016, D3D9ClientR4.11, Orbiter Sound 5.0, lc39a_space_x, Falcon9_2016. Running any scenarios from falcon 9 addon...any quicksaves after 1st stage separation can't be run. This while using desktop. I even re-downloaded all zips and re-installed. Works fine on laptop with a clunky frame rate but saving any Falcon 9 scenarios work fine after separations and jettisons. On desktop when attempting to run quicksave or <current_state>, it starts loading & then crashes to desktop. Desktop seems to run saved Atlantis scenarios fine after booster separation through entire missions. Problem with Space_X stuff. No other addons on either machine. Have tried running windowed and full screen. Not sure where to start looking. Thanks in advance for any suggestions.
Problem Falcon 9 Everything works on laptop but not on desktop
- Thread starter jungzimm
- Start date
You have the latest and greatest versions of everything jungzimm.
Quicksaves of the Falcon work fine after stage separation, after a couple of tests. So this'll be an easy fix.
As soumya-8974 asks, a Orbiter.log file will help the experts (not me) sort it out. As soon you have the CTD, open the Orbiter.log file and copy and paste here.
It'll be a missing mesh file, my guess.
You could also copy the whole working laptop Orbiter folder over to the desktop and see the result.
Brian's SpaceX addons are a must have
Quicksaves of the Falcon work fine after stage separation, after a couple of tests. So this'll be an easy fix.
As soumya-8974 asks, a Orbiter.log file will help the experts (not me) sort it out. As soon you have the CTD, open the Orbiter.log file and copy and paste here.
It'll be a missing mesh file, my guess.
You could also copy the whole working laptop Orbiter folder over to the desktop and see the result.
Brian's SpaceX addons are a must have
BrianJ
Addon Developer
Hi,
does it work OK if you run the scenario using default Orbiter2016 graphics (not D3D9Client)?
Also, does it work OK if you disable Orbiter Sound 5.0?
If it still crashes-to-desktop, post the scenario that causes crash and your orbiter.log here, it might give us a clue.
Cheers,
Brian
Thank you all. Will try side by side of files on laptop and desktop when able.
Brian J--yes I tried on an install w/o D3D9 and w/o sound.
Here's log after crash; and, after that, a quicksave that caused a crash when I tried to run it. The quick save was scenario: NROL76 launch(LC39A LZ1 flyback).scn
Brian J--yes I tried on an install w/o D3D9 and w/o sound.
Here's log after crash; and, after that, a quicksave that caused a crash when I tried to run it. The quick save was scenario: NROL76 launch(LC39A LZ1 flyback).scn
Here's the quicksave scn:
BrianJ
Addon Developer
Hi,
I can't see anything obviously suspicious in your orbiter.log, and the scenario you posted works OK for me on my desktop PC. I can't think of any further analytical tests - but here's a couple of wild guesses you could try:
1) Exit Orbiter launchpad completely before restarting a saved scenario.
2) Start Orbiter "Paused" (tick the Start Paused check-box on Orbiter launchpad).
3) Delete the satellite and 2nd stage vessel entry from your saved scenario (see below) - if it runs OK, we know the 2nd stage is responsible(possibly the nozzle glow effect, has caused CTD in past) and you can still watch the 1st stage land at LZ1 ;-)
Other than that, I'm stumped - sorry!
I can't see anything obviously suspicious in your orbiter.log, and the scenario you posted works OK for me on my desktop PC. I can't think of any further analytical tests - but here's a couple of wild guesses you could try:
1) Exit Orbiter launchpad completely before restarting a saved scenario.
2) Start Orbiter "Paused" (tick the Start Paused check-box on Orbiter launchpad).
3) Delete the satellite and 2nd stage vessel entry from your saved scenario (see below) - if it runs OK, we know the 2nd stage is responsible(possibly the nozzle glow effect, has caused CTD in past) and you can still watch the 1st stage land at LZ1 ;-)
Other than that, I'm stumped - sorry!
Code:
BEGIN_DESC
Orbiter saved state at T = 396
END_DESC
BEGIN_ENVIRONMENT
System Sol
Date MJD 57874.4712524908
Context SpaceX
Help CurrentState_img
END_ENVIRONMENT
BEGIN_FOCUS
Ship Falcon9
END_FOCUS
BEGIN_CAMERA
TARGET Falcon9
MODE Extern
POS 6.278367 126.186020 -9.794137
TRACKMODE AbsoluteDirection
FOV 30.00
END_CAMERA
BEGIN_HUD
TYPE Surface
END_HUD
BEGIN_MFD Left
TYPE Surface
SPDMODE 1
END_MFD
BEGIN_MFD Right
TYPE Map
REF Earth
POS 0.00 0.00
END_MFD
BEGIN_SHIPS
LZ1:Falcon9R_V12\landingpad
STATUS Landed Earth
POS -80.5430200 28.4857580
HEADING 180.00
ALT 0.418
AROT -118.158 -4.495 171.671
AFCMODE 7
NAVFREQ 0 0
PADVIS 1
END
Strongback:Falcon9R_V12\lc39a_strongback_r
STATUS Landed Earth
POS -80.6041192 28.6082840
HEADING 0.00
ALT 21.500
AROT 61.716 4.483 8.266
AFCMODE 7
PRPLEVEL 0:1.000000
NAVFREQ 0 0
ANM 1.0000 0.1401 0.1730 1.0000 1.0000
STTS 5 3 2
ARMVIS 0
END
Falcon9_Stg1:Falcon9R_V12/f9_v12_stg1
STATUS Orbiting Earth
RPOS 3536060.329 4646833.051 -2823945.220
RVEL 967.5619 596.6346 288.0184
AROT -128.943 33.382 -106.924
VROT 0.0269 0.1104 0.0026
AFCMODE 7
PRPLEVEL 0:0.074203 1:0.757454
THLEVEL 25:1.000000
NAVFREQ 0 0
LEGS 0 0.0000 0.0000 0.0000 2.0000
FINS 0 0.0000 0.5000 0.5000
APST 1 0 3 0 2 0 0 0.0000 0 0
LPRM LZ1
END
Fair1:Falcon9R_V12/f9_v12_fair_nopara
STATUS Orbiting Earth
RPOS 3540087.064 4651849.082 -2820702.182
RVEL 1409.6874 1138.9091 680.5419
AROT -31.142 17.900 36.396
VROT -11.5433 -0.0000 0.0000
AFCMODE 7
NAVFREQ 0 0
END
Fair2:Falcon9R_V12/f9_v12_fair_nopara
STATUS Orbiting Earth
RPOS 3540102.695 4651877.232 -2820764.473
RVEL 1411.4715 1142.1223 673.4321
AROT 161.082 -8.622 140.780
VROT -11.3704 0.0000 0.0000
AFCMODE 7
NAVFREQ 0 0
END
END_SHIPSOK...So I tranferred the whole Orbiter 2016 directory from the laptop where everything runs perfect to the offensive desktop; and the desktop still has the same problems with any saved space_X scenarios that were saved after 1st-Stage Separation. If I save a scenario prior to 1st stage sep, I can load and run it fine from that point forward. It's gotta be some kind of hardware problem. Something or some setting on the desktop doesn't play well with some orbiter configurations. I even took one of my desktop- saved, post 1st Stage Sep scenarios and was able to run it on the laptop, save it on the laptop and run it again. Copied and brought it back to desktop and it crashes to desktop. Just can't get my head around it. . Major differences between the 2 machines is the AMD based motherboard on the desktop and the intel based laptop set-up. All drivers and windows versions up-to-date. Thanks for your suggestions. I may play around with video and sound settings on the desktop and see what happens.
