vbazillio

For those not monitoring Flightbeam forum nor launching Flightbeam Manager :

Yep. Thanks to point it out. I didn't even notice it (from the ground) and didn't look closely at my screen shot 🙂 Bill Womack has explained : Source : http://flightbeam.net/forums/viewtopic.php?f=38&t=3156#p17521

Version 1.0.0.5 is on page #2 :

Just bought it. I would buy Flightbeam product eyes closed. Portland brings me a lot of aviation souvenir (my first VFR short approach after few hours flying in US). Performance are great (not visible on video, perf. hit by the Shadow play recording feature). Details are great and I love parking my Cessna at Flightcraft/Atlantic FBO 😉

Merry Christmas to the whole community !

And with Symbolic Links, it’s very easy and fast to move big folders (Orbx, add-on, Simobject...) to the new drive without reinstalling anything. For example : http://20-100-video.blogspot.com/2018/01/how-to-move-orbx-folder-or-any-big-p3d.html

Thank to all for your help !

When launching the version downloaded at 7:56am GMT, it says "PTA 2.62 is now available with Prepar3D v4.3 compatibility"

These two's were the first one (v18.11.24.0) and now an update 18.11.27.0 is available

They say that they have fixed those 3 aircraft.cfg's. I just ran FLAI (version 14, latest version 14) release notes said A320s have bee fixed but the update remove the line/space above [fltsim.0] ;(

Hum... Other aircraft.cfg don't have the // comment section and start at line 0 (without space/line) with the [fltsim.0]

To test : switch from unlimited to lock to whatever fps (or the reverse but go from one to another).

I did it (see previous posts) but each time I launch FLAi Upate it replaces the 3 files and I have to manage it again. Any tips on that ? Furthermore I didn't understand why we should add this blank line to this 3 specific planes (except that I brings an error) and not thousand of other AI planes that don't have the blank line...

C172 et C182 are updated

Pretty much strange because it needs only to add a empty blank line on the first [fltsim.0] entry (after the /// remark). I didn't get thru all other one. Thank for your support.