Most of the airports will work fine now that objectflow.dll has been updated to work with V3. Even if the airports don't have a V3 installer or even a V2 installer they will work with the migration tool.

 

Some of the airports won't work because they have specific objectflow.dlls that aren't updated by the ORBXLIBS installer and they will cause an error message when you load the sim because those objectflow.dlls aren't compatible with p3dv3. If you try to run them the sim will crash and if you don't load them most of the buildings and objects at those airports will not appear at all. This video will show you how to get those airports and objectflow working correctly.

Hope this helps some folks

 

Most of the airports will work fine now that objectflow.dll has been updated to work with V3. Even if the airports don't have a V3 installer or even a V2 installer they will work with the migration tool.

 

Some of the airports won't work because they have specific objectflow.dlls that aren't updated by the ORBXLIBS installer and they will cause an error message when you load the sim because those objectflow.dlls aren't compatible with p3dv3. If you try to run them the sim will crash and if you don't load them most of the buildings and objects at those airports will not appear at all. This video will show you how to get those airports and objectflow working correctly.

Hope this helps some folks

 

 

Thanks,i will try KTVL as it does not work

 

Michael Moe

hey, thanks! i was having a similar issue with KMRY and YMML in FSX-SE and this technique also seems to alleviate the problem for now. i suspected that the specific .dll files might just be renamed versions of the main one but was reluctant to test it since i am lazy

 

cheers

-andy crosby

Fantastic, thanks.   I have 3 or 4 in PNW that don't work (they are displaying no objects at all, as you described).  Will follow this tutorial to get them working.    Thanks for sharing.

Boy, Orbx will be so pleased with this...  :rolleyes:

Boy, Orbx will be so pleased with this...  :rolleyes:

They are making installers for all the airports this just let's people use their products without having to wait.

Thanks from me as well. I had bought some NCA airports that weren't v3 updated but used your technique and everything worked fine.

David, thanks for the very helpful video. It's a great fix for the impatient among us.

They are making installers for all the airports this just let's people use their products without having to wait.

 

That much I understand. I was thinking about the support. This is a user solution, not an Orbx one. How many users following your instructions will come to the Orbx support forums if things do not work as advertised? Just saying.

As an Orbx developer I would not be pleased...

That much I understand. I was thinking about the support. This is a user solution, not an Orbx one. How many users following your instructions will come to the Orbx support forums if things do not work as advertised? Just saying.

As an Orbx developer I would not be pleased...

I don't think many who are willing to use this fix would expect Orbx to give support for it. Honestly the only major change in V2 to V3 for addon airports at least was the installer paths,all of the V2 compatible airports should work in v3 just as they did in V2 as they even have the baked in shadows removed. The FSX only airports seem to be working fine too. I've been using all of my Orbx airports since they got objectflow working for V2 a few years back long before any installers and had no issues. I just like to help the community where I can with my limited knowledge also I figure this might help orbx get a few extra sales as well.

 

I can add a note on my video basicly saying this is a user method,and is not supported by Orbx so expect no support if issues arise.

You can do anything you want to but I don't think you can publish this workaround or even share it here without ruffling feathers over at ORBX. I could be wrong but this is my impression.

 

You can do anything you want to but I don't think you can publish this workaround or even share it here without ruffling feathers over at ORBX. I could be wrong but this is my impression.

I don't see any wrong doing,I'm not distributing copyrighted material or anything of the sort I'm just showing a way to take files you already have and make then work,why orbx would care is beyond me. They are painfully slow with v3 installers,FSDT had all of there airports working in V3 a few days after release(yes they have far fewer products) Orbx a few months later only has a handful,and some airports aren't even V2 compatible more than two years after its release.

I don't think many who are willing to use this fix would expect Orbx to give support for it. 

 

Do you really think so? Again, as a developer of Orbx software I would not be pleased.

I brought this back to life.  I checked in with an Orbx Dev, they weren't opposed to this but be aware you'll give up the right for any support, you've been warned.

 

Cheers, Rob.

Thanks Rob!