Tino

Hi Nico, I've changed all these within the General section of the aircraft.cfg. This is why AILGenerator should give you errors upon compiling, correct? It doesn't for the B77W. ATC_Model is currently B77W. ATC_Model IS Currently B77W. When compiled, all B77W's show as B773 in the txt output file. Each repaint has it's down ATC Model or UI Type as B77W. Any other ideas?

Good Afternoon, Just wanted to point out that AI Generator complies incorrect codes for some aircraft. For example, A B777-300ER should have an identifier code of B77W. Currently, in the AI Text list, it shows as B773, which is incorrect. This will lead to incorrect aircraft being displayed. (e.x FR24 shows a BA B77W at YSSY. In the sim, it reverts to a B772). This creates issues for carriers flying the B773 version as well. Cathay, ANA, JAL, Thai, all fly the B77W and B773 variants. I have fix this by manually editing the AI text file but, doing it every time I compile is tiresome. Is there a way to change this? Just to be aware, UI_Type in each of my aircraft configs all have the correct corresponding aircraft codes. Ex. B77W, B773, B772, A333, A332... so on and so on. Really enjoying your program. I can't fly without it. Especially with over 4000 custom AI aircraft. Just thought I'd give some feedback. Cheers.

It should be available this year but, just like any development, that can change.

That's correct. It's currently delayed right now due construction. In the mean time, Mir focused his time towards a smaller airfield (Wellington), in order to fill the gap. You can read more about the delay of NZAA on our forums here: http://flightbeam.net/forums/viewtopic.php?f=25&t=2930 Cheers.

The speculation is funny! Lots of interesting guesses. Mir has already arrived in Vegas and will be preparing the booth. Just In case the reveal is not broadcaster live, an announcement will be made on our forums & on our Facebook page, tomorrow. If you are at FSExpo this year, stop by the booth and say hi to Mir. Cheers.

Still in progress. Bill Womack is the developer for that one and will likely go into 2019. KPDX will not interfere with other developments.

All of you will find out in a couple days (Cough) FSExpo (Cough). Announcements will be on our forums and Facebook as well. If any of you are attending, be sure to stop by and say hello to Mir. He will have a booth setup. Cheers.

Win Win. You get a nice slick haircut at the same time!

3km south of YVR.

Nice to see another local nearby!

Completely agree! Uploading winds makes a big different for me. Still, even in it's current state, it's a great product. Can't wait to see how it matures.

This is correct. When releasing a Beta version, it's good to have testers from all sides of the community. Not just pilots or technical individuals. tackling a beta product from multiple view points is a good way to see how the product behaves. Majority of simmers are just looking to fly from "A to B" anyway. I do not see anything wrong with the beta tester in question. Sure, he may be young but, he was enjoying his time in the sim. Which is what FS is all about.

I second this! It's an absolute joy to see real live traffic in the sim.

Now I'm going to have to try Duke's, next time I visit DC. ;)

Ok, I will check the atc model section and report back. I do remember changing this for the FSP a330's as they didn't show up at first. They weren't using the standard ICAO format. I will get back to you on that. I appreciate the help.

Thanks very much Nico. This is exactly the information I was looking for. The only reason I do not like the parked aircraft is due to the issues with livery matching. My matching is about 99% accurate with live aircraft but, I get random ones with the parked aircraft. Oh, and one more thing: I noticed that the FSPXAI 789 does not get complied into the VMRGenerator txt file. When you open the txt file to check, it shows all 789's as 788 ICAO codes. So I have to keep editing the file in order for them to display properly in the sim. Is this because VMR does not see it as a 789? I believe this also happens with the TFS A300's.(AIG released a new updated model on their forums). ICAO for those should be A306, if i'm not mistaken. These A300's don't even show up when complied. Thank you!

Hi there, Wonderful program you have. I've been having a ton of fun testing out traffic this past weekend. I've always loved installing AI aircraft. I have an extensive AI collection that is mostly FSPXAI and FAIB aircraft. Just about 4000 livery's now! (I getting there and it’s absolutely satisfying seeing your hard work come to fruition). My question is, is there a way to get rid of the parked aircraft? I tried looking for information in your manual but, couldn't find any answers. I know how to use the parkgenerator but, switching it to 0% parked didn't help.Seems that non-live aircraft have a “_” at the end of their names, when viewing the aircraft in the sim. Is there a way to only have the live ones? I find this to be a lot better. Thanks for your time. Really enjoying your program!

Hmm... Here I am, just very very happy to see that we have a x64bit sim, that is constantly being updated and worked on. May not have all the features requested in this update but, it's nice to know we can all look forward to improvements, regardless if large or small.

I remember having 183 knts on the tail a few years back/ NRT-YVR. Flight time was 6 hours 50 min.

All of our products are compatible with V4 already. MSP will be the first to utilize V4 features such as Dynamic Lighting and the new Flightbeam Manager. Previous products will eventually be rolled into the new manager in the coming months. Cheers.

Depending if there are no last minute issues of course. As of right now, everything looks good. :)

None. :) MSP comes with the new Flightbeam Manager and eventually, all of the products will be moved to the new system. Some features of the new Flightbeam Manager are: - Send Support emails which can automatically attach your FSX/P3D.cfg and other vital files - Display a News Feed with our latest articles - Displays our FAQ - Allows automatic downloads of product updates (with user input) - Automatically updates itself (with user input) - Troubleshooting tool that can dynamically search and de-activate duplicate AFCADs, without ever leaving the Flightbeam Manager Cheers,

I currently have 8GB 2400 Mhz in my current build. Couldn't be happier. It's all about CAS latency, for ESP platforms anyway. On another note: If people are going to be running 4K resolution on every product they have, (Within a 64bit sim), then more than 8GB would be beneficial. I don't run 4k, so keeping my current P3D V3.4 settings the same in V4 should be totally fine (with regards to VAS). To be frank, VAS isn't something you have to worry about in a 64bit environment. The new issue will be with the physical memory you have available in your PC. Cheers,

Hi Martin, Yes, getting the non-k 7600 was essential for reducing the cost of the overall build. (Keeping it under 1000$ CAD with tax). I can still manage to achieve 4.2Ghz with the Intel Turboboost Technology. If I were to go with a K version, I would have needed to purchase a more expensive motherboard. The build you've listed looks great! Cheers.

Thanks! I am actually really impressed on how this system is currently performing. I'll post more results as I add more addon's. Cheers.