Tagged: SODE. KMSP
- This topic has 9 replies, 3 voices, and was last updated 6 years, 3 months ago by stevenka.
-
AuthorPosts
-
10. November 2017 at 23:18 #1944ryand63Participant
I am using the KMSP airport and the sode jetways don’t show up. I download the program and run it. Im using FSX:SE and its saying the Platform location is: C:\Program Files (x86)\Steam\steamapps\common\FSX but the exe and dll is going to C:\Users\Ryan\AppData\Roaming\Microsoft\FSX. I do not have FSX box edition installed on my pc. How can I get the jetways to show up?
2. December 2017 at 04:56 #1995stevenkaParticipantI too have the same issue with KMSP. FSX deluxe boxed. I get no sode in addons menu and sode does not exit when FSX shuts down unless using task manager. No problem with shutting down FSX. All else is working and have done several reinstalls of SODE and KMSP. All other features of GSX functioning fine.
3. December 2017 at 11:00 #200112bPilotKeymasterI too have the same issue with KMSP. FSX deluxe boxed. I get no sode in addons menu and sode does not exit when FSX shuts down unless using task manager. No problem with shutting down FSX. All else is working and have done several reinstalls of SODE and KMSP. All other features of GSX functioning fine.
Hi,
What I need is a simconnect.log, see FAQ Section D: https://sode.12bpilot.ch/?topic=faq
Start the sim, launch a flight and then (try to) close the sim again. It just has to be a short session where the SODE process keeps running.
The generated simconnect.log should give me more info.And of course, the SODE.log at C:\ProgramData\12bPilot\SODE\log may also give hints…
3. December 2017 at 23:53 #2002stevenkaParticipanthere it is…
[17:44:17.523] INFO : SODE Version 1.5.3
[17:44:17.523] INFO : Targetting Platform ‘FSX’
[17:44:17.523] DEBUG SODE.SETTINGS : All Settings successfully read.
[17:44:17.523] DEBUG SODE.SETTINGS : Current Settings (1) -> SoundEngine=1; WatchDog=1; SecMenuHotKey=NONE
[17:44:17.523] DEBUG SODE.SETTINGS : Current Settings (2) -> UserJetwaySound=1; ForceHorizontalJetway=1
[17:44:17.523] DEBUG SODE.SETTINGS : Current Settings (3) -> AIDetection=0; AIJetwaySound=0
[17:44:17.523] DEBUG : Initializing Text Menus…
[17:44:17.523] DEBUG : Initializing Seasonal Object Handler…
[17:44:17.523] DEBUG : Initializing SimObject Lists…
[17:44:17.523] DEBUG : Initializing QuadTree…
[17:44:17.523] DEBUG : Initializing Sound Engine…
That’s all of it… Thanks for the help !4. December 2017 at 02:15 #2003stevenkaParticipantIs there any directions on creating a simconnect.ini for FSX to create that log file ?? Thank You again !
6. December 2017 at 15:56 #201012bPilotKeymasterHi,
What kind of motherboard/soundcard do you have?
Sometimes, SODE’s internal sound engine (DirectSound) crashes for unknown (at least for me) reasons.Try to disable SODE’s sound engine from within the SODEPlatformManager: Tools -> Settings -> Enable Sound Engine => False.
14. December 2017 at 04:05 #2013stevenkaParticipantI can dig up the exact model but I do know it’s an Intel MB something like …55wg with an intell i5 . I disabled the onboard audio as it was totally messing up my fa2crew voice recognition from working. I instead installed an old PCI sound blaster card and that fixed that. Should I do a quick switch back to the onboard audio and try a reinstall of SODE to test it ? Thank you again for the help. I’m getting so tired of all the tweaking required for everything installed and never get to flying.
Steve
14. December 2017 at 04:11 #2014stevenkaParticipantSorry I forgot to ask…. Can you open the SodePlatformManager outside of the FSX addons menu ? I don’t get the sode in the FSX addons menu.
16. December 2017 at 15:06 #201512bPilotKeymasterSorry I forgot to ask…. Can you open the SodePlatformManager outside of the FSX addons menu ? I don’t get the sode in the FSX addons menu.
Yes, the SODEPlatformManager.exe is a stand alone tool. It should be installed in C:\Program Files (x86)\12bPilot\SODE.
16. December 2017 at 15:42 #2016stevenkaParticipantOK I think I got things working ! In order to improve my VAS I reinstalled the original Nvidia graphics driver for my GTX660 and sode reinstall after that and everything looks good now. Thanks for the help
Steve
-
AuthorPosts
- You must be logged in to reply to this topic.