Jump to content
The simFlight Network Forums

Recommended Posts

Posted

Hi

 

Pulling my hair out with this

 

If I load default aircraft and default airport - no issues

 

If I load default aircraft and any other airport - immediate crash

 

If I uninstall FSUIPC works fine

 

I get these two lines at end of log when it crashes

 

35680 Hook Error: can't find .1617821344 in SIM1.dll

35680 Hook Error: can't find .1617821344 in VISUALFX.dll

 

These two files are in the root P3d V3 folder albeit in lower case

 

I am using

 

windows 10  says windows 8 in FSUIPC log

Prepare3D V3.1   version 3.01.2.15831

FSUIPC 4.949h

 

********* FSUIPC4, Version 4.949h by Pete Dowson *********
Prepar3D.exe version = 3.1.2.15831
Reading options from "C:\Lockheed Martin\Prepar3D v3\Modules\FSUIPC4.ini"
Running inside Prepar3D v3 on Windows 8.0
Module base=60630000
User Name="xxxx xxxxxx"
User Addr="xxxx@xxxxxxxxxxxxxxxxx"
FSUIPC4 Key is provided
WIDEFS7 not user registered, or expired
     1610 System time = 08/03/2016 15:53:51
     1610 FLT path = "C:\Users\davyc\Documents\Prepar3D v3 Files\"
     1610 ------ Module Version Check ------
     1610        acontain.dll: 3.1.2.15831
     1610             api.dll: 3.1.2.15831
     1610        controls.dll: 3.1.2.15831
     1610      fs-traffic.dll: 3.1.2.15831
     1610             G3D.dll: 3.1.2.15831
     1610        language.dll: 3.1.2.15831
     1610            sim1.dll: 3.1.2.15831
     1610        visualfx.dll: 3.1.2.15831
     1610         weather.dll: 3.1.2.15831
     1610          window.dll: 3.1.2.15831
     1610 ----------------------------------
     1610 Trying C:\Lockheed Martin\Prepar3D v3\Modules\SimConnectP3D2.dll
     1610 Found it: trying to connect
     1610 FS path = "C:\Lockheed Martin\Prepar3D v3\"
     1797 ---------------------- Joystick Device Scan -----------------------
     1797 Product= Saitek Pro Flight Rudder Pedals
     1797    Manufacturer= Saitek
     1797    Vendor=06A3, Product=0763 (Version 1.1)
     1797    Serial Number= Saitek
     1797 Product= Saitek Pro Flight Yoke
     1797    Manufacturer= Saitek
     1797    Vendor=06A3, Product=0BAC (Version 3.4)
     1797    Serial Number= Saitek
     1797 -------------------------------------------------------------------
     1813 LogOptions=00000000 00000001
     1813 -------------------------------------------------------------------
     1813 ------ Setting the hooks and direct calls into the simulator ------
     1813 --- CONTROLS timer memory location obtained ok
     1813 --- SIM1 Frictions access gained
     1829 ASN active function link set
     1829 --- FS Controls Table located ok
     1829 --- Installed Mouse Macro hooks ok.
     1829 Wind smoothing may be by ASN, not FSUIPC, if it is running
     1829 Will switch smoothing action when ASN starts/stops
     1829 --- All links okay (except older global weather setting method)
     1829 -------------------------------------------------------------------
     1829 SimConnect_Open succeeded: waiting to check version okay
     1829 Trying to use SimConnect Prepar3D
     1829 Running in "Lockheed Martin® Prepar3D® v3", Version: 3.1.3.1 (SimConnect: 3.1.0.0)
     1829 Initialising SimConnect data requests now
     1829 FSUIPC Menu entry added
     1844 C:\Users\davyc\AppData\Local\Lockheed Martin\Prepar3D v3\Prepar3D_Default.fxml
     1844 C:\Lockheed Martin\Prepar3D v3\SimObjects\Airplanes\IRIS Raptor Driver\Raptor.air
    26672 System time = 08/03/2016 15:54:16, Simulator time = 08:00:01 (07:00Z)
    26672 Aircraft="F-22 Raptor - 525th Fighter Squadron"
    27688 Starting everything now ...
    27766 Ready for ASN WX radar
    35860 Hook Error: can't find .1617821344 in SIM1.dll
    35860 Hook Error: can't find .1617821344 in VISUALFX.dll

 

I have ASN and Aivlasoft EFB on another PC in LAN and working with SimConnect with no issues???

 

Any help appreciated.

 

Davy C

Posted

Hi

 

Pulling my hair out with this

 

If I load default aircraft and default airport - no issues

 

If I load default aircraft and any other airport - immediate crash

 

If I uninstall FSUIPC works fine

 

I get these two lines at end of log when it crashes

 

35680 Hook Error: can't find .1617821344 in SIM1.dll

35680 Hook Error: can't find .1617821344 in VISUALFX.dll

 

These two files are in the root P3d V3 folder albeit in lower case

 

