Jump to content
The simFlight Network Forums

Recommended Posts

Posted

Does the same fix that you use for FSX g3d.dll crashes work in Prepar3D? It seems myself and other users are experiencing g3d.dll crashes in prepar3d.

No.

I'm not in favour of working around bugs in code which is being actively supported and developed, because then it may never be fixed, and it should be. I'd rather everyone who experiences these crashes submit the appropriate bug reports to LM.

If they want to know what my workaround patch did, I can by all means tell them what i checked, though it was pure luck that it worked with no evident adverse results.

Regards

Pete

Posted

I'll forward that along I guess, then.

Thanks. I looked at the reports, and the crash at offset BA66D is identical to the one which FSUIPC patches around in FSX SP1 and ACC versions of G3D.DLL. I can easily make this patch work in P3D 1.3 as well -- but as explained above, I'd rather LM fixed the problem at source, as all my patch does is force the function to exit with a "false" result if the value about to be used would give an access violation. It was pure luck in FSX that this had no evident adverse affect. I assume that something wasn't drawn on that pass which otherwise would have been (apart from the crash).

If LM support agree, I will add the workaround to an interim update of FSUIPC4, but i would hope they would fix this in their next update in any case, and if they do I'd like direct confirmation so i can rmove the work-around.

I added this reply to the P3D thread.

Regards

Pete

Posted

Hi Pete,

I hate to bump this, but it doesn't look like LM responded at all in the thread. P3D runs significantly better for me than FSX, so I'd really like to convert to it, however the g3d.dll crashes seem more common. If I can get rid of those, I'd be exceptionally happy.

In the absence of comments from LM, and if it's a quick fix for you, I'd really appreciate it if you could put the fix in as it would make a world of a difference. I certainly won't begrudge you if you don't wish to, since your reasoning is valid and it's your program anyways, but I'd appreciate it. :)

Thanks,

-stefan

Posted

I hate to bump this, but it doesn't look like LM responded at all in the thread. P3D runs significantly better for me than FSX, so I'd really like to convert to it, however the g3d.dll crashes seem more common. If I can get rid of those, I'd be exceptionally happy.

In the absence of comments from LM, and if it's a quick fix for you, I'd really appreciate it if you could put the fix in as it would make a world of a difference. I certainly won't begrudge you if you don't wish to, since your reasoning is valid and it's your program anyways, but I'd appreciate it. :)

I've just written directly to my contact in LM. I'll get back to you when I have a reply.

Regards

Pete

Posted

I've just written directly to my contact in LM. I'll get back to you when I have a reply

I got a reply and permission directly. Please download FSUIPC4825

and test it for me -- I haven't got any G3D crashes here. When you confirm, I'll upload it to Download Links and you can notify folks in that P3D Forum thread. Okay?

Regards

Pete

Posted

Alright, I've flown across most of new zealand and no g3d.dll crash, which I got pretty much every other time. I think it's good. Does it log traps anywhere?

Yes, there's a summary at the end of the log after the Sm has closed. There may also be one or more lines showing:

*** G3D bad pointer trapped and crash prevented ***

but this is only logged at most once per second, to aboid filling the log if there's a whole bunch. The summary contains the true count.

Regards

Pete

Posted

Appears to work to me!

********* FSUIPC4, Version 4.825 by Pete Dowson *********
User Name="REDACTED"
User Addr="REDACTED"
FSUIPC4 Key is provided
WideFS7 Key is provided
Running inside Prepar3D on Windows 7
Module base=120F0000
	  687 System time = 25/04/2012 17:36:22
	  733 FLT UNC path = "\\MEGATRON\Users\stefan\Documents\Prepar3D Files\"
	  733 Trying C:\Prepar3D\Modules\SimConnectP3D.dll
	  749 Found it: trying to connect
	  765 FS UNC path = "C:\Prepar3D\"
	 1108 LogOptions=00000000 00000001
	 1108 Wind smoothing fix is fully installed
	 1108 G3D.DLL fix attempt installed ok
	 1108 SimConnect_Open succeeded: waiting to check version okay
	 1108 Trying to use SimConnect Prepar3D
	 4009 Running in "Lockheed Martin® Prepar3D®", Version: 1.3.3708.0 (SimConnect: 1.3.0.0)
	 4009 Initialising SimConnect data requests now
	 4009 FSUIPC Menu entry added
	 4041 C:\Prepar3D\FLIGHTS\OTHER\Prepar3D.FLT
	 4041 C:\Prepar3D\SimObjects\Airplanes\Mooney_Bravo\Mooney_Bravo.AIR
    48204 System time = 25/04/2012 17:37:09, Simulator time = 11:00:02 (15:00Z)
    48267 Aircraft="Mooney Bravo With G1000"
    48891 Starting everything now ...
    50186 Advanced Weather Interface Enabled
   320691 *** G3D bad pointer trapped and crash prevented ***
  1250972 *** G3D bad pointer trapped and crash prevented ***
  6034634 Sim stopped: average frame rate for last 5867 secs = 29.8 fps
  7884509 *** G3D bad pointer trapped and crash prevented ***
  7964522 *** G3D bad pointer trapped and crash prevented ***
  8173532 Sim stopped: average frame rate for last 2126 secs = 30.0 fps
  8185934 System time = 25/04/2012 19:52:47, Simulator time = 09:13:34 (22:13Z)
  8185934 *** FSUIPC log file being closed
