LatinVFR has released a P3D3 specific executable for KRSW South West Florida Fort Myers.  (There is a separate executable for FSX/P3D/P3D2).

I just want to say thanks to the people keeping this important thread going,keep up the good work

peter

+1

FlightBeam has a new version of KDEN V1.2

 

http://www.flightbeam.net/kden.html/

 

be cautious with this update...wait for the new addon manager...some of us has issues with it... IT could introduce a stealthy CTD and you may not be able to figure out what went wrong 

 

IT ruined my whole day yesterday... because of the buggy Addon Manager

 

http://www.avsim.com/topic/480192-p3d-v3-ctd-all-of-a-sudden/#entry3343258

be cautious with this update...wait for the new addon manager...some of us has issues with it... IT could introduce a stealthy CTD and you may not be able to figure out what went wrong 

 

IT ruined my whole day yesterday... because of the buggy Addon Manager

 

http://www.avsim.com/topic/480192-p3d-v3-ctd-all-of-a-sudden/#entry3343258

thanks for the heads up. I was gonna install this tonight.

Taxi2Gate EDDM has been released...

 

http://secure.simmarket.com/taxi2gate-munich-airport-eddm-fsx-p3d-%28de_9947%29.phtml

Prepar3D 3.1 has been released and is ready for download!

Simple update,,,,

 

2 errors so far,

 

ASN

 

ASConnect error , Incompatible with P3D 3.1

 

So now i don't have my ASN weather.

 

Orbx

Object flow error, Has not been tested with 3.1 and may cause instability or crash. Run Once or Don't run options.

 

I select run and the sim runs ok.

 

I was going to spend some serious Christmas money but, now? I either go back and reinstall 3.0 and buy add-on's that do work in 3.0 and just wait awhile for company's to get caught back up again?

 

Hope this does not mean that with every incremental update 3.1, 3.2 etc.... That your add-ons will not be compatible and thus will have to wait for company's to update their stuff every time?

 

Ed

Hope this does not mean that with every incremental update 3.1, 3.2 etc.... That your add-ons will not be compatible and thus will have to wait for company's to update their stuff every time?

 

 

That was already the case with the point updates for Prepar3D v2.x. Better get used to it... ;-)

That was already the case with the point updates for Prepar3D v2.x. Better get used to it... ;-)

I think im going to do a clean install of 3.0 and stay with 3.0 for a while, then when the dust settles, Then I'll update to 3.x.

Ok... I keep seeing posts where someone's grousing about how each release requires a new software update from third party addons. That would not be Lockheed-Martin's responsibility. That would be the third party developer's responsibility. They're hacking into the core sim for whatever reason and thus whenever the core sim's code changes, the hack locations are different... and their software crashes.

 

You have a choice as to whether you want to use the addons or not... but it is not Lockheed-Martin's responsibility to support third party hacks.

Ok... I keep seeing posts where someone's grousing about how each release requires a new software update from third party addons. That would not be Lockheed-Martin's responsibility. That would be the third party developer's responsibility. They're hacking into the core sim for whatever reason and thus whenever the core sim's code changes, the hack locations are different... and their software crashes.

 

You have a choice as to whether you want to use the addons or not... but it is not Lockheed-Martin's responsibility to support third party hacks.

 

 

Agreed.

Ok... I keep seeing posts where someone's grousing about how each release requires a new software update from third party addons. That would not be Lockheed-Martin's responsibility. That would be the third party developer's responsibility. They're hacking into the core sim for whatever reason and thus whenever the core sim's code changes, the hack locations are different... and their software crashes.

 

You have a choice as to whether you want to use the addons or not... but it is not Lockheed-Martin's responsibility to support third party hacks.

AMEN!

 

Vic

I am assuming that it would be more difficult for ORBx (and other developers) to modify their software so that they are not "hacking into the core sim"? Is it even possible for something like ObjectFlow to be moved outside the core?

Orbx NA Gold USA Southern California released

 

http://www.flightsimstore.com/product_info.php?products_id=3602

FSS server has taken a dump. Did you have any luck Rich?