VisualPSX Suite upgrade to versions 6.6, 7.6 and 8.6, build 5821 released

[cavaricooper]

Garry-

Thanks for your responses. VisualPSX is a treasure and your continued and evolving efforts are very appreciated!

Best- C

[GodAtum]

Hi Carl, Chris and Alex,

These are intriguing behaviours that prompted me to check the P3D SDKs in case I had overlooked any changed SimConnect usage.

There weren't any that are relevant to VisualPSX and that leads me to suspect interactions with other addons. I suggest you try running VisualPSX with no other addons to see if that eliminates the problems. If we can identify one or more that result in VisualPSX behaving strangely we might be able to work out how to make our addons work well together.

That's my best guess at the moment.

Cheers,

Hi Garry. I fixed the ground issue by using x64 for the runway generator.

P3D v2.5 still crashed when I select the use PSX weather option. No addons apart from scenery and REX Textures. In P3D i get the error

Code Select Expand

Version=1
EventType=BEX
EventTime=130986301423334871
ReportType=2
Consent=1
ReportIdentifier=1c6730d0-c74c-11e5-b397-60a44c64925e
IntegratorReportIdentifier=1c6730cf-c74c-11e5-b397-60a44c64925e
WOW64=1
Response.type=4
Sig[0].Name=Application Name
Sig[0].Value=Prepar3D.exe
Sig[1].Name=Application Version
Sig[1].Value=2.5.12946.0
Sig[2].Name=Application Timestamp
Sig[2].Value=555f2e54
Sig[3].Name=Fault Module Name
Sig[3].Value=MSVCR100.dll
Sig[4].Name=Fault Module Version
Sig[4].Value=10.0.40219.325
Sig[5].Name=Fault Module Timestamp
Sig[5].Value=4df2be1e
Sig[6].Name=Exception Offset
Sig[6].Value=0008af3e
Sig[7].Name=Exception Code
Sig[7].Value=c0000417
Sig[8].Name=Exception Data
Sig[8].Value=00000000
DynamicSig[1].Name=OS Version
DynamicSig[1].Value=6.1.7601.2.1.0.256.48
DynamicSig[2].Name=Locale ID
DynamicSig[2].Value=2057
DynamicSig[22].Name=Additional Information 1
DynamicSig[22].Value=e853
DynamicSig[23].Name=Additional Information 2
DynamicSig[23].Value=e85344b7ae8a756199f104201315f46a
DynamicSig[24].Name=Additional Information 3
DynamicSig[24].Value=edae
DynamicSig[25].Name=Additional Information 4
DynamicSig[25].Value=edae0ffe38290de94dfbeab02e9d5f57
UI[2]=C:\P3D\Prepar3D v2\Prepar3D.exe
UI[3]=Prepar3D exe has stopped working
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:\P3D\Prepar3D v2\Prepar3D.exe
LoadedModule[1]=C:\Windows\SysWOW64\ntdll.dll
LoadedModule[2]=C:\Windows\syswow64\kernel32.dll
LoadedModule[3]=C:\Windows\syswow64\KERNELBASE.dll
LoadedModule[4]=C:\Windows\syswow64\USER32.dll
LoadedModule[5]=C:\Windows\syswow64\GDI32.dll
LoadedModule[6]=C:\Windows\syswow64\LPK.dll
LoadedModule[7]=C:\Windows\syswow64\USP10.dll
LoadedModule[8]=C:\Windows\syswow64\msvcrt.dll
LoadedModule[9]=C:\Windows\syswow64\ADVAPI32.dll
LoadedModule[10]=C:\Windows\SysWOW64\sechost.dll
LoadedModule[11]=C:\Windows\syswow64\RPCRT4.dll
LoadedModule[12]=C:\Windows\syswow64\SspiCli.dll
LoadedModule[13]=C:\Windows\syswow64\CRYPTBASE.dll
LoadedModule[14]=C:\Windows\syswow64\ole32.dll
LoadedModule[15]=C:\P3D\Prepar3D v2\api.dll
LoadedModule[16]=C:\Windows\system32\Cabinet.dll
LoadedModule[17]=C:\Windows\syswow64\WS2_32.dll
LoadedModule[18]=C:\Windows\syswow64\NSI.dll
LoadedModule[19]=C:\Windows\system32\MSWSOCK.dll
LoadedModule[20]=C:\Windows\WinSxS\x86_microsoft.windows.common-controls_6595b64144ccf1df_5.82.7601.18837_none_ec86b8d6858ec0bc\COMCTL32.dll
LoadedModule[21]=C:\Windows\system32\WINMM.dll
LoadedModule[22]=C:\Windows\system32\VERSION.dll
LoadedModule[23]=C:\Windows\syswow64\IMM32.dll
LoadedModule[24]=C:\Windows\syswow64\MSCTF.dll
LoadedModule[25]=C:\P3D\Prepar3D v2\IP2Lib32.DLL
LoadedModule[26]=C:\Windows\system32\WINSPOOL.DRV
LoadedModule[27]=C:\Windows\syswow64\comdlg32.dll
LoadedModule[28]=C:\Windows\syswow64\SHLWAPI.dll
LoadedModule[29]=C:\Windows\syswow64\SHELL32.dll
LoadedModule[30]=C:\Windows\syswow64\OLEAUT32.dll
LoadedModule[31]=C:\Windows\system32\OLEACC.dll
LoadedModule[32]=C:\Windows\system32\oledlg.dll
LoadedModule[33]=C:\Windows\system32\WSOCK32.dll
LoadedModule[34]=C:\P3D\Prepar3D v2\acontain.dll
LoadedModule[35]=C:\P3D\Prepar3D v2\ai_player.dll
LoadedModule[36]=C:\P3D\Prepar3D v2\atc.dll
LoadedModule[37]=C:\P3D\Prepar3D v2\demo.dll
LoadedModule[38]=C:\P3D\Prepar3D v2\controls.dll
LoadedModule[39]=C:\Windows\system32\DINPUT8.dll
LoadedModule[40]=C:\P3D\Prepar3D v2\flight.dll
LoadedModule[41]=C:\P3D\Prepar3D v2\facilities.dll
LoadedModule[42]=C:\P3D\Prepar3D v2\fe.dll
LoadedModule[43]=C:\Windows\syswow64\USERENV.dll
LoadedModule[44]=C:\Windows\syswow64\profapi.dll
LoadedModule[45]=C:\P3D\Prepar3D v2\main.dll
LoadedModule[46]=C:\P3D\Prepar3D v2\fs-traffic.dll
LoadedModule[47]=C:\P3D\Prepar3D v2\g3d.dll
LoadedModule[48]=C:\Windows\system32\d3dx9_43.dll
LoadedModule[49]=C:\P3D\Prepar3D v2\g2d.dll
LoadedModule[50]=C:\Windows\system32\d3dx11_43.dll
LoadedModule[51]=C:\Windows\system32\D3DCOMPILER_43.dll
LoadedModule[52]=C:\Windows\system32\d3d9.dll
LoadedModule[53]=C:\Windows\system32\d3d8thk.dll
LoadedModule[54]=C:\Windows\system32\dwmapi.dll
LoadedModule[55]=C:\Windows\system32\d3d11.dll
LoadedModule[56]=C:\Windows\system32\dxgi.dll
LoadedModule[57]=C:\Windows\system32\OPENGL32.dll
LoadedModule[58]=C:\Windows\system32\GLU32.dll
LoadedModule[59]=C:\Windows\system32\DDRAW.dll
LoadedModule[60]=C:\Windows\system32\DCIMAN32.dll
LoadedModule[61]=C:\Windows\syswow64\SETUPAPI.dll
LoadedModule[62]=C:\Windows\syswow64\CFGMGR32.dll
LoadedModule[63]=C:\Windows\syswow64\DEVOBJ.dll
LoadedModule[64]=C:\P3D\Prepar3D v2\PDK.dll
LoadedModule[65]=C:\Windows\system32\MSVCR100.dll
LoadedModule[66]=C:\Windows\system32\MSVCP100.dll
LoadedModule[67]=C:\P3D\Prepar3D v2\simscheduler.dll
LoadedModule[68]=C:\P3D\Prepar3D v2\simprop.dll
LoadedModule[69]=C:\P3D\Prepar3D v2\util.dll
LoadedModule[70]=C:\Windows\system32\d3dx10_43.dll
LoadedModule[71]=C:\P3D\Prepar3D v2\weather.dll
LoadedModule[72]=C:\P3D\Prepar3D v2\sim1.dll
LoadedModule[73]=C:\P3D\Prepar3D v2\multiplayer.dll
LoadedModule[74]=C:\Windows\system32\DSOUND.dll
LoadedModule[75]=C:\Windows\system32\POWRPROF.dll
LoadedModule[76]=C:\P3D\Prepar3D v2\panels.dll
LoadedModule[77]=C:\P3D\Prepar3D v2\sound.dll
LoadedModule[78]=C:\P3D\Prepar3D v2\window.dll
LoadedModule[79]=C:\P3D\Prepar3D v2\terrain.dll
LoadedModule[80]=C:\P3D\Prepar3D v2\visualfx.dll
LoadedModule[81]=C:\Windows\system32\MSACM32.dll
LoadedModule[82]=C:\P3D\Prepar3D v2\livingwater.dll
LoadedModule[83]=C:\P3D\Prepar3D v2\gps.dll
LoadedModule[84]=C:\P3D\Prepar3D v2\symmap.dll
LoadedModule[85]=C:\P3D\Prepar3D v2\menus.dll
LoadedModule[86]=C:\P3D\Prepar3D v2\language.dll
LoadedModule[87]=C:\Windows\system32\uxtheme.dll
LoadedModule[88]=C:\ProgramData\MyStart Anti-phishing Domain Advisor\mystart_antiphishing.dll
LoadedModule[89]=C:\Windows\SysWOW64\HsSrv.dll
LoadedModule[90]=C:\P3D\Prepar3D v2\uiInterface.dll
LoadedModule[91]=C:\Windows\SYSTEM32\MSCOREE.DLL
LoadedModule[92]=C:\Windows\system32\apphelp.dll
LoadedModule[93]=C:\Windows\Microsoft.NET\Framework\v4.0.30319\mscoreei.dll
LoadedModule[94]=C:\Windows\Microsoft.NET\Framework\v4.0.30319\clr.dll
LoadedModule[95]=C:\Windows\system32\MSVCR120_CLR0400.dll
LoadedModule[96]=C:\Windows\assembly\NativeImages_v4.0.30319_32\mscorlib\8e3404c758efee6c7eb3ec52c38e1ed8\mscorlib.ni.dll
LoadedModule[97]=C:\Windows\Microsoft.NET\Framework\v4.0.30319\clrjit.dll
LoadedModule[98]=C:\Windows\assembly\NativeImages_v4.0.30319_32\System\fe14a7fe1d472136dc5deec73d296ba9\System.ni.dll
LoadedModule[99]=C:\Windows\assembly\NativeImages_v4.0.30319_32\WindowsBase\11557080b6265b8acc82753c12a39eff\WindowsBase.ni.dll
LoadedModule[100]=C:\Windows\system32\CRYPTSP.dll
LoadedModule[101]=C:\Windows\system32\rsaenh.dll
LoadedModule[102]=C:\Windows\assembly\NativeImages_v4.0.30319_32\PresentationCore\6110db7fbf63fae3df491b0292a5983a\PresentationCore.ni.dll
LoadedModule[103]=C:\Windows\assembly\NativeImages_v4.0.30319_32\Presentatio5ae0f00f#\0687c5b76cddd5a14a74071004df1882\PresentationFramework.ni.dll
LoadedModule[104]=C:\Windows\assembly\NativeImages_v4.0.30319_32\System.Xaml\a8931fb2e0400290b53e054b4e007821\System.Xaml.ni.dll
LoadedModule[105]=C:\Windows\system32\dwrite.dll
LoadedModule[106]=C:\Windows\Microsoft.NET\Framework\v4.0.30319\WPF\wpfgfx_v0400.dll
LoadedModule[107]=C:\Windows\Microsoft.NET\Framework\v4.0.30319\WPF\PresentationNative_v0400.dll
LoadedModule[108]=C:\Windows\Microsoft.NET\Framework\v4.0.30319\nlssorting.dll
LoadedModule[109]=C:\Windows\system32\PROPSYS.dll
LoadedModule[110]=C:\Windows\system32\ntmarta.dll
LoadedModule[111]=C:\Windows\syswow64\WLDAP32.dll
LoadedModule[112]=C:\Windows\system32\iphlpapi.dll
LoadedModule[113]=C:\Windows\system32\WINNSI.DLL
LoadedModule[114]=C:\Windows\system32\dhcpcsvc.DLL
LoadedModule[115]=C:\Windows\system32\dhcpcsvc6.DLL
LoadedModule[116]=C:\Windows\syswow64\CLBCatQ.DLL
LoadedModule[117]=C:\Windows\system32\wbem\wbemprox.dll
LoadedModule[118]=C:\Windows\system32\wbemcomn2.dll
LoadedModule[119]=C:\Windows\system32\RpcRtRemote.dll
LoadedModule[120]=C:\Windows\system32\wbem\wbemsvc.dll
LoadedModule[121]=C:\Windows\system32\wbem\fastprox.dll
LoadedModule[122]=C:\Windows\system32\NTDSAPI.dll
LoadedModule[123]=C:\Windows\SysWOW64\FirewallAPI.dll
LoadedModule[124]=C:\Windows\syswow64\WinInet.DLL
LoadedModule[125]=C:\Windows\syswow64\api-ms-win-downlevel-user32-l1-1-0.dll
LoadedModule[126]=C:\Windows\syswow64\api-ms-win-downlevel-shlwapi-l1-1-0.dll
LoadedModule[127]=C:\Windows\syswow64\api-ms-win-downlevel-version-l1-1-0.dll
LoadedModule[128]=C:\Windows\syswow64\api-ms-win-downlevel-normaliz-l1-1-0.dll
LoadedModule[129]=C:\Windows\syswow64\normaliz.DLL
LoadedModule[130]=C:\Windows\syswow64\iertutil.dll
LoadedModule[131]=C:\Windows\syswow64\api-ms-win-downlevel-advapi32-l1-1-0.dll
LoadedModule[132]=C:\Windows\system32\Secur32.dll
LoadedModule[133]=C:\Windows\system32\api-ms-win-downlevel-advapi32-l2-1-0.dll
LoadedModule[134]=C:\Windows\syswow64\api-ms-win-downlevel-ole32-l1-1-0.dll
LoadedModule[135]=C:\Windows\System32\wship6.dll
LoadedModule[136]=C:\Windows\syswow64\CRYPT32.dll
LoadedModule[137]=C:\Windows\syswow64\MSASN1.dll
LoadedModule[138]=C:\Windows\syswow64\urlmon.dll
LoadedModule[139]=C:\Windows\system32\api-ms-win-downlevel-shlwapi-l2-1-0.dll
LoadedModule[140]=C:\Windows\system32\DNSAPI.dll
LoadedModule[141]=C:\Windows\System32\netprofm.dll
LoadedModule[142]=C:\Windows\System32\nlaapi.dll
LoadedModule[143]=C:\Windows\System32\wshtcpip.dll
LoadedModule[144]=C:\Program Files (x86)\Common Files\Microsoft Shared\Windows Live\WLIDNSP.DLL
LoadedModule[145]=C:\Windows\syswow64\PSAPI.DLL
LoadedModule[146]=C:\Program Files (x86)\Bonjour\mdnsNSP.dll
LoadedModule[147]=C:\Windows\System32\npmproxy.dll
LoadedModule[148]=C:\Windows\system32\rasadhlp.dll
LoadedModule[149]=C:\Windows\System32\fwpuclnt.dll
LoadedModule[150]=C:\Windows\WinSxS\x86_microsoft.windows.common-controls_6595b64144ccf1df_6.0.7601.18837_none_41e855142bd5705d\Comctl32.dll
LoadedModule[151]=C:\Windows\system32\credssp.dll
LoadedModule[152]=C:\Windows\SysWOW64\schannel.dll
LoadedModule[153]=C:\Windows\system32\ncrypt.dll
LoadedModule[154]=C:\Windows\system32\bcrypt.dll
LoadedModule[155]=C:\Windows\SysWOW64\bcryptprimitives.dll
LoadedModule[156]=C:\Windows\syswow64\WINTRUST.dll
LoadedModule[157]=C:\Windows\system32\GPAPI.dll
LoadedModule[158]=C:\Windows\system32\MSXML6.DLL
LoadedModule[159]=C:\Program Files\WIDCOMM\Bluetooth Software\SysWOW64\BtMmHook.dll
LoadedModule[160]=C:\Windows\assembly\NativeImages_v4.0.30319_32\System.Core\00ee33b342bdb1e43546f57cf9b4b998\System.Core.ni.dll
LoadedModule[161]=C:\Windows\assembly\NativeImages_v4.0.30319_32\Presentatio1c9175f8#\db284fa7d92793ad81f09b2813d22748\PresentationFramework.Aero.ni.dll
LoadedModule[162]=C:\Windows\system32\WindowsCodecs.dll
LoadedModule[163]=C:\Windows\system32\aticfx32.dll
LoadedModule[164]=C:\Windows\system32\atiu9pag.dll
LoadedModule[165]=C:\Windows\system32\atiumdag.dll
LoadedModule[166]=C:\Windows\system32\atiumdva.dll
LoadedModule[167]=C:\Windows\assembly\NativeImages_v4.0.30319_32\System.Drawing\41eec1898296247c2db5ca0349968e0e\System.Drawing.ni.dll
LoadedModule[168]=C:\Windows\assembly\NativeImages_v4.0.30319_32\System.Windows.Forms\3fa7114a8f3bafc0b1629481a95c6f3b\System.Windows.Forms.ni.dll
LoadedModule[169]=C:\Windows\system32\WtsApi32.dll
LoadedModule[170]=C:\Windows\system32\WINSTA.dll
LoadedModule[171]=C:\Windows\assembly\NativeImages_v4.0.30319_32\System.Configuration\22fc06b1b63f48a720e8b57be13adb06\System.Configuration.ni.dll
LoadedModule[172]=C:\Windows\assembly\NativeImages_v4.0.30319_32\System.Xml\b8640a66b3cde1da414744cf108b11b3\System.Xml.ni.dll
LoadedModule[173]=C:\Windows\assembly\NativeImages_v4.0.30319_32\Presentatio49d6fefe#\e1e3fbd1aebe16d7c0b28e6d758a9f02\PresentationFramework-SystemXml.ni.dll
LoadedModule[174]=C:\Windows\system32\msctfui.dll
LoadedModule[175]=C:\Windows\assembly\NativeImages_v4.0.30319_32\UIAutomationTypes\ff9c6e5242d4a603baa27498cf974818\UIAutomationTypes.ni.dll
LoadedModule[176]=C:\Windows\system32\UIAutomationCore.dll
LoadedModule[177]=C:\Windows\assembly\NativeImages_v4.0.30319_32\System.Runteb92aa12#\8f156237205ff8ddf2498735b6a98386\System.Runtime.Serialization.ni.dll
LoadedModule[178]=C:\Windows\assembly\NativeImages_v4.0.30319_32\SMDiagnostics\b0c43c58fc21ec2af0232b6ed1719f77\SMDiagnostics.ni.dll
LoadedModule[179]=C:\Windows\assembly\NativeImages_v4.0.30319_32\System.Servd1dec626#\85552e0bf5c3c855a53a8b3349f21dc6\System.ServiceModel.Internals.ni.dll
LoadedModule[180]=C:\Windows\WinSxS\x86_microsoft.windows.gdiplus_6595b64144ccf1df_1.1.7601.18946_none_72d45ee78666ea32\gdiplus.dll
LoadedModule[181]=C:\Windows\system32\atiuxpag.dll
LoadedModule[182]=C:\Windows\system32\atidxx32.dll
LoadedModule[183]=C:\Users\Chris\AppData\Roaming\Dropbox\bin\DropboxExt.28.dll
LoadedModule[184]=C:\Windows\system32\ntshrui.dll
LoadedModule[185]=C:\Windows\system32\srvcli.dll
LoadedModule[186]=C:\Windows\system32\cscapi.dll
LoadedModule[187]=C:\Windows\system32\slc.dll
LoadedModule[188]=C:\Windows\system32\netutils.dll
LoadedModule[189]=C:\Windows\System32\MMDevApi.dll
LoadedModule[190]=C:\Windows\system32\wdmaud.drv
LoadedModule[191]=C:\Windows\system32\ksuser.dll
LoadedModule[192]=C:\Windows\system32\AVRT.dll
LoadedModule[193]=C:\Windows\system32\AUDIOSES.DLL
LoadedModule[194]=C:\Windows\system32\msacm32.drv
LoadedModule[195]=C:\Windows\system32\midimap.dll
LoadedModule[196]=C:\Windows\system32\HID.DLL
LoadedModule[197]=C:\Windows\system32\XInput9_1_0.dll
LoadedModule[198]=C:\P3D\Prepar3D v2\Gauges\TargetInfo.dll
LoadedModule[199]=C:\P3D\Prepar3D v2\radar.dll
LoadedModule[200]=C:\P3D\Prepar3D v2\Modules\FSUIPC4.dll
LoadedModule[201]=C:\Windows\system32\SHFolder.DLL
LoadedModule[202]=C:\P3D\Prepar3D v2\Modules\SimConnectP3D2.dll
LoadedModule[203]=C:\Windows\system32\DINPUT.DLL
LoadedModule[204]=C:\P3D\Prepar3D v2\SODE\SimObjectAnimationModule.dll
LoadedModule[205]=C:\Windows\WinSxS\x86_microsoft.flightsimulator.simconnect_67c7c14424d61b5b_10.0.61259.0_none_55f5ecdc14f60568\SimConnect.dll
LoadedModule[206]=C:\Windows\WinSxS\x86_microsoft.vc80.crt_1fc8b3b9a1e18e3b_8.0.50727.6195_none_d09154e044272b9a\MSVCR80.dll
LoadedModule[207]=C:\Windows\WinSxS\x86_microsoft.vc80.crt_1fc8b3b9a1e18e3b_8.0.50727.6195_none_d09154e044272b9a\MSVCP80.dll
LoadedModule[208]=C:\P3D\Prepar3D v2\SimDirector.dll
LoadedModule[209]=C:\P3D\Prepar3D v2\simpropext.dll
LoadedModule[210]=C:\Windows\assembly\NativeImages_v4.0.30319_32\PresentationUI\e0b66ea4f08f08cd6f30cdf76fd3772c\PresentationUI.ni.dll
LoadedModule[211]=C:\Windows\assembly\NativeImages_v4.0.30319_32\System.Web\8b123086229d00802b5cab77dae28478\System.Web.ni.dll
LoadedModule[212]=C:\Windows\Microsoft.NET\Framework\v4.0.30319\webengine4.dll
LoadedModule[213]=C:\P3D\Prepar3D v2\SlimDX.dll
LoadedModule[214]=C:\Windows\assembly\NativeImages_v4.0.30319_32\UIAutomationProvider\d0cfdc59ebb86ae8e4d532b8ca0912d0\UIAutomationProvider.ni.dll
LoadedModule[215]=C:\P3D\Prepar3D v2\GAUGES\BoeingGeneric.dll
LoadedModule[216]=C:\P3D\Prepar3D v2\GAUGES\Magnetic_Compass.dll
LoadedModule[217]=C:\Windows\system32\msadp32.acm
LoadedModule[218]=C:\Windows\system32\sxs.dll
LoadedModule[219]=C:\Windows\SysWOW64\ieframe.dll
LoadedModule[220]=C:\Windows\SysWOW64\api-ms-win-downlevel-shell32-l1-1-0.dll
LoadedModule[221]=C:\Windows\SysWOW64\mshtml.dll
LoadedModule[222]=C:\Windows\system32\MLANG.dll
LoadedModule[223]=C:\P3D\Prepar3D v2\TritonResources\vc10\win32\TritonCUDA-MT-DLL.dll
LoadedModule[224]=C:\P3D\Prepar3D v2\TritonResources\dll\cudart32_42_9.dll
LoadedModule[225]=C:\P3D\Prepar3D v2\TritonResources\dll\cufft32_42_9.dll
LoadedModule[226]=C:\P3D\Prepar3D v2\TritonResources\vc10\win32\TritonComputeShader-MT-DLL.dll
LoadedModule[227]=C:\Windows\system32\d3dcsx_43.dll
LoadedModule[228]=C:\Windows\assembly\NativeImages_v4.0.30319_32\Presentatio84a6349c#\53f176161bdf838f576dbd183442b408\PresentationFramework-SystemCore.ni.dll
FriendlyEventName=Stopped working
ConsentKey=BEX
AppName=Prepar3D exe
AppPath=C:\P3D\Prepar3D v2\Prepar3D.exe


