Jump to content
The simFlight Network Forums

Matt Davies

Members
  • Posts

    10
  • Joined

  • Last visited

Matt Davies's Achievements

Newbie

Newbie (1/14)

0

Reputation

  1. You're actually a genius - that worked perfectly. Unfortunately, active dev on FSINN stopped some years ago so there isn't really anything I can do to get it "sorted" - this is a perfect workaround though, so thank you! (drinks on me)
  2. Hi Pete, Yes, "Prepar3D.exe" is what I meant. How am I retrieving the logs? I can't get P3D to run so I'm unsure if FSUIPC will generate logs? Cheers, Matt.
  3. Sorry for the late reply - I completely forgot I posted this. I keep the exe with the name of P3Dv2.exe, but change the version number with resource hacker. I'll grab the logs when I get back into P3D, but I have a feeling its not gonna work due to the second statement you made. Nothing that FSUIPC is doing wrong, it's just FSINN - always presenting problems!
  4. Hi there Peter, In order to get FSINN working correctly with P3Dv2, you have to "trick" FSINN into thinking that P3D.exe is a different version than the one that's currently shipped. The tutorial provided on the FSINN support forum states to get Resource Hacker and change it, which I've done. The problem is now that FSUIPC4.dll crashes P3Dv2 (when I go back to the original .exe, it works perfectly), is there any work around for this (apart from obviously reverting back to the original P3D.exe)? Apologies if this has already been answered, I've had a quick scout of the forums and couldn't see anything. Cheers, Matt.
  5. Hi Pete, Rolled back the drivers to the suggested ones and after 1 Simconnect trust message, we're all back to normal. nVidia, how you frustrate me! Thanks for your help, it's much appreciated. Lets hope when the beta drivers come to release, they'll have fixed the issues! Once again, thank you.
  6. Well, that's nVidia for you! Will roll back and see how I get on. Thanks for your help, appreciated!
  7. Hi Pete, Yes, I use nVidia's "Surround" mode via 3 screens. Crash Log: Log Name: Application Source: Application Hang Date: 29/08/2012 10:38:35 Event ID: 1002 Task Category: (101) Level: Error Keywords: Classic User: N/A Computer: Matt-PC Description: The program fsx.exe version 10.0.61637.0 stopped interacting with Windows and was closed. To see if more information about the problem is available, check the problem history in the Action Center control panel. Process ID: e3c Start Time: 01cd85c9ee389a4e Termination Time: 5 Application Path: E:\FSX\fsx.exe Report Id: 4c6f74b2-f1bd-11e1-bb7e-c86000ca489f Event Xml: <Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event"> <System> <Provider Name="Application Hang" /> <EventID Qualifiers="0">1002</EventID> <Level>2</Level> <Task>101</Task> <Keywords>0x80000000000000</Keywords> <TimeCreated SystemTime="2012-08-29T09:38:35.000000000Z" /> <EventRecordID>2259</EventRecordID> <Channel>Application</Channel> <Computer>Matt-PC</Computer> <Security /> </System> <EventData> <Data>fsx.exe</Data> <Data>10.0.61637.0</Data> <Data>e3c</Data> <Data>01cd85c9ee389a4e</Data> <Data>5</Data> <Data>E:\FSX\fsx.exe</Data> <Data>4c6f74b2-f1bd-11e1-bb7e-c86000ca489f</Data> <Binary>430072006F00730073002D00740068007200650061006400000044006500610064006C006F0063006B0000000000</Binary> </EventData> </Event> [/CODE] [i][u][b]DLL.XML:[/b][/u][/i] [CODE] <?xml version="1.0" encoding="Windows-1252"?> <SimBase.Document Type="Launch" version="1,0"> <Descr>Launch</Descr> <Filename>dll.xml</Filename> <Disabled>False</Disabled> <Launch.ManualLoad>False</Launch.ManualLoad> <Launch.Addon> <Name>Addon Manager</Name> <Disabled>False</Disabled> <ManualLoad>False</ManualLoad> <Path>bglmanx.dll</Path> </Launch.Addon> <Launch.Addon> <Name>Object Placement Tool</Name> <Disabled>True</Disabled> <ManualLoad>False</ManualLoad> <Path>..\Microsoft Flight Simulator X SDK\SDK\Mission Creation Kit\object_placement.dll</Path> </Launch.Addon> <Launch.Addon> <Name>Traffic Toolbox</Name> <Disabled>True</Disabled> <ManualLoad>False</ManualLoad> <Path>..\Microsoft Flight Simulator X SDK\SDK\Environment Kit\Traffic Toolbox SDK raffictoolbox.dll</Path> </Launch.Addon> <Launch.Addon> <Name>Visual Effects Tool</Name> <Disabled>True</Disabled> <ManualLoad>False</ManualLoad> <Path>..\Microsoft Flight Simulator X SDK\SDK\Environment Kit\Special Effects SDK\visualfxtool.dll</Path> </Launch.Addon> <Launch.Addon> <Name>A2A Feel</Name> <Disabled>False</Disabled> <Path>Modules\A2A_Feel.dll</Path> <DllStartName>module_init</DllStartName> <DllStopName>module_deinit</DllStopName> </Launch.Addon> <Launch.Addon> <Name>AccuFeelMenu</Name> <Disabled>False</Disabled> <ManualLoad>False</ManualLoad> <Path>Modules\AccuFeelMenu.dll</Path> </Launch.Addon> <Launch.Addon> <Name>IvAp</Name> <Disabled>False</Disabled> <Path>D:\IvAp v2\ivap_fsx_bootstrap.dll</Path> <Commandline></Commandline> </Launch.Addon> <Launch.Addon> <Name>PMDG HUD interface</Name> <Disabled>False</Disabled> <Path>PMDG\DLLs\PMDG_HUD_interface.dll</Path> <DllStartName>module_init</DllStartName> <DllStopName>module_deinit</DllStopName> </Launch.Addon> <Launch.Addon> <Name>FSUIPC 4</Name> <Disabled>False</Disabled> <Path>Modules\FSUIPC4_Loader.dll</Path> </Launch.Addon> <Launch.Addon> <Name>FSCopilot</Name> <Disabled>False</Disabled> <Path>Modules\FSCopilot.dll</Path> </Launch.Addon> </SimBase.Document> [/CODE] [i][u][b]EXE.XML:[/b][/u][/i] [CODE] <?xml version="1.0" encoding="windows-1252"?> <SimBase.Document Type="Launch" version="1,0"> <Descr>Launch</Descr> <Filename>exe.xml</Filename> <Disabled>False</Disabled> <Launch.ManualLoad>False</Launch.ManualLoad> <Launch.Addon> <Name>Couatl</Name> <Disabled>False</Disabled> <ManualLoad>False</ManualLoad> <Path>fsdreamteam\couatl\couatl.exe</Path> </Launch.Addon> <Launch.Addon> <Name>Saitek DirectOutput RadioStack</Name> <Disabled>False</Disabled> <Path>C:\Program Files (x86)\Saitek\DirectOutput\SaiFlightSimX.exe</Path> <CommandLine>-run</CommandLine> </Launch.Addon> </SimBase.Document> [/CODE] Cheers.
  8. Hi Pete, Sorry I couldn't be more specific - It was very late/early! This is the said error (I also get it with the FSUIPC4_Loader.dll too): Yeah, It was the Trust error one (this one for clarity) There is no .LOG file, only an Install log file (in the Modules folder). I Installed XPlane 10, that was about it. I have deleted both .cfg to let it rebuild, still no luck. Cheers.
  9. Morning, I have the latest version of FSUIPC installed and have had no issues with it at all. I shut down my FSX after a flight to Italy last week, went to boot it up yesterday and just as in the FAQ of this forum, I got the "FSUIPC DLL: FS new universal IPC interface" error. Now, I did everything that was suggested and It worked, the FSUIPC_loader seemed to do the trick, or so I thought. I've just come back to boot FSX again, now it's giving me the same error but with the faulting module as the loader. I've done a repair of Acceleration pack, plus all the usual suggestions on this forum! Any further help would be appreciated, I'm going slightly crazy. Thanks.
×
×
  • Create New...

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.