Jump to content
The simFlight Network Forums
wlix261

Crash Loading P3Dvhttp://forum.simflight.com/topic/82599-crash-loading-p3dv34-reporte-fsuipc4dll/3.4 reporte FSUIPC4.dll

Recommended Posts

Hello, I use W10, P3D version 3.4.14.and  FSUIPC Version 4.95

I am having crash when trying to load P3Dv3.4, and I get a windows crash report that lists the fault module name as FSUIPC4.dll.

I was asked to ask here in the FSUIPC support forum for help.

Thanks in advance

regards

Alvaro Escorcia

======================

Version=1
EventType=APPCRASH
EventTime=131270548622828061
ReportType=2
Consent=1
UploadTime=131270548623687519
ReportIdentifier=91c8cece-c9d1-11e6-a988-d8cb8a5ad4fb
IntegratorReportIdentifier=91c8cecd-c9d1-11e6-a988-d8cb8a5ad4fb
WOW64=1
AppSessionGuid=00000bb0-0001-0039-0b2b-954dde5dd201
TargetAppId=W:0000da39a3ee5e6b4b0d3255bfef95601890afd80709!0000da39a3ee5e6b4b0d3255bfef95601890afd80709!Prepar3D.exe
TargetAppVer=2016//10//27:17:31:14!6cc50!Prepar3D.exe
BootId=4294967295
Response.BucketId=a8a1b4db5c4504c465b2e4a7a87ac757
Response.BucketTable=1
Response.LegacyBucketId=108646897907
Response.type=4
Sig[0].Name=Application Name
Sig[0].Value=Prepar3D.exe
Sig[1].Name=Application Version
Sig[1].Value=3.4.14.18870
Sig[2].Name=Application Timestamp
Sig[2].Value=581239e2
Sig[3].Name=Fault Module Name
Sig[3].Value=FSUIPC4.dll
Sig[4].Name=Fault Module Version
Sig[4].Value=4.9.5.8
Sig[5].Name=Fault Module Timestamp
Sig[5].Value=5857240f
Sig[6].Name=Exception Code
Sig[6].Value=c0000005
Sig[7].Name=Exception Offset
Sig[7].Value=0001f044
DynamicSig[1].Name=OS Version
DynamicSig[1].Value=10.0.14393.2.0.0.256.48
DynamicSig[2].Name=Locale ID
DynamicSig[2].Value=1033
UI[2]=C:\Prepar3Dv3\Prepar3D.exe
UI[3]=A fatal error occurred.
UI[4]=Windows can check online for a solution to the problem.
UI[5]=Check online for a solution and close the program
UI[6]=Check online for a solution later and close the program
UI[7]=Close the program
LoadedModule[0]=C:\Prepar3Dv3\Prepar3D.exe
LoadedModule[1]=C:\WINDOWS\SYSTEM32\ntdll.dll
LoadedModule[2]=C:\WINDOWS\System32\KERNEL32.DLL
LoadedModule[3]=C:\WINDOWS\System32\KERNELBASE.dll
LoadedModule[4]=C:\Program Files (x86)\AVG\Av\avghookx.dll
LoadedModule[5]=C:\WINDOWS\system32\apphelp.dll
LoadedModule[6]=C:\WINDOWS\AppPatch\AcGenral.DLL
LoadedModule[7]=C:\WINDOWS\System32\msvcrt.dll
LoadedModule[8]=C:\WINDOWS\System32\sechost.dll
LoadedModule[9]=C:\WINDOWS\System32\RPCRT4.dll
LoadedModule[10]=C:\WINDOWS\System32\SspiCli.dll
LoadedModule[11]=C:\WINDOWS\System32\CRYPTBASE.dll
LoadedModule[12]=C:\WINDOWS\System32\bcryptPrimitives.dll
LoadedModule[13]=C:\WINDOWS\System32\SHLWAPI.dll
LoadedModule[14]=C:\WINDOWS\System32\combase.dll
LoadedModule[15]=C:\WINDOWS\System32\ucrtbase.dll
LoadedModule[16]=C:\WINDOWS\System32\GDI32.dll
LoadedModule[17]=C:\WINDOWS\System32\gdi32full.dll
LoadedModule[18]=C:\WINDOWS\System32\USER32.dll
LoadedModule[19]=C:\WINDOWS\System32\win32u.dll
LoadedModule[20]=C:\WINDOWS\System32\ole32.dll
LoadedModule[21]=C:\WINDOWS\System32\OLEAUT32.dll
LoadedModule[22]=C:\WINDOWS\System32\msvcp_win.dll
LoadedModule[23]=C:\WINDOWS\System32\SHELL32.dll
LoadedModule[24]=C:\WINDOWS\System32\cfgmgr32.dll
LoadedModule[25]=C:\WINDOWS\System32\windows.storage.dll
LoadedModule[26]=C:\WINDOWS\System32\powrprof.dll
LoadedModule[27]=C:\WINDOWS\System32\advapi32.dll
LoadedModule[28]=C:\WINDOWS\System32\kernel.appcore.dll
LoadedModule[29]=C:\WINDOWS\System32\shcore.dll
LoadedModule[30]=C:\WINDOWS\System32\profapi.dll
LoadedModule[31]=C:\WINDOWS\SYSTEM32\UxTheme.dll
LoadedModule[32]=C:\WINDOWS\SYSTEM32\WINMM.dll
LoadedModule[33]=C:\WINDOWS\SYSTEM32\samcli.dll
LoadedModule[34]=C:\WINDOWS\SYSTEM32\MSACM32.dll
LoadedModule[35]=C:\WINDOWS\SYSTEM32\VERSION.dll
LoadedModule[36]=C:\WINDOWS\SYSTEM32\USERENV.dll
LoadedModule[37]=C:\WINDOWS\SYSTEM32\dwmapi.dll
LoadedModule[38]=C:\WINDOWS\SYSTEM32\urlmon.dll
LoadedModule[39]=C:\WINDOWS\SYSTEM32\WINSPOOL.DRV
LoadedModule[40]=C:\WINDOWS\SYSTEM32\MPR.dll
LoadedModule[41]=C:\WINDOWS\SYSTEM32\WINMMBASE.dll
LoadedModule[42]=C:\WINDOWS\SYSTEM32\iertutil.dll
LoadedModule[43]=C:\WINDOWS\SYSTEM32\bcrypt.dll
LoadedModule[44]=C:\WINDOWS\System32\IMM32.DLL
LoadedModule[45]=C:\Prepar3Dv3\api.dll
LoadedModule[46]=C:\WINDOWS\System32\WS2_32.dll
LoadedModule[47]=C:\WINDOWS\System32\CRYPT32.dll
LoadedModule[48]=C:\WINDOWS\System32\MSASN1.dll
LoadedModule[49]=C:\WINDOWS\SYSTEM32\MSVCP120.dll
LoadedModule[50]=C:\WINDOWS\SYSTEM32\MSVCR120.dll
LoadedModule[51]=C:\WINDOWS\SYSTEM32\Cabinet.dll
LoadedModule[52]=C:\WINDOWS\SYSTEM32\MSWSOCK.dll
LoadedModule[53]=C:\WINDOWS\SYSTEM32\WINHTTP.dll
LoadedModule[54]=C:\WINDOWS\WinSxS\x86_microsoft.windows.common-controls_6595b64144ccf1df_5.82.14393.447_none_5507ded2cb4f7f4c\COMCTL32.dll
LoadedModule[55]=C:\Prepar3Dv3\acontain.dll
LoadedModule[56]=C:\Prepar3Dv3\ai_player.dll
LoadedModule[57]=C:\Prepar3Dv3\atc.dll
LoadedModule[58]=C:\Prepar3Dv3\controls.dll
LoadedModule[59]=C:\WINDOWS\System32\SETUPAPI.dll
LoadedModule[60]=C:\Prepar3Dv3\demo.dll
LoadedModule[61]=C:\Prepar3Dv3\DIS.dll
LoadedModule[62]=C:\Prepar3Dv3\facilities.dll
LoadedModule[63]=C:\Prepar3Dv3\fe.dll
LoadedModule[64]=C:\Prepar3Dv3\flight.dll
LoadedModule[65]=C:\Prepar3Dv3\fs-traffic.dll
LoadedModule[66]=C:\Prepar3Dv3\g2d.dll
LoadedModule[67]=C:\WINDOWS\System32\WLDAP32.dll
LoadedModule[68]=C:\Prepar3Dv3\g3d.dll
LoadedModule[69]=C:\Prepar3Dv3\gps.dll
LoadedModule[70]=C:\Prepar3Dv3\livingwater.dll
LoadedModule[71]=C:\Prepar3Dv3\main.dll
LoadedModule[72]=C:\WINDOWS\System32\COMDLG32.dll
LoadedModule[73]=C:\Prepar3Dv3\menus.dll
LoadedModule[74]=C:\Prepar3Dv3\multiplayer.dll
LoadedModule[75]=C:\Prepar3Dv3\pdk.dll
LoadedModule[76]=C:\Prepar3Dv3\panels.dll
LoadedModule[77]=C:\Prepar3Dv3\sim1.dll
LoadedModule[78]=C:\Prepar3Dv3\simscheduler.dll
LoadedModule[79]=C:\Prepar3Dv3\simprop.dll
LoadedModule[80]=C:\Prepar3Dv3\sound.dll
LoadedModule[81]=C:\Prepar3Dv3\symmap.dll
LoadedModule[82]=C:\Prepar3Dv3\terrain.dll
LoadedModule[83]=C:\Prepar3Dv3\util.dll
LoadedModule[84]=C:\Prepar3Dv3\visualfx.dll
LoadedModule[85]=C:\Prepar3Dv3\weather.dll
LoadedModule[86]=C:\Prepar3Dv3\window.dll
LoadedModule[87]=C:\WINDOWS\SYSTEM32\HID.DLL
LoadedModule[88]=C:\WINDOWS\SYSTEM32\DINPUT8.dll
LoadedModule[89]=C:\Prepar3Dv3\mplEasyBlendSDKDX11.dll
LoadedModule[90]=C:\WINDOWS\SYSTEM32\MFReadWrite.dll
LoadedModule[91]=C:\WINDOWS\SYSTEM32\MFPlat.DLL
LoadedModule[92]=C:\WINDOWS\SYSTEM32\dxgi.dll
LoadedModule[93]=C:\WINDOWS\SYSTEM32\d3d9.dll
LoadedModule[94]=C:\WINDOWS\SYSTEM32\d3d11.dll
LoadedModule[95]=C:\Prepar3Dv3\D3DCOMPILER_47.dll
LoadedModule[96]=C:\WINDOWS\SYSTEM32\OPENGL32.dll
LoadedModule[97]=C:\WINDOWS\SYSTEM32\GLU32.dll
LoadedModule[98]=C:\WINDOWS\SYSTEM32\d3dx9_43.dll
LoadedModule[99]=C:\WINDOWS\SYSTEM32\d3dx11_43.dll
LoadedModule[100]=C:\Prepar3Dv3\d3dcsx_47.dll
LoadedModule[101]=C:\WINDOWS\SYSTEM32\DSOUND.dll
LoadedModule[102]=C:\Prepar3Dv3\audiere.dll
LoadedModule[103]=C:\WINDOWS\SYSTEM32\D3DCOMPILER_43.dll
LoadedModule[104]=C:\WINDOWS\SYSTEM32\DDRAW.dll
LoadedModule[105]=C:\WINDOWS\SYSTEM32\DCIMAN32.dll
LoadedModule[106]=C:\WINDOWS\SYSTEM32\RTWorkQ.DLL
LoadedModule[107]=C:\Prepar3Dv3\language.dll
LoadedModule[108]=C:\WINDOWS\SYSTEM32\MSXML6.DLL
LoadedModule[109]=C:\WINDOWS\SYSTEM32\ntmarta.dll
LoadedModule[110]=C:\Prepar3Dv3\uiInterface.dll
LoadedModule[111]=C:\WINDOWS\SYSTEM32\mscoree.dll
LoadedModule[112]=C:\Windows\Microsoft.NET\Framework\v4.0.30319\mscoreei.dll
LoadedModule[113]=C:\Windows\Microsoft.NET\Framework\v4.0.30319\clr.dll
LoadedModule[114]=C:\WINDOWS\SYSTEM32\MSVCR120_CLR0400.dll
LoadedModule[115]=C:\WINDOWS\assembly\NativeImages_v4.0.30319_32\mscorlib\40571abae9422cd2ca6fafbbde1c3cdc\mscorlib.ni.dll
LoadedModule[116]=C:\Windows\Microsoft.NET\Framework\v4.0.30319\clrjit.dll
LoadedModule[117]=C:\WINDOWS\assembly\NativeImages_v4.0.30319_32\System\08da6b6698b412866e6910ae9b84f363\System.ni.dll
LoadedModule[118]=C:\WINDOWS\assembly\NativeImages_v4.0.30319_32\PresentationCore\051a282e157a228405b2e0d867c3ce1d\PresentationCore.ni.dll
LoadedModule[119]=C:\WINDOWS\SYSTEM32\CRYPTSP.dll
LoadedModule[120]=C:\WINDOWS\system32\rsaenh.dll
LoadedModule[121]=C:\WINDOWS\assembly\NativeImages_v4.0.30319_32\Presentatio5ae0f00f#\5272cb4aeec65bec2fffb45e9cb22910\PresentationFramework.ni.dll
LoadedModule[122]=C:\WINDOWS\assembly\NativeImages_v4.0.30319_32\System.Core\f6ebd52be27fe627fed0d185c6a9c0d5\System.Core.ni.dll
LoadedModule[123]=C:\WINDOWS\assembly\NativeImages_v4.0.30319_32\WindowsBase\5751e969e4789e60d3ad463cb6024006\WindowsBase.ni.dll
LoadedModule[124]=C:\WINDOWS\assembly\NativeImages_v4.0.30319_32\System.Xaml\04c4f83e0b62ff553abff98943e45f42\System.Xaml.ni.dll
LoadedModule[125]=C:\WINDOWS\SYSTEM32\dwrite.dll
LoadedModule[126]=C:\Windows\Microsoft.NET\Framework\v4.0.30319\WPF\wpfgfx_v0400.dll
LoadedModule[127]=C:\Windows\Microsoft.NET\Framework\v4.0.30319\WPF\PresentationNative_v0400.dll
LoadedModule[128]=C:\WINDOWS\SYSTEM32\PROPSYS.dll
LoadedModule[129]=C:\WINDOWS\SYSTEM32\iphlpapi.dll
LoadedModule[130]=C:\WINDOWS\System32\NSI.dll
LoadedModule[131]=C:\WINDOWS\SYSTEM32\dhcpcsvc6.DLL
LoadedModule[132]=C:\WINDOWS\SYSTEM32\dhcpcsvc.DLL
LoadedModule[133]=C:\WINDOWS\SYSTEM32\ondemandconnroutehelper.dll
LoadedModule[134]=C:\WINDOWS\System32\MSCTF.dll
LoadedModule[135]=C:\WINDOWS\SYSTEM32\secur32.dll
LoadedModule[136]=C:\WINDOWS\SYSTEM32\DNSAPI.dll
LoadedModule[137]=C:\WINDOWS\System32\fwpuclnt.dll
LoadedModule[138]=C:\Windows\System32\rasadhlp.dll
LoadedModule[139]=C:\WINDOWS\system32\nvapi.dll
LoadedModule[140]=C:\WINDOWS\System32\DriverStore\FileRepository\nv_dispiwu.inf_amd64_9ff5ab165faead52\nvwgf2um.dll
LoadedModule[141]=C:\WINDOWS\SYSTEM32\DEVOBJ.dll
LoadedModule[142]=C:\WINDOWS\System32\WINTRUST.dll
LoadedModule[143]=C:\WINDOWS\SYSTEM32\WTSAPI32.DLL
LoadedModule[144]=C:\WINDOWS\SYSTEM32\WINSTA.dll
LoadedModule[145]=C:\WINDOWS\System32\clbcatq.dll
LoadedModule[146]=C:\WINDOWS\system32\ntshrui.dll
LoadedModule[147]=C:\WINDOWS\system32\srvcli.dll
LoadedModule[148]=C:\WINDOWS\SYSTEM32\cscapi.dll
LoadedModule[149]=C:\WINDOWS\WinSxS\x86_microsoft.windows.common-controls_6595b64144ccf1df_6.0.14393.447_none_89c64d28dafea4b9\comctl32.dll
LoadedModule[150]=C:\WINDOWS\system32\netutils.dll
LoadedModule[151]=C:\WINDOWS\System32\coml2.dll
LoadedModule[152]=C:\WINDOWS\system32\mssprxy.dll
LoadedModule[153]=C:\WINDOWS\SYSTEM32\LINKINFO.dll
LoadedModule[154]=C:\WINDOWS\System32\MMDevApi.dll
LoadedModule[155]=C:\WINDOWS\SYSTEM32\AUDIOSES.DLL
LoadedModule[156]=C:\WINDOWS\SYSTEM32\wintypes.dll
LoadedModule[157]=C:\WINDOWS\SYSTEM32\avrt.dll
LoadedModule[158]=C:\WINDOWS\SYSTEM32\XInput9_1_0.dll
LoadedModule[159]=C:\WINDOWS\assembly\NativeImages_v4.0.30319_32\Presentatioaec034ca#\def8702c6e883330fb8cb8e3f5c5e665\PresentationFramework.Aero2.ni.dll
LoadedModule[160]=C:\WINDOWS\SYSTEM32\WindowsCodecs.dll
LoadedModule[161]=C:\WINDOWS\System32\DriverStore\FileRepository\nv_dispiwu.inf_amd64_9ff5ab165faead52\nvd3dum.dll
LoadedModule[162]=C:\WINDOWS\assembly\NativeImages_v4.0.30319_32\System.Drawing\c2abcda8f96d67fa6ff5665fd21dddff\System.Drawing.ni.dll
LoadedModule[163]=C:\WINDOWS\assembly\NativeImages_v4.0.30319_32\System.Windows.Forms\c02fbf560e52a1aab432a90d4c613af4\System.Windows.Forms.ni.dll
LoadedModule[164]=C:\WINDOWS\SYSTEM32\wdmaud.drv
LoadedModule[165]=C:\WINDOWS\SYSTEM32\ksuser.dll
LoadedModule[166]=C:\WINDOWS\SYSTEM32\msacm32.drv
LoadedModule[167]=C:\WINDOWS\SYSTEM32\midimap.dll
LoadedModule[168]=C:\Prepar3Dv3\radar.dll
LoadedModule[169]=C:\Prepar3Dv3\VirtualReality.dll
LoadedModule[170]=C:\Prepar3Dv3\openvr_api.dll
LoadedModule[171]=C:\Prepar3Dv3\ControllableCamera.dll
LoadedModule[172]=C:\Prepar3Dv3\SimDirector.dll
LoadedModule[173]=C:\Prepar3Dv3\BGLCompLib.dll
LoadedModule[174]=C:\Prepar3Dv3\simpropext.dll
LoadedModule[175]=C:\Prepar3Dv3\PMDG\DLLs\PMDG_HUD_interface.dll
LoadedModule[176]=C:\WINDOWS\WinSxS\x86_microsoft.flightsimulator.simconnect_67c7c14424d61b5b_10.0.61259.0_none_55f5ecdc14f60568\SimConnect.dll
LoadedModule[177]=C:\WINDOWS\SYSTEM32\MSVCR100.dll
LoadedModule[178]=C:\WINDOWS\WinSxS\x86_microsoft.vc80.crt_1fc8b3b9a1e18e3b_8.0.50727.9268_none_d08e1538442a243e\MSVCR80.dll
LoadedModule[179]=C:\WINDOWS\WinSxS\x86_microsoft.vc80.crt_1fc8b3b9a1e18e3b_8.0.50727.9268_none_d08e1538442a243e\MSVCP80.dll
LoadedModule[180]=C:\WINDOWS\SYSTEM32\SHFOLDER.dll
LoadedModule[181]=C:\Prepar3Dv3\PMDG\DLLs\PMDG_Interface.dll
LoadedModule[182]=C:\Prepar3Dv3\RAASPRO\RAASPRO.dll
LoadedModule[183]=C:\WINDOWS\SYSTEM32\WININET.dll
LoadedModule[184]=C:\WINDOWS\SYSTEM32\WINNSI.DLL
LoadedModule[185]=C:\Program Files (x86)\Common Files\System\ado\msado15.dll
LoadedModule[186]=C:\WINDOWS\SYSTEM32\MSDART.DLL
LoadedModule[187]=C:\Program Files (x86)\Common Files\System\Ole DB\oledb32.dll
LoadedModule[188]=C:\WINDOWS\SYSTEM32\DPAPI.dll
LoadedModule[189]=C:\Windows\System32\comsvcs.dll
LoadedModule[190]=C:\Windows\System32\msjetoledb40.dll
LoadedModule[191]=C:\Windows\System32\msjet40.dll
LoadedModule[192]=C:\Windows\System32\msjter40.dll
LoadedModule[193]=C:\Windows\System32\mswstr10.dll
LoadedModule[194]=C:\Windows\System32\MSJINT40.DLL
LoadedModule[195]=C:\Windows\System32\mstext40.dll
LoadedModule[196]=C:\WINDOWS\SYSTEM32\mlang.dll
LoadedModule[197]=C:\WINDOWS\SYSTEM32\RAASAUDIO32.DLL
LoadedModule[198]=C:\WINDOWS\SYSTEM32\X3DAudio1_6.dll
LoadedModule[199]=C:\WINDOWS\System32\xactengine3_4.dll
LoadedModule[200]=C:\WINDOWS\System32\XAudio2_4.dll
LoadedModule[201]=C:\Prepar3Dv3\Gauges\TargetInfo.dll
LoadedModule[202]=C:\Prepar3Dv3\Gauges\Fury_1500.dll
LoadedModule[203]=C:\Prepar3Dv3\Modules\FSX-JoinD.dll
LoadedModule[204]=C:\WINDOWS\SYSTEM32\mfc100.dll
LoadedModule[205]=C:\WINDOWS\SYSTEM32\MSIMG32.dll
LoadedModule[206]=C:\WINDOWS\SYSTEM32\MFC100ENU.DLL
LoadedModule[207]=C:\Program Files\IvAp v2\ivap_fsx_bootstrap.dll
LoadedModule[208]=C:\WINDOWS\System32\PSAPI.DLL
LoadedModule[209]=C:\WINDOWS\SYSTEM32\MSVCP100.dll
LoadedModule[210]=C:\WINDOWS\assembly\NativeImages_v4.0.30319_32\System.Configuration\aa9c29b70b4cceab890eb841f89d73e9\System.Configuration.ni.dll
LoadedModule[211]=C:\WINDOWS\assembly\NativeImages_v4.0.30319_32\System.Xml\7532301b00fac8def2f526ca8b480e11\System.Xml.ni.dll
LoadedModule[212]=C:\WINDOWS\system32\dataexchange.dll
LoadedModule[213]=C:\WINDOWS\system32\dcomp.dll
LoadedModule[214]=C:\WINDOWS\system32\twinapi.appcore.dll
LoadedModule[215]=C:\WINDOWS\system32\msctfui.dll
LoadedModule[216]=C:\WINDOWS\assembly\NativeImages_v4.0.30319_32\UIAutomationTypes\75ed56cf95fe6228472b5e57ac7a76b7\UIAutomationTypes.ni.dll
LoadedModule[217]=C:\WINDOWS\SYSTEM32\UIAutomationCore.dll
LoadedModule[218]=C:\WINDOWS\SYSTEM32\sxs.dll
LoadedModule[219]=C:\WINDOWS\assembly\NativeImages_v4.0.30319_32\System.Runteb92aa12#\213003369298faf75651a6b8981dce12\System.Runtime.Serialization.ni.dll
LoadedModule[220]=C:\WINDOWS\assembly\NativeImages_v4.0.30319_32\SMDiagnostics\1b144b0155aa14719ac0b83f038abbd5\SMDiagnostics.ni.dll
LoadedModule[221]=C:\WINDOWS\assembly\NativeImages_v4.0.30319_32\System.Servd1dec626#\d842ac6dc0b94d7516b2d43a62b8f4d7\System.ServiceModel.Internals.ni.dll
LoadedModule[222]=C:\WINDOWS\WinSxS\x86_microsoft.windows.gdiplus_6595b64144ccf1df_1.1.14393.321_none_baab3cb4359688b4\gdiplus.dll
LoadedModule[223]=C:\Prepar3Dv3\Carenavigraph.dll
LoadedModule[224]=C:\Prepar3Dv3\Modules\FSUIPC4.dll
State[0].Key=Transport.DoneStage1
State[0].Value=1
FriendlyEventName=Stopped working
ConsentKey=APPCRASH
AppName=Lockheed Martin® Prepar3D®
AppPath=C:\Prepar3Dv3\Prepar3D.exe
ApplicationIdentity=00000000000000000000000000000000
MetadataHash=1432479682