In VisualPSX:

Code Select Expand

Version=1
EventType=CLR20r3
EventTime=130986301743453181
ReportType=2
Consent=1
ReportIdentifier=2f82109d-c74c-11e5-b397-60a44c64925e
IntegratorReportIdentifier=2f82109c-c74c-11e5-b397-60a44c64925e
WOW64=1
Response.type=4
Sig[0].Name=Problem Signature 01
Sig[0].Value=VisualPsx.exe
Sig[1].Name=Problem Signature 02
Sig[1].Value=7.6.5821.21938
Sig[2].Name=Problem Signature 03
Sig[2].Value=56677fc3
Sig[3].Name=Problem Signature 04
Sig[3].Value=LockheedMartin.Prepar3D.SimConnect
Sig[4].Name=Problem Signature 05
Sig[4].Value=2.5.0.0
Sig[5].Name=Problem Signature 06
Sig[5].Value=54e36923
Sig[6].Name=Problem Signature 07
Sig[6].Value=2ad
Sig[7].Name=Problem Signature 08
Sig[7].Value=2c
Sig[8].Name=Problem Signature 09
Sig[8].Value=PSZQOADHX1U5ZAHBHOHGHLDGIY4QIXHX
DynamicSig[1].Name=OS Version
DynamicSig[1].Value=6.1.7601.2.1.0.256.48
DynamicSig[2].Name=Locale ID
DynamicSig[2].Value=2057
DynamicSig[22].Name=Additional Information 1
DynamicSig[22].Value=0a9e
DynamicSig[23].Name=Additional Information 2
DynamicSig[23].Value=0a9e372d3b4ad19135b953a78882e789
DynamicSig[24].Name=Additional Information 3
DynamicSig[24].Value=0a9e
DynamicSig[25].Name=Additional Information 4
DynamicSig[25].Value=0a9e372d3b4ad19135b953a78882e789
UI[2]=C:\P3D\Version 7 for P3Dv2.5\VisualPsx.exe
UI[3]=VisualPSX for P3D v2 has stopped working
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:\P3D\Version 7 for P3Dv2.5\VisualPsx.exe
LoadedModule[1]=C:\Windows\SysWOW64\ntdll.dll
LoadedModule[2]=C:\Windows\SYSTEM32\MSCOREE.DLL
LoadedModule[3]=C:\Windows\syswow64\KERNEL32.dll
LoadedModule[4]=C:\Windows\syswow64\KERNELBASE.dll
LoadedModule[5]=C:\Windows\syswow64\ADVAPI32.dll
LoadedModule[6]=C:\Windows\syswow64\msvcrt.dll
LoadedModule[7]=C:\Windows\SysWOW64\sechost.dll
LoadedModule[8]=C:\Windows\syswow64\RPCRT4.dll
LoadedModule[9]=C:\Windows\syswow64\SspiCli.dll
LoadedModule[10]=C:\Windows\syswow64\CRYPTBASE.dll
LoadedModule[11]=C:\Windows\system32\apphelp.dll
LoadedModule[12]=C:\Windows\Microsoft.NET\Framework\v4.0.30319\mscoreei.dll
LoadedModule[13]=C:\Windows\syswow64\SHLWAPI.dll
LoadedModule[14]=C:\Windows\syswow64\GDI32.dll
LoadedModule[15]=C:\Windows\syswow64\USER32.dll
LoadedModule[16]=C:\Windows\syswow64\LPK.dll
LoadedModule[17]=C:\Windows\syswow64\USP10.dll
LoadedModule[18]=C:\Windows\system32\IMM32.DLL
LoadedModule[19]=C:\Windows\syswow64\MSCTF.dll
LoadedModule[20]=C:\Windows\system32\VERSION.dll
LoadedModule[21]=C:\Windows\Microsoft.NET\Framework\v4.0.30319\clr.dll
LoadedModule[22]=C:\Windows\system32\MSVCR120_CLR0400.dll
LoadedModule[23]=C:\Windows\assembly\NativeImages_v4.0.30319_32\mscorlib\8e3404c758efee6c7eb3ec52c38e1ed8\mscorlib.ni.dll
LoadedModule[24]=C:\Windows\syswow64\ole32.dll
LoadedModule[25]=C:\Windows\system32\uxtheme.dll
LoadedModule[26]=C:\ProgramData\MyStart Anti-phishing Domain Advisor\mystart_antiphishing.dll
LoadedModule[27]=C:\Windows\syswow64\WS2_32.dll
LoadedModule[28]=C:\Windows\syswow64\NSI.dll
LoadedModule[29]=C:\Windows\syswow64\SHELL32.dll
LoadedModule[30]=C:\Windows\syswow64\OLEAUT32.dll
LoadedModule[31]=C:\Windows\SysWOW64\HsSrv.dll
LoadedModule[32]=C:\Windows\SysWOW64\WINMM.dll
LoadedModule[33]=C:\Windows\SysWOW64\DSOUND.dll
LoadedModule[34]=C:\Windows\SysWOW64\POWRPROF.dll
LoadedModule[35]=C:\Windows\syswow64\SETUPAPI.dll
LoadedModule[36]=C:\Windows\syswow64\CFGMGR32.dll
LoadedModule[37]=C:\Windows\syswow64\DEVOBJ.dll
LoadedModule[38]=C:\Windows\assembly\NativeImages_v4.0.30319_32\System\fe14a7fe1d472136dc5deec73d296ba9\System.ni.dll
LoadedModule[39]=C:\Windows\assembly\NativeImages_v4.0.30319_32\System.Drawing\41eec1898296247c2db5ca0349968e0e\System.Drawing.ni.dll
LoadedModule[40]=C:\Windows\assembly\NativeImages_v4.0.30319_32\System.Windows.Forms\3fa7114a8f3bafc0b1629481a95c6f3b\System.Windows.Forms.ni.dll
LoadedModule[41]=C:\Windows\Microsoft.NET\Framework\v4.0.30319\clrjit.dll
LoadedModule[42]=C:\Windows\assembly\NativeImages_v4.0.30319_32\System.Core\00ee33b342bdb1e43546f57cf9b4b998\System.Core.ni.dll
LoadedModule[43]=C:\Windows\assembly\NativeImages_v4.0.30319_32\Microsoft.V9921e851#\cde53109ff563d01f47875360a3239c4\Microsoft.VisualBasic.ni.dll
LoadedModule[44]=C:\Windows\Microsoft.NET\Framework\v4.0.30319\nlssorting.dll
LoadedModule[45]=C:\Windows\system32\CRYPTSP.dll
LoadedModule[46]=C:\Windows\system32\rsaenh.dll
LoadedModule[47]=C:\Windows\system32\RpcRtRemote.dll
LoadedModule[48]=C:\P3D\Version 7 for P3Dv2.5\LockheedMartin.Prepar3D.SimConnect.dll
LoadedModule[49]=C:\Windows\system32\MSVCR100.dll
LoadedModule[50]=C:\Windows\system32\MSVCP100.dll
LoadedModule[51]=C:\Windows\WinSxS\x86_microsoft.windows.common-controls_6595b64144ccf1df_5.82.7601.18837_none_ec86b8d6858ec0bc\comctl32.dll
LoadedModule[52]=C:\Windows\system32\dwmapi.dll
LoadedModule[53]=C:\Windows\syswow64\psapi.dll
LoadedModule[54]=C:\Windows\system32\RichEd20.DLL
LoadedModule[55]=C:\Windows\WinSxS\x86_microsoft.windows.gdiplus_6595b64144ccf1df_1.1.7601.18946_none_72d45ee78666ea32\gdiplus.dll
LoadedModule[56]=C:\Windows\syswow64\CLBCatQ.DLL
LoadedModule[57]=C:\Windows\SysWOW64\ieframe.dll
LoadedModule[58]=C:\Windows\syswow64\api-ms-win-downlevel-advapi32-l1-1-0.dll
LoadedModule[59]=C:\Windows\syswow64\api-ms-win-downlevel-shlwapi-l1-1-0.dll
LoadedModule[60]=C:\Windows\syswow64\api-ms-win-downlevel-user32-l1-1-0.dll
LoadedModule[61]=C:\Windows\SysWOW64\api-ms-win-downlevel-shell32-l1-1-0.dll
LoadedModule[62]=C:\Windows\syswow64\api-ms-win-downlevel-version-l1-1-0.dll
LoadedModule[63]=C:\Windows\syswow64\api-ms-win-downlevel-normaliz-l1-1-0.dll
LoadedModule[64]=C:\Windows\syswow64\normaliz.DLL
LoadedModule[65]=C:\Windows\syswow64\iertutil.dll
LoadedModule[66]=C:\Windows\WinSxS\x86_microsoft.windows.common-controls_6595b64144ccf1df_6.0.7601.18837_none_41e855142bd5705d\comctl32.dll
LoadedModule[67]=C:\Windows\system32\SXS.DLL
LoadedModule[68]=C:\Windows\system32\api-ms-win-downlevel-shlwapi-l2-1-0.dll
LoadedModule[69]=C:\Windows\system32\PROPSYS.dll
LoadedModule[70]=C:\Windows\syswow64\api-ms-win-downlevel-ole32-l1-1-0.dll
LoadedModule[71]=C:\Windows\syswow64\urlmon.dll
LoadedModule[72]=C:\Windows\syswow64\WININET.dll
LoadedModule[73]=C:\Windows\syswow64\USERENV.dll
LoadedModule[74]=C:\Windows\syswow64\profapi.dll
LoadedModule[75]=C:\Windows\system32\Secur32.dll
LoadedModule[76]=C:\Windows\system32\api-ms-win-downlevel-advapi32-l2-1-0.dll
LoadedModule[77]=C:\Windows\system32\mswsock.dll
LoadedModule[78]=C:\Windows\system32\IPHLPAPI.DLL
LoadedModule[79]=C:\Windows\system32\WINNSI.DLL
LoadedModule[80]=C:\Windows\System32\wship6.dll
LoadedModule[81]=C:\Windows\system32\DNSAPI.dll
LoadedModule[82]=C:\Windows\System32\netprofm.dll
LoadedModule[83]=C:\Windows\System32\nlaapi.dll
LoadedModule[84]=C:\Windows\system32\dhcpcsvc.DLL
LoadedModule[85]=C:\Windows\system32\dhcpcsvc6.DLL
LoadedModule[86]=C:\Windows\System32\wshtcpip.dll
LoadedModule[87]=C:\Program Files (x86)\Common Files\Microsoft Shared\Windows Live\WLIDNSP.DLL
LoadedModule[88]=C:\Program Files (x86)\Bonjour\mdnsNSP.dll
LoadedModule[89]=C:\Windows\System32\npmproxy.dll
LoadedModule[90]=C:\Windows\system32\rasadhlp.dll
LoadedModule[91]=C:\Windows\system32\MSHTML.dll
LoadedModule[92]=C:\Windows\system32\MLANG.dll
LoadedModule[93]=C:\Program Files\WIDCOMM\Bluetooth Software\SysWOW64\BtMmHook.dll
LoadedModule[94]=C:\Windows\system32\msimtf.dll
LoadedModule[95]=C:\Windows\system32\msls31.dll
LoadedModule[96]=C:\Windows\system32\d2d1.dll
LoadedModule[97]=C:\Windows\system32\DWrite.dll
LoadedModule[98]=C:\Windows\system32\dxgi.dll
LoadedModule[99]=C:\Windows\syswow64\WINTRUST.dll
LoadedModule[100]=C:\Windows\syswow64\CRYPT32.dll
LoadedModule[101]=C:\Windows\syswow64\MSASN1.dll
LoadedModule[102]=C:\Windows\system32\d3d11.dll
LoadedModule[103]=C:\Windows\system32\D3D10Warp.dll
LoadedModule[104]=C:\Windows\system32\ntmarta.dll
LoadedModule[105]=C:\Windows\syswow64\WLDAP32.dll
LoadedModule[106]=C:\Windows\system32\windowscodecs.dll
LoadedModule[107]=C:\Windows\assembly\NativeImages_v4.0.30319_32\System.Configuration\22fc06b1b63f48a720e8b57be13adb06\System.Configuration.ni.dll
LoadedModule[108]=C:\Windows\assembly\NativeImages_v4.0.30319_32\System.Xml\b8640a66b3cde1da414744cf108b11b3\System.Xml.ni.dll
LoadedModule[109]=C:\Windows\System32\fwpuclnt.dll
LoadedModule[110]=C:\Windows\SysWOW64\uiautomationcore.dll
LoadedModule[111]=C:\Windows\SysWOW64\OLEACC.dll
LoadedModule[112]=C:\Windows\SysWOW64\jscript9.dll
LoadedModule[113]=C:\Windows\Microsoft.NET\Framework\v4.0.30319\diasymreader.dll
FriendlyEventName=Stopped working
ConsentKey=CLR20r3
AppName=VisualPSX for P3D v2
AppPath=C:\P3D\Version 7 for P3Dv2.5\VisualPsx.exe


