![]() |
|
|||||||
| MFD Questions & Help Post your questions here for help with the Multi-Function Displays. |
![]() |
|
|
Thread Tools |
|
|
#1 |
|
Aviation Connoisseur
|
I tried using GlideslopeMFD (
) with Orbiter 2010P1, which works fine.
But after installing Shuttle Fleet 4.7, Orbiter crashes when the GlideslopeMFD initialization reaches the Doberai entry. From what I can tell, Shuttle Fleet doesn't update the Doberai.cfg file in the Base folder. So I thought maybe it's something else and Doberai.cfg is unrelated. (the rest of my troubleshooting was done AFTER Shuttle Fleet 4.7 was installed, since I confirmed Glideslope already works on a clean Orbiter 2010P1 install) I don't know much about the file structure for bases, but I looked in my main config folder and the only base files I could find that were outside the Base folder were VBG.cfg, KSC.cfg, EDW.cfg, and ZZA.cfg. I looked in the Base folder and I have 36 files. The four .cfg files listed above were also in the Base folder, but had different names. VBG was Vandenburg, KSC was Canaveral, EDW was Edwards, and ZZA was the same. How many base files should I have in the Base folder? Also noticed that the KSC.cfg and Canaveral.cfg files have a discrepancy. At line 106 on the Canaveral file, it lists: Code:
SOLARPLANT
POS 366 0 546
GRID 10 10
ROT 30
TEX Solpanel
Code:
MESH
FILE vab
OWNMATERIAL
POS -7070 0 2280
ROT 10
SHADOW
PRELOAD
Also, looked at my log file and saw this bit: Code:
--------------------------------------------------------------- >>> 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. --------------------------------------------------------------- Does anyone else here use GlideslopeMFD with 2010P1 and Shuttle Fleet 4.7 and it works? I'm totally stuck on this one. |
|
|
|
|
|
#2 |
|
Clueless developer
![]() |
The next letter after D is E. Where does the config for Edwards reside?
|
|
|
|
|
|
#3 |
|
Aviation Connoisseur
|
Actually I went a step further and started testing the Shuttle Fleet 4.7 install file by file to see which one either:
1. Caused Orbiter to CTD on program launch 2. Caused Orbiter to CTD after initializing GlideslopeMFD So here are my findings. (all testing done with Space Shuttle Atlantis/Atlantis docked at ISS default stock scenario) I limited my testing to the Base folder only, since the initialization caused the original CTD after getting to a certain base file, namely Doberai. Wishbone you were 100% correct, the file it first had trouble reading was Edwards.cfg. The files are completely different in terms of code. (however, GlideslopeMFD crashing Orbiter wasn't just limited to the Edwards.cfg file. Once I remedied Edwards, I found another issue. Details below) Here is the default Edwards.cfg file: Code:
BASE-V2.0
Name = Edwards
Location = -117.89 +34.92
Size = 2000
BEGIN_OBJECTLIST
LPAD2
POS 0 0 0
SCALE 0 0 0
TEX Lpad02
NAV 128.05
END
END_OBJECTLIST
Code:
BASE-V2.0
Name = EDW - Edwards AFB
Location =-117.92 +34.892
Size = 200
MapObjectsToSphere = TRUE
BEGIN_NAVBEACON
VOR EDWX -117.92 34.892 112.55 1500
END_NAVBEACON
BEGIN_OBJECTLIST
BLOCK
POS -1645.882513 0 1453.751956
SCALE 3 3 0.01
ROT 35
TEX1 mark15 1 1
TEX2
TEX3
END
BLOCK
POS -1717.553331 0 1368.338001
SCALE 3 3 0.01
ROT 35
TEX1 mark15 1 1
TEX2
TEX3
END
BLOCK
POS 1717.553331 0 -1368.338001
SCALE 3 3 0.01
ROT 35
TEX1 mark15 1 1
TEX2
TEX3
END
BLOCK
POS 1645.882513 0 -1453.751956
SCALE 3 3 0.01
ROT 35
TEX1 mark15 1 1
TEX2
TEX3
END
BLOCK
POS -1412.389327 0 1257.82791
SCALE 3 3 0.01
ROT 35
TEX1 mark14 1 1
TEX2
TEX3
END
BLOCK
POS -1484.060146 0 1172.413955
SCALE 3 3 0.01
ROT 35
TEX1 mark14 1 1
TEX2
TEX3
END
BLOCK
POS 1484.060146 0 -1172.413955
SCALE 3 3 0.01
ROT 35
TEX1 mark14 1 1
TEX2
TEX3
END
BLOCK
POS 1412.389327 0 -1257.82791
SCALE 3 3 0.01
ROT 35
TEX1 mark14 1 1
TEX2
TEX3
END
BLOCK
POS -1178.896142 0 1061.903864
SCALE 3 3 0.01
ROT 35
TEX1 mark13 1 1
TEX2
TEX3
END
BLOCK
POS -1250.56696 0 976.4899089
SCALE 3 3 0.01
ROT 35
TEX1 mark13 1 1
TEX2
TEX3
END
BLOCK
POS 1250.56696 0 -976.4899089
SCALE 3 3 0.01
ROT 35
TEX1 mark13 1 1
TEX2
TEX3
END
BLOCK
POS 1178.896142 0 -1061.903864
SCALE 3 3 0.01
ROT 35
TEX1 mark13 1 1
TEX2
TEX3
END
BLOCK
POS -945.4029564 0 865.9798184
SCALE 3 3 0.01
ROT 35
TEX1 mark12 1 1
TEX2
TEX3
END
BLOCK
POS -1017.073775 0 780.565863
SCALE 3 3 0.01
ROT 35
TEX1 mark12 1 1
TEX2
TEX3
END
BLOCK
POS 1017.073775 0 -780.565863
SCALE 3 3 0.01
ROT 35
TEX1 mark12 1 1
TEX2
TEX3
END
BLOCK
POS 945.4029564 0 -865.9798184
SCALE 3 3 0.01
ROT 35
TEX1 mark12 1 1
TEX2
TEX3
END
BLOCK
POS -711.9097709 0 670.0557726
SCALE 3 3 0.01
ROT 35
TEX1 mark11 1 1
TEX2
TEX3
END
BLOCK
POS -783.5805893 0 584.6418172
SCALE 3 3 0.01
ROT 35
TEX1 mark11 1 1
TEX2
TEX3
END
BLOCK
POS 783.5805893 0 -584.6418172
SCALE 3 3 0.01
ROT 35
TEX1 mark11 1 1
TEX2
TEX3
END
BLOCK
POS 711.9097709 0 -670.0557726
SCALE 3 3 0.01
ROT 35
TEX1 mark11 1 1
TEX2
TEX3
END
BLOCK
POS -478.4165853 0 474.1317267
SCALE 3 3 0.01
ROT 35
TEX1 mark10 1 1
TEX2
TEX3
END
BLOCK
POS -550.0874038 0 388.7177713
SCALE 3 3 0.01
ROT 35
TEX1 mark10 1 1
TEX2
TEX3
END
BLOCK
POS 550.0874038 0 -388.7177713
SCALE 3 3 0.01
ROT 35
TEX1 mark10 1 1
TEX2
TEX3
END
BLOCK
POS 478.4165853 0 -474.1317267
SCALE 3 3 0.01
ROT 35
TEX1 mark10 1 1
TEX2
TEX3
END
BLOCK
POS -244.9233998 0 278.2076808
SCALE 3 3 0.01
ROT 35
TEX1 mark9 1 1
TEX2
TEX3
END
BLOCK
POS -316.5942183 0 192.7937254
SCALE 3 3 0.01
ROT 35
TEX1 mark9 1 1
TEX2
TEX3
END
BLOCK
POS 316.5942183 0 -192.7937254
SCALE 3 3 0.01
ROT 35
TEX1 mark9 1 1
TEX2
TEX3
END
BLOCK
POS 244.9233998 0 -278.2076808
SCALE 3 3 0.01
ROT 35
TEX1 mark9 1 1
TEX2
TEX3
END
BLOCK
POS -11.43021424 0 82.28363497
SCALE 3 3 0.01
ROT 35
TEX1 mark8 1 1
TEX2
TEX3
END
BLOCK
POS -83.10103272 0 -3.130320438
SCALE 3 3 0.01
ROT 35
TEX1 mark8 1 1
TEX2
TEX3
END
BLOCK
POS -1645.782513 0 1453.751956
SCALE 3 3 0.01
ROT 35
TEX1 mark1 1 1
TEX2
TEX3
END
BLOCK
POS -1717.453331 0 1368.338001
SCALE 3 3 0.01
ROT 35
TEX1 mark1 1 1
TEX2
TEX3
END
BLOCK
POS 1717.453331 0 -1368.338001
SCALE 3 3 0.01
ROT 35
TEX1 mark1 1 1
TEX2
TEX3
END
BLOCK
POS 1645.782513 0 -1453.751956
SCALE 3 3 0.01
ROT 35
TEX1 mark1 1 1
TEX2
TEX3
END
BLOCK
POS -1412.289327 0 1257.82791
SCALE 3 3 0.01
ROT 35
TEX1 mark2 1 1
TEX2
TEX3
END
BLOCK
POS -1483.960146 0 1172.413955
SCALE 3 3 0.01
ROT 35
TEX1 mark2 1 1
TEX2
TEX3
END
BLOCK
POS 1483.960146 0 -1172.413955
SCALE 3 3 0.01
ROT 35
TEX1 mark2 1 1
TEX2
TEX3
END
BLOCK
POS 1412.289327 0 -1257.82791
SCALE 3 3 0.01
ROT 35
TEX1 mark2 1 1
TEX2
TEX3
END
BLOCK
POS -1178.796142 0 1061.903864
SCALE 3 3 0.01
ROT 35
TEX1 mark3 1 1
TEX2
TEX3
END
BLOCK
POS -1250.46696 0 976.4899089
SCALE 3 3 0.01
ROT 35
TEX1 mark3 1 1
TEX2
TEX3
END
BLOCK
POS 1250.46696 0 -976.4899089
SCALE 3 3 0.01
ROT 35
TEX1 mark3 1 1
TEX2
TEX3
END
BLOCK
POS 1178.796142 0 -1061.903864
SCALE 3 3 0.01
ROT 35
TEX1 mark3 1 1
TEX2
TEX3
END
BLOCK
POS -945.3029564 0 865.9798184
SCALE 3 3 0.01
ROT 35
TEX1 mark4 1 1
TEX2
TEX3
END
BLOCK
POS -1016.973775 0 780.565863
SCALE 3 3 0.01
ROT 35
TEX1 mark4 1 1
TEX2
TEX3
END
BLOCK
POS 1016.973775 0 -780.565863
SCALE 3 3 0.01
ROT 35
TEX1 mark4 1 1
TEX2
TEX3
END
BLOCK
POS 945.3029564 0 -865.9798184
SCALE 3 3 0.01
ROT 35
TEX1 mark4 1 1
TEX2
TEX3
END
BLOCK
POS -711.8097709 0 670.0557726
SCALE 3 3 0.01
ROT 35
TEX1 mark5 1 1
TEX2
TEX3
END
BLOCK
POS -783.4805893 0 584.6418172
SCALE 3 3 0.01
ROT 35
TEX1 mark5 1 1
TEX2
TEX3
END
BLOCK
POS 783.4805893 0 -584.6418172
SCALE 3 3 0.01
ROT 35
TEX1 mark5 1 1
TEX2
TEX3
END
BLOCK
POS 711.8097709 0 -670.0557726
SCALE 3 3 0.01
ROT 35
TEX1 mark5 1 1
TEX2
TEX3
END
BLOCK
POS -478.3165853 0 474.1317267
SCALE 3 3 0.01
ROT 35
TEX1 mark6 1 1
TEX2
TEX3
END
BLOCK
POS -549.9874038 0 388.7177713
SCALE 3 3 0.01
ROT 35
TEX1 mark6 1 1
TEX2
TEX3
END
BLOCK
POS 549.9874038 0 -388.7177713
SCALE 3 3 0.01
ROT 35
TEX1 mark6 1 1
TEX2
TEX3
END
BLOCK
POS 478.3165853 0 -474.1317267
SCALE 3 3 0.01
ROT 35
TEX1 mark6 1 1
TEX2
TEX3
END
BLOCK
POS -244.8233998 0 278.2076808
SCALE 3 3 0.01
ROT 35
TEX1 mark7 1 1
TEX2
TEX3
END
BLOCK
POS -316.4942183 0 192.7937254
SCALE 3 3 0.01
ROT 35
TEX1 mark7 1 1
TEX2
TEX3
END
BLOCK
POS 316.4942183 0 -192.7937254
SCALE 3 3 0.01
ROT 35
TEX1 mark7 1 1
TEX2
TEX3
END
BLOCK
POS 244.8233998 0 -278.2076808
SCALE 3 3 0.01
ROT 35
TEX1 mark7 1 1
TEX2
TEX3
END
RUNWAY
END1 -1915.1 0 1606.969024
END2 1915.1 0 -1606.969024
WIDTH 91.5
ILS1 114.3
ILS2 114.3
RWTEX Runway2
NRWSEG 15
RWSEG1 1 0.025 0.5 0.75 1 0.852
RWSEG2 1 0.025 0.5 0.75 1 0.852
RWSEG3 1 0.007 0.5 0.75 0.852 0.7305
RWSEG4 1 0.06 0.5 0.75 0.5 0.03125
RWSEG5 1 0.007 0.5 0.75 0.7305 0.6133
RWSEG6 1 0.1 0.5 0.75 0.5 0.03125
RWSEG7 1 0.007 0.5 0.75 0.6133 0.5
RWSEG8 6 0.538 0.5 0.75 0.5 0.03125
RWSEG9 1 0.007 0.5 0.75 0.5 0.6133
RWSEG10 1 0.1 0.5 0.75 0.03125 0.5
RWSEG11 1 0.007 0.5 0.75 0.6133 0.7305
RWSEG12 1 0.06 0.5 0.75 0.03125 0.5
RWSEG13 1 0.007 0.5 0.75 0.7305 0.852
RWSEG14 1 0.025 0.5 0.75 0.852 1
RWSEG15 1 0.025 0.5 0.75 0.852 1
END
RUNWAYLIGHTS
END1 -1915.1 0 1606.969024
END2 1915.1 0 -1606.969024
WIDTH 91.5
PAPI 20.0 2.0 -2287
VASI 1.5 152 671
END
END_OBJECTLIST
So I've determined that a part of the coding in the new Edwards.cfg is causing the CTD on Glideslope initialization, but I wanted to see if the other 3 base config files in the 4.7 install also caused issues. My findings: (Updated file) Canaveral.cfg - loaded correctly in Glideslope (Updated file) Edwards.cfg - (previously discussed) (Updated file) Vandenburg.cfg - loaded correctly in Glideslope (NEW file) ZZA.cfg - loaded correctly in Glideslope BUT Orbiter randomly CTDs on program launch I don't have experience editing .dll files so I have no way of knowing what kind of naming structure the module looks for when reading the base config files. All I know is Shuttle Fleet's Edwards.cfg has something in it GlideslopeMFD doesn't like. There could be more issues with additional files Shuttle Fleet adds to the Orbiter installation but all I tested were the four base config files it adds. ---------- Post added at 05:19 ---------- Previous post was at 05:12 ---------- I found the culprit. The first part of the modified Edwards.cfg file: Code:
BASE-V2.0 Name = EDW - Edwards AFB Location =-117.92 +34.892 Size = 200 MapObjectsToSphere = TRUE For good measure I also deleted the extra spaces between -117.92 and +34.892. Glideslope was able to completely load all bases using the same stock Atlantis scenario. Now it's time to test out a full Shuttle Fleet 4.7 install. ---------- Post added at 05:26 ---------- Previous post was at 05:19 ---------- Tested the Discovery on orbit scenario file provided by Shuttle Fleet 4.7. Orbiter CTD'd on program launch 2 out of 5 times. The three times it did launch though, all bases successfully loaded into GlideslopeMFD. Hooray! Now I have to figure out why Glideslope doesn't like the ZZA.cfg file. It's the only file that was added to the Base folder, so my thoughts are it's not somehow hard coded into the module? Even though it reads it just fine as is. This issue I may need some help with. Last edited by halcyon; 03-14-2011 at 09:28 AM. |
|
|
|
| Thanked by: |
|
|
#4 |
|
Orbinaut
|
Quote:
I have known about this problem before and it happened exactly the same way for me. So when I installed the Shuttle Fleet I just used GPC MFD for all vessels. Eventually I stopped using Glideslope / it will become interesting again once setting custom descent profiles is more user-friendly (loading them from file). Last edited by hribek; 03-14-2011 at 02:05 PM. |
|
|
|
| Thanked by: |
|
|
#5 |
|
Aviation Connoisseur
|
Quote:
Now that GlideslopeMFD works for me with Shuttle Fleet 4.7, I gave my first manual reentry a try, and wow. Glideslope tape display, coupled with the horizontal display and used along with GPCMFD Ops 3 and SurfaceMFD showed me EXACTLY where I had to be on reentry. Ops 3 provided the visual representation of my deceleration plus current drag, SurfaceMFD gave me faster updates on my vacc, the tape display gave great references on required altitude/vspd/AoA for my current range, and the DelAz along with the horizontal display was great at keeping me on the reentry course all the way to the HAC turn. I successfully entered a left HAC turn and was lined up with KSC runway 33 at the proper altitude. The only thing I don't quite get is when to start making the rolls, although I figured if I could see myself on GPCMFD Ops 3 I had to start adding drag to go down the speed corridor. Also don't know how far to roll, or how much DelAz should display until I have to make a roll reversal. I just kind of winged it and it turned out perfect, so maybe there's lots of margin for error as long as I'm keeping my deceleration and required alt vs range in check. |
|
|
|
|
|
#7 |
|
Donator
![]() ![]() |
Quote:
I usually use ~80° for the first one. The Vacc tape on SurfaceMFD is very usefull for getting it right. Or are you talking about DelAz?
|
|
|
|
|
|
#8 |
|
Aviation Connoisseur
|
I think he's talking about DelAz, which makes sense.
|
|
|
|
|
|
#9 |
|
Orbinaut
|
Thanks to this thread I found out what crashes Glide Slope MFD. In the added files from Shuttle 4.7 the "Location" line has TABS seperating the values.
Delete the tab(s) and replace them with 1 space and it loads fine. I had to do this to Canveral, Edwards, Vandenburg, and ZZA There are other places where tabs are used instead of spaces, but Glide Slope doesn't seem to mind them.... If I get random crashes though, I'll go back and remove all of them as well. Hope this helps!!
|
|
|
|
| Thanked by: |
![]() |
|
| Thread Tools | |
|
|
|||||
| Quick Links | Need Help? |