Share this post


Link to post
Share on other sites

Hi,

FSUIPC will not be the faulty module. It is only listed because it runs within the P3D process, like any other P3d module (DLL) is listed of course.

Most likely it is a corrupt weather file problem or the weather station file itself that is corrupt and forces a crash as soon it is loaded. That this happens with FSUIPC depends on that FSUIPC forces P3D (or FSX) to load the weather. It is only happening when FSUIPC is present because it still causes SimConnect to read the weather.

You can try deleting the wxstationlist.bin and the .WX files? That's fixed such problems in the past.

To stop that entirely you'd need to set "NoWeatherAtAll=Yes".

Thomas

Share this post


Link to post
Share on other sites

I have the same problem: The latest version of P3D 3.4 together with the latest (registered) version of FSUIPC will result in the simulator not getting to the initial screen where you can elect vehicles, flight plans etc. Here are a few more details.

- I have added ManualLoad = True to the dll.xml file. P3D 3.4 works fine if I do not load FSUIPC, but it normally (not always) "crashes" if I do.

- P3D is not really closing. It is still visible in the Windows Task manager and draws significant system resources (CPU load about 25%). I have to stop P3D manually there.

- A fresh install of FSUIPC using the latest installer usually helps for the first 1-2 runs. After that, P3D fails to launch again.