[Garry Richards]

Hi Chris,

Thanks for your report. I have checked all my weather-related code and analysed data flow and content but I cannot reproduce the problem you are experiencing. P3D, PSX and VisualPSX all remain stable and respond correctly to weather settings and changes. I ran these tests against both FSX and P3D v2.5 with identical results so I guess the cause is related somehow to your system. I hope you can track it down.

Cheers,

[cavaricooper]

Garry-

I read this in another post and it piqued my interest as it refers to the BEACON switch... where my "fade to black" issue manifests itself.... does it provide any pointers?

Best- C

Francois,

That's caused by VisualPSX; it has some re-positioning "tricks" in which the beacon plays a role.
If you run PSXseeconTraffic without VisualPSX, you will notice that it remains rock stable...

This unlucky interaction is inconvenient, so I think I will remove my test on repositioning. Drawback being that PSXseeconTraffic might run into an exception situation (indicated at the bottom with a red message). You have to exit PSXseeconTraffic then manually (but only in real repositioning situation).

Nico

[Garry Richards]

Sorry, no pointers. Your fade to black issue has been "solved"or at least plausibly explained in « Reply #39 on: Thu, 28 Jan 2016 23:28 » in this thread.

Thanks for drawing my attention to the other thread. I will respond.

Cheers,

