pbar1469

Hi Roland. Indeed I tried that, but the approach was still not ok. I believe this is because LPMA is one of those top 10 "dangerous" airports, and it has it's own specific approach. I believe that in real life, pilots have to be have a specific certification to be able to land at that airport. So I tried to create the approach file instead. It works ok, except for the last bit, where the last two waypoints are very close to the runway (GELO and ROSARIO as per plates) where the aircraft has to perform a visual approach in a tight turn onto the runway. It seems that AIController ignores the last two waypoints and switches to Landing mode instead, because it's already too close to the runway. The plane still lands fine, it's just that it goes to much over land in order to align with the runway, almost crashing onto the hill side. Is there a way to specifically change the distance at which AIController switches to Landing mode for a specific airport? Here's the approach file I created: <main> <patternname> VOR.VIS.RNW05 </patternname> <patterntype> approach </patterntype> <icao> LPMA </icao> <runways> 05 </runways> <bearingrange> </bearingrange> <comments> </comments> </main> <dependency> <waypoint> <waypointnumber> 1 </waypointnumber> <fixname> ABUSU </fixname> <latitude> N32-52.02066 </latitude> <longitude> W16-38.13252 </longitude> <altitudefeet> 3000 </altitudefeet> <altitudemeters> </altitudemeters> <speedknots> </speedknots> <comments> </comments> </waypoint> <waypoint> <waypointnumber> 2 </waypointnumber> <fixname> FUN </fixname> <latitude> N32-44.49700 </latitude> <longitude> W16-42.19700 </longitude> <altitudefeet> 2000 </altitudefeet> <altitudemeters> </altitudemeters> <speedknots> </speedknots> <comments> </comments> </waypoint> <waypoint> <waypointnumber> 3 </waypointnumber> <fixname> D6FUN </fixname> <latitude> N32-38.53900 </latitude> <longitude> W16-45.53500 </longitude> <altitudefeet> 1140 </altitudefeet> <altitudemeters> </altitudemeters> <speedknots> </speedknots> <comments> </comments> </waypoint> <waypoint> <waypointnumber> 4 </waypointnumber> <fixname> D4FUN </fixname> <latitude> N32-38.32400 </latitude> <longitude> W16-47.11400 </longitude> <altitudefeet> 1000 </altitudefeet> <altitudemeters> </altitudemeters> <speedknots> </speedknots> <comments> </comments> </waypoint> <waypoint> <waypointnumber> 5 </waypointnumber> <fixname> GELO </fixname> <latitude> N32-39.57100 </latitude> <longitude> W16-48.13700 </longitude> <altitudefeet> 850 </altitudefeet> <altitudemeters> </altitudemeters> <speedknots> </speedknots> <comments> </comments> </waypoint> <waypoint> <waypointnumber> 6 </waypointnumber> <fixname> ROSARIO </fixname> <latitude> N32-40.35300 </latitude> <longitude> W16-47.58100 </longitude> <altitudefeet> 460 </altitudefeet> <altitudemeters> </altitudemeters> <speedknots> </speedknots> <comments> </comments> </waypoint> </dependency>

Hey Roland. Did a few tests with Vector on LIPZ and LOWW, seems all is well. On the other hand, not Vector related, is there a way to force the approach autogen to do right hand circuits instead of left? With LPMA, the AI always goes over the island mountains (5000 ft) instead of going over the ocean as per plates. Cheers.

Hey Roland! Found the problem! Activated the Local Policy for file access for all the P3D folder, and watched as each file was accessed. AIMonitor stops after accessing a specific bgl file, namely "coolconeslib.bgl". It's from a freeware scenery pack for Coolangata airport in Australia (YBCG) from AVSIM. The scenery zip file is called goldcoastairport.zip and it's by John Ross. As soon as I removed that file from the folder, AIMonitor finished fine and the Taxi_graph.txt file was finally generated and the AIControllerPath.txt was finally updated with the TAXI statements!! Might be a good idea to download that scenery to investigate why that specific bgl is killing AIMonitor. Cheers!!!!!! YAY! Finally!!

Hi Roland. I've completely cleaned the previous version from my PC. Installed as per instructions, Ran SIDSTAR converted (new one) again over PMDG data for the 1406 cycle, all good, data generated as expected. Single folder structure. Ran AiMonitor, added the correct paths, and did the Force Update. Again, same results. Aircraft data is generated OK, progress windows for aircraft is fine, and ends correctly. When it gets to scenery decompiling, this time is a bit different. It immediately goes to 100% CPU, and never seems to read any file whatsoever. And yes, it is in P3D mode (sorry I didn't reply to that earlier). Left it running for about 3 hours, no change. No Taxi_graph.txt file is ever generated. Memory usage for AIMonitor stays at around 15Mb, sometimes 10Mb. And I've run as user and as admin. Same. Even tried moving the scenery.cfg to a different folder and updated paths, but same result... Any ideas? Is there a way to run AIMonitor so that a log file is generated when decompiling sceneries? Thanks!!

Hi again. I do not see any pop up for the decompile, nor does it go beyond 0% complete on the progress meter. Regarding CPU usage, the first 30 secs or thereabout, it stays in 10% CPU, then slowly grows to 25% CPU, where it stays forever. Yes, I have run it as admin too. Thanks!