Average frame rate for running time of 8010 secs = 29.8 fps
G3D fix: Passes 1399489, Null pointers 0, Bad pointers 8, Separate instances 4
Memory managed: 3313 Allocs, 3313 Freed
********* FSUIPC Log file closed ***********

-stefan

Posted

Appears to work to me!

Good! Thanks for testing. The current release is 4.827 (other urelated corrections, to do with Lua). I'll build a new Install package tomorrow. Meanwhile you can notify the others in the P3D Forum thread.

Best Regards

Pete

Posted

The version is 4.827 in Prepar3D on Windows 7 64Bit

There have been no other reports of any crashes with FSUIPC in P3D.

As always with any problems I need to see logs. You'll find the Install log and the FSUIPC4 log in the P3D Modules folder. I also need to know the version of P3D (is it 1.3?) and a fuller description of the crash -- i.e. what leads to it, what actually happens and what, if any, information you can glean about it. Ideally the module name and offset address. These will be in the Windows application logs if Windows detected the crash.

You can paste logs and other data in a reply here.

Regards

Pete

Posted (edited)

Hi Peter

Version 1.3 for the P3D and the crash starts before the scenery and terrian loads up.(no memory address conflict or similar)

There is a Windows remark of problems and closing down.(see below)

p3d.png

Uploaded with ImageShack.us

Here are the files:

********* FSUIPC4, Version 4.827 by Pete Dowson *********

User Name="David Williams"

User Addr="david_wi@netvision.net.il"

FSUIPC4 Key is provided

WIDEFS7 not user registered, or expired

Running inside Prepar3D on Windows 7

Module base=13D10000

858 System time = 29/04/2012 20:00:57

858 FLT path = "C:\Users\David\Documents\Prepar3D Files\"

858 Trying E:\Program Files (x86)\Lockheed Martin\Prepar3D\Modules\SimConnectP3D.dll

889 Found it: trying to connect

904 FS path = "E:\Program Files (x86)\Lockheed Martin\Prepar3D\"

1856 LogOptions=00000000 00000001

1856 Wind smoothing fix is only partially installed

1856 SimConnect_Open succeeded: waiting to check version okay

1856 Trying to use SimConnect Prepar3D

4664 Exception 5 "VERSION_MISMATCH", Ref 1, Version 2.0: Open: SimConnect Version incorrect!

4664 Trying another version of SimConnect ...

4758 Trying E:\Program Files (x86)\Lockheed Martin\Prepar3D\Modules\SimConnectP3D.dll

4758 Found it: trying to connect

4758 SimConnect_Open succeeded: waiting to check version okay

Installer for FSUIPC4.DLL version 4.827

Looking in registry for SOFTWARE\Microsoft\Microsoft Games\Flight Simulator\10.0 install path:

HKEY_LOCAL_MACHINE\(null)

Parameter"SetupPath"

... >>> OK! FOUND FSX! <<< ...

Looking in registry for SOFTWARE\Microsoft\Microsoft ESP\1.0 install path:

HKEY_LOCAL_MACHINE\(null)

Parameter"SetupPath"

Not there, so looking in:

HKEY_CURRENT_USER\ESP

Parameter"AppPath"

... NOT found! ...

Looking in registry for SOFTWARE\LockheedMartin\Prepar3D install path:

HKEY_LOCAL_MACHINE\(null)