[cavaricooper]

Garry:

Are all versions of Simconnect "supposed" to co-exist happily with each other?  After upgrading EZCA (EZDock Camera) to the latest version I seem to be getting a horrid interaction with VisualPSX... the only cure so far has been removing EZCA.... I simply can't remove VisualPSX .

Thoughts...?

TIA

C

PS- checking shows the latest version of EZCA needs Simconnect v.10.0.61259.0.  Would you be aware of any conflicts between Simconnect versions,  or solutions? Basically if I run EZCA and VisualPSX I get a stutter every 5 secs.  If I delete EZCA and use VisualPSX- P3d is silky smooth. If I use EZCA and do not use VisualPSX, P3d is silky smooth. ASN doesnt change the dynamic with its Simconnect version.  I have installed all 3 stock P3d Simconnect msi as well as trying to install the 259.0 version that comes with EZCA's latest.....

[Garry Richards]

Hi Carl,

EZCA can run with FSX so it has to use the original SimConnect.DLL (as confirmed by its version number). The version is locked in when the developer compiles the application from source code. Other versions will be ignored. That's why there are several versions of VisualPSX, each compiled with a different version of the SimConnect.DLL to provide maximum compatibility with either FSX or a specific version of P3D.

Later versions of P3D have retained compatibility with previous versions of SimConnect so that applications compiled for earlier versions can run, but in this case I think the demands of EZCA and VisualPSX are too high to run together on your system. The smooth movements in FSX/P3D that EZCA produces suggest that it uses high speed data transfer just like VisualPSX does. That's why applications that can communicate more slowly, like ASN, don't cause this problem.

