Jump to content
The simFlight Network Forums

billn53

Members
  • Content Count

    24
  • Joined

  • Last visited

Community Reputation

0 Neutral

About billn53

  • Rank
    Member
  1. Burkhard, Can I use the manual install procedure you described above (for P3Dv2) work if I only have MyTraffic X for FSX? Or must I already have the P3D v1.4 version of MyTraffic X installed?
  2. billn53

    5.4c CTD problem - a solution?

    Inept user here... How do I revert to 2012 schedules? I recently installed 5.4C and am getting the ntdll.dll crashes discussed in this thread? -Bill
  3. Pete, Just got back Thursday from my trips to both US coasts and want to give you a quick follow-up. Looks like I've solved the problem by rolling-back my NVidia driver to 304.48, as Jess suggested. Thanks to you and Jess for all your help! I just paid for a registered version of FSUIPC, not that I need all the bells-and-whistles that come with it but because I appreciate your support and this is a small way I can reimburse you for your efforts! -Bill
  4. Jess - Thanks for the input. When I de-selected multiple monitor mode, FSX ran fine. I'll check out the 304.48 driver and see if it helps, though my motherboard is finicky about which drivers it will let me use Surround with. Pete - My default aircraft is the default ultralight. I'm also thinking this is a driver issue. I am using the latest NVidia 'beta' drivers. I'll try going back to 304.48 and see how that works. Have a good holiday. I'm flying in and out (real life) for a couple of weeks beginning Wednesday and don't know how much time I'll have available to troubleshoot. Good news is I have a second PC (single monitor, no Surround) as backup for anything that needs FSUIPC. But the triple-monitor display is certainly nice! -Bill
  5. Tried the new unsigned loader, go directly to d) below for those (unhappy) results. Just to add to the confusion: As I mentioned, FSUIPC has run in the past on my system. As a test, I removed all traces of FSUIPC4 from my Modules folder, dll.xml and fsx.cfg. I then uninstalled and re-installed the QualityWings 757, which includes FSUIPC 4.70b. I also re-loaded the latest Addon Manager from FSDreamteam. FSX started up and FSUIPC ran a-ok, creating a FSUIPC4.LOG file and showing on the 'Addon' tab in FSX. However, it only ran once. Every subsequent attempt was the same old story as before. I even tried using the FSUIPC_Loader dll with 4.70b, no joy. << This was not the new 'unsigned' loader, go to d) below for those results. a) Retracing my steps, I removed everything from dll.xml except the FSUIPC entry, and deleted the trust line for FSUIPC in fsx.cfg. Starting FSX, a trust entry was created, FSUIPC ran (log file created), and everything worked fine. I re-started FSX three times just to be sure it wasn't a fluke. This was with 4.70b. B) Next, I added the bglmanx.dll section to xml.dll (just after the fsuipc section). PROBLEM RETURNS! No FSUIPC4.LOG created, and FSX hangs. SimConnect.Log looks exactly the same as previously reported. c) I then removed the bglmanx.dll section from xml.dll (leaving just the FSUIPC entry), but the problem didn't go away. I again removed the trust entry for FSUIPC from fsx.cfg and re-started FSX. A trust entry was created but nothing more--FSUIPC would not start. I tried re-starting FSX three times without success, even though the configuration seems to be exactly the same as in a), above. Now I'm really scratching my head... d) Later... Just got the new 'unsigned' loader version. Ran it with 4.844c (first I deleted the old trust entries from fsx.cfg). My dll.xml has only an entry for the loader. Interesting result: FSX tried to run (the interface music began, which is more than before) but soon afterward crashed (hung up), without getting to the flight options screen. FSUIPC did not start (no FSUIPC4.LOG was created). Here's the excerpt from the Simconnect log: 0.00000 SimConnect version 10.0.61259.0 0.00404 Server: Scope=local, Protocol=Auto, Address=::1, Port=51703, MaxClients=64 0.02393 Server: Scope=local, Protocol=Pipe, Name=\\.\pipe\Microsoft Flight Simulator\SimConnect, MaxClients=64 0.02515 Server: Scope=local, Protocol=IPv6, Address=::1, Port=51704, MaxClients=64 0.02685 Server: Scope=local, Protocol=IPv4, Address=127.0.0.1, Port=51705, MaxClients=64 0.45914 Exe Launched: Path="fsdreamteam\couatl\couatl.exe" CommandLine="" Version="2.0.0.2315" 0.46130 Exe Launched: Path="C:\Program Files (x86)\Saitek\Pro Flight Panels\SaiPanels.exe" CommandLine="-run" Version="1.0.0.1" 0.47501 Exe Launched: Path="C:\Program Files (x86)\EZCA\EZCA.exe" CommandLine="" Version="1.1.7.0" 9.13202 Panels data export found and set to 20B319D8 9.13213 DLL Loaded: Path="Modules\FSUIPC4_loader.dll" Version="1.1.0.0" > 21.75455 [191, 1]Open: Version=0x00000002 Name="Saitek Flight Sim X Plugin" > 21.75466 [191, 2]SubscribeToSystemEvent:EventID=1, SystemEventName="SimStart" > 21.75468 [191, 3]SubscribeToSystemEvent:EventID=2, SystemEventName="SimStop" > 21.75469 [191, 4]SubscribeToSystemEvent:EventID=3, SystemEventName="Paused" > 21.75471 [191, 5]SubscribeToSystemEvent:EventID=4, SystemEventName="Unpaused" > 21.75472 [191, 6]AddToDataDefinition:DefineID=2, DatumName="AUTOPILOT ALTITUDE LOCK VAR", UnitsName="Feet", DatumType=3, fEpsilon=0.000000, DatumID=0 etc... > 21.76062 [190, 82]MenuAddItem:szMenuItem="EZdok camera addon", MenuEventID=4100, dwData=0 > 21.76064 [190, 83]MenuAddSubItem:MenuEventID=4100, szMenuItem="Show studio..", SubMenuEventID=4000, dwData=0 > 21.76065 [190, 84]MenuAddSubItem:MenuEventID=4100, szMenuItem="Global Disable", SubMenuEventID=4001, dwData=0 end.
  6. You're right, the added delay didn't help. I have one more thing I'm going to try, but don't hold out much hope. Regards, Bill
  7. Sorry to report that neither 4844c by itself nor using the loader show any improvement. The Simconnect.log reads exactly the same as before, and the FSUIPC.Log is not created. Thanks for all your effort, though. -Bill
  8. Wow! Talk about support. I'll try each approach and get back to you this evening. -bill
  9. I assume you've tried different video drivers? Not much choice there, no change. Is it possible to delay the change to surround mode or isnt' it that switchable? Surround must be active before starting FSX and can't be switched without first closing FSX. What happens if you've closed FS in Windowed mode so it starts up like that next time? Then just use ALT + ENTER to go to full screen mode afterwards? Good idea, didn't work. :-(
  10. Thought I'd give one last try, using your suggestion to re-name the EXE.XML file so its programs are no longer in play. Short story is, No Joy. Here's the SimConnect log (NVidia Surround active): 0.00000 SimConnect version 10.0.61259.0 0.00452 Server: Scope=local, Protocol=Auto, Address=::1, Port=52530, MaxClients=64 0.01714 Server: Scope=local, Protocol=Pipe, Name=\\.\pipe\Microsoft Flight Simulator\SimConnect, MaxClients=64 0.01863 Server: Scope=local, Protocol=IPv6, Address=::1, Port=52531, MaxClients=64 0.02072 Server: Scope=local, Protocol=IPv4, Address=127.0.0.1, Port=52532, MaxClients=64 -Bill
  11. Back again, with more info. Thanks for the new version 4.884b. I installed it and did some testing with and without NVidia Surround. First, I stripped everything out of my dll.xml except for the FSUIPC entry. Running with NVidia Surround active (triple screen display), some things of note: - I do get the "Flight Simulater has detected a problem..." error and, after clicking 'yes' to run FSX 'hangs' at the spash screen - I do get a trust entry created in my FSX.cfg file. - No FSUIPC4.log is created - The Simconnect0.log is very short: 0.00000 SimConnect version 10.0.61259.0 0.00441 Server: Scope=local, Protocol=Auto, Address=::1, Port=58024, MaxClients=64 0.01580 Server: Scope=local, Protocol=Pipe, Name=\\.\pipe\Microsoft Flight Simulator\SimConnect, MaxClients=64 0.01722 Server: Scope=local, Protocol=IPv6, Address=::1, Port=58025, MaxClients=64 0.01923 Server: Scope=local, Protocol=IPv4, Address=127.0.0.1, Port=58026, MaxClients=64 0.25955 Exe Launched: Path="fsdreamteam\couatl\couatl.exe" CommandLine="" Version="2.0.0.2315" 0.26780 Exe Launched: Path="C:\Program Files (x86)\Saitek\Pro Flight Panels\SaiPanels.exe" CommandLine="-run" Version="1.0.0.1" 0.28797 Exe Launched: Path="C:\Program Files (x86)\EZCA\EZCA.exe" CommandLine="" Version="1.1.7.0" Here is where it gets interesting... With NVidia Surround deactivated (single screen display): - I do get the "Flight Simulater has detected a problem..." error, but after clicking 'yes' to run FSX starts-up a-ok - An FSUIPC4.log is successfully created: ********* FSUIPC4, Version 4.844b by Pete Dowson ********* Running inside FSX on Windows 7 Module base=61000000 User Name="" User Addr="" FSUIPC4 not user registered WIDEFS7 not user registered, or expired 47 System time = 09/08/2012 09:45:21 47 FLT path = "C:\Users\Administrator\Documents\Flight Simulator X Files\" 94 Trying to connect to SimConnect Acc/SP2 Oct07 ... 94 FS path = "E:\FlightSims\Microsoft Games\Microsoft Flight Simulator X\" 593 LogOptions=00000000 00000001 593 Wind smoothing fix is fully installed 593 G3D.DLL fix attempt installed ok 593 SimConnect_Open succeeded: waiting to check version okay 593 Trying to use SimConnect Acc/SP2 Oct07 11809 Running in "Microsoft Flight Simulator X", Version: 10.0.61637.0 (SimConnect: 10.0.61259.0) 11809 Initialising SimConnect data requests now 11825 FSUIPC Menu entry added 11934 E:\FlightSims\Microsoft Games\Microsoft Flight Simulator X\FLIGHTS\OTHER\FLTSIM.FLT 11934 E:\FlightSims\Microsoft Games\Microsoft Flight Simulator X\SimObjects\Airplanes\Aircreation_582SL\Aircreation_582SL.AIR 65099 System time = 09/08/2012 09:46:26 65099 *** FSUIPC log file being closed G3D fix: Passes 4505, Null pointers 0, Bad pointers 0, Separate instances 0 Memory managed: 4 Allocs, 4 Freed ********* FSUIPC Log file closed *** ******* - The Simconnect0.log is contains much more info (384kb long): 0.00000 SimConnect version 10.0.61259.0 0.00430 Server: Scope=local, Protocol=Auto, Address=::1, Port=58074, MaxClients=64 0.01638 Server: Scope=local, Protocol=Pipe, Name=\\.\pipe\Microsoft Flight Simulator\SimConnect, MaxClients=64 0.01781 Server: Scope=local, Protocol=IPv6, Address=::1, Port=58075, MaxClients=64 0.01964 Server: Scope=local, Protocol=IPv4, Address=127.0.0.1, Port=58076, MaxClients=64 0.26019 Exe Launched: Path="fsdreamteam\couatl\couatl.exe" CommandLine="" Version="2.0.0.2315" 0.26851 Exe Launched: Path="C:\Program Files (x86)\Saitek\Pro Flight Panels\SaiPanels.exe" CommandLine="-run" Version="1.0.0.1" 0.28865 Exe Launched: Path="C:\Program Files (x86)\EZCA\EZCA.exe" CommandLine="" Version="1.1.7.0" 17.49535 Panels data export found and set to 20B319D8 18.03476 DLL Loaded: Path="Modules\FSUIPC4.dll" Version="4.8.4.4" > 29.21597 [191, 1]Open: Version=0x00000002 Name="Saitek Flight Sim X Plugin" > 29.21612 [191, 2]SubscribeToSystemEvent:EventID=1, SystemEventName="SimStart" > 29.21615 [191, 3]SubscribeToSystemEvent:EventID=2, SystemEventName="SimStop" > 29.21616 [191, 4]SubscribeToSystemEvent:EventID=3, SystemEventName="Paused" > 29.21617 [191, 5]SubscribeToSystemEvent:EventID=4, SystemEventName="Unpaused" > 29.21619 [191, 6]AddToDataDefinition:DefineID=2, DatumName="AUTOPILOT ALTITUDE LOCK VAR", UnitsName="Feet", DatumType=3, fEpsilon=0.000000, DatumID=0 ...and a bunch of other stuff that's probably not relevant to the problem What does seem important is that, with NVidia Surround active, the SimConnect log never gets to the entry: 17.49535 Panels data export found and set to 20B319D8 Thus I conclude that there may be some incompatibility between SimConnect and NVidia Surround, at least on my system. Since Surround is a 'must have' for me, I'm not sure I can do anything other than hope that a new NVidia driver appears and the problem goes away. Finally, FSUIPC _has_ run, a handful of times over the past few weeks, with Surround active. Maybe I was just lucky and the stars were aligned correctly. For completeness, I'm attaching my FSUIPC Install Log -Bill ================================================================ FSUIPC Install.log Installer for FSUIPC4.DLL version 4.84 Looking in registry for FSX install path: HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Microsoft Games\Flight Simulator\10.0 Parameter"SetupPath" ... >>> OK! FOUND FSX! <<< ... Looking in registry for ESP install path: HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Microsoft ESP\1.0 Parameter"SetupPath" Not there, so looking in: HKEY_CURRENT_USER\ESP Parameter"AppPath" ... NOT found! ... Looking in registry for Prepar3D install path: HKEY_LOCAL_MACHINE\SOFTWARE\LockheedMartin\Prepar3D Parameter"SetupPath" ... >>> OK! FOUND Prepar3D! <<< ... =========================================================== INSTALLATION FOR FSX: SetupPath="E:\FlightSims\Microsoft Games\Microsoft Flight Simulator X" Checking version of FSX.EXE: ... Version 10.0.61637.0 (Need at least 10.0.60905.0) Checking compatibility with installed SimConnect: Found SimConnect build 60905 (Original) Found SimConnect build 61242 (SP1 May07) Found SimConnect build 61259 (Acc/SP2 Oct07) Checking if there's already a version of FSUIPC4 installed in: E:\FlightSims\Microsoft Games\Microsoft Flight Simulator X\Modules\FSUIPC4.DLL ... Version 4.840 found. FSX Modules folder already exists. Okay -- installed FSUIPC4 into "E:\FlightSims\Microsoft Games\Microsoft Flight Simulator X\Modules\FSUIPC4.DLL" Looking for the current user's Application Data path: ... found as "C:\Users\Administrator\AppData\Roaming" Now finding \Microsoft\FSX\FSX.CFG for all users, including this one Looking in "C:\Users\Administrator\AppData\Roaming" Found FSX.CFG in "C:\Users\Administrator\AppData\Roaming\Microsoft\FSX\FSX.CFG" Now checking DLL.XML ... ... There is a previous DLL.XML, checking for FSUIPC4 section. ... FSUIPC4 section already exists but will be replaced. ... FSUIPC4 section of DLL.XML written okay Now checking for a SimConnect.XML file ... ... There is a SimConnect.XML, checking for "local" section. ... "local" section already exists, file not modified. Looking in "C:\Users\All Users\AppData\Roaming" ... No FSX.CFG there Looking in "C:\Users\Default\AppData\Roaming" ... No FSX.CFG there Looking in "C:\Users\Default User\AppData\Roaming" ... No FSX.CFG there Looking in "C:\Users\Public\AppData\Roaming" ... No FSX.CFG there Looking in "C:\Users\UpdatusUser\AppData\Roaming" ... No FSX.CFG there "Modules\FSUIPC Documents" folder already exists. Now installing additional files into the "Modules\FSUIPC Documents" folder: Installed "FSUIPC4 User Guide.pdf" okay Installed "FSUIPC4 for Advanced Users.pdf" okay Installed "FSUIPC4 History.pdf" okay Installed "List of FSX controls.pdf" okay Installed "GlobalSign Root.exe" okay Installed "FSUIPC Lua Library.pdf" okay Installed "FSUIPC Lua Plug-Ins.pdf" okay Installed "Lua License.pdf" okay Installed "Lua Plugins for VRInsight Devices.pdf" okay Installed "LuaFileSystem.pdf" okay Installed "Example LUA plugins.zip" okay Installed "Offset Mapping for PMDG 737NGX.pdf" okay FSUIPC4.DLL installed and signature checked out okay! Deleted GlobalSign Root fix program ... no longer relevant =========================================================== INSTALLATION FOR Prepar3D: SetupPath="F:\flightsims\Lockheed Martin\Prepar3D\" Checking version of Prepar3D.EXE: ... Version 1.3.3708.0 (Need at least 1.0.677.0) Checking compatibility with installed SimConnect: Found SimConnect build 60905 (Original) Found SimConnect build 195 (ESP Orig) Found SimConnect build 61242 (SP1 May07) Found SimConnect build 61259 (Acc/SP2 Oct07) Checking if there's already a version of FSUIPC4 installed in: F:\flightsims\Lockheed Martin\Prepar3D\Modules\FSUIPC4.DLL ... Version 4.840 found. Prepar3D Modules folder already exists. Okay -- installed FSUIPC4 into "F:\flightsims\Lockheed Martin\Prepar3D\Modules\FSUIPC4.DLL" Looking for the current user's Application Data path: ... found as "C:\Users\Administrator\AppData\Roaming" Now finding \Lockheed Martin\Prepar3D\Prepar3D.CFG for all users, including this one Looking in "C:\Users\Administrator\AppData\Roaming" Found Prepar3D.CFG in "C:\Users\Administrator\AppData\Roaming\Lockheed Martin\Prepar3D\Prepar3D.CFG" Now checking DLL.XML ... ... There is a previous DLL.XML, checking for FSUIPC4 section. ... FSUIPC4 section already exists but will be replaced. ... FSUIPC4 section of DLL.XML written okay Now checking for a SimConnect.XML file ... ... No SimConnect.XML file found. This is okay. Looking in "C:\Users\All Users\AppData\Roaming" ... No Prepar3D.CFG there Looking in "C:\Users\Default\AppData\Roaming" ... No Prepar3D.CFG there Looking in "C:\Users\Default User\AppData\Roaming" ... No Prepar3D.CFG there Looking in "C:\Users\Public\AppData\Roaming" ... No Prepar3D.CFG there Looking in "C:\Users\UpdatusUser\AppData\Roaming" ... No Prepar3D.CFG there "Modules\FSUIPC Documents" folder already exists. Now installing the Prepar3D SimConnect interface for FSUIPC4 into the "Modules" folder: Installed "SimConnectP3D.dll" okay Now installing additional files into the "Modules\FSUIPC Documents" folder: Installed "FSUIPC4 User Guide.pdf" okay Installed "FSUIPC4 for Advanced Users.pdf" okay Installed "FSUIPC4 History.pdf" okay Installed "List of FSX controls.pdf" okay Installed "GlobalSign Root.exe" okay Installed "FSUIPC Lua Library.pdf" okay Installed "FSUIPC Lua Plug-Ins.pdf" okay Installed "Lua License.pdf" okay Installed "Lua Plugins for VRInsight Devices.pdf" okay Installed "LuaFileSystem.pdf" okay Installed "Example LUA plugins.zip" okay Installed "Offset Mapping for PMDG 737NGX.pdf" okay FSUIPC4.DLL installed and signature checked out okay! Deleted GlobalSign Root fix program ... no longer relevant =========================================================== All installer tasks completed. *************** End of Install Log ***************
  12. Thanks, Pete! That's more support than I have the right to ask for. I will be flying this evening (real life pilot) so won't have a chance to try your new code for a day or two. I'll give you a report-back as soon as I am able. -Bill
  13. I just found this post: http://forum.simflight.com/topic/72140-fsuipc-crash-on-nvidia-surround/page__hl__surround in which it is reported that the problem is somehow related to using NVidia 'Surround' (i.e., display spanning multiple monitors). I have the same configuration. hmmmm...
  14. Thanks, and welcome back, Pete! Some responses to your comments & questions 1) If FSUIPC is supposed to create a new FSUIPC4.LOG after I click 'yes' to the question "Do you want to run this software (not recommended)?, then it looks like FSUIPC isn't getting started (the only log file I have is from the last time I was able to run FSX successfully with FSUIPC). 2) I've been running FSX 'as administrator' only because the moderators at the REX forum insist that's what should be done. I'll follow your advice and run it normally from now on. 3) I 'reinstalled' Simconnect by running the SimConnect.msi found in ghe FSX SDK/SDK/Core Utilities Kit/SimConnect SDK/lib folder. 4) I'll check out how to get a SimConnect log created. But if the problem is that FSUIPC isn't even getting started then the problem may not be with simconnect. Thanks again, Bill
  15. I have been struggling for the past week with what appears to be the dreaded simconnect bug (i.e., FSX 'hangs' when loading FSUIPC). Following the advice in the FAQ section, I edited my dll.xml so that the only entry was the one for FSUIPC. With only this entry, FSUIPC started fine and a trust string for FSUIPC was entered in my FSX.cfg file. I did the exact same procedure for bglmanx.dll (which has also been giving me problems). With only the bglmanx.dll entry in dll.xml, everything works fine and a trust string for bglmanx.dll was entered in my FSX.cfg file. However, When I edited my dll.xml to include entries for both FSUIPC and bglmanx.dll, I get the error message about Flight Simulator having detected a problem with FSUIPC, and when I click 'yes' to run it anyway, FSX goes into 'hang' mode (i.e., have only the FSX 'splash' screen and the spinning blue circle, nothing further). The order of the entries in dll.xml also doesn't make any difference. Note that with the two together, bglmanx seems to be loading fine (at least, I'm not getting the 'Flight Simulator has detected a problem' message for bglmanx.dll), it is just when FSUIPC tries to load that the hand occurs. Any ideas on what I should try next? I know Pete says persistance is the answer but I've probably spent 20-hours so far trying to get things working. Some other questions: - Should I delete the FSX.cfg trust entry for FSUIPC (the one that was created when only FSUIPC was in my dll.xml)? - Do I need to re-boot my PC each time I try to run FSX? - Other than the FSUIPC.log, are there any other error logs I can check to see what's going on? For reference, I'm using: FSUIPC 4.84 and the most current version of Addon Manager (which includes bglmanx.dll). 64-bit Windows 7 Real-time protection in Microsoft Security Essentials (my only AV program) is turned off. FSX is installed on a separate SSD from my OS I always run FSX 'as administrator' UAC and DEP are off I did follow the suggestions in the FAQ (I have installed a security certificate, and initdelay is set to 10) I did do a re-install of simconnect just in case the problem was there, but that didn't help Thanks in advance, Bill
×

Important Information

By using this site, you agree to our Terms of Use. Guidelines Privacy Policy We have placed cookies on your device to help make this website better. You can adjust your cookie settings, otherwise we'll assume you're okay to continue.