Software Hi res KSC + Hi Res launchpads, issues, issues

[destinos]

Hey everbody,

I spent a solid 90 minutes right now working and reworking these addon installs with the (fairly) simple goal of rigging up some hi res shuttle launchpads on a hi res version of KSC. I had various levels of crashing, but could never get it all to work together.

I know that, for example, LC-39 High Detail Version 8 says it needs Shuttle Fleet 3.6 or higher to work properly, but it doesn't seem to be compatible at all with the latest release, 4.2. Trying Slat's pads with the same high res ksc file produce a...high order crash, i guess you'd say, where the entire program "needed to shut down", and no log was preserved.

If anyone has a tried and true method for accomplishing this setup would you mind listing it here so I can just copy it? Thank you all for sticking with me this far.

 

[zerofay32]

If you are trying to use scenarios that came with the pad addons the they won't work. Try removing the shuttles from those scenarios and see if that helps. The scenario code for shuttle fleet has changed, so this is one cause of the CTDs.

Zerofay32

 

[destinos]

Yeah that occurred to me to try. But I'm not sure how to edit elements of a scenario like launch position, and pad type and stuff. I've never seen options for those when poking around in the scenario editor. Am I missing it?

 

[zerofay32]

Open the scenario files in the scenario folder using a text editor like notepad.
Open this file:

Orbiter Root/Scenarios/Atlantis Launch K-LC-39B-v8

And remove this section:

Atlantis:ShuttleAtlantis
STATUS Landed Earth
POS -80.6247534 28.6196317
HEADING 0.00
PRPLEVEL 0:1.000 1:1.000 2:1.000
NAVFREQ 0 0
CONFIGURATION 0
CARGODOOR 0 0.0000
KUBAND 0 0.0000
PRADIATOR 0 0.0000
SRADIATOR 0 0.0000
GEAR 0 0.0000
PAYLOAD_MASS 0.0000
ARM_STATUS 0.5000 0.0000 0.0000 0.5000 0.5000 0.5000
SAT_OFS_X 0.000
SAT_OFS_Y -2.200
SAT_OFS_Z 1.200
TGT_HEADING 90.000
END

Save the file then try to run that same file in Orbiter. See if that works.

Zerofay32

 

[destinos]

based on the first error that i was getting, sounds like this would work, but how would the scenario know what ship to supplement for the missing one deleted here?

 

[Saturn V]

If I'm not mistaken, I think Zerofay's suggestion was intended to see if the scenario would actually load & run at all without the shuttle. If it does, you'd know for sure that it was the shuttle causing the crash. If it doesn't, you'd know it had to be something else (or at the very least a combination of things).

At this point you're only trying to isolate the issue, not repair the scenario all in one shot.

 

[zerofay32]

If I'm not mistaken, I think Zerofay's suggestion was intended to see if the scenario would actually load & run at all without the shuttle. If it does, you'd know for sure that it was the shuttle causing the crash. If it doesn't, you'd know it had to be something else (or at the very least a combination of things).

At this point you're only trying to isolate the issue, not repair the scenario all in one shot.

Exactly.