- Here is my Windows event viewer log:

Faulting application name: Prepar3D.exe, version: 3.4.18.19475, time stamp: 0x5851bfd2
Faulting module name: FSUIPC4.dll_unloaded, version: 4.9.5.8, time stamp: 0x5857240f
Exception code: 0xc0000005
Fault offset: 0x00067797
Faulting process id: 0x3168
Faulting application start time: 0x01d25ef2fd44e6d1
Faulting application path: D:\P3D-3.0\Prepar3D.exe
Faulting module path: FSUIPC4.dll
Report Id: 457a7181-a525-44aa-941d-d2f3059eefa0
Faulting package full name: 
Faulting package-relative application ID: 

- You may notice that it states version 4.9.5.8, and this may be at the heart of the problem. I have re-downloaded the 4.9.5.9 installer multiple times, and it does contain the list of 4.9.5.9 changes. However, it appears to install version 4.9.5.8 of FSUIPC.dll

Thanks and best regards,

Peter

 

Share this post


Link to post
Share on other sites

Hi,

it is always the FSUIPC log file needed to see how far or what FSUIPC logs, always copy and paste the full content of the log file to your message.

@qquertz: When you successfully installed latest FSUIPC4 the log will show the installed version, here:

********* FSUIPC4, Version 4.959 (19th December 2016) by Pete Dowson *********

The DLL version No. seems to be not updated in the latest version 4.959 and show still 4.958.

Did you try the above suggestion, here more detailed?

Most likely it is a corrupt weather file problem or the weather station file itself that is corrupt and forces a crash as soon it is loaded.
It is only happening when FSUIPC is present because it still causes SimConnect to read the weather.
You can try deleting the wxstationlist.bin and the .WX files? That's fixed such problems in the past.
For FSX the wxstationlist.bin file you will find under:
C:\Users\TSR\AppData\Roaming\Microsoft\FSX\

For P3Dv3 the wxstationlist.bin file you will find under:
C:\Users\YourLogin\AppData\Roaming\Lockheed Martin\Prepar3D v3\

