Jake, are you using any of the bloom mods at all? I have had many crashes previously and decided to reinstall windows and a fresh copy of Prepar3d. What I am doing is installing one addon at a time and waiting (even if it takes a couple of weeks for each). I think that some of these bloom mods do not play nice with the graphic engine in either FSX ot Prepar3d. I have installed and so far have had no issues with crashes (touch wood). I'm still monitoring it though.

Hi guys,

No. I did use Shade in FSX but haven't even tried to get it working in P3D. I can't get ENB to work in FSX so again, haven't tried it.

List of addons in P3D:

FSDT P3D compatible airports: KLAX; KJFK; GSX and the SA Addon manager
ORBX Au SBSL
RealAir Beech Duke T ("installed" to P3d using F1 reg tool)
PMDG NGX (ported acros using edited xml.dll)
REX (not "installed" as such, I havbe merely pointed it to my P3D folders)

Also, this happened with no weather injection taking place. I have another error that happened after REX texture injection for which I'll open a new thread in the appropriate forum.

I am going to run a totally vanilla P3D for a few weeks to see if I can make it happen again. I'm changing my whole PC at the moment so will leave P3D alone when it goes on the new box.

From my experiences with FSX, this was like the old UIAutmationCore issues of right-clicking..It seemed to correlate with my mouse click back onto the radio unit..Possible a non-P3D compatible gauge or gauge texture or perhaps dll file in the Duke? (I know you can't/won't know this as you don't have it)

Thanks for the speedy replies, guys. Most impressed (with LM and P3D - keep it up!)

best

jake

Here is a post from Pete Dowson over at avsim on how he used FSUIPC to stop the g3d.dll crashes in fsx.

It may be helpful.

http://forum.avsim.net/topic/353179-gd3dllhelp/page__st__575#entry2178291

here is my event viewer log, Orbx Scenery ( PNW and NRM ) and Captain Sim 757-200 flying CYYC to KSEA at FL300, using a terrain lod of 6.5

Faulting application name: Prepar3D.exe, version: 1.3.3708.0, time stamp: 0x4f516cc9
Faulting module name: g3d.dll, version: 0.0.0.0, time stamp: 0x4f516d2d
Exception code: 0xc0000005
Fault offset: 0x000ba66d
Faulting process id: 0x109c
Faulting application start time: 0x01cd0c487e67fe87
Faulting application path: E:\Prepar3D\Prepar3D.exe
Faulting module path: E:\Prepar3D\g3d.dll
Report Id: 1e4981de-7842-11e1-8741-1c6f65906ddd

Sadly my gfx card died on me so testing for more g3d crashes is impossible at the moment until i get a new card.

I also got this yesterday about 40 minutes into a flight originating at NZMF heading east and it crashed near Glenorchy. This was using ORBX terrain and the aerosoft katana copied over from FSX. REX clouds were installed but no weather was being injected.

Basic specs:
i7 2600k @4.6ghz
8GB RAM
GTX 570

latest FSUIPC is installed.

-stefan

Have had this twice in two days.. I ignored it the first time hoping it was just some fluke, then just happened today flying out of Orbx 3W5 and made it half way to KHQM before the sim G3D.dll crashed.

Hi,

Got a response from Pete Dowson:

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

Hopefully LM will provide a fix.

Thanks,

-stefan

That's ashame but can perfectly understand his stance. I set P3D aside for now as I just can't risk dedicating time to a flight at the risk of it ending abruptly. Ashame but that's life..