3.4.9.18400

I've also had As16 running when mine crashed. That said I've been using it since release without issue. Only thing to change on my system is the Objextflow update a couple of days ago.

 

Just crashed again for a second time.

 

Will try and disable it.

3.4.9.18400

 

Interesting.

Cheers, Ed

 

 

Hi, Jim, thanks for the explanation. ORBX released the new ObjectFlow.dll days ago, supposedly compatible with the newest P3Dv3.4.14 and I've updated it when I was asked to do it, upon running P3D. It seems, because of the crashes, that for some reason the update is buggy. Are you going to post this at the ORBX forums? I haven't seen anything related to this at their forums yet.
C

 

I don't have any crashes with my P3D, but I did get 2 different updates for Objectflow when starting P3D, one day apart. Probably the first one was buggy, but it never caused any problems for me. 

Just confirming that I successfully updated P3D to v3.4.14.18870. I followed the AVSIM Lockheed Martin Prepar3D_Guide, deleted the shader and config file.

1. I successfully upgraded 3 areas of P3D (Client, Content and scenery) as per the guide.

2. I then disabled P3d default traffic, loaded P3D and activated it - let it load and flew a default flight to let the shaders load.

3. I then exited P3D, reinstalled ORBX Global, FSDT Addon Manager and the latest FSUIPC.

4. I checked all the exe and dll entries and had to delete a duplicate entry of "<Name>ObjectFlow_P3D</Name>".

5. I then loaded P3D as per normal and successfully completed a PMDG 777 from Flytampa YSSY to Orbx YMML V3.. No crashes or anything..

 

Am happy to report that with a default P3D config file, everything is working very smoothly.

 

Regards,

Mars

I had the dreaded NTDLL crash, always at random times. I made sure AS2016 and FSUIPC were the last entries in the DLL.XML. Never had another crash after that.

I don't have any crashes with my P3D, but I did get 2 different updates for Objectflow when starting P3D, one day apart. Probably the first one was buggy, but it never caused any problems for me. 

 

 

Hi Bob, I only had one update of the ObjectFlow.dll upon starting P3D four days ago (+/-). You know you can force an update of this module by going to the ORBX folder inside your P3D main directory, and inside the Scripts subfolder, run the file named ObjectFlowUpdate.exe (see pictures below). Current version I have after forcing the update again today is the v1.0.14.2.

 

 

 

Cheers, Ed

Just had a crash flying from KSFO to KSAN over LAX. P3D 3.4.9.18400. FTX Global, UTX, Aerosoft A320, AS16, ASCA, Pilot2ATC. I haven't had this happen before so I'm not sure what triggered it.

 

 

Current version I have after forcing the update again today is the v1.0.14.2.

 

That's the version I have too.  The key to the crash is the fact you are loading FTX scenery or flying over it.  I am not certain if I started in St Louis and flew to Washington if the crash would still occur as none of the FTX scenery should be loading there.  I posted something at the FTX/Orbx forums in response to someone there who had a crash when loading P3D but he posted back that he disabled the module and he still got the crashes.

 

Personally I could care less about using this module while using FTX scenery.  I see no difference in the scenery with it loaded and not loaded.  I just wanted to bring this to everyone's attention in case they are getting this crash with the new P3D update.

 

Best regards,

Jim

 

 

Personally I could care less about using this module while using FTX scenery. I see no difference in the scenery with it loaded and not loaded. I just wanted to bring this to everyone's attention in case they are getting this crash with the new P3D update.

 

I made the move to P3Dv3.4.14 today and for now I'm keeping the ObjectFlow.dll module activated in the DLL.xml file. Will need to test a lot more tomorrow and in case I find something useful, I'll post it here.

Keep in touch.

Cheers, Ed