Assuming it isn't a corrupted P3D install (which is usually the reason for hook errors), I can only think one of two things. Either your ASN is out of date, or the order of its entry in the DLL.XML file is wrong. It should come AFTER FSUIPC4's, apparently. Usually ASN warns you about that, corrects it automatically, and tells you to restart FS.

 

Pete

Posted

Pete

 

Appreciate your help.

 

I double checked but FSUIPC is higher up the DLL file than ASN.

 

ASN is just a new install and I haven't had it running on these tests as it is on another pc.

 

I changed the name of the two dll files SIM1 and Visualfx to .old files and ran the p3d repair function, which created new files - no difference. 

 

I have uninstalled and re-installed FSUIPC as this is the easy option.  I have noted that the crashes only happen when I select an airport in Europe.

 

I am reluctant to uninstall P3D as I have spent 3-4 weeks building up my software and systems on a new pc

 

I think the best option is to uninstall and re-install V3.2

 

Thanks again for your help it is appreciated.

 

DC

Posted

I have noted that the crashes only happen when I select an airport in Europe.

 

I think the best option is to uninstall and re-install V3.2

 

Yes, probably. But you might also want to check what scenery files you have which encompass Europe, or at least the airports you've tried and had this problem with. FSUIPC has no idea and does not care at all where your airport is, there is nothing in FSUIPC which is dependent in any way on location.

 

If it still happens after reinstalling 3.2 I would proceed on a series of eliminations of the assorted scenery layers you have added, starting with any which is handling an area inclding those airports, like a UTX or Orbx terrain or LandClass layer.

 

Pete

Posted

Hi

 

Still stumped

 

I have uninstalled v3.1 and installed v3.2 - same errors.

 

I have

 

EZDok

Orbx Global

Orbx Vectors

UK2000 Gatwick, Leeds and Cardiff

ASN

Virtual Avionics

 

I unloaded Ezdok - no change

I uninstalled Orbx no

I uninstalled UK2000 no change

I uninstall ASN

 

I changed the dll.xml file no change

I deleted cfg files and rebuilt - no change

 

I have found that the FSUIPC does not appear in the menu unless the loader dll file is in the modules folder

 

I think it is a sim connect issue.

 

I have P3D sim connect 3.2

and 4 versions of Microsoft installed including a Microsoft ESP ver 1.xxxx  I have tried different settings with these present and missing but no change

 

When the loader dll file is not in the modules folder no crashing but no FSUIPC

 

The airports are very hit and miss but does not like any UK airport default or otherwise.

 

Going to bed spent 8 hours plus today at this - head swimming it will be something simple I hope when I get home from work tomorrow.

 

Thanks

 

DC

Posted

I have found that the FSUIPC does not appear in the menu unless the loader dll file is in the modules folder

 

Hmm, that's a pretty serious problem. The loader should never be needed. It's a last desperate attempt to get around some timing compatibility problems with other SimConnect loading DLLs or EXEs.

 

Is this also true when there is nothing else loading in the DLL.XML, and no EXE.XML? Have you tried that? If not, please do and let me know. Try it without the Loader. Easiest way to do this test is rename the EXE.DLL and DLL.XML and remove the loader from the Modules folder, then re-run the FSUIPC installer. No need to reregister, that won't get lost.

 

I think it is a sim connect issue.

I have P3D sim connect 3.2

and 4 versions of Microsoft installed including a Microsoft ESP ver 1.xxxx  I have tried different settings with these present and missing but no change

 

 

The different SimConnect DLLs are just interfaces with differing  functions translated into calls to the real functions which are within the main code in P3D. It doesn't matter which one gets used, it just may affect the facilities available if it's an old one. FSUIPC only uses a subset in any case, and its subset are translated by the SimConnectP3D2.DLL which gets installed in your Modules folder.

 

Looking back at the Log you posted earlier, you'll see this line:

 

 1829 Running in "Lockheed Martin® Prepar3D® v3", Version: 3.1.3.1 (SimConnect: 3.1.0.0)

 

The SimConnect version shown is always the one being used -- the information in this line is that returned by the call to SimConnect to open the link.

 

The airports are very hit and miss but does not like any UK airport default or otherwise.

 

That is extremely odd. There is no way FSUIPC is involved in that. It seems something which provides data for the whole of the UK is corrupt -- maybe some of the base files being loaded via the SCENERY.CFG file?

 

Pete

Posted

Pete

 

Sorry I deleted and uninstalled everything.  Added a new SSD drive and installed everything onto it.  Works a treat now.. so don't know what caused the problem.

 

I have discovered that soon before this started to happen I installed one of my old UK2000 airport scenery and used an FSX version by mistake.  This created an entry in the registry that pointed FSX to the PSD v3 folder, I never had FSX on this pc - I really have no idea if that caused the problem but it is gone in any case...

 

Once again thanks for taking the time to answer my problems

 

Davy C

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
×
×
  • 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.