Parameter"SetupPath"

... >>> OK! FOUND Prepar3D! <<< ...

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

INSTALLATION FOR FSX:

SetupPath="C:\Program Files (x86)\Microsoft Games\Microsoft Flight Simulator X\"

Checking version of FSX.EXE:

... Version 10.0.61637.0 (Need at least 10.0.60905.0)

Checking compatibility with installed SimConnect:

Found SimConnect build 60905 (Original)

Found SimConnect build 61242 (SP1 May07)

Found SimConnect build 61259 (Acc/SP2 Oct07)

Checking if there's already a version of FSUIPC4 installed in:

C:\Program Files (x86)\Microsoft Games\Microsoft Flight Simulator X\Modules\FSUIPC4.DLL

... Version 4.827 found.

FSX Modules folder already exists.

Okay -- installed FSUIPC4 into "C:\Program Files (x86)\Microsoft Games\Microsoft Flight Simulator X\Modules\FSUIPC4.DLL"

Looking for the current user's Application Data path:

... found as "C:\Users\David\AppData\Roaming"

Now finding \Microsoft\FSX\FSX.CFG for all users, including this one

Looking in "C:\Users\All Users\AppData\Roaming"

... No FSX.CFG there

Looking in "C:\Users\David\AppData\Roaming"

Found FSX.CFG in "C:\Users\David\AppData\Roaming\Microsoft\FSX\FSX.CFG"

Now checking DLL.XML ...

... There is a previous DLL.XML, checking for FSUIPC4 section.

... FSUIPC4 section already exists but will be replaced.

... FSUIPC4 section of DLL.XML written okay

Now checking for a SimConnect.XML file ...

... There is a SimConnect.XML, checking for "local" section.

... "local" section already exists, file not modified.

Looking in "C:\Users\Default\AppData\Roaming"

... No FSX.CFG there

Looking in "C:\Users\Default User\AppData\Roaming"

... No FSX.CFG there

Looking in "C:\Users\Public\AppData\Roaming"

... No FSX.CFG there

Looking in "C:\Users\TEMP\AppData\Roaming"

... No FSX.CFG there

Looking in "C:\Users\UpdatusUser\AppData\Roaming"

... No FSX.CFG there

Looking in "C:\Users\UpdatusUser.David-PC\AppData\Roaming"

... No FSX.CFG there

"Modules\FSUIPC Documents" folder already exists.

Now installing additional files into the "Modules\FSUIPC Documents" folder:

Installed "FSUIPC4 User Guide.pdf" okay

Installed "FSUIPC4 for Advanced Users.pdf" okay

Installed "FSUIPC4 History.pdf" okay

Installed "List of FSX controls.pdf" okay

Installed "GlobalSign Root.exe" okay

Installed "FSUIPC Lua Library.pdf" okay

Installed "FSUIPC Lua Plug-Ins.pdf" okay

Installed "Lua License.pdf" okay

Installed "Lua Plugins for VRInsight Devices.pdf" okay

Installed "LuaFileSystem.pdf" okay

Installed "Example LUA plugins.zip" okay

FSUIPC4.DLL installed and signature checked out okay!

Deleted GlobalSign Root fix program ... no longer relevant

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

INSTALLATION FOR Prepar3D:

SetupPath="E:\Program Files (x86)\Lockheed Martin\Prepar3D"

Checking version of Prepar3D.EXE:

... Version 1.2.3253.0 (Need at least 1.0.677.0)

Checking compatibility with installed SimConnect:

Found SimConnect build 60905 (Original)

Found SimConnect build 195 (ESP Orig)

Found SimConnect build 61242 (SP1 May07)

Found SimConnect build 61259 (Acc/SP2 Oct07)

Checking if there's already a version of FSUIPC4 installed in:

E:\Program Files (x86)\Lockheed Martin\Prepar3D\Modules\FSUIPC4.DLL

... No previous valid version found.

Prepar3D Modules folder already exists.

Okay -- installed FSUIPC4 into "E:\Program Files (x86)\Lockheed Martin\Prepar3D\Modules\FSUIPC4.DLL"

Looking for the current user's Application Data path:

... found as "C:\Users\David\AppData\Roaming"

Now finding \Lockheed Martin\Prepar3D\Prepar3D.CFG for all users, including this one

Looking in "C:\Users\All Users\AppData\Roaming"

... No Prepar3D.CFG there