I don't know whether the more recent versions of SimConnect produced for P3D v2.5 and 3.0 would overcome the difficulty. That would require multiple versions of EZCA to be compiled, specific to each version of P3D.

Cheers,

[cavaricooper]

Garry-

I just installed a D-Link Gigabit switch to network all the computers together.  Prior to that they were running on 10/100.  Will test this weekend and report back.

I already installed all 3 versions of Simconnect that come with P3d v2.5.

Ta!

C

PS- Is there a source for the Simconnect file in P3d v3 and v3.1 that is legally available?  I did find the SDK available from LM, however, looking inside the folders did not reveal a simconnect.msi......

[JRBarrett]

Hi Scud, Derek and everyone,

Another feature that I didn't include in the notes is that the offset processing now accepts only exact matches to the airport and runway names between FSX/P3D and PSX. Previously if there wasn't an exact name match it would try to find the best match from nearby airports and runways. This sometimes led to incorrect matching so I dropped the feature. You will now get either the correct offset or none.

Hi Garry. I am using the latest version of VisualPSX (8.7), in P3D Version 3.2, and it is working extremely well. However, I ran into a problem that may be related to the new feature mentioned above - where runways.psx will skip airports which are not an exact match to PSX.

I ran runwayspsx after initial install, choosing the P3D Version 3 64 bit option. I did a flight from Victorville (KVCV) to KLAX. KVCV is a default airport, and it appeared by name on the Status screen of VPSX after I selected my departure runway 35.

