regulate

Roland and Matias, Thanks for your help. I purchased updated data from Navigraph (3/5/15) and all of the states converted just fine except for one, Oklahoma. My outdated data was the culprit with the conversion of the data. Brian

Roland, Mine says 1.4.1.1 in the properties of the file. I suspect because I converted the PMDG nav data from the newly released (patched PMDG 737 NGX) that maybe the navdata is old? EDIT: I just looked, the navdata in the fresh install of the PMDG is from 2011.

Matias, The error box says "SID,STAR and Final Approach Conversion Utility (AIConv.exe) for use with AI Controller. has stopped working." Then it gives me the option to close the program, at which point the program starts with the next state that is not corrupted. I ran the conversion with the AI Controller.exe boxed checked. In the window in AIConv.exe (which by default does not open all the way so it's difficult to read the full message) stopped in California at airport KL71. The message within AiConv.exe box says "The user should manually insepct the converted SID files and remove waypoints to......", message cut off on my screen shot so I don't know what the rest says. Anyway, you asked if I can try and only convert the state by itself, but I am not sure how to do that? Can you give me a little run through? Not sure if that would change anything though. I have run through the complete conversion process three times. Every country converts fine except the following U.S. states. CA, CO, GA, IL, MD, MA, TX and WA. There are a lot of airport missing in each of those states that received the error message. Did anyone else experience this? If not, maybe it's me but I don't understand the issue. Also, is the Runway.xml Path line mandatory to fill in? I don't believe I have the makerunways utility. Thanks Brian

Matias, When converting the SID/Star from my PMDG nav data (latest version of SID/STAR convertor), I get an error message on several US states, such as California and Texas. Most states compile fine, but several stop, for example, California only compiles the data to KL71, every airport after that there is no data. Texas only goes to KDAL. I have tried twice, same results. If you click close when the error message comes up, it starts in the next state. Seems like all other nations were fine. Thanks Brian

Roland, Could you consider making the UI interface window more expandable vertically and horizontally so it can be dragged further to see all of the columns of data? By the way, I also see these crazy approaches and landings on invisible runways at KLAX from weird angles, especially after the program runs for a while. I do not do spotting in a secondary window. I will see if the cache clearing will fix it. Thank you, Brian

Thank you for your work on this project. Does AI SIDSTAR have any way of controlling the AI taxi speed in P3DV2.2? I have not been able to find a tool to speed up the AI taxi (and time out mode too) for P3D. I don't believe the utility I used in FSX works in P3DV2.2 for this purpose.

Thank you Roland. I will give it a try!

I am being a little lazy here, but can someone post their ini file settings for a busy airport like LAX. I use 100% AI settings within P3D, all custom AI aircraft and flightplans based upon real life schedules so the airport is very busy. Thank you.

Can't wait to test the next version in P3D.

Thanks so much for this. Looking forward to the update.

The point being LM is doing something about a broken FSX, that was never designed or coded well in the first place. It's a start, and if they continue to make advances to make the simulation work better so I can enjoy, at a higher level of fidelity than previously flying aircraft in a realistic manner, then more power to them and more enjoyment/realism for me and all of the rest of the simulation/training community. I attended the AVSIM conference in 2006 in Washington DC when FSX was introduced, and the excitement for a new product was high, with MS FSX pundits in attendence to promote the product. One of their team members stood behind me as I fired up FSX for the first time on what was a state of the art computer at the time. My jaw dropped, but not in a good way. I turned around to told the rep (I'm sorry, I have forgotten his name) that they were going to be in trouble if this was the release RTM version. He said it was. Now 7 years later LM has taken it up themselves to develop off of that MS platform and bring the base up to modern hardware standards, recoding the product to what it should of been in the first place. So my hat's off to them! I refuse to be a naysayer. I only had a chance to fly for one hour last night, and I cannot wait to port over the licensed products I own that will allow me to do that! So thank you LM, you will have my continued support. Respectfully, Brian S.

+1000 B) For this post. If we get to a P3D version 3.0 at some point, I would really like to see this: 1) 64-bit code for the OOM's! 2) ATC and AI traffic do-over or 3) As stated above, ATC/AI traffic SDK release so third party developers can fix the issues. As shown by the amount of downloads on AVSIM and other sites, AI traffic is one of the areas that does not generate a ton of discussion, but is tremendously popular from users updating their flight sim world to make it realistic when flying. FSX (and FS9) where not developed to handle a full world of AI traffic based upon real-world flight schedules. Reggie Fields and Jim Vile were some of the pioneers looking into how MSFS works with AI traffic and can explain most of the technical aspects and limitation of FS. AI aircraft do not maintain proper separation from user aircraft or each other, along with the issue of multiple AI aircraft all going to the same approach runway when other parallel runways are available. Approach altitudes for AI aircraft are wrong and often do not follow proper airways. For instance, AI aircraft approaching KLAX often fly level at 2,600 ft for 40 miles + on approch until hitting the marker. Ugh! As a AI junkie and member of the Alpha India Group testing team, this is a must for me. Someday maybe, someday.......

Will AI aircraft traffic separation (from other AI traffic and/or user aircraft) and AI altitude on approach (correct altitudes for approach) be addressed by LM or an updated SDK for a third party developer?

Can anyone who has the beta comment on frame rates and compatibility of AI aircraft, such as FAIB, AIA, and TFS models?

Nothing in the thread states P3D V2 is going to reduce OOM's. V2 is not 64 bit. Hopefully a future release will be. That is the key.