Looking in "C:\Users\David\AppData\Roaming"

Found Prepar3D.CFG in "C:\Users\David\AppData\Roaming\Lockheed Martin\Prepar3D\Prepar3D.CFG"

Now checking DLL.XML ...

... There is a previous DLL.XML, checking for FSUIPC4 section.

... FSUIPC4 section already exists but will be replaced.

... FSUIPC4 section of DLL.XML written okay

Now checking for a SimConnect.XML file ...

... No SimConnect.XML file found. This is okay.

Looking in "C:\Users\Default\AppData\Roaming"

... No Prepar3D.CFG there

Looking in "C:\Users\Default User\AppData\Roaming"

... No Prepar3D.CFG there

Looking in "C:\Users\Public\AppData\Roaming"

... No Prepar3D.CFG there

Looking in "C:\Users\TEMP\AppData\Roaming"

... No Prepar3D.CFG there

Looking in "C:\Users\UpdatusUser\AppData\Roaming"

... No Prepar3D.CFG there

Looking in "C:\Users\UpdatusUser.David-PC\AppData\Roaming"

... No Prepar3D.CFG there

"Modules\FSUIPC Documents" folder already exists.

Now installing the Prepar3D SimConnect interface for FSUIPC4 into the "Modules" folder:

Installed "SimConnectP3D.dll" okay

Now installing additional files into the "Modules\FSUIPC Documents" folder:

Installed "FSUIPC4 User Guide.pdf" okay

Installed "FSUIPC4 for Advanced Users.pdf" okay

Installed "FSUIPC4 History.pdf" okay

Installed "List of FSX controls.pdf" okay

Installed "GlobalSign Root.exe" okay

Installed "FSUIPC Lua Library.pdf" okay

Installed "FSUIPC Lua Plug-Ins.pdf" okay

Installed "Lua License.pdf" okay

Installed "Lua Plugins for VRInsight Devices.pdf" okay

Installed "LuaFileSystem.pdf" okay

Installed "Example LUA plugins.zip" okay

FSUIPC4.DLL installed and signature checked out okay!

Deleted GlobalSign Root fix program ... no longer relevant

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

All installer tasks completed.

*************** End of Install Log ***************

Edited by david1952
Posted

Version 1.3 for the P3D and the crash starts before the scenery and terrian loads up.(no memory address conflict or similar)

There is a Windows remark of problems and closing down.(see below)

There's really no point in providing an unreadable image. You need to go to the Windows logs and provide the information on the crash

If you don't know where to look, press your Windows Start button, type "Event viewer" into the search edit box and press return. When the viewer appears select "Windows Logs" then "Application". Scroll down looking for a red ! marking an error, and the one referring to the Prepar3D process. -- you can see all the details in the pane below when you select it. If you double clcik it you'll get a window with a "copy" button so you can copy the text ready to paste into a message.

From the Log, the main problem appears to be that your P3D installation is corrupted:

1856 Trying to use SimConnect Prepar3D

4664 Exception 5 "VERSION_MISMATCH", Ref 1, Version 2.0: Open: SimConnect Version incorrect!

4664 Trying another version of SimConnect ...

4758 Trying E:\Program Files (x86)\Lockheed Martin\Prepar3D\Modules\SimConnectP3D.dll

4758 Found it: trying to connect

4758 SimConnect_Open succeeded: waiting to check version okay

That error can only possibly occur if the installation is bad.

You could try renaming the file "SimConnectP3D.dll" or moving it out of the Prepar3D Modules folder. This will force FSUIPC to use the ESP version of SimConnect which you also have installed according to the Install log..

INSTALLATION FOR Prepar3D:

SetupPath="E:\Program Files (x86)\Lockheed Martin\Prepar3D"

Checking version of Prepar3D.EXE:

... Version 1.2.3253.0 (Need at least 1.0.677.0)

And this shows that you are NOT using version 1.3 of P3D, or at least that it isn't installed correctly. You have 1.2. The version number for version 1.3 is 1.3.3708.0.

I strongly suggest you update to version 1.3.

Regards

Pete

Posted

Hi Peter

You are right,the version is 1.2 and not 1.3

Here is the Windows log:

Log Name: Application

Source: .NET Runtime

Date: 29/04/2012 21:50:00

Event ID: 1026

Task Category: None

Level: Error

Keywords: Classic

User: N/A

Computer: David-PC

Description:

Application: Prepar3D.exe