The .wx file of the flight that currently is loaded is located in your saved flights folder,
i.e. C:\Users\TSR\Documents\Prepar3D v3 Files\
To stop that entirely you'd need to set/add "NoWeatherAtAll=Yes" in/to FSUIPC4.ini file.

Thomas

 

Share this post


Link to post
Share on other sites

Thomas

Thank you for the advice.

I found the instances you refer to for the .WX files and for the wxstationlist.bin file which I deleted. I also added the line "NoWeatherAtAll=Yes" to the FSUIPC.ini file.

I did that having P3D open. I then closed it , opened it again and It loaded OK. I hope this stays like this and I can close/open P3D at my will without having the crashes.

 ===> Update: Yet P3D crashed again. The fix worked for 1 time only. After crash I checked the FSUIPC.ini file still with the new line, and the wxstationlist.bin back where it was before, as well as 1 .wx file (the previous file one).

Another observation: having deleted the .bin and .wx files did not get P3D back to be able to start. Really the only way I get P3D back to start is by re-running the Install FSUIPC4.exe (it finds the installation and I tell him to use existing registration. So it really doesn't seem to install anything, but perhaps cleans up or re-initiate something that makes P3D to load OK the next time I rune it.... I can use P3D OK ...but P3D still reports an error when closing and goes back to not load, and the cycle starts again).

By the way, can you tell me if having added the line to the FSUIPC.ini file will prevent using my external weather engine = AS2016?

Thanks and regards

Alvaro Escorcia

 

Edited by wlix261
Updated test

Share this post


Link to post
Share on other sites

Hi,

the flight-plan .WX gets sometimes corrupt and forces FS to crash while loading a flight, i.e. on FS start-up.

The wxstationlist.bin gets updated when loading real-weather and can get corrupt when loading over the internet, but it will be recreated by FS (or P3D) when it doesn't exist on start-up. So by deleting it makes sure you will get a fresh default one.

The added line in FSUIPC INI "NoWeatherAtAll=Yes":

14. A diagnostic facility to make FSUIPC avoid all weather reading and writing activities has been added. This is invoked by adding “NoWeatherAtAll=Yes” to the [General] section of the FSUIPC4.INI file.

That means FSUIPC doesn't care about the weather, so it will not read or manipulate, like wind smoothing  ..., the FS weather. What external programs like ASN... writes into FS(P3D) is not effected because it is not written via FSUIPC, they use SimConnect direct.

Thomas

Share this post


Link to post
Share on other sites
9 minutes ago, wlix261 said:

I have updated this post

And here is the content of the FSUIPC4 log file

********* FSUIPC4, Version 4.959 (19th December 2016) by Pete Dowson *********
Windows version reported as 6.2.?.9200
Prepar3D.exe version = 3.4.14.18870
Reading options from "C:\Prepar3Dv3\Modules\FSUIPC4.ini"
Running inside Prepar3D v3 on Windows 8.0 or later
Module base=52240000
User Name="Alvaro Escorcia"
User Addr="aescorcia@comcast.net"
FSUIPC4 Key is provided
WIDEFS7 not user registered, or expired
       32 System time = 26/12/2016 06:55:00
       32 FLT path = "C:\Users\ESCORCIAW10\Documents\Prepar3D v3 Files\"
       32 NOTE: configuring for no weather reads or writes!
       32 ------ Module Version Check ------
       32        acontain.dll: 3.4.14.18870
       32             api.dll: 3.4.14.18870
       32        controls.dll: 3.4.14.18870
       32      fs-traffic.dll: 3.4.14.18870
       32             G3D.dll: 3.4.14.18870
       32        language.dll: 3.4.14.18870
       32            sim1.dll: 3.4.14.18870
       32        visualfx.dll: 3.4.14.18870
       32          window.dll: 3.4.14.18870
       32 ----------------------------------
       32 Trying C:\Prepar3Dv3\Modules\SimConnectP3D3.dll
       63 Found it: trying to connect
       78 FS path = "C:\Prepar3Dv3\"
      203 ---------------------- Joystick Device Scan -----------------------
      203 Product= Saitek Pro Flight Rudder Pedals
      203    Manufacturer= Saitek
      203    Vendor=06A3, Product=0763 (Version 1.1)
      203    Serial Number= Saitek
      203 Product= Saitek Pro Flight Yoke
      203    Manufacturer= Saitek
      203    Vendor=06A3, Product=0BAC (Version 3.2)
      203    Serial Number= Saitek
      203 -------------------------------------------------------------------
      235 LogOptions=00000000 00000001
      235 -------------------------------------------------------------------
      235 ------ Setting the hooks and direct calls into the simulator ------
      235 --- CONTROLS timer memory location obtained ok
      235 --- SIM1 Frictions access gained
      235 --- FS Controls Table located ok
      235 --- Installed Mouse Macro hooks ok.
      235 --- Wind smoothing fix is not installed
      235 --- SimConnect intercept for texts and menus option is off
      235 --- All links okay (with no weather related ones)
      235 -------------------------------------------------------------------
      235 SimConnect_Open succeeded: waiting to check version okay
      235 Trying to use SimConnect Prepar3D
      235 Opened separate AI Traffic client okay
    52891 Running in "Lockheed Martin® Prepar3D® v3", Version: 3.4.14.18870 (SimConnect: 3.4.0.0)
    52891 Initialising SimConnect data requests now
    52891 FSUIPC Menu entry added
    52891 C:\Users\ESCORCIAW10\Documents\Prepar3D v3 Files\LEVC A2A C172 AHS GA PARKING.fxml
    52891 C:\Prepar3Dv3\SimObjects\Airplanes\A2A_C172\C172.air

 

Share this post


Link to post
Share on other sites

Hi, here is the content of FSUIPC4 Log file during the full cycle of crash-fix-load:

I loaded P3d selecting a default Aircraft, and after a minute or so I closed P3D. After the Icon disappeared I noticed in Win Task manager that the P3D process was still running, and after a few more minutes it stopped on its own with a little window (crash or error) message.

This is the FSUIPC4 log right at that moment : P3D closed with default plane and reported a bad exit:

********* FSUIPC4, Version 4.959 (19th December 2016) by Pete Dowson *********
Windows version reported as 6.2.?.9200
Prepar3D.exe version = 3.4.14.18870
Reading options from "C:\Prepar3Dv3\Modules\FSUIPC4.ini"
Running inside Prepar3D v3 on Windows 8.0 or later
Module base=52240000
User Name="Alvaro Escorcia"
User Addr="aescorcia@comcast.net"
FSUIPC4 Key is provided
WIDEFS7 not user registered, or expired
       32 System time = 26/12/2016 06:55:00
       32 FLT path = "C:\Users\ESCORCIAW10\Documents\Prepar3D v3 Files\"
       32 NOTE: configuring for no weather reads or writes!
       32 ------ Module Version Check ------
       32        acontain.dll: 3.4.14.18870
       32             api.dll: 3.4.14.18870
       32        controls.dll: 3.4.14.18870
       32      fs-traffic.dll: 3.4.14.18870
       32             G3D.dll: 3.4.14.18870
       32        language.dll: 3.4.14.18870
       32            sim1.dll: 3.4.14.18870
       32        visualfx.dll: 3.4.14.18870
       32          window.dll: 3.4.14.18870
       32 ----------------------------------
       32 Trying C:\Prepar3Dv3\Modules\SimConnectP3D3.dll
       63 Found it: trying to connect
       78 FS path = "C:\Prepar3Dv3\"
      203 ---------------------- Joystick Device Scan -----------------------
      203 Product= Saitek Pro Flight Rudder Pedals
      203    Manufacturer= Saitek
      203    Vendor=06A3, Product=0763 (Version 1.1)
      203    Serial Number= Saitek
      203 Product= Saitek Pro Flight Yoke
      203    Manufacturer= Saitek
      203    Vendor=06A3, Product=0BAC (Version 3.2)
      203    Serial Number= Saitek
      203 -------------------------------------------------------------------
      235 LogOptions=00000000 00000001
      235 -------------------------------------------------------------------
      235 ------ Setting the hooks and direct calls into the simulator ------
      235 --- CONTROLS timer memory location obtained ok
      235 --- SIM1 Frictions access gained
      235 --- FS Controls Table located ok
      235 --- Installed Mouse Macro hooks ok.
      235 --- Wind smoothing fix is not installed
      235 --- SimConnect intercept for texts and menus option is off
      235 --- All links okay (with no weather related ones)
      235 -------------------------------------------------------------------
      235 SimConnect_Open succeeded: waiting to check version okay
      235 Trying to use SimConnect Prepar3D
      235 Opened separate AI Traffic client okay
    52891 Running in "Lockheed Martin® Prepar3D® v3", Version: 3.4.14.18870 (SimConnect: 3.4.0.0)
    52891 Initialising SimConnect data requests now
    52891 FSUIPC Menu entry added
    52891 C:\Users\ESCORCIAW10\Documents\Prepar3D v3 Files\LEVC A2A C172 AHS GA PARKING.fxml
    52891 C:\Prepar3Dv3\SimObjects\Airplanes\A2A_C172\C172.air
  1757032 C:\Prepar3Dv3\SimObjects\Airplanes\Mooney_Bravo\Mooney_Bravo.air
  1817188 User Aircraft ID 2 supplied, now being used
  1817547 System time = 26/12/2016 07:25:17, Simulator time = 09:07:39 (08:07Z)
  1817547 Aircraft="Mooney Bravo"
  1819500 Starting everything now ...
  1819532 ASN active function link set
  1819532 Ready for ASN WX radar
  1839969 Sim stopped: average frame rate for last 23 secs = 38.7 fps
  1839969    Max AI traffic was 0 aircraft
  1886313 Sim stopped: average frame rate for last 41 secs = 49.6 fps
  1886313    Max AI traffic was 0 aircraft
  1949016 === Calling SimConnect_Close ...
  1949219 === SimConnect_Close done!
  1950219 System time = 26/12/2016 07:27:30, Simulator time = 09:08:25 (08:08Z)
  1950219 *** FSUIPC log file being closed
Minimum frame rate was 30.0 fps, Maximum was 61.4 fps
Minimum available memory recorded was 1687Mb
Average frame rate for running time of 69 secs = 46.3 fps
Maximum AI traffic for session was 0 aircraft
Memory managed: 5 Allocs, 4 Freed
********* FSUIPC Log file closed ***********

Without changing anything else I try to load P3D and as expected I get a fatal crash.

This is the FSUIPC4 log file I get.

Seems to be the same content as before the missed-load-attempt despite the fact that I opened and closed it a few times to be sure is the fresh version

********* FSUIPC4, Version 4.959 (19th December 2016) by Pete Dowson *********
Windows version reported as 6.2.?.9200
Prepar3D.exe version = 3.4.14.18870
Reading options from "C:\Prepar3Dv3\Modules\FSUIPC4.ini"
Running inside Prepar3D v3 on Windows 8.0 or later
Module base=52240000
User Name="Alvaro Escorcia"
User Addr="aescorcia@comcast.net"
FSUIPC4 Key is provided
WIDEFS7 not user registered, or expired
       32 System time = 26/12/2016 06:55:00
       32 FLT path = "C:\Users\ESCORCIAW10\Documents\Prepar3D v3 Files\"
       32 NOTE: configuring for no weather reads or writes!
       32 ------ Module Version Check ------
       32        acontain.dll: 3.4.14.18870
       32             api.dll: 3.4.14.18870
       32        controls.dll: 3.4.14.18870
       32      fs-traffic.dll: 3.4.14.18870
       32             G3D.dll: 3.4.14.18870
       32        language.dll: 3.4.14.18870
       32            sim1.dll: 3.4.14.18870
       32        visualfx.dll: 3.4.14.18870
       32          window.dll: 3.4.14.18870
       32 ----------------------------------
       32 Trying C:\Prepar3Dv3\Modules\SimConnectP3D3.dll
       63 Found it: trying to connect
       78 FS path = "C:\Prepar3Dv3\"
      203 ---------------------- Joystick Device Scan -----------------------
      203 Product= Saitek Pro Flight Rudder Pedals
      203    Manufacturer= Saitek
      203    Vendor=06A3, Product=0763 (Version 1.1)
      203    Serial Number= Saitek
      203 Product= Saitek Pro Flight Yoke
      203    Manufacturer= Saitek
      203    Vendor=06A3, Product=0BAC (Version 3.2)
      203    Serial Number= Saitek
      203 -------------------------------------------------------------------
      235 LogOptions=00000000 00000001
      235 -------------------------------------------------------------------
      235 ------ Setting the hooks and direct calls into the simulator ------
      235 --- CONTROLS timer memory location obtained ok
      235 --- SIM1 Frictions access gained
      235 --- FS Controls Table located ok
      235 --- Installed Mouse Macro hooks ok.
      235 --- Wind smoothing fix is not installed
      235 --- SimConnect intercept for texts and menus option is off
      235 --- All links okay (with no weather related ones)
      235 -------------------------------------------------------------------
      235 SimConnect_Open succeeded: waiting to check version okay
      235 Trying to use SimConnect Prepar3D
      235 Opened separate AI Traffic client okay
    52891 Running in "Lockheed Martin® Prepar3D® v3", Version: 3.4.14.18870 (SimConnect: 3.4.0.0)
    52891 Initialising SimConnect data requests now
    52891 FSUIPC Menu entry added
    52891 C:\Users\ESCORCIAW10\Documents\Prepar3D v3 Files\LEVC A2A C172 AHS GA PARKING.fxml
    52891 C:\Prepar3Dv3\SimObjects\Airplanes\A2A_C172\C172.air
  1757032 C:\Prepar3Dv3\SimObjects\Airplanes\Mooney_Bravo\Mooney_Bravo.air
  1817188 User Aircraft ID 2 supplied, now being used
  1817547 System time = 26/12/2016 07:25:17, Simulator time = 09:07:39 (08:07Z)
  1817547 Aircraft="Mooney Bravo"
  1819500 Starting everything now ...
  1819532 ASN active function link set
  1819532 Ready for ASN WX radar
  1839969 Sim stopped: average frame rate for last 23 secs = 38.7 fps
  1839969    Max AI traffic was 0 aircraft
  1886313 Sim stopped: average frame rate for last 41 secs = 49.6 fps
  1886313    Max AI traffic was 0 aircraft
  1949016 === Calling SimConnect_Close ...
  1949219 === SimConnect_Close done!
  1950219 System time = 26/12/2016 07:27:30, Simulator time = 09:08:25 (08:08Z)
  1950219 *** FSUIPC log file being closed
Minimum frame rate was 30.0 fps, Maximum was 61.4 fps
Minimum available memory recorded was 1687Mb
Average frame rate for running time of 69 secs = 46.3 fps
Maximum AI traffic for session was 0 aircraft
Memory managed: 5 Allocs, 4 Freed
********* FSUIPC Log file closed ***********

Then I run my onetimefix (FSUIPC4 installer), so I can load P3D again. I chose a default (mooney) aircraft, and it loads OK.

At that point this is what I get from the FSUIPC4 Log File:

********* FSUIPC4, Version 4.959 (19th December 2016) by Pete Dowson *********
Windows version reported as 6.2.?.9200
Prepar3D.exe version = 3.4.14.18870
Reading options from "C:\Prepar3Dv3\Modules\FSUIPC4.ini"
Running inside Prepar3D v3 on Windows 8.0 or later
Module base=52240000
User Name="Alvaro Escorcia"
User Addr="aescorcia@comcast.net"
FSUIPC4 Key is provided
WIDEFS7 not user registered, or expired
       16 System time = 26/12/2016 07:43:02
       16 FLT path = "C:\Users\ESCORCIAW10\Documents\Prepar3D v3 Files\"
       16 NOTE: configuring for no weather reads or writes!
       16 ------ Module Version Check ------
       16        acontain.dll: 3.4.14.18870
       16             api.dll: 3.4.14.18870
       16        controls.dll: 3.4.14.18870
       16      fs-traffic.dll: 3.4.14.18870
       16             G3D.dll: 3.4.14.18870
       16        language.dll: 3.4.14.18870
       16            sim1.dll: 3.4.14.18870
       16        visualfx.dll: 3.4.14.18870
       16          window.dll: 3.4.14.18870
       16 ----------------------------------
       16 Trying C:\Prepar3Dv3\Modules\SimConnectP3D3.dll
       47 Found it: trying to connect
       63 FS path = "C:\Prepar3Dv3\"
      188 ---------------------- Joystick Device Scan -----------------------
      188 Product= Saitek Pro Flight Rudder Pedals
      188    Manufacturer= Saitek
      188    Vendor=06A3, Product=0763 (Version 1.1)
      188    Serial Number= Saitek
      188 Product= Saitek Pro Flight Yoke
      188    Manufacturer= Saitek
      188    Vendor=06A3, Product=0BAC (Version 3.2)
      188    Serial Number= Saitek
      188 -------------------------------------------------------------------
      219 LogOptions=00000000 00000001
      219 -------------------------------------------------------------------
      219 ------ Setting the hooks and direct calls into the simulator ------
      219 --- CONTROLS timer memory location obtained ok
      219 --- SIM1 Frictions access gained
      219 --- FS Controls Table located ok
      219 --- Installed Mouse Macro hooks ok.
      219 --- Wind smoothing fix is not installed
      219 --- SimConnect intercept for texts and menus option is off
      219 --- All links okay (with no weather related ones)
      219 -------------------------------------------------------------------
      219 SimConnect_Open succeeded: waiting to check version okay
      219 Trying to use SimConnect Prepar3D
      219 Opened separate AI Traffic client okay
    52750 Running in "Lockheed Martin® Prepar3D® v3", Version: 3.4.14.18870 (SimConnect: 3.4.0.0)
    52750 Initialising SimConnect data requests now
    52750 FSUIPC Menu entry added
    52766 C:\Users\ESCORCIAW10\Documents\Prepar3D v3 Files\LEVC A2A C172 AHS GA PARKING.fxml
    52766 C:\Prepar3Dv3\SimObjects\Airplanes\A2A_C172\C172.air
    81391 C:\Prepar3Dv3\SimObjects\Airplanes\Mooney_Bravo\Mooney_Bravo.air
   140735 User Aircraft ID 2 supplied, now being used
   140860 System time = 26/12/2016 07:45:23, Simulator time = 08:44:20 (07:44Z)
   140860 Aircraft="Mooney Bravo"
   142844 Starting everything now ...
   142875 ASN active function link set
   142875 Ready for ASN WX radar
   163141 Sim stopped: average frame rate for last 22 secs = 38.4 fps
   163141    Max AI traffic was 0 aircraft
=================

 

 

 

Share this post


Link to post
Share on other sites

Hi,

as I said I would first start FS with a default A/C and not loading already an Add-on and then switching to a default, just to eliminate any interference of an Add-on.

You still have the A2A loaded first.

52891 C:\Users\ESCORCIAW10\Documents\Prepar3D v3 Files\LEVC A2A C172 AHS GA PARKING.fxml
    52891 C:\Prepar3Dv3\SimObjects\Airplanes\A2A_C172\C172.air

Thomas

Share this post


Link to post
Share on other sites

Hi Thomas,

thanks a lot for your help. The last 2-3 attempts on my system were successful, so I will wait with deleting the weather stations until the problem occurs again (and then I would send the logs). I did check the logs and they refer to 4.959.

Thanks,

Peter

Share this post


Link to post
Share on other sites

Peter: What is that worked for you?

Thomas: Thanks for your patience. I have loaded P3D, selected the default scenario with a default (mooney) airplane and saved it as default. Problem persists.

Here is the FSUIPC4 Log File

********* FSUIPC4, Version 4.959 (19th December 2016) by Pete Dowson *********
Windows version reported as 6.2.?.9200
Prepar3D.exe version = 3.4.14.18870
Reading options from "C:\Prepar3Dv3\Modules\FSUIPC4.ini"
Running inside Prepar3D v3 on Windows 8.0 or later
Module base=51010000
User Name="Alvaro Escorcia"
User Addr="aescorcia@comcast.net"
FSUIPC4 Key is provided
WIDEFS7 not user registered, or expired
       32 System time = 27/12/2016 07:08:35
       32 FLT path = "C:\Users\ESCORCIAW10\Documents\Prepar3D v3 Files\"
       32 NOTE: configuring for no weather reads or writes!
       32 ------ Module Version Check ------
       32        acontain.dll: 3.4.14.18870
       32             api.dll: 3.4.14.18870
       32        controls.dll: 3.4.14.18870
       32      fs-traffic.dll: 3.4.14.18870
       32             G3D.dll: 3.4.14.18870
       32        language.dll: 3.4.14.18870
       32            sim1.dll: 3.4.14.18870
       32        visualfx.dll: 3.4.14.18870
       32          window.dll: 3.4.14.18870
       32 ----------------------------------
       32 Trying C:\Prepar3Dv3\Modules\SimConnectP3D3.dll
       79 Found it: trying to connect
       94 FS path = "C:\Prepar3Dv3\"
      235 ---------------------- Joystick Device Scan -----------------------
      235 Product= Saitek Pro Flight Rudder Pedals
      235    Manufacturer= Saitek
      235    Vendor=06A3, Product=0763 (Version 1.1)
      235    Serial Number= Saitek
      235 Product= Saitek Pro Flight Yoke
      235    Manufacturer= Saitek
      235    Vendor=06A3, Product=0BAC (Version 3.2)
      235    Serial Number= Saitek
      235 -------------------------------------------------------------------
      266 LogOptions=00000000 00000001
      266 -------------------------------------------------------------------
      266 ------ Setting the hooks and direct calls into the simulator ------
      266 --- CONTROLS timer memory location obtained ok
      266 --- SIM1 Frictions access gained
      266 --- FS Controls Table located ok
      266 --- Installed Mouse Macro hooks ok.
      266 --- Wind smoothing fix is not installed
      266 --- SimConnect intercept for texts and menus option is off
      266 --- All links okay (with no weather related ones)
      266 -------------------------------------------------------------------
      266 SimConnect_Open succeeded: waiting to check version okay
      266 Trying to use SimConnect Prepar3D
      266 Opened separate AI Traffic client okay
    56782 Running in "Lockheed Martin® Prepar3D® v3", Version: 3.4.14.18870 (SimConnect: 3.4.0.0)
    56782 Initialising SimConnect data requests now
    56782 FSUIPC Menu entry added
    56813 C:\Users\ESCORCIAW10\Documents\Prepar3D v3 Files\DEFAULT PLANE LEVC.fxml
    56813 C:\Prepar3Dv3\SimObjects\Airplanes\Mooney_Bravo\Mooney_Bravo.air
   140750 User Aircraft ID 2 supplied, now being used
   141579 System time = 27/12/2016 07:10:57, Simulator time = 08:55:08 (07:55Z)
   141594 Aircraft="Mooney Bravo"
   147610 Starting everything now ...
   147641 ASN active function link set
   147641 Ready for ASN WX radar
   165750 Sim stopped: average frame rate for last 25 secs = 36.4 fps
   165750    Max AI traffic was 0 aircraft
   337688 Sim stopped: average frame rate for last 167 secs = 47.3 fps
   337688    Max AI traffic was 0 aircraft
   367844 === Calling SimConnect_Close ...
   368047 === SimConnect_Close done!
   369047 System time = 27/12/2016 07:14:44, Simulator time = 08:57:54 (07:57Z)
   369047 *** FSUIPC log file being closed
Minimum frame rate was 23.3 fps, Maximum was 60.0 fps
Minimum available memory recorded was 1572Mb
Average frame rate for running time of 192 secs = 45.9 fps
Maximum AI traffic for session was 0 aircraft
Memory managed: 5 Allocs, 4 Freed
********* FSUIPC Log file closed ***********

 

 

 

Share this post


Link to post
Share on other sites

Hello, I have the exact same situation.After installing FSUIPC I can run it maybe 1-2 times, then P3D hangs. If I disable FSUIPC in dll.xml P3D runs OK.

The only solution I was able to find is to run FSUIPC installation again.

 

Here is my log:

===============================

********* FSUIPC4, Version 4.959 (19th December 2016) by Pete Dowson *********
Windows version reported as 6.2.?.9200
Prepar3D.exe version = 3.4.18.19475
Reading options from "G:\Prepar3D\Modules\FSUIPC4.ini"
Running inside Prepar3D v3 on Windows 8.0 or later
Module base=11050000
User Name="--------------------------"
User Addr="---------------------------"
FSUIPC4 Key is provided
WIDEFS7 not user registered, or expired
       47 System time = 29/12/2016 15:34:12
       47 FLT path = "C:\Users\sandb0x\Documents\Prepar3D v3 Files\"
       47 NOTE: configuring for no weather reads or writes!
       47 ------ Module Version Check ------
       47        acontain.dll: 3.4.18.19475
       47             api.dll: 3.4.18.19475
       47        controls.dll: 3.4.18.19475
       47      fs-traffic.dll: 3.4.18.19475
       47             G3D.dll: 3.4.18.19475
       47        language.dll: 3.4.18.19475
       47            sim1.dll: 3.4.18.19475
       47        visualfx.dll: 3.4.18.19475
       47          window.dll: 3.4.18.19475
       47 ----------------------------------
       47 Trying G:\Prepar3D\Modules\SimConnectP3D3.dll
       47 Found it: trying to connect
       47 FS path = "G:\Prepar3D\"
      297 Finished: 0 Profile files created
      359 ---------------------- Joystick Device Scan -----------------------
      359 Product= T.16000M
      359    Manufacturer= Thrustmaster
      359    Vendor=044F, Product=B10A (Version 5.0)
      359    Serial Number= Thrustmaster
      359 Product= Pro Flight TPM System
      375    Manufacturer= Mad Catz
      375    Vendor=06A3, Product=0B4D (Version 1.100)
      375    Serial Number= GO000204
      375 Product= Button Box Interface
      375    Manufacturer= Leo Bodnar
      375    Vendor=1DD2, Product=1150 (Version 2.4)
      375    Serial Number= B57006
      375 -------------------------------------------------------------------
      453 Run: "G:\Prepar3D\Modules\linda.exe"
      484 LogOptions=80000000 00000001
      484 -------------------------------------------------------------------
      484 ------ Setting the hooks and direct calls into the simulator ------
      484 --- CONTROLS timer memory location obtained ok
      484 --- SIM1 Frictions access gained
      484 --- FS Controls Table located ok
      484 --- Installed Mouse Macro hooks ok.
      484 --- Wind smoothing fix is not installed
      484 --- SimConnect intercept for texts and menus option is off
      484 --- All links okay (with no weather related ones)
      484 -------------------------------------------------------------------
      484 SimConnect_Open succeeded: waiting to check version okay
      484 Trying to use SimConnect Prepar3D
      484 Opened separate AI Traffic client okay
     2266 Running in "Lockheed Martin® Prepar3D® v3", Version: 3.4.18.19475 (SimConnect: 3.4.0.0)
     2266 Initialising SimConnect data requests now
     2266 FSUIPC Menu entry added
     2281 C:\Users\sandb0x\AppData\Local\Lockheed Martin\Prepar3D v3\Prepar3D_Default.fxml
     2281 G:\Prepar3D\SimObjects\Airplanes\IRIS Raptor Driver\Raptor.air
    15797 Weather Mode now = Theme

 

Share this post


Link to post
Share on other sites

Hi,

when you say the only solution is to run the installer again, then there is something that changes when you run P3D up to it crashes.

So what the installer is doing is it places the DLL and PDF's in the module folder, it DOESN'T do any changes to your FSUIPC4.ini file and there is NO registration in Windows of FSUIPC4 at all. In addition it checks the correct registration of P3D in Windows Registry and if need and possible it will correct it. The only file it actually changes is the DLL.XML file in C:\Users\YourLogin\AppData\Roaming\Lockheed Martin\Prepar3D v3\ where it adds the launch part for FSUIPC4 and the end.

<?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>FSUIPC 4</Name>
    <Disabled>False</Disabled>
    <Path>Modules\FSUIPC4.dll</Path>
  </Launch.Addon>

</SimBase.Document>
 
As you all say the solution is to re-run the installer you might check the DLL.XML file after the installer and again when P3D starts crashing if there is a change.
Also I would advise for testing that all installed add-ons, other than FSUIPC, are disabled and a default A/C is already launched on start-up of P3D.

Thomas

Share this post


Link to post
Share on other sites

Hello all.

I am having the same issue.  If I install the newest FSUIPC module P3D will run fine the first time.  It will crash and leave a process running on the machine on any subsequent attempts to start P3D.  I have reduced the DLL.XML file to just FSUIPC....and this behavior persists.  If I disable FSUIPC in the DLL file P3D then starts fine.  If I turn FSUIPC back on in DLL.XML P3D repeats the crash behavior.  Turing FSUIPC on/off in the DLL.XML file generates repeatable cases as described above.

<?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>FSUIPC 4</Name>
    <Disabled>False</Disabled>
    <Path>Modules\FSUIPC4.dll</Path>
  </Launch.Addon>
</SimBase.Document>

When P3D does crash there is no FSUIPC log file generated.  The only other addons running are the FSDT addons associated with GSX.  There is an as_btstrp_config_manager loaded in EXE,XML but disabling that load has no affect on whether P3D starts,

Given this it appears that The new FSUIPC module has an issue with P3D, unless there is some adverse interaction with the GSX programs.  Below is the FSUIPC log from the successful initial start of P3D. Minus my personal information.  

I'm running out of ideas here.

 

********* FSUIPC4, Version 4.959 (19th December 2016) by Pete Dowson *********
Windows version reported as 6.2.?.9200
Prepar3D.exe version = 3.4.18.19475
Reading options from "P:\Program Files (x86)\Lockheed Martin\Prepar3D v3\Modules\FSUIPC4.ini"
Running inside Prepar3D v3 on Windows 8.0 or later
Module base=54F10000
User Name=
User Addr=
FSUIPC4 Key is provided
WideFS7 Key is provided
      109 System time = 29/12/2016 06:14:14
      109 FLT UNC path = "C:\Users\Gypsy\Documents\Prepar3D v3 Files\"
      109 NOTE: configuring for no weather reads or writes!
      109 ------ Module Version Check ------
      109        acontain.dll: 3.4.18.19475
      109             api.dll: 3.4.18.19475
      109        controls.dll: 3.4.18.19475
      109      fs-traffic.dll: 3.4.18.19475
      109             G3D.dll: 3.4.18.19475
      109        language.dll: 3.4.18.19475
      109            sim1.dll: 3.4.18.19475
      109        visualfx.dll: 3.4.18.19475
      109          window.dll: 3.4.18.19475
      109 ----------------------------------
      109 Trying P:\Program Files (x86)\Lockheed Martin\Prepar3D v3\Modules\SimConnectP3D3.dll
      109 Found it: trying to connect
      109 FS UNC path = "P:\Program Files (x86)\Lockheed Martin\Prepar3D v3\"
      359 Finished: 0 Profile files created
      391 ---------------------- Joystick Device Scan -----------------------
      391 Product= Saitek Pro Flight Quadrant
      391    Manufacturer= Saitek
      391    Vendor=06A3, Product=0C2D (Version 2.0)
      391    Serial Number= Saitek
      406 Product= CH PRO PEDALS USB 
      406    Manufacturer= CH PRODUCTS
      406    Vendor=068E, Product=00F2 (Version 0.0)
      406    Serial Number= CH PRODUCTS
      406 Product= Pro Flight X65 Control System
      406    Manufacturer= Saitek
      406    Vendor=06A3, Product=0B6A (Version 1.101)
      406    Serial Number= Saitek
      406 -------------------------------------------------------------------
      406 LogOptions=00000000 00000001
      422 -------------------------------------------------------------------
      422 ------ Setting the hooks and direct calls into the simulator ------
      422 --- CONTROLS timer memory location obtained ok
      422 --- SIM1 Frictions access gained
      422 --- FS Controls Table located ok
      422 --- Installed Mouse Macro hooks ok.
      422 --- Wind smoothing fix is not installed
      422 --- SimConnect intercept for texts and menus option is off
      422 --- All links okay (with no weather related ones)
      422 -------------------------------------------------------------------
      422 SimConnect_Open succeeded: waiting to check version okay
      422 Trying to use SimConnect Prepar3D
      422 Opened separate AI Traffic client okay
    16594 Running in "Lockheed Martin® Prepar3D® v3", Version: 3.4.18.19475 (SimConnect: 3.4.0.0)
    16594 Initialising SimConnect data requests now
    16594 FSUIPC Menu entry added
    16609 C:\Users\Gypsy\AppData\Local\Lockheed Martin\Prepar3D v3\Prepar3D_Default.fxml
    16609 P:\Program Files (x86)\Lockheed Martin\Prepar3D v3\SimObjects\Airplanes\IRIS Raptor Driver\Raptor.air
    42953 User Aircraft ID 1 supplied, now being used
    43516 System time = 29/12/2016 06:14:57, Simulator time = 05:14:01 (11:14Z)
    43531 Aircraft="F-22 Raptor - 525th Fighter Squadron"
    44547 Starting everything now ...
    44547 LUA.0: beginning "P:\Program Files (x86)\Lockheed Martin\Prepar3D v3\Modules\ipcReady.lua"
    44547 LUA.0: ended "P:\Program Files (x86)\Lockheed Martin\Prepar3D v3\Modules\ipcReady.lua"
    44562 LUA.1:  *************************** STARTING LINDA **************************
    44562 LUA.1: LINDA:: [START] Loading System Configuration files
    44594 LUA.1: LINDA:: [START] VRInsight MCP Set = mcp
    44609 LUA.1: LINDA:: [START] System Configuration files loaded
    44750 LUA.1: LINDA:: [START] *************************************************************
    44750 LUA.1: LINDA:: [START] New Aircraft Selected - restarting...
    44750 LUA.1: LINDA:: [START] *************************************************************
    44750 LUA.1: LINDA:: [START] Current Aircraft: F-22 Raptor - 525th Fighter Squadro
    44906 LUA.1: LINDA:: [START] Aircraft module detected: FSX Default
    44922 LUA.1: LINDA:: [START] *************************************************************
    44969 LUA.0: LINDA:: [INIT] Starting Initialisation...
    45016 LUA.0: LINDA:: [INIT] Loading Libraries...
    45016 LUA.0: LINDA:: [LIB]  AivlaSoft library loaded...
    45016 LUA.0: LINDA:: [LIB]  ATC library loaded...
    45031 LUA.0: LINDA:: [LIB]  FSX standard library loaded...
    45031 LUA.0: LINDA:: [LIB]  FS2Crew library loaded...
    45047 LUA.0: LINDA:: [LIB]  FSX Functions loaded...
    45047 LUA.0: LINDA:: [LIB]  IVAO library loaded...
    45047 LUA.0: LINDA:: [LIB]  RealityXP library loaded...
    45062 LUA.0: LINDA:: [LIB]  Saitek Functions loaded...
    45062 LUA.0: LINDA:: [LIB]  VATSIM library loaded...
    45078 LUA.0: LINDA:: [LIB]  VRInsight Function Library loaded...
    45078 LUA.0: LINDA:: [LIB]  Weather library loaded...
    45078 LUA.0: LINDA:: [LIB]  A2A MAP library loaded...
    45078 LUA.0: LINDA:: [INIT] Initializing Common Variables...
    45125 LUA.0: LINDA:: [INIT] User GLOBAL config loaded...
    45141 LUA.0: LINDA:: User's modifications script is loaded...
    45141 LUA.0: LINDA:: [INIT] User FUNCTIONS loaded...
    45156 LUA.0: LINDA:: [INIT] Finalising Initialisation...
    45312 LUA.0: LINDA:: [COMM] Checking VRI
    45328 LUA.0: LINDA:: [INIT] Module: FSX Default Started...
    45469 LUA.0: LINDA:: [INIT] Ready to go, Captain!
    45469 LUA.0: LINDA:: [INIT] ***************************************************************
    68594 === Calling SimConnect_Close ...
    68797 === SimConnect_Close done!
    69797 System time = 29/12/2016 06:15:23, Simulator time = 05:15:09 (11:15Z)
    69797 *** FSUIPC log file being closed
Minimum frame rate was 19.7 fps, Maximum was 20.0 fps
Minimum available memory recorded was 2084Mb
Average frame rate for running time of 13 secs = 19.8 fps
Maximum AI traffic for session was 0 aircraft
Memory managed: 100 Allocs, 96 Freed
********* FSUIPC Log file closed ***********

 

Share this post


Link to post
Share on other sites

UPDATE:

I restored the original DLL.XML file with all addons.  I then reinstalled the GSX app.  P3d started fine with FSUIPC enabled the first time.  The second attempt at P3D start repeated the crash behavior.  Disabling FSUIPC had no affect on performing a succesfull start.  I then reinstalled GSX again, enabled FSUIPC and P3D started fine the first time.  The second P3d start failed.  I then reinstalled FSUIPC and P3D started fine. Once again, the next P3D start failed.

 

It looks like there is some interaction with addon installs going on that I cannot find

Share this post


Link to post
Share on other sites

Hi,

as I said before I would just start without ANY add-on to find the problem. Here I neither see a problem with P3Dv3.4.14...(Hotfix 1) nor with P3Dv3.4.18... (Hotfix 2) BUT I don't have add-on installed.

@gypsyczar you say you only have GSX as add-on installed that runs at the same time but this is from your log file!?

    44562 LUA.1:  *************************** STARTING LINDA **************************
    44562 LUA.1: LINDA:: [START] Loading System Configuration files
    44594 LUA.1: LINDA:: [START]
VRInsight MCP Set = mcp
    44609 LUA.1: LINDA:: [START] System Configuration files loaded
    44750 LUA.1: LINDA:: [START] *************************************************************
    44750 LUA.1: LINDA:: [START] New Aircraft Selected - restarting...
    44750 LUA.1: LINDA:: [START] *************************************************************
    44750 LUA.1: LINDA:: [START] Current Aircraft: F-22 Raptor - 525th Fighter Squadro
    44906 LUA.1: LINDA:: [START] Aircraft module detected: FSX Default
    44922 LUA.1: LINDA:: [START] *************************************************************
    44969 LUA.0: LINDA:: [INIT] Starting Initialisation...
    45016 LUA.0: LINDA:: [INIT] Loading Libraries...
    45016 LUA.0: LINDA:: [LIB]  
AivlaSoft library loaded...
    45016 LUA.0: LINDA:: [LIB]  ATC library loaded...
    45031 LUA.0: LINDA:: [LIB]  FSX standard library loaded...
    45031 LUA.0: LINDA:: [LIB]  FS2Crew library loaded...
    45047 LUA.0: LINDA:: [LIB]  FSX Functions loaded...
    45047 LUA.0: LINDA:: [LIB]  IVAO library loaded...
    45047 LUA.0: LINDA:: [LIB]  RealityXP library loaded...
    45062 LUA.0: LINDA:: [LIB]  Saitek Functions loaded...
    45062 LUA.0: LINDA:: [LIB]  VATSIM library loaded...
    45078 LUA.0: LINDA:: [LIB]  VRInsight Function Library loaded...
    45078 LUA.0: LINDA:: [LIB]  Weather library loaded...
    45078 LUA.0: LINDA:: [LIB]  A2A MAP library loaded...
    45078 LUA.0: LINDA:: [INIT] Initializing Common Variables...
    45125 LUA.0: LINDA:: [INIT] User GLOBAL config loaded...
    45141 LUA.0: LINDA:: User's modifications script is loaded...
    45141 LUA.0: LINDA:: [INIT] User FUNCTIONS loaded...
    45156 LUA.0: LINDA:: [INIT] Finalising Initialisation...
    45312 LUA.0: LINDA:: [COMM] Checking VRI
    45328 LUA.0: LINDA:: [INIT] Module: FSX Default Started...
    45469 LUA.0: LINDA:: [INIT] Ready to go, Captain!
    45469 LUA.0: LINDA:: [INIT] ***************************************************************

Lots of stuff loading there, also I remember problem with this Linda couple weeks ago?

Disable this and the Lua file first.

Also the P3D version you use came out after the FSUIPC release and maybe Pete didn't know about it.

Thomas

Share this post


Link to post
Share on other sites

Peter: What is that worked for you?

Thomas: Thanks for your patience. I have loaded P3D, selected the default scenario with a default (mooney) airplane and saved it as default. Problem persists.

Here is the FSUIPC4 Log File

********* FSUIPC4, Version 4.959 (19th December 2016) by Pete Dowson *********
Windows version reported as 6.2.?.9200
Prepar3D.exe version = 3.4.14.18870
Reading options from "C:\Prepar3Dv3\Modules\FSUIPC4.ini"
Running inside Prepar3D v3 on Windows 8.0 or later
Module base=51010000
User Name="Alvaro Escorcia"
User Addr="aescorcia@comcast.net"
FSUIPC4 Key is provided
WIDEFS7 not user registered, or expired
       32 System time = 27/12/2016 07:08:35
       32 FLT path = "C:\Users\ESCORCIAW10\Documents\Prepar3D v3 Files\"
       32 NOTE: configuring for no weather reads or writes!
       32 ------ Module Version Check ------
       32        acontain.dll: 3.4.14.18870
       32             api.dll: 3.4.14.18870
       32        controls.dll: 3.4.14.18870
       32      fs-traffic.dll: 3.4.14.18870
       32             G3D.dll: 3.4.14.18870
       32        language.dll: 3.4.14.18870
       32            sim1.dll: 3.4.14.18870
       32        visualfx.dll: 3.4.14.18870
       32          window.dll: 3.4.14.18870
       32 ----------------------------------
       32 Trying C:\Prepar3Dv3\Modules\SimConnectP3D3.dll
       79 Found it: trying to connect
       94 FS path = "C:\Prepar3Dv3\"
      235 ---------------------- Joystick Device Scan -----------------------
      235 Product= Saitek Pro Flight Rudder Pedals
      235    Manufacturer= Saitek
      235    Vendor=06A3, Product=0763 (Version 1.1)
      235    Serial Number= Saitek
      235 Product= Saitek Pro Flight Yoke
      235    Manufacturer= Saitek
      235    Vendor=06A3, Product=0BAC (Version 3.2)
      235    Serial Number= Saitek
      235 -------------------------------------------------------------------
      266 LogOptions=00000000 00000001
      266 -------------------------------------------------------------------
      266 ------ Setting the hooks and direct calls into the simulator ------
      266 --- CONTROLS timer memory location obtained ok
      266 --- SIM1 Frictions access gained
      266 --- FS Controls Table located ok
      266 --- Installed Mouse Macro hooks ok.
      266 --- Wind smoothing fix is not installed
      266 --- SimConnect intercept for texts and menus option is off
      266 --- All links okay (with no weather related ones)
      266 -------------------------------------------------------------------
      266 SimConnect_Open succeeded: waiting to check version okay
      266 Trying to use SimConnect Prepar3D
      266 Opened separate AI Traffic client okay
    56782 Running in "Lockheed Martin® Prepar3D® v3", Version: 3.4.14.18870 (SimConnect: 3.4.0.0)
    56782 Initialising SimConnect data requests now
    56782 FSUIPC Menu entry added
    56813 C:\Users\ESCORCIAW10\Documents\Prepar3D v3 Files\DEFAULT PLANE LEVC.fxml
    56813 C:\Prepar3Dv3\SimObjects\Airplanes\Mooney_Bravo\Mooney_Bravo.air
   140750 User Aircraft ID 2 supplied, now being used
   141579 System time = 27/12/2016 07:10:57, Simulator time = 08:55:08 (07:55Z)
   141594 Aircraft="Mooney Bravo"
   147610 Starting everything now ...
   147641 ASN active function link set
   147641 Ready for ASN WX radar
   165750 Sim stopped: average frame rate for last 25 secs = 36.4 fps
   165750    Max AI traffic was 0 aircraft
   337688 Sim stopped: average frame rate for last 167 secs = 47.3 fps
   337688    Max AI traffic was 0 aircraft
   367844 === Calling SimConnect_Close ...
   368047 === SimConnect_Close done!
   369047 System time = 27/12/2016 07:14:44, Simulator time = 08:57:54 (07:57Z)
   369047 *** FSUIPC log file being closed
Minimum frame rate was 23.3 fps, Maximum was 60.0 fps
Minimum available memory recorded was 1572Mb
Average frame rate for running time of 192 secs = 45.9 fps
Maximum AI traffic for session was 0 aircraft
Memory managed: 5 Allocs, 4 Freed
********* FSUIPC Log file closed ***********

 

 

 

Share this post


Link to post
Share on other sites

I still lave the problem

I use Lockheed Martin® Prepar3D® v3, Version: 3.4.14.18870 and FSUIPC4, Version 4.959

Hopefully Pete has the opportunity to look at this when he gets back from holidays

regards

Alvaro Escorcia

 

Share this post


Link to post
Share on other sites

Hello..

I still lave the problem

I use Lockheed Martin® Prepar3D® v3, Version: 3.4.18.19475 and FSUIPC4, Version 4.959

With or without addon, that changes nothing, I have to reinstall FSCuip every time P3D crash

 

Good holiday of the end of year

 

Bye

 

 

Share this post


Link to post
Share on other sites

Hi,

I am having exactly the same issue. P3Dv3 3.4.18.19475, FSUIPC 4.959. Reinstalling FSUIPC is the only thing that works for one time only.

However, I noticed, that trouble started when I installed some more scenery via Orbx FTX Central v3 (FTX Pacific Northwest and Pacific Fjords to be precise). I also use chase plane and every time after I installed some scenery and start P3D, I get a notification from chase plane that WideViewAspect=true was missing from my prepar3d.cfg. However, I didn't made any changes to that file. I highly suspect FTX Central v3 3.0.2.2 being the cause of my trouble. I also noticed that after the FSUIPC installation, my Prepar3D.exe is not set to start in admin mode anymore (which never happened before using FTXCv3). Do you guys use Orbx?

Regards,

Jan

Share this post


Link to post
Share on other sites
On 12/29/2016 at 2:49 PM, gypsyczar said:

It looks like there is some interaction with addon installs going on that I cannot find

I cannot reproduce this problem here at all.

I've found in the past that the order of loads in the DLL.XML file can be critical  FSUIP4.DLL generally likes to be the last entry in the copy of DLL.XML in the AppData\Roaming folder -- excepting the Active Sky connect module (as_btstrp) which needs to come later.

Reinstalling FSUIPC recopies the exact same DLL into the Modules folder but it does also check that it is still in the best place in the DLL.XML file and if not moves it. So when P3D won't run, check the DLL.XML and see if something has changed the order again.

Also check that there is no entry for FSUIPC in the ProgramData folder version of DLL.XML.

Pete

 

Share this post


Link to post
Share on other sites

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.

Guest
Reply to this topic...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

Loading...

×
×
  • 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.