I landed on runway 25L at KLAX. Everything appeared to work perfectly. The runway in P3D was perfectly aligned vertically and laterally with its representation in the windscreen of PSX during landing. However, after I parked, set the parking brake and turned off the beacon switch, the VPSX Status screen did show that the position was locked, but there was an amber text message that said that no P3D airport could be identified, and no offset was applied.

My KLAX is not default - it is the FSDT add-on. I noticed that in the scenery library, FSDT uses a non-standard naming convention for the KLAX scenery files. The folder is named "KLAXV2" rather than simply "KLAX". Probably to differentiate it from their original Version 1 release.

I am wondering if runwayspsx may have skipped over this scenery when it was run because of the non-standard folder name? As an experiment, I disabled FSDT KLAX by setting it to "False" in the scenery config using notepad, then ran runwayspsx again. I then re-enabled the scenery.cfg entry, started P3D and PSX. Now, VPSX does recognize that I am at KLAX. The runways program probably picked up the default KLAX.

I was wondering if, in a future release, it would be possible to have the skipping of non-standard airport or runway names made a user-selectable option? I have several other payware airport add-ons in P3D that also use a non-standard folder name for their location in the scenery.cfg, and I fear those airports may also have been skipped over when runwayspsx was run.

I would rather accept the risk of possibly getting an incorrect offset applied, than to try to land at an airport with no offsets at all. It did work out OK at FSDT KLAX despite the fact that VPSX did not know what airport I was landing at, but might not do so when landing or departing from other add-ons, that may have been skipped over.