Orbiter was trying to load the module: ShuttleAtlantis. This is an old version of shuttle fleet (ie a module you don't have) and is causing the Crash To Desktop (CTD). To have a shuttle in that scenario you have to replace the section I told you to remove, with this:

Atlantis:Shuttle
  STATUS Landed Earth
  POS -80.6247534 28.6196317
  HEADING 0.00
  PRPLEVEL 0:1.000 1:1.000 2:1.000
  NAVFREQ 0 0
  CONFIGURATION 0
  OV-104
  ODS
  RMSARM
  CARGODOOR 0 0.0000
  KUBAND 0 0.0000
  POSTLAND 0 0.0000
  SSMES 0 0.0000
  ADTA 0 0.0000
  PETD 1 1.0000
  SETD 1 1.0000
  ARMTILT 0 0.0000 0 0.0000
  PRADIATOR 0 0.0000
  SRADIATOR 0 0.0000
  GEAR 0 0.0000
  PAYLOAD_MASS 0.0000
  OMS
  ASSIST 134.0 77.0
  CALLOUT
  TGT_HEADING  42.000 228.0
END

This will tell Orbiter to load the correct module.

But by trying to load the scenario without the shuttle entry, this will narrow the options if you still get a CTD.

Zerofay32

 

[destinos]

Ok good news. now that I understand a little bit about how scenarios are written i was able to rewrite it with just the stock atlantis shuttle in the correct place. However, now there's this issue where it looks like what's happening, is that the hi res pads are still loading low res images for KSC immediately around the pad. Further out i can see the high res images populating properly. Lets see if I can get a screen shot of it. Ok not without uploading it someplace first. lets see if anyone knows what im talking about first before i bother!

 

[Oceanic]

Ok good news. now that I understand a little bit about how scenarios are written i was able to rewrite it with just the stock atlantis shuttle in the correct place. However, now there's this issue where it looks like what's happening, is that the hi res pads are still loading low res images for KSC immediately around the pad. Further out i can see the high res images populating properly. Lets see if I can get a screen shot of it. Ok not without uploading it someplace first. lets see if anyone knows what im talking about first before i bother!

that happens because you have 2 ksc base files, one is KSC.cfg in your ...orbiter\config\... folder the second is canaveral.cfg in ...orbiter\config\earth\base\...

both have surface-titles in them. you have a few option here (not sure witch is the best)

most shuttle fleet scenarios use this in the scenario file:

BEGIN_ENVIRONMENT
  System Sol_Alt
  Date MJD 55027.91539352
END_ENVIRONMENT

the sol_alt config uses the earth_alt.cfg file which has only the ksc.cfg file configured.

if you look at the earth.cfg file you will find this:

; === Surface Bases ===
; place additional bases or
; base directories in this list
BEGIN_SURFBASE
[B]DIR Earth\Base[/B]
AMB:	+152.715	-27.6383
AML:	-22.9517	+16.745
AWG:	-69.338	-51.6098
BDA:	-64.68	+32.365
BEJ:	-7.933	+38.079
BEN:	-7.88	      +32.12667
BYD:	-16.6517	+13.3383
DDN:	+130.8717	-12.4167
EDF:	-149.7939	+61.2531
EDW:	-117.92	+34.892
EIP:	-109.4283	-27.1617
FMH:	-70.522	+41.658
FMI:  +4.93433    +43.50871
GUA:	+144.927	+13.582
HAO:	-140.945	-18.075
HAW:	-14.4053	-7.9628
HNL:	-157.928	+21.30719
INN:	-8.917	+52.7
JDG:	+72.4117	-7.3117
JTY:	+139.3483	+35.7483
KKI:	+46.685590	+24.954800
[B]KSC:	-80.672 	+28.528[/B]
LAJ:	-27.095	+38.765
MRN:	-5.615	+37.1783
NKT:	-76.882	+34.903
NOR:	-106.42	+32.95
RCA:  -103.09248	+44.14593
ROB:	-10.365	+6.2328
WAK:	+166.6417	+19.28
YYT:	-52.7375	+47.625
ZZA:	-1.0467	+41.6683
VBG:	-120.5694 	+34.7345
XTA:  -115.79806	+37.24167
Baikonur: 	+63.33 	+45.92
END_SURFBASE

since your canaveral.cfg file is in ..orbiter\config\earth\base\... this is why it overlaps. the earth_alt.cfg doesn't have the DIR Earth\Base entry.

so now you options:

#1 delete the canaveral.cfg file (make sure to backup it) - the problem here is that some scenarios might not run because they need the landing pads from the canaveral base

#2 delete the BEGIN_SURFTILELIST ~ END_SURFTILELIST entry in the canaveral.cfg or ksc.cfg entry. not sure which one has the old surface titles on your system. - problem here is that you still have 2 bases on the same location.

#3 delete the entry KSC: -80.672 +28.528 in the earth.cfg file. - problem here is that you can't use autofcs for ksc anymore.

#4 you only use the sol_alt scenarios. - problem here is that the default scenarios (deltaglider & co) still have the overlapping surface-titles and other bases like habana and any 3rd party add-on bases (example wideawake international) wont's show up

 

[count_volta]

There is another problem with the Hi res KSC addon. Just look.

Isn't there something I can edit in some file to move it to the correct position?

I just installed this [ame="http://www.orbithangar.com/searchid.php?ID=2811"]Hi-res Kennedy Space Center[/ame]

and then Shuttle fleet 4.2 on clean orbiter 2006 and it gives me what you see in the screenshot.

 

[count_volta]

Okay apparently [ame="http://www.orbithangar.com/searchid.php?ID=3846"]STS Expansion Pack V4.2.0 (Special Edition) [/ame]

fixes this problem. Will try.
[ame="http://www.orbithangar.com/searchid.php?ID=3846"][/ame]