OHM Glideslope 2.7 for Orbiter 2016

OrbitHangar

Addon Comments
Joined
Apr 9, 2008
Messages
3,832
Reaction score
13
Points
0

Author: adswnj

*** Do not use for Orbiter 2010 ***

V2.7 release: now using MMExt2, and no more Error 126. Minor changes on non-atmo data screen: added VAcc and HAcc indications. For best experience, please also install ModuleMessagingExt 2.1 or later. 

Glideslope 2 is a reentry guidance utility to assist you to make precision landings from orbit to the runway or landing pad. It is based on the original Glideslope by Chris Jeppesen. For atmospheric landings, Glideslope 2 calculates the reentry profile downt to a Heading Alignment Cylinder (HAC) tun similar to the profile that the Space Shuttle used to fly. The utility has extensive configuration files to allow you to create your own custom reference landing profiles for different vessels or types of reentry (e.g. you could create an emergency descent profile for a DG, or an max weight landing for a Shuttle).



DOWNLOAD
 

ADSWNJ

Scientist
Addon Developer
Joined
Aug 5, 2011
Messages
1,667
Reaction score
3
Points
38
New release of Glideslope 2 for Orbiter 2016. Enjoy!

---------- Post added at 05:22 PM ---------- Previous post was at 05:12 PM ----------

By the way - if anyone has tried the old Glideslope 2.4 or earlier on Orbiter 2016, I have some homework for you:

1. delete GS2.* from Modules/Plugin
2. delete directory Config/MFD/GS2 and all sub-files
3. delete directory Doc/MFD/GS2 and all sub-files
4. delete Orbitersdk/GS2_*.zip