Hi There! The program is indeed installed in the deafult program folder, as in d:\AIController\AIControllerV14B. And yes, I've tried running as admin as well. This time I was able to capture a few screens of what Perfmon shows. This first one shows that indeed AIMonitor is reading the right files: On this second one, you can see that the only file now being accessed is a .NET one, and the processor is now at 100% (25 because its quad), and stays there forever without accessing any other files: Hope this helps. Thanks!!

Hi again Roland. Thanks for your reply. Indeed the folders I generated with SIDSTAR converter contain the txt files themselves, as oposed to being in subfolders per airport. I've done what you requested, and got the Aicontrollerlist.txt from the ZIP file so it would only go through the airport folders that you ship with the ZIP. I've done the config paths, and the Force update. I am quite sure that AImonitor is reading the scenery.cfg properly because I added an error on purpose to it (a non existing scenery folder) and AImonitor complained about it! But the result was the same... The AI_cfg_data.txt file is created correctly (and the progress bar ends ok along with the window popping up saying it's finished), but when it gets to the Scenery Decompile, it just goes to 100% CPU, no files being accessed in the disk (checked it via PerfMon), and no Taxi_graph.txt is ever created. Aimonitor.exe just has 6 threads open (sometimes 9) and stays there doing nothing at 100% usage. Also, I've tried this with Version 1.3, and the result was the same.... Just so you know, the AicontrollerPath.txt file does not contain all my scenery declarations in the spath statements. It stops with SPath=C:\P3D\Scenery\1107, but there are a lot more of the default P3D scenery files that do not get listed there. My full Scenery.cfg contains 198 entries, but only 97 are listed. All add-on sceneries are there, it's just the default ones that are missing. Also, for the generation of the SID STARS txt files, I'vw used PMDG data from the 1406 cycle. Anything you want me to send you? Thanks for you support!!!

I have a similar problem.Im using 1.4b with hf6 and whenever I try to update the approaches and taxi data, ai monitor (item 2 from the options menu) gets stuck to 100% cpu and does nothing for hours. Ive tried with lots of airports and with just a few. Same result. Ai monitor sometimes starts reading some bgl but then stops, or sometimes doesnt read anything at all. All paths are created fine for P3D. Taxi_graph never gets created. Do you have any idea of what could cause this Roland? Im using P3D v2.4, win 7 64 bits, and I have the correct vcredist installed and well as .net 4, 0. Thanks!

Roy, As I've already stated at the PATC forum, the problem isn't the support, on which you do excel tremendously. The problem is just that unsatisfied users cannot voice their discontempt. Currently there are two options for that: - Post it in the forum (but the threads either get closed or posts deleted - and I believe when you say that they are deleted for a good reason) - Email the developer, which I think isn't a good idea anyway given that if the developer is using his time to finish the update, he shouldn't be spending his time calming down angry customers on a one-by-one basis. Costumer complaints are part of software support, and they should not be ignored... For most of what I have read in the PATC forum, paying users just want a simple "hello" from the developer, just stating that indeed he is working and that he will deliver the goods. No need to reveal any "secrets". If Mourad doesn't want to spend a mere 2 minutes ONCE just doing that, (which is a very simple and effective way to do public relations) I really cannot blame the people that feel ripped off and ignored. Can you? Again, you do a great job at supporting users, but you do have to take in that you are also the "face" of the company in the absence of Mourad, wether you like it or not. I do not own the software, and I won't, but on behalf of those paying users who might feel "betrayed", please ask Mourad to post in the forum. It's not a big ask is it? And it will certainly do wonders for the image of the product. Like I also said, I believe that Pro-ATC does seem to be what we have all been waiting for, a proper ATC for FSX. But not yet. Simple issues like the occasional failure to get a TOD clearance are a total disruption. But now it's a bit too late for me, because I don't have much money to spend on my hobby, and I've gone elsewhere for ATC. All the best Roy.

And it's now June, still no update (even though the developer told me via email that it would be done in two or three weeks back in March), and if you try to complain about it in their forum, your post either gets deleted or the thread locked. This is straight out of the 80's customer support rulebook for software companies! I really really wanted to purchase this software, but now I'm quite convinced that I never will. No because of the quality of it or it's possible features, but because if there is one thing I cannot stand for is a poor (almost dictatorial) customer support... Honestly, I can only feel sorry for people that paid 50 euros, and are still waiting for over a year now for their issues to be addressed...

Good day. I know that due to the nature of the Q400, the FSX default pushback cannot be used by FS2Crew, but given that Majestic implements the pushback via FMS, can't FS2Crew connect to that instead? Just because it's a bit annoying that while I'm able to talk to ground crew with FS2Crew, I will have to click buttons on the FMS to get a pushback... Detracts from "suspension of disbelief". Can't that be worked out together with Majestic? Thanks!!!

Thanks a lot!!

Hi. In the Manual, in the Tutorial Flight section, it mentions the following: 2. To keep this tutorial short, we'll only mention the "critical" FS2Crew related items that you need to hit. If you want a expanded explanation of the various systems tests you can perform during the Originating flow, please consult Brendan Ratchford's excellent Tutorial. Is there such a tutorial, or is it just a mistake referencing the tutorial within the tutorial? Because I could not find it anywhere in the fs2crew site... Thanks!

Reinstalling Airbus X did the trick !! Thanks everyone!

Thanks! I'll try that one. I had seen another thread somewhere that said that re-installing another version of the AIRAC (for the ATR for example) would reinstall the magvar.dat, but it didn't. I'll try reinstalling Airbus X, makes sense. I'll let you know soon. Cheers.