Regards,

Jim Barrett

[G-CIVA]

Did you have all of your addon scenery activated BEFORE you run RunwaysPSX?

Whenever I install a new scenery I go through a set routine of making sure all additional scenery is activated, then I boot p3D once before closing it.

Once I have done this & because I have Orbx products installed I run the Airport Elevation Correction Tool from Orbx Global Vector to smooth out any terrain elevation issues that may occur with the newly installed scenery vs Orbx products.

I then run p3D once again before closing it down.

I then fire up RunwaysPSX to do an entire scan.

After that I de activate all the addon scenery I do not need.

That way RunwaysPSX has a entire 'picture' of all of the airports inside my p3D installation.

It's important to remember at this stage to place the file that RunwaysPSX creates into the correct folder where visualPSX & trafficPSX 'live' - this might even be on a different computer if like me you are running visualPSX & trafficPSX across a multi computer network.

I also use this excellent scenery configuration editor, which allows you to edit the scenery configuration file without FSX/p3D running.  It enables you to quickly add/delete/enable/disable scenery in the scenery configuration file quickly.  Once you have grasped it you will find it is a must have.  Although it was originally designed for FS2004 it works perfectly in FSX & p3D.

http://www.prepar3d.com/forum/viewtopic.php?t=113495

Using this method I have seen Garys software blend all the nicks & niggles & offsets inside the FSX/p3D world seamlessly into the PSX world time after time.