Reason ... new version uses Glideslope as the new MFD name, not GS2. I figured that the new Orbiter 2016 deserves a proper name for the Glideslope MFD. (The old GS2 name was out of respect for kwan3217's original Glideslope 1.x on Orbiter 2010)
 

turtle91

Active member
Joined
Nov 1, 2010
Messages
319
Reaction score
7
Points
33
There seems to be a bug in....Glideslope or/and BaseSync MFD.
I guess it's a BasesyncMFD issue, but only aplies when using GS-MFDs DEO-feature.
So, I report it here.

The facts:
I want to perform a deorbit with Baseync-Glideslope-combo.
-left MFD = BaseSyncMFD
-right MFD = Glideslope-MFD
=
When using the de-orbit mode of GS, the deorbit-data is transfered into Basesync's DEO program.
But when trying to "target" Basesync-MFD to GS, it fails...
I tried: "gs", "GS", "GS2", "gs2", "Gs2", "gS2", "GSII", "GSii", "gSII".....before I went out of ideas...

So basicly GS "talks" to BaseSync....but Basesync does not give feedback to GS.(maybe just to "GS2"...which is not here anymore)
Maybe BasesncMFD has no clue about the new GS vs GS2 naming-convention ?

That are the versions I have tried:
Module BaseSyncMFD.dll ....... [Build 160910, API 160828]
Module Glideslope.dll ........ [Build 160910, API 160828]
 

turtle91

Active member
Joined
Nov 1, 2010
Messages
319
Reaction score
7
Points
33
Did you enter "GS" into BaseSync's target input box?
Yes...plus all the combinations, mentioned in my post.

---------- Post added at 10:01 PM ---------- Previous post was at 09:54 PM ----------

From BaseSyncMFD.hpp

Code:
const   struct  GlideslopeExportTgtStruct *gs2trgt;
bool    usingGS2;
 

ADSWNJ

Scientist
Addon Developer
Joined
Aug 5, 2011
Messages
1,667
Reaction score
3
Points
38
Hmm - works for me. Can you give me a reproduction script, from a known baseline?
 

turtle91

Active member
Joined
Nov 1, 2010
Messages
319
Reaction score
7
Points
33
Hm...I tried the same scenario again, and now it seems to be working (I used "GS" as BS-target).
I believe I found the problem:

The new Glideslope-files are also have to "obey" the new naming-convention, too.
I.e.
old : GS2glideslope_DG
new: Glideslope_DG

And I have had some previous GS2-configs in my GS("1"..one...without "2")-folder
It seems to be, that the parser gets confused when findig old GS2-config-file-names

So I just renamed the files to new naming-convention and, BS-target-box accepted the "GS" value (so MFD cross-communication-link was established in both directions)

Btw, I don't like renaming in general...I remember the confusions between "Solaris7" and SunOS 2.7"....many problems just because of the naming-convention...
Just my experience...renaming=problems/confusions

However, one problem is persistent across all version of GS2 and GS:

The config says(as per default):
Code:
PREFS DATA VSIT HSIT METRIC "Cape Canaveral" "KSC33" XR

But the parser says, in all versions I have tested so far:

PREFS LOADED: Mode=3/1/4 Units=METRIC Base=Cape Canaveral Runway=PAD01 Glideslope=XR
Successfully parsed Glideslope.cfg

So...PAD01...why ?

The problem with that is, if you go to the HAC-page, it shows PAD01 with a zero-radius HAC.
So the user must then evtl. re-select a RW and the corresponding HAC and clicking on "+" to have a non-zero-HAC.
As long as the HAC has a zero-radius, all other pages are showing wrong/missing information.
And cycling over the different pages as long as there are invalid values...sometimes caused GS2 (yes...just GS2..not GS so far) to CTD.
 

ADSWNJ

Scientist
Addon Developer
Joined
Aug 5, 2011
Messages
1,667
Reaction score
3
Points
38
Sounds like you have a mess of old and new Glideslopes in your Orbiter 2016 install. I took this opportunity to rename everything as the new Glideslope name (vs GS2) was important to me.

Ideally, delete every GS2*.* and you will be good, or if you need to copy across, be really careful with any syntax checking.
 

turtle91

Active member
Joined
Nov 1, 2010
Messages
319
Reaction score
7
Points
33
Ideally, delete every GS2*.*....
...I have done this allready as mentioned in your first post, but....

.. if you need to copy across, be really careful with any syntax checking
I just forgot to rename the old GLIDESLOPE2-glideslopes

But the PAD01-problem is still there, even in GS2.
I can remember, that in very early versions of GS2, the configured default RW worked as expected. (means...the pre-defiened RW was selected as "default" after opening the GS2-MFD).
 

paddy

Addon Developer
Addon Developer
Joined
Jul 14, 2012
Messages
80
Reaction score
0
Points
0
Does any one have a cfg file for a DG IV. I just can not get the DG version to work.
I leave IIS, adjust orbit to 200km by 200km, use basesync to get the best orbit.
At the right time my orbit changes and I start to re enter...... all so good
If I control it by hand I burn up or bounce off, if I use the ALT7 auto re entry It saves an empty user config file??
Help!!!!
 

rcraig42

New member
Joined
Jan 23, 2012
Messages
70
Reaction score
0
Points
0
Well now that I am trying an earlier dated scenario where Base Sync works, Glideslope doesn't work. I get no reference data, starting with range and azimuth, trying to approach canaveral rnwy 33 or 15, tried each GS in confg, doesn't matter.

I tried repairing the vc 2015 redist and the MSVC++ 2010 SP1 with no effect. Is there some other dependency I may be missing for the mfd to be able to get the range and azimuth data that it needs to show me the reference data?

The non atmospheric landing autopilot seems to work okay on the moon though. but I had to finish the landing myself as it had me descending at -1.5 m/s at 5000m altitude.

The quicksave scenario is a little more than a half orbit before deorbit burn and prior to loading glideslope and base sync, the current state scenario is after deorbit and descent to around 110k altitude.

well nvm I guess, I reloaded that current scenario myself and it was all working, I guess I need to quit and reload when that happens
 

Attachments

  • 1 - Ready for Takeoff to ISS 0001 0001 0001 0001.scn
    6.5 KB · Views: 0
  • (Current state).scn
    6.5 KB · Views: 0
Last edited:

ADSWNJ

Scientist
Addon Developer
Joined
Aug 5, 2011
Messages
1,667
Reaction score
3
Points
38
Something really weird with your config, RCraig !! If you are all good now, then I'll leasve it.

I suspect it my be something to do with static linking (Enjo's curse! :hello: ) but I'll lay low in case I have to open that can of worms.
 

rcraig42

New member
Joined
Jan 23, 2012
Messages
70
Reaction score
0
Points
0
Something really weird with your config, RCraig !! If you are all good now, then I'll leasve it.

I suspect it my be something to do with static linking (Enjo's curse! :hello: ) but I'll lay low in case I have to open that can of worms.

well it works fine if I quit and come back to the current scenario. But I have yet to get the references to show (for canaveral on earth anyway) if I run orbiter continuously from orbit insertion.
 

ADSWNJ

Scientist
Addon Developer
Joined
Aug 5, 2011
Messages
1,667
Reaction score
3
Points
38
New v2.6 release of Glideslope for Orbiter 2016.

I've fixed the 0km HAC / NAN bug reported by turtle91 and davidweb. I updated the dependencies between BaseSync and Glideslope, to clarify that BaseSync 3.1 or higher is now the min version for full interconnectivity.

I also added turtle91's XR1 from ISS scenario - nice job with the custom save file editing, turtle!
 

Battlestar

New member
Joined
May 25, 2008
Messages
10
Reaction score
0
Points
1
Hi,

I am fairly new to orbiter, but i find my way around. I was just following TEX's deorbit and reentry tutorials. At some point you need to use Glideslope MFD. Whenever i hit the button to activate the mfd orbiter crashes. I'm using the newest version of GS2 in Orbiter 2016, of course. I tried to uninstall every not necessary module/plugin from orbiter to test GS2 in a mostly clean environment, but unfortunately it crashes every time. I attached my orbiter log. From what i can see with my rather poor knowledge, it really seams to be a GS 2 problem.
Here comes the logfile text. Sorry for not knowing how to put it here in a better way, so i just copy and paste the text:
__________________________________________________________
**** Orbiter.log
000000.000: Build Aug 28 2016 [v.160828]
000000.000: Timer precision: 3.95061e-007 sec
000000.000: Found 0 joystick(s)
000000.000: Module AtlantisConfig.dll .... [Build 160828, API 160828]
000000.000: Module AtmConfig.dll ......... [Build 160828, API 160828]
000000.000: Module DGConfigurator.dll .... [Build 160828, API 160828]
000000.000: Module ScnEditor.dll ......... [Build 160828, API 160828]
000000.000: Module D3D9Client.dll ........ [Build 170406, API 160828]
000000.000: Module BaseSyncMFD.dll ....... [Build 160910, API 160828]
000000.000: ---------------------------------------------------------------
000000.000: >>> WARNING: Obsolete API function used: oapiRegisterMFDMode
000000.000: At least one active module is accessing an obsolete interface function.
000000.000: Addons which rely on obsolete functions may not be compatible with
000000.000: future versions of Orbiter.
000000.000: ---------------------------------------------------------------
000000.000: Module HUDDrawer.dll ......... [Build 160907, API 160828]
000000.000: Module LaunchMFD.dll ......... [Build 160905, API 160828]
000000.000: Module Framerate.dll ......... [Build 160828, API 160828]
000000.000: Module OrbiterSound.dll ...... [Build 121120, API 100830]
============================ ERROR: ===========================
Failed loading module Modules\Plugin\LandMFD.dll (code 126)
[Orbiter::LoadModule | .\Orbiter.cpp | 600]
===============================================================
000000.000: Module Glideslope.dll ........ [Build 170415, API 160828]
000000.000: Glideslope module init: version v2.5, date Apr 15 2017
000000.000:
000000.000: **** Creating simulation session
000000.000: D3D9: [DirectX 9 Initialized]
000000.000: D3D9: 3D-Adapter = NVIDIA GeForce GTX 960M
000000.000: D3D9: MaxTextureWidth........: 16384
000000.000: D3D9: MaxTextureHeight.......: 16384
000000.000: D3D9: MaxTextureRepeat.......: 8192
000000.000: D3D9: VolTexAddressCaps......: 0x3F
000000.000: D3D9: NumSimultaneousRTs.....: 4
000000.000: D3D9: VertexDeclCaps.........: 0x30F
000000.000: D3D9: XNA Math Support.......: Yes
000000.000: D3D9: Vertex Texture.........: Yes
000000.000: D3D9: Shadow Mapping.........: Yes
000000.000: D3D9: D3DFMT_A16B16G16R16F...: Yes
000000.000: D3D9: D3DFMT_A32B32G32R32F...: Yes
000000.000: D3D9: D3DFMT_D32F_LOCKABLE...: Yes
000000.000: D3D9: D3DFMT_A2R10G10B10.....: Yes
000000.000: D3D9: D3DDTCAPS_DEC3N........: No
000000.000: D3D9: D3DDTCAPS_FLOAT16_2....: Yes
000000.000: D3D9: D3DDTCAPS_FLOAT16_4....: Yes
000000.000: D3D9: Available Texture Memory = 4080 MB
000000.000: D3D9: [3DDevice Initialized]
000000.000: D3D9: [Loading Constellations]
000000.000: D3D9: [D3D9Client Initialized]
000000.000: Module Sun.dll ............... [Build 160828, API 160828]
VSOP87(E) Sun: Precision 1e-006, Terms 554/6634
000000.000: Module Mercury.dll ........... [Build 160828, API 160828]
VSOP87(B) Mercury: Precision 1e-005, Terms 167/7123
000000.000: Module Venus.dll ............. [Build 160828, API 160828]
000000.000: Module VenusAtm2006.dll ...... [Build 160828, API 160828]
VSOP87(B) Venus: Precision 1e-005, Terms 79/1710
000000.000: Module Earth.dll ............. [Build 160828, API 160828]
000000.000: Module EarthAtmJ71G.dll ...... [Build 160828, API 160828]
VSOP87(B) Earth: Precision 1e-008, Terms 2564/2564
000000.000: Module Moon.dll .............. [Build 160828, API 160828]
ELP82: Precision 1e-005, Terms 116/829
000000.000: Module Mars.dll .............. [Build 160828, API 160828]
000000.000: Module MarsAtm2006.dll ....... [Build 160828, API 160828]
VSOP87(B) Mars: Precision 1e-005, Terms 405/6400
000000.000: Module Phobos.dll ............ [Build ******, API 060425]
000000.000: Module Deimos.dll ............ [Build ******, API 060425]
000000.000: Module Galsat.dll ............ [Build 160828, API 160828]
000000.000: Module Jupiter.dll ........... [Build 160828, API 160828]
VSOP87(B) Jupiter: Precision 1e-006, Terms 1624/3625
000000.000: Module Io.dll ................ [Build 160828, API 160828]
000000.000: Module Europa.dll ............ [Build 160828, API 160828]
000000.000: Module Ganymede.dll .......... [Build 160828, API 160828]
000000.000: Module Callisto.dll .......... [Build 160828, API 160828]
000000.000: Module Satsat.dll ............ [Build 160828, API 160828]
000000.000: Module Saturn.dll ............ [Build 160828, API 160828]
VSOP87(B) Saturn: Precision 1e-006, Terms 2904/6365
000000.000: Module Mimas.dll ............. [Build 160828, API 160828]
SATSAT Mimas: Terms 113
000000.000: Module Enceladus.dll ......... [Build 160828, API 160828]
SATSAT Enceladus: Terms 33
000000.000: Module Tethys.dll ............ [Build 160828, API 160828]
SATSAT Tethys: Terms 101
000000.000: Module Dione.dll ............. [Build 160828, API 160828]
SATSAT Dione: Terms 59
000000.000: Module Rhea.dll .............. [Build 160828, API 160828]
SATSAT Rhea: Terms 68
000000.000: Module Titan.dll ............. [Build 160828, API 160828]
SATSAT Titan: Terms 100
000000.000: Module Iapetus.dll ........... [Build 160828, API 160828]
SATSAT Iapetus: Terms 605
000000.000: Module Uranus.dll ............ [Build 160828, API 160828]
VSOP87(B) Uranus: Precision 1e-006, Terms 1827/5269
000000.000: Module Miranda.dll ........... [Build ******, API 060425]
000000.000: Module Ariel.dll ............. [Build ******, API 060425]
000000.000: Module Umbriel.dll ........... [Build ******, API 060425]
000000.000: Module Titania.dll ........... [Build ******, API 060425]
000000.000: Module Oberon.dll ............ [Build ******, API 060425]
000000.000: Module Neptune.dll ........... [Build 160828, API 160828]
VSOP87(B) Neptune: Precision 1e-006, Terms 391/2024
000000.000: Finished initialising world
000000.000: Module DeltaGlider.dll ....... [Build 160828, API 160828]
000000.000: Module LuaInline.dll ......... [Build 160828, API 160828]
000000.000: Module ShuttleA.dll .......... [Build 160828, API 160828]
000000.000: Finished initialising status
000000.000: Finished initialising camera
000000.000: Finished setting up render state
000000.000: D3D9: [Scene Initialized]
000000.000: Glideslope module sim start
000000.000: Finished initialising panels
000000.000: ---------------------------------------------------------------
000000.000: >>> WARNING: Obsolete API function used: VESSEL::GetHorizonAirspeedVector
000000.000: At least one active module is accessing an obsolete interface function.
000000.000: Addons which rely on obsolete functions may not be compatible with
000000.000: future versions of Orbiter.
000000.000: ---------------------------------------------------------------

Anyways, thanks for your hard work and your fine mfd's and utilities. I enjoy using them. :thumbup:
 

Battlestar

New member
Joined
May 25, 2008
Messages
10
Reaction score
0
Points
1
Thanks for your rather short reply. I don't know what you want to tell me. That "LaunchMFD.dll" is not installed, or that i need to install "ModuleMessagingExt" ? Rest assured, neither is the problem.
"ModuleMessagingExt" (latest version) is installed and always was installed. And for the "LaunchMFD.dll" message in the log file i created a completly fresh Orbiter installation even without Orbitersound. The only two addons i installed are "ModuleMessagingExt" and "Glideslope for Orbiter 2016 v2.6". Still, starting Orbiter 2016 with the default Delta-Glider scenario "Docked at ISS" and then clicking on the "Glideslope" MFD Button instantaniously crashes Orbiter. It doesn't matter if i use the Orbiter_ng.exe in an D3D9 environment, or just the "normal" orbiter.exe without D3D9. Again, here's the log file:
Code:
**** Orbiter.log
000000.000: Build Aug 28 2016 [v.160828]
000000.000: Timer precision: 3.95062e-007 sec
000000.000: Found 0 joystick(s)
000000.000: Module AtlantisConfig.dll .... [Build 160828, API 160828]
000000.000: Module AtmConfig.dll ......... [Build 160828, API 160828]
000000.000: Module DGConfigurator.dll .... [Build 160828, API 160828]
000000.000: Module D3D9Client.dll ........ [Build 160830, API 160828]
000000.000: Module ScnEditor.dll ......... [Build 160828, API 160828]
000000.000: Module Framerate.dll ......... [Build 160828, API 160828]
000000.000: Module Glideslope.dll ........ [Build 170415, API 160828]
000000.000: Glideslope module init: version v2.5, date Apr 15 2017
000000.000: 
000000.000: **** Creating simulation session
000000.000: D3D9: [DirectX 9 Initialized]
000000.000: D3D9: 3D-Adapter = NVIDIA GeForce GTX 960M
000000.000: D3D9: MaxTextureWidth........: 16384
000000.000: D3D9: MaxTextureHeight.......: 16384
000000.000: D3D9: MaxTextureRepeat.......: 8192
000000.000: D3D9: VolTexAddressCaps......: 0x3F
000000.000: D3D9: NumSimultaneousRTs.....: 4
000000.000: D3D9: VertexDeclCaps.........: 0x30F
000000.000: D3D9: XNA Math Support.......: Yes
000000.000: D3D9: Vertex Texture.........: Yes
000000.000: D3D9: Shadow Mapping.........: Yes
000000.000: D3D9: D3DFMT_A16B16G16R16F...: Yes
000000.000: D3D9: D3DFMT_A32B32G32R32F...: Yes
000000.000: D3D9: D3DFMT_D32F_LOCKABLE...: Yes
000000.000: D3D9: D3DFMT_A2R10G10B10.....: Yes
000000.000: D3D9: D3DDTCAPS_DEC3N........: No
000000.000: D3D9: D3DDTCAPS_FLOAT16_2....: Yes
000000.000: D3D9: D3DDTCAPS_FLOAT16_4....: Yes
000000.000: D3D9: Available Texture Memory = 4080 MB
000000.000: D3D9: [3DDevice Initialized]
000000.000: D3D9: [Loading Constellations]
000000.000: D3D9: [D3D9Client Initialized]
000000.000: Module Sun.dll ............... [Build 160828, API 160828]
VSOP87(E) Sun: Precision 1e-006, Terms 554/6634
000000.000: Module Mercury.dll ........... [Build 160828, API 160828]
VSOP87(B) Mercury: Precision 1e-005, Terms 167/7123
000000.000: Module Venus.dll ............. [Build 160828, API 160828]
000000.000: Module VenusAtm2006.dll ...... [Build 160828, API 160828]
VSOP87(B) Venus: Precision 1e-005, Terms 79/1710
000000.000: Module Earth.dll ............. [Build 160828, API 160828]
000000.000: Module EarthAtmJ71G.dll ...... [Build 160828, API 160828]
VSOP87(B) Earth: Precision 1e-008, Terms 2564/2564
000000.000: Module Moon.dll .............. [Build 160828, API 160828]
ELP82: Precision 1e-005, Terms 116/829
000000.000: Module Mars.dll .............. [Build 160828, API 160828]
000000.000: Module MarsAtm2006.dll ....... [Build 160828, API 160828]
VSOP87(B) Mars: Precision 1e-005, Terms 405/6400
000000.000: Module Phobos.dll ............ [Build ******, API 060425]
000000.000: Module Deimos.dll ............ [Build ******, API 060425]
000000.000: Module Galsat.dll ............ [Build 160828, API 160828]
000000.000: Module Jupiter.dll ........... [Build 160828, API 160828]
VSOP87(B) Jupiter: Precision 1e-006, Terms 1624/3625
000000.000: Module Io.dll ................ [Build 160828, API 160828]
000000.000: Module Europa.dll ............ [Build 160828, API 160828]
000000.000: Module Ganymede.dll .......... [Build 160828, API 160828]
000000.000: Module Callisto.dll .......... [Build 160828, API 160828]
000000.000: Module Satsat.dll ............ [Build 160828, API 160828]
000000.000: Module Saturn.dll ............ [Build 160828, API 160828]
VSOP87(B) Saturn: Precision 1e-006, Terms 2904/6365
000000.000: Module Mimas.dll ............. [Build 160828, API 160828]
SATSAT Mimas: Terms 113
000000.000: Module Enceladus.dll ......... [Build 160828, API 160828]
SATSAT Enceladus: Terms 33
000000.000: Module Tethys.dll ............ [Build 160828, API 160828]
SATSAT Tethys: Terms 101
000000.000: Module Dione.dll ............. [Build 160828, API 160828]
SATSAT Dione: Terms 59
000000.000: Module Rhea.dll .............. [Build 160828, API 160828]
SATSAT Rhea: Terms 68
000000.000: Module Titan.dll ............. [Build 160828, API 160828]
SATSAT Titan: Terms 100
000000.000: Module Iapetus.dll ........... [Build 160828, API 160828]
SATSAT Iapetus: Terms 605
000000.000: Module Uranus.dll ............ [Build 160828, API 160828]
VSOP87(B) Uranus: Precision 1e-006, Terms 1827/5269
000000.000: Module Miranda.dll ........... [Build ******, API 060425]
000000.000: Module Ariel.dll ............. [Build ******, API 060425]
000000.000: Module Umbriel.dll ........... [Build ******, API 060425]
000000.000: Module Titania.dll ........... [Build ******, API 060425]
000000.000: Module Oberon.dll ............ [Build ******, API 060425]
000000.000: Module Neptune.dll ........... [Build 160828, API 160828]
VSOP87(B) Neptune: Precision 1e-006, Terms 391/2024
000000.000: Finished initialising world
000000.000: Module DeltaGlider.dll ....... [Build 160828, API 160828]
000000.000: Module LuaInline.dll ......... [Build 160828, API 160828]
000000.000: Module ShuttleA.dll .......... [Build 160828, API 160828]
000000.000: Finished initialising status
000000.000: Finished initialising camera
000000.000: Finished setting up render state
000000.000: D3D9: [Scene Initialized]
000000.000: Glideslope module sim start
000000.000: Finished initialising panels
I hope anyone can help. Would be nice if an possible answer would be a little more elaborate.
 

Face

Well-known member
Orbiter Contributor
Addon Developer
Beta Tester
Joined
Mar 18, 2008
Messages
4,390
Reaction score
577
Points
153
Location
Vienna
Thanks for your rather short reply. I don't know what you want to tell me.
<snip>
Would be nice if an possible answer would be a little more elaborate.

Well, your posted log contained the line about a load error 126 for LandMFD (which I quoted), and I pointed you at a thread talking about this. There was nothing else to write about, because it all was in that thread.

Sorry if it was no solution for you.

---------- Post added at 19:23 ---------- Previous post was at 19:05 ----------

The only two addons i installed are "ModuleMessagingExt" and "Glideslope for Orbiter 2016 v2.6".

Do you have this ModuleMessagingExt installed for 2016: [ame="http://www.orbithangar.com/searchid.php?ID=6966"]ModuleMessagingExt for Orbiter 2016[/ame] ?
EDIT: In order to be more elaborate this time, the reason I'm asking is because this is in the description of the version mentioned:
 
Last edited:

Battlestar

New member
Joined
May 25, 2008
Messages
10
Reaction score
0
Points
1
But let's get to the point now.
Have you installed MS VC++ 2015 Redist (the x86 version)?

Thanks for your reply. Yes, "unfortunately" i have it installed (otherwise it would be the solution... :( ). Btw. i am using Win 10.

And another "btw": I have the same problem with Orbiter 2010 and the corresponding version of Glidslope.

Usually i don't have such problems, or i can figure it out by myself, but this time i just have no idea...

---------- Post added at 05:40 PM ---------- Previous post was at 05:30 PM ----------



Do you have this ModuleMessagingExt installed for 2016: ModuleMessagingExt for Orbiter 2016 ?
EDIT: In order to be more elaborate this time, the reason I'm asking is because this is in the description of the version mentioned:

Yes, this is the version i have installed. I also had the VC2015 package installed. I even reinstalled it. But it just does not work.
 
Top