boogabooga
Bug Crusher
- Joined
- Apr 16, 2011
- Messages
- 3,010
- Reaction score
- 16
- Points
- 63
Agghh, if you don't tell exactly where it is, I'm going to spend the afternoon looking for it. :facepalm: :blush:
OHM BaseSyncMFD 3.3 for Orbiter 2010
- Thread starter OrbitHangar
- Start date
Agghh, if you don't tell exactly where it is, I'm going to spend the afternoon looking for it. :facepalm: :blush:
ADSWNJ
Scientist
- Joined
- Aug 5, 2011
- Messages
- 1,667
- Reaction score
- 7
- Points
- 38
It's a "13,063" instead of a "10,063" on p4 (Closest Passage documentation). I misread the screen clip on p3, due to the line of nodes being right on the time! Ripley pays very close attention to these things, as he translates documentation into Italian for our Forum Orbiter Italia friends. That's all 
Enjo
Mostly harmless
- Joined
- Nov 25, 2007
- Messages
- 1,667
- Reaction score
- 19
- Points
- 38
- Location
- Germany
- Website
- www.enderspace.de
- Preferred Pronouns
- Can't you smell my T levels?
Geez. You sure like your job very much.
boogabooga
Bug Crusher
- Joined
- Apr 16, 2011
- Messages
- 3,010
- Reaction score
- 16
- Points
- 63
It was Sunday.
Enjo
Mostly harmless
- Joined
- Nov 25, 2007
- Messages
- 1,667
- Reaction score
- 19
- Points
- 38
- Location
- Germany
- Website
- www.enderspace.de
- Preferred Pronouns
- Can't you smell my T levels?
I meant playing Orbiter as a secondary job. Hard joke.
ADSWNJ
Scientist
- Joined
- Aug 5, 2011
- Messages
- 1,667
- Reaction score
- 7
- Points
- 38
For @Iacomus_Maximus and @ChrisHill ... can you let me know if you are able to run this version, or are you still getting error 126?
126 indicates that one of the pre-requisite dependencies is not found. Could be a VC runtime file, or MMExt, or it could be permissioning. If you are feelubng inquisitive - download Process Monitor and run it whilst trying to start Orbiter. You should get a ton of data, including file not founds that are legitimate (as it searches the path for dependencies, etc), but this will get us closer to the problem. If you want, I'll run the same for comparison.
---------- Post added at 01:42 PM ---------- Previous post was at 11:33 AM ----------
Quick tutorial on how to capture the ProcMon data.
1. Download and unzip the ProcessMonitor.zip from the link above.
2. Run procmon.exe.
3. Run orbiter and recreate the problem, then exit orbiter if it didn't crash first.
4. In Process Monitor, File and Capture Events and confirm that the tick mark goes off alongside Capture Events.
5. Filter, Filter... "Process Name" "contains" "orbiter" then "Include" ... Add, Apply, then...
6. "Operation" "begins with" "Reg" then "Exclude" ... Add, Apply, then...
7. "Operation" "is" "ReadFile" then "Exclude" ... Add, Apply, OK. (You should have 1000-3000 lines now showing in the filter (see the status line on the bottom of the window).)
8. File, Save, choose "Events displayed using current filter", select "Also include profiling events", choose "Comma-Separated values", and OK.
9. Zip up the resulting file for upload. It should be less than 60KB if all is good.
126 indicates that one of the pre-requisite dependencies is not found. Could be a VC runtime file, or MMExt, or it could be permissioning. If you are feelubng inquisitive - download Process Monitor and run it whilst trying to start Orbiter. You should get a ton of data, including file not founds that are legitimate (as it searches the path for dependencies, etc), but this will get us closer to the problem. If you want, I'll run the same for comparison.
---------- Post added at 01:42 PM ---------- Previous post was at 11:33 AM ----------
Quick tutorial on how to capture the ProcMon data.
1. Download and unzip the ProcessMonitor.zip from the link above.
2. Run procmon.exe.
3. Run orbiter and recreate the problem, then exit orbiter if it didn't crash first.
4. In Process Monitor, File and Capture Events and confirm that the tick mark goes off alongside Capture Events.
5. Filter, Filter... "Process Name" "contains" "orbiter" then "Include" ... Add, Apply, then...
6. "Operation" "begins with" "Reg" then "Exclude" ... Add, Apply, then...
7. "Operation" "is" "ReadFile" then "Exclude" ... Add, Apply, OK. (You should have 1000-3000 lines now showing in the filter (see the status line on the bottom of the window).)
8. File, Save, choose "Events displayed using current filter", select "Also include profiling events", choose "Comma-Separated values", and OK.
9. Zip up the resulting file for upload. It should be less than 60KB if all is good.
Last edited:
ADSWNJ
Scientist
- Joined
- Aug 5, 2011
- Messages
- 1,667
- Reaction score
- 7
- Points
- 38
To upload the ProcMon file, "Post Reply" to this thread (Quick Reply is not good), press Manage Attachments at the bottom, then select your .zip file and upload.
Mine's attached. We can then compare & contrast.
Within this log, the important piece is what happens in and around the entry "Load Image" and your full path to BaseSyncMFD.dll. You should have the following:
1. Query Open, Create File, Create File Mapping x2, Load Image, CloseFile, CreateFile, QueryBasicInformationFile, CloseFile for BaseSyncMFD.DLL.
2. A series of QueryOpen and CreateFile entries with NAME NOT FOUND, trying to locate ModuleMessagingExt.dll (it's searching the path to resolve this dependency)
3. QueryOpen SUCCESS on ModuleMessagingDLL in your Orbiter\Modules directory, then Create File, Create File Mapping x2, Load Image, CloseFile.
4. Same pattern trying to locate msvcr100.dll (the release version of the C runtime library for VC++ 2010), and when successful - a QueryBasicInformation sequence, and a LoadImage sequence.
5. A QueryBasicInformation sequence on ModuleMessagignExt.dll
6. A locate pattern on msvcp100.dll (the release version of the standard C++ library for VC++ 2010), and when successful - a QueryBasicInformation sequence, and a LoadImage sequence.
7. A write sequence updating Orbiter.log to say we loaded it OK, and then it moves on to other modules.
This is the pattern we want to diagnose.
Mine's attached. We can then compare & contrast.
Within this log, the important piece is what happens in and around the entry "Load Image" and your full path to BaseSyncMFD.dll. You should have the following:
1. Query Open, Create File, Create File Mapping x2, Load Image, CloseFile, CreateFile, QueryBasicInformationFile, CloseFile for BaseSyncMFD.DLL.
2. A series of QueryOpen and CreateFile entries with NAME NOT FOUND, trying to locate ModuleMessagingExt.dll (it's searching the path to resolve this dependency)
3. QueryOpen SUCCESS on ModuleMessagingDLL in your Orbiter\Modules directory, then Create File, Create File Mapping x2, Load Image, CloseFile.
4. Same pattern trying to locate msvcr100.dll (the release version of the C runtime library for VC++ 2010), and when successful - a QueryBasicInformation sequence, and a LoadImage sequence.
5. A QueryBasicInformation sequence on ModuleMessagignExt.dll
6. A locate pattern on msvcp100.dll (the release version of the standard C++ library for VC++ 2010), and when successful - a QueryBasicInformation sequence, and a LoadImage sequence.
7. A write sequence updating Orbiter.log to say we loaded it OK, and then it moves on to other modules.
This is the pattern we want to diagnose.
Last edited:
Enjo
Mostly harmless
- Joined
- Nov 25, 2007
- Messages
- 1,667
- Reaction score
- 19
- Points
- 38
- Location
- Germany
- Website
- www.enderspace.de
- Preferred Pronouns
- Can't you smell my T levels?
Shall I compile it for you, Andrew?
ADSWNJ
Scientist
- Joined
- Aug 5, 2011
- Messages
- 1,667
- Reaction score
- 7
- Points
- 38
Hi Enjo - you think this is just a recompile issue? Looking at bcirka's ProcMon file - I see no trace of BaseSyndMFD.dll at all, so I think this is a different problem.
@bcirka - can you upload your Orbiter.log, or give any more color around what you were doing to get this 126 error?
@bcirka - can you upload your Orbiter.log, or give any more color around what you were doing to get this 126 error?
ADSWNJ
Scientist
- Joined
- Aug 5, 2011
- Messages
- 1,667
- Reaction score
- 7
- Points
- 38
Announcing the new BaseSyncMFD v3.0 ! !
Base Sync is a utility to determine the best orbit for reentry to arrive at a target base, and then to determine the deorbit burn information. It predicts your closest approach on up to 99 orbits, and calculates the optimal plane change for direct over-flight of the base, and the retro-burn for re-entry on the desired angle, anticipation and entry interface altitude.
**NEW** in v3.0 is the interconnectors to Glideslope 2.4 to drive a fully automated reentry burn for Glideslope.
Base Sync is a utility to determine the best orbit for reentry to arrive at a target base, and then to determine the deorbit burn information. It predicts your closest approach on up to 99 orbits, and calculates the optimal plane change for direct over-flight of the base, and the retro-burn for re-entry on the desired angle, anticipation and entry interface altitude.
**NEW** in v3.0 is the interconnectors to Glideslope 2.4 to drive a fully automated reentry burn for Glideslope.
garyw
O-F Administrator
- Joined
- May 14, 2008
- Messages
- 10,548
- Reaction score
- 347
- Points
- 173
- Location
- East Sussex
- Website
- blog.gdwnet.com
- Preferred Pronouns
- He/Him
Nicely done! Thank you ADSWNJ!
jgrillo2002
Conservative Pioneer
Excellent work man.
Hi, I downloaded new BaseSyncMFD v3.0 from orbiter hangar but after I added it in 'modules' i get message that application can not be run becouse of missing ModuleMessagingExt.dll
Does anybody know how to fix it?
Does anybody know how to fix it?
IronRain
The One and Only (AFAIK)
- Joined
- Oct 11, 2009
- Messages
- 3,488
- Reaction score
- 407
- Points
- 123
- Location
- Utrecht
- Website
- www.spaceflightnewsapi.net
Thanks for the hard work!
Unfortunately I must report that I'm getting the 126 error too.
Unfortunately I must report that I'm getting the 126 error too.
Code:
Error loading module Modules\Plugin\BaseSyncMFD.dll (code 126)
Error loading module Modules\Plugin\GS2.dll (code 126)Enjo
Mostly harmless
- Joined
- Nov 25, 2007
- Messages
- 1,667
- Reaction score
- 19
- Points
- 38
- Location
- Germany
- Website
- www.enderspace.de
- Preferred Pronouns
- Can't you smell my T levels?
Got [ame="http://www.orbithangar.com/searchid.php?ID=6889"]ModuleMessagingExt[/ame] ?
IronRain
The One and Only (AFAIK)
- Joined
- Oct 11, 2009
- Messages
- 3,488
- Reaction score
- 407
- Points
- 123
- Location
- Utrecht
- Website
- www.spaceflightnewsapi.net
Yes, I even re-installed it to rule this out.
IronRain
The One and Only (AFAIK)
- Joined
- Oct 11, 2009
- Messages
- 3,488
- Reaction score
- 407
- Points
- 123
- Location
- Utrecht
- Website
- www.spaceflightnewsapi.net
Never mind, I screwed up.
Installed the SDK. That won't work...
Time for some
Installed the SDK. That won't work...
Time for some
ADSWNJ
Scientist
- Joined
- Aug 5, 2011
- Messages
- 1,667
- Reaction score
- 7
- Points
- 38
Never mind, I screwed up.
Installed the SDK. That won't work...
Time for some
Do tell ... in what way did you screw up? Interested in what you are doing to analyze the problem and then fix it.
126 is an error in DLL LoadLibrary, which is almost certainly going to be the ModuleMessagingExt.DLL. Two things to look at: is ModuleMessagingExt.DLL in your Modules directory, and are the permissions OK for you to open it? I forget - maybe it needs enabling in the Orbiter config screen (i.e. where you enable MFD's). That, plus the VC++ 2010 redist is basically all that could be missing.
Similar threads