Hope this helps.

[JRBarrett]

Did you have all of your addon scenery activated BEFORE you run RunwaysPSX?

Whenever I install a new scenery I go through a set routine of making sure all additional scenery is activated, then I boot p3D once before closing it.

Once I have done this & because I have Orbx products installed I run the Airport Elevation Correction Tool from Orbx Global Vector to smooth out any terrain elevation issues that may occur with the newly installed scenery vs Orbx products.

I then run p3D once again before closing it down.

I then fire up RunwaysPSX to do an entire scan.

After that I de activate all the addon scenery I do not need.

That way RunwaysPSX has a entire 'picture' of all of the airports inside my p3D installation.

It's important to remember at this stage to place the file that RunwaysPSX creates into the correct folder where visualPSX & trafficPSX 'live' - this might even be on a different computer if like me you are running visualPSX & trafficPSX across a multi computer network.

I also use this excellent scenery configuration editor, which allows you to edit the scenery configuration file without FSX/p3D running.  It enables you to quickly add/delete/enable/disable scenery in the scenery configuration file quickly.  Once you have grasped it you will find it is a must have.  Although it was originally designed for FS2004 it works perfectly in FSX & p3D.

http://www.prepar3d.com/forum/viewtopic.php?t=113495

Using this method I have seen Garys software blend all the nicks & niggles & offsets inside the FSX/p3D world seamlessly into the PSX world time after time.

Hope this helps.

Yes, I definitely had all my add-on scenery activated, and the file generated by runwayspsx is in the correct folder. (Visual PSX will crash if it is not).

VPSX works very well indeed in P3D. I've been using it since it first came out - (at that time in FSX), and each new version gets better and better.

In this case, VPSX is not recognizing FS Dream Team KLAX as being a legitimate P3D airport, and thus reports that it cannot apply any offsets. It does work well at other airports which are pure default, and I do not as yet know if any other add-on airport sceneries (of which I have quite a few)  may also have this issue.

I know that an earlier version of VPSX did formerly recognize the same FSDT KLAX scenery as being KLAX - (at least it did in FSX).

If I disable FSDT KLAX in the scenery.cfg, which allows the lower-priority default KLAX to load instead, then VSPX does recognize the airport.

Since an earlier version of VPSX used to recognize this particular add-on scenery, and in light of Garry's mention that he made his software more "strict" about the naming conventions used for airports and runways to avoid possible offset bugs, I thought that this change may be responsible for the failure to recognize FSDT KLAX, since the actual scenery folder where all the BGLs live is named "KLAX_V2", rather than "KLAX".

On the other hand, FSDT sceneries use the somewhat infamous Couatl DRM system, which is always running in the background in P3D to keep the various FSDT sceneries in an activated state, and possibly that is interfering in some way. (Couatl is constantly being updated by its author).

Despite the apparent lack of applied offsets at FSDT KLAX, the PSX and P3D aircraft are aligned perfectly with each other in this scenery when I run PSX and P3D linked via VPSX.   

[Garry Richards]

Hi Jim and Steve,

That's an unusual problem. I can't offer a solution yet but I expect to have time to investigate over the next week. I can tell you that the folder names for addon airports are irrelevant. They can be anything and located anywhere so long as they are referred to in the working copy of the scenery.cfg file.

The airport name and code are buried and encoded in one of the .bgl files, as are the runway identifiers. When you run runwaysPSX you should see the folders being processed and the airport being selected, but the details may flash past too quickly to read.

When you park PSX after landing and turn off the beacons VisualPSX goes into lock mode and removes any offset that was in place by moving PSX to the FSX/P3D position. The only error that you have positively identified so far is VisualPSX not finding a nearby airport even though it is at one. It is possible that there was an offset in place before landing, unless you have seen otherwise. There could be several reasons for the error and they will form the basis of my investigation.

Cheers,

[JRBarrett]

Hi Jim and Steve,

That's an unusual problem. I can't offer a solution yet but I expect to have time to investigate over the next week. I can tell you that the folder names for addon airports are irrelevant. They can be anything and located anywhere so long as they are referred to in the working copy of the scenery.cfg file.

The airport name and code are buried and encoded in one of the .bgl files, as are the runway identifiers. When you run runwaysPSX you should see the folders being processed and the airport being selected, but the details may flash past too quickly to read.

When you park PSX after landing and turn off the beacons VisualPSX goes into lock mode and removes any offset that was in place by moving PSX to the FSX/P3D position. The only error that you have positively identified so far is VisualPSX not finding a nearby airport even though it is at one. It is possible that there was an offset in place before landing, unless you have seen otherwise. There could be several reasons for the error and they will form the basis of my investigation.

Cheers,

I later performed a runway 25R departure from the FSDT KLAX scenery, and again, my windscreen view on the 25R centerline in lining up for takeoff was in perfect sync between PSX and P3D.

It's possible I suppose that there is little if any offset between the PSX and FSX positions at this particular airport, even without corrections being applied.

I also run Pete Dowson's makerwys.exe on my P3D machine, which produces quite a few files used by various add-ons. One of the generated files is (I believe) called something like runways.dat, and is a very large formatted text file with all sorts of extracted info for every stock and add-on airport. I loaded it into Wordpad, and did a quick search on "KLAX". It found two sections relating to both the FSDT add-on scenery, and also the original stock P3D KLAX. Might be some info in there relating to the internal naming conventions being used in the two versions. Would be glad to zip that file up and send it to you if you would like to peruse it.

Jim Barrett

[Garry Richards]

Ok, I have made some discoveries:

1 The FSDT KLAX data is loading correctly into the RunwaysPSX data file.

2 VisualPSX applied an automatic offset correctly on approach to the FSDT KLAX 24L.

3 VisualPSX is behaving erratically when setting offsets on the ground.

4 The same errors seem to occur in VisualPSX whether the FSDT scenery or the standard scenery is used but I need to test further to be sure.

More to come.

[JRBarrett]

Ok, I have made some discoveries:

1 The FSDT KLAX data is loading correctly into the RunwaysPSX data file.

2 VisualPSX applied an automatic offset correctly on approach to the FSDT KLAX 24L.

3 VisualPSX is behaving erratically when setting offsets on the ground.

4 The same errors seem to occur in VisualPSX whether the FSDT scenery or the standard scenery is used but I need to test further to be sure.

More to come.

Interesting! It would explain why everything appeared to line up so well, despite the error message. Thanks for looking into this.