Framework Version: v4.0.30319

Description: The process was terminated due to an unhandled exception.

Exception Info: System.InvalidOperationException

Stack:

at System.Windows.Threading.Dispatcher.VerifyAccess()

at MS.Internal.Media.VisualTreeUtils.AsVisual(System.Windows.DependencyObject, System.Windows.Media.Visual ByRef, System.Windows.Media.Media3D.Visual3D ByRef)

at MS.Internal.Media.VisualTreeUtils.AsNonNullVisual(System.Windows.DependencyObject, System.Windows.Media.Visual ByRef, System.Windows.Media.Media3D.Visual3D ByRef)

at System.Windows.Media.VisualTreeHelper.GetChildrenCount(System.Windows.DependencyObject)

at System.Windows.BroadcastEventHelper.AreThereLoadedChangeHandlersInSubtree(MS.Internal.FrameworkObject ByRef)

at System.Windows.BroadcastEventHelper.UpdateHasLoadedChangeHandlerFlagInAncestry(System.Windows.DependencyObject, Boolean)

at System.Windows.FrameworkElement.OnRemoveHandler(System.Windows.RoutedEvent, System.Delegate)

at System.Windows.UIElement.RemoveHandler(System.Windows.RoutedEvent, System.Delegate)

at AwesomiumSharp.Windows.Controls.WebControl.Close()

at AwesomiumSharp.Windows.Controls.WebControl.Finalize()

Event Xml:

<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">

<System>

<Provider Name=".NET Runtime" />

<EventID Qualifiers="0">1026</EventID>

<Level>2</Level>

<Task>0</Task>

<Keywords>0x80000000000000</Keywords>

<TimeCreated SystemTime="2012-04-29T18:50:00.000000000Z" />

<EventRecordID>7989</EventRecordID>

<Channel>Application</Channel>

<Computer>David-PC</Computer>

<Security />

</System>

<EventData>

<Data>Application: Prepar3D.exe

Framework Version: v4.0.30319

Description: The process was terminated due to an unhandled exception.

Exception Info: System.InvalidOperationException

Stack:

at System.Windows.Threading.Dispatcher.VerifyAccess()

at MS.Internal.Media.VisualTreeUtils.AsVisual(System.Windows.DependencyObject, System.Windows.Media.Visual ByRef, System.Windows.Media.Media3D.Visual3D ByRef)

at MS.Internal.Media.VisualTreeUtils.AsNonNullVisual(System.Windows.DependencyObject, System.Windows.Media.Visual ByRef, System.Windows.Media.Media3D.Visual3D ByRef)

at System.Windows.Media.VisualTreeHelper.GetChildrenCount(System.Windows.DependencyObject)

at System.Windows.BroadcastEventHelper.AreThereLoadedChangeHandlersInSubtree(MS.Internal.FrameworkObject ByRef)

at System.Windows.BroadcastEventHelper.UpdateHasLoadedChangeHandlerFlagInAncestry(System.Windows.DependencyObject, Boolean)

at System.Windows.FrameworkElement.OnRemoveHandler(System.Windows.RoutedEvent, System.Delegate)

at System.Windows.UIElement.RemoveHandler(System.Windows.RoutedEvent, System.Delegate)

at AwesomiumSharp.Windows.Controls.WebControl.Close()

at AwesomiumSharp.Windows.Controls.WebControl.Finalize()

</Data>

</EventData>

</Event>

Posted

You are right,the version is 1.2 and not 1.3

You really do need to update. The crash is almost certainly because the SimConnectP3D.DLL installed with FSUIPC4 now is for 1.3 only. Remove it from the Modules folder and it should be okay using the ESP SimConnect you still have installed.

if it isn't you need to send the Windows error log to Lockheed Martin. However, they will no doubt tell you that 1.2 is no longer supported.

Next time i make a new Installer update I shall need to check for the older version and delete my interfacing Simconnect DLL automatically. but I honestly didn't think it would happen. with an ongoing development like P3D.

Regards

Pete

Posted

Hi Peter

Yes,when I moved the SimConnectP3D.DLL from the Modules folder all went fine.

But never the less,I installed ver 1.3 of the P3D and all work ok now. (it's all in your credit :cool: )

Thanks for all your patience.

Bye,

David

  • 2 months later...

Create an account or sign in to comment

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

Create an account

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

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
×
×
  • Create New...

Important Information

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