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.

Amen!

My question for the developers is, besides adding water masking to the Sim Savy product, are they doing any color correction to make the different photos sources blend better? In many photo scenery products, it's very noticeable when the source imagery has marked differences in quality, color, and lighting. I realize you can only do so much with what you have as the source, I just would like to know if any effort is being made to improve the image. Also, for owners of Megaearth of certain states, any discount for 2.0 purchases? As far as photoscenery goes, I don't think it's outrageous price wise, but it would be smart to make some price bundles of regions or give discounts for multiple purchases of areas to make the price point more attractive. Where it gets really expensive, and in my book and its a must for all photo scenery aficionados, is you have to have your photoscenery on SSD drives, especially if you own several large areas. With regular 7200 drives, you will soon be waiting for 10 + minutes for the scenery to load if you don't make the transition. It's the best thing I ever did, besides to switch to DX10 in FSX quite a while back, that has improved my enjoyment 10 fold. I currently own the following: California-A combination of Mega earth, Mega scenery So Cal, Vero for the SF Bay area (Mega did not have enough clarity in my book for that important region), and a little bit of FS Dreamscapes (it was not published for sale, got it through a connection) for some of Imperial and eastern San Diego County that somehow fails to get any coverage from any one, like it doesn't exist! Almost forgot, have some Blue Sky freeware (I make donations, you should too!) in there too, especially for the eastern Sierra Nevada and Mojave desert areas, their product is better than Mega earth due to lack of color correction by the Mega folks. Oregon-I have the Mega earth western half of Oregon, which is very good. Too bad they only did half of the state. Washington-I have the whole state of Washington in Mega earth, good product! Montana, Wyoming, Colorado and Nevada (the big mystery state, no one seems to have good color product for it, must be a secret)-I have bits and pieces of all those through Blue Sky donation ware, it's well done, and has water masking too! Some of is in 2M though vs 1M, not as high quality. Utah-I have all of this state, done wonderfully by FSDreamscapes. Unfortunately, Dean is not selling this product anymore. All of the photo areas were finished, and have fantastic color matching (best I have seen) however it lacked water masking. Have used some of Blue Sky's water masking scenery of Lake Powell to at least of some there. Salt Lake desperately needs water masking. Arizona-I have Megascenery Phoenix (good) and Megaearth Northern Arizona (not so good, poor dark earthtones). Hawaii-Have all of the Islands except the Big Island, through Mega scenery, Lock On file freeware of Kauai, and payware of Maui and Molokai from Newport. Massachusetts-Own through Megaearth. If that data existed for the Big Island of Hawaii (too expensive or no good data due to cloud cover) or Alaska (same), they would be huge sellers. I would also like to see some good Idaho scenery to fill in the western states gaps. Thanks for listening.

I'll take you up on that bet as far as getting the "facts straight". I use a lot of photoscenery. I have all of California, Arizona, Utah, Washington, half of Oregon, parts of Nevada, Colorado, Montana, Hawaii, and other areas around the U.S. in photoscenery. Over the years, the photoscenery increase had led to a huge delay in loading times when I go from the free flight screen until the aircraft is on the tarmac. It usually takes about 12-15 minutes for the initial flight loading times. Too much time and very frustrating. When I built the new system, I had to order my 512 GB Crucial SSD drives from two different vendors due to lack of inventory. When the first drive came in I built my system, and copied my C drive over with FSX, all of my aircraft, including as substantial amount of AI planes, and my C drive contained one photoscenery area only, SO CAL megascenery. All of my other photoscenery was on my D drive. SInce my other SSD drive was delayed in delivery, naturally I fired up FSX and temporairly used my old 7200 rpm D drive with all of the photoscenery. While load times were noticably improved, it still took several minutes due to the old D drive scenery load time. Granted, it was faster than before, but still not acceptable. When my second SSD drive finally arrived, I copied over my old D drive with the majority of my photoscenery to the SSD. Now everything was on SSD and what a difference maker. Less than 90 seconds for my flights to load. Sure, the faster processor, better pipelines with improved SATA etc are a factor, but the overriding factor is the brutal speed of the SSD's. I am a happy camper.

I use a Samsung S27A550H 27 inch lcd monitor at 1900x1200 Brian

My previous setup was an i7 920 overclocked to 4.0, gtx580, and a 500 gb and 1 TB 7200 rpm drives.

I am very happy to report I have put together my dream rig, and although I need to do a little more tweaking, both with my overclock settings and my FSX configuration, the new build went very well. My new setup: Intel Core i7-2700K Sandy Bridge 3.5GHz overclocked to 5.0 GHZ Corsair H100 liquid CPU cooler Asus P8 Z77 V-Pro Motherboard Corsair Obsidian 650D Computer tower 2 SSD Crucial M4 512 GB drives (giving me enough room for all of my photoscenery) Asus GTX 680 Direct Cut II at 1201 MHZ 16 GB G Skill Ripjaws DDR3 2133 MHZ Asus 24X DVD Corsair 750 HTX power supply For those considering going to SSD drives, I would highly recommend them if you have long loading times in FSX (especially those with a lot of photoscenery). The transfer of my nearly 1 TB of FSX and Photoscenery went flawless onto the 2 SSD drives with Crucial's copy software kit. I went from nearly 12-15 minutes of load time for a flight to start due to the photoscenery to about 60 to 90 seconds. To say I am a happy camper is an understatement. :rolleyes: Brian S.

As previously mentioned in this thread, there is a payware product that fixes this issue here http://www.flightsimtools.com/adconvx/ I bought it two years ago and it works great. Have been flying in DX10 for a long time. These new fixes coming out (1/2 vsync and new shader have been great!)

This is what I prefer also, photoscenery and high LOD radius. The parts are slowly starting to come in for my new set up. Hopefully by this coming weekend I will be able to put the rig together and give it a shot. Never tried a "data transfer" from one full hard drive to another. Hopefully using the Crucial data transfer kit is fairly simple.

I have about 1.1 TB on my current 7200 RPM HD's. The big issue for me is load time, and waiting 15 minutes for FSX to boot at my home airport is very frustrating to say the least, so that's why I am asking about multiple SSD's on one rig. Thanks for your imput. Today I purchased a Asus P8Z77-V Pro motherboard (with 4 SATA III ports) and a Crucial 512 GB SSD. I will most likely add 1 or 2 more SSD drives. I will see how my new system handles the primary SSD drive and FSX boot times before adding another to handle the majority of my photoscenery. Thanks for the reply.

Okay, I am looking after about 3 years to build a new rig for FSX. I run FSX in Direct X 10 preview, and have a huge amount of photoscenery, which I do almost all my flying in around the western U.S. The problem right now is, due to the huge amount of photoscenery and a large amount of AI, FSX takes 10-15 minutes to boot up before I can fly, and that gets real old. I am looking at getting a SB 2700K which I will OC to close to 5 GHZ, some 2133 MHZ ram, Corsair H100 cooling, and an Asus gtx 670 or 680 direct cut II Top (if I can find one). My question is, since I dont have any experience with SSD drives, and due to the current price of 1 TB ssd drives, is it possible to have three 512 GB SSD drives in one computer so I would have 1.5 TB of ssd space? I realize most people have the SSD for the OS and maybe for FSX, but if I have too much photoscenery to load just onto the primary SSD, I think that would defeat the purpose of wanting FSX to load quickly if mosts of my photo scenery was on a secondary regular 7200 rpm HD. Thanks Brian S.