Thank you Jacques  :smile:

 

 

Who's Vic?  our own Vic (Moderator) are the Vic on the FTX forums?    and why are you dropping his name  :Shame On You:

 

Because I choose to. And he's not `your` moderator, he's `our` moderator, based on aged moderation maturation...  :wink:

 

https://youtu.be/YlbcNvlseVI

 

 

Because I choose to. And he's not `your` moderator, he's `our` moderator, based on aged moderation maturation...  :wink:

 

That's the same thing Mallcott,  we are both saying the same thing.    You seem a bit pumped up today Mallcott,  maybe you could climb off your soap box long enough to have a nice cup of lemon tea   

 

Anyways.  dropping names is soooo  90's  

I know, but Vic is more than a name, it's a song... And it's chocolate mini Mars Bars, not lemon tea.

 

Managed to dose the neighbourhood brats with chocolate ex-lax during their halloween door-to-door scrounging last night, so as you might imagine it's been very quiet in the street today.

 

Smelly, but quiet... 

Thanks, that was a lot of help..I will run out and spend another 200 bucks just to have Objectflow work. I will wait for Orbx to fix it instead but this is something that should have been addressed before v3 was released.

The problem with that is that objectflow.dll links to precise memory addresses in the Prepare3d.exe file when it's running, and those specific memory addresses are not "knowable" by a 3rd party developer until the final retail version of the software is released by Lockheed Martin.

 

I'm sure that major developers like Orbx, PMDG, Aerosoft etc, do have direct "behind the scenes" lines of communication with the developers at LM, and probably all had access to pre-release beta versions of P3D V3, but that would not have been enough for Orbx to have made a pre-release version of objectflow.dll. If LM made any last minute changes in the P3D source code, (and they most likely did), the memory addresses would change in the final compiled versions, which would have made a pre-release objectflow incompatible.

Question:   I read somewhere you are supposed to restart you computer when Object flow updates itself.   Is that true ? 

 

It depends ... if you're comfortable with Process explorer and know your EXE.XML entries then you can restart P3D AFTER you clear out any processes that might have been launch via references in the EXE.XML.

 

Prepar3d.exe can take up to 60 seconds (in some cases longer) to fully unload after you exit P3D and return to Desktop.  It's possible that some processes in the EXE.XML might also remain running (i.e. SODE - SimObjectDisplayEngine.exe, APController.exe, couatl.exe, GFDevP3D.exe, and others) ... since ObjectFlow can terminate P3D before these other EXE.XML tasks get an opportunity to unload or force to unload.

 

So for the casual user, I'd recommend you restart your PC after an ObjectFlow update.  For the experienced user who knows his EXE.XML entries, bring up Process Explorer and manually terminate those executables if still running.

 

Cheers, Rob.

Excellent Rob thank you,   I knew i read it somewhere,   yes ill be restarting my PC after updating Object Flow  

If you're using an SSD and enjoy a reasonably quick boot time. it's a good idea to reboot the PC before starting the sim anyway.

If you're using an SSD and enjoy a reasonably quick boot time. it's a good idea to reboot the PC before starting the sim anyway.

I really agree with this although it can be a PITA sometimes. There are so many variables that must be properly initialized when P3D starts. I cannot count the number of times I've had to diagnose an issue in both FSX and P3D that turned out to be bad aircraft initialization that trashed the sim later in the flight.

 

I've found it a good idea to have a safe default flight that starts up and then I switch a/c and airports after load. Takes a bit longer but better in the long run.

 

Vic