I have not been tempted to try Pro ATC/X with IF, since I see that they both use the GPS and planner. I am frightened of something disasterous happening as a result, so not worth the risk!

 

...this is the way to make programs compatible and work properly with FSX. :)

 

All the best

Steve

 

(they don't use the FSX planner but use .PLN. .FLT functions for GPS and ATC)

- do you not think that this would be a classic example of a UIAutomationCore.dll problem?

 

Nye Jones did some interesting work to resolve issues surrounding UIAutomationCore.dll over at FSN.

 

I would also try a default fsx.cfg, maybe even dll.xml, and exe.xml.

 

Steve

Jim - given his statement"

- d[/font][/color]o you not think that this would be a classic example of a UIAutomationCore.dll problem?

 

No but the uiautomationcore.dll is part of the Microsoft.net framework package. One of the functions of dotnet is to manage memory for a developers product/addon. FSX was developed when the first version of dotnet was developed and that was with the Vista OS. Dotnet is now at Version 4 and that comes with the Windows 7 installation. Vista did not come with the dotnet package and it had to be installed when FSX/Acceleration or a FSX addon was installed. So most likely you have all the versions. They are not backward compatible so Version 4 may not work with FSX all the time. I know Orbx/FTX requires version 3.2 installed for their products and they have a link to that version on their website (or they use to have it). Dotnet helps the developer manage the runtime functions of their software. The same goes for Microsoft Visuals (MSV) C++ Redistributables 2005 thru 2010. MSV's are used by developers to make sure their application or addon is installed properly. MSV's are not backward compatible and FSX was developed with the 2005 version. Acceleration too but there's a SP1 to the 2005 version that needs to be installed as it did not make it in time when Acceleration was published. Just little things like this can make a difference. Software may look like they are operating perfectly for some time then there is an unexplained glitch. The appropriate MSV is installed when the software or addon is installed (normally) unless it is not already on the system. I think the uiautomationcore.dll solution (putting the Vista version in the main FSX folder) helped resolve FSX Menu crashes but that was hit or miss too as the 'solution' doesn't work for everyone. Of course it doesn't hurt to try it for any crash.

 

Steve has some good ideas too by trying a default fsx.cfg. Sometimes the config gets so bloated with tweaks it becomes useless (or there might be a typo giving a wrong value). Flight one has a tool in their library for repairing the dll.xml. Just google repairing the dll.xml fsx.

 

Hope this helps.

 

Best regards,

Jim

After been reading through all 23 pages in this thread a question has come to my mind,

It seems to handle sid and stars the way it should...

 

But it seems that you have to generate the flight plan in pro atc, and then import it into fsx...

 

Is it possible to enter your own routes... for example if you want to fly real world routes that you already have printed out on a paper...

is it possible to enter that into pro atc or do you have to use the one that pro atc generates for you?

 

The ProATC flightplan is developed in the ProATC program. When you set up a flight plan from Point A to Point B, ProATC will give you several different routes (in most cases). Once you select the route you want to take to get to Point B, you save it then startup FSX. At the FSX screen you load your aircraft, the weather, the date and time and put the aircraft at a gate located at Point A (like KLAX Gate 10). You then hit the FlyNow button (you still have no flight plan loaded). Once FSX has loaded, you then startup ProATC and right click the flightplan you developed and click on Fly Now. ProATC is then activated and you'll begin to hear chatter (if you have background chatter). In the default aircraft, say the B737, you just hit the '1' key and ask for clearance. Your co-pilot takes over from now on totally setting up your aircraft with the right transponder codes, headings, NAV and COM frequencies. All you have to do is steer the aircraft to the departing runway, contact ground and get permission to take off. You take off and the co-pilot raises your gear and the flaps and talks to departure. You will need to activate the autopilot once safely off the ground. Your co-pilot will do the rest and you can enjoy the scenery you bought last week.

 

So it is possible to enter your own routes, one you got off the Internet or even one you developed with the FSX flightplan program. You just need to know the waypoints in between and enter those waypoints when you develop the flightplan in ProATC. ProATC will provide the proper SID and STARS. The ProATC flightplan is just as configurable as the one in FSX.

 

Best regards,

Jim

Pro-ATC/X assigns a provisional SD and STAR at the planning stage. Waypoints before the end of the SD and after the start of the STAR can't be edited. Apart from this restriction (which makes sense, I suppose), you can edit the en route part of the plan to your heart's content. I tend not to do this, since you can ask Pro-ATC/X to think again as much as you want, and it will keep generating a new route until it exhausts the possibilities, or you find one to you liking, whichever comes first! Secondly, fiddling about too much with the auto-route generator detracts from the amazing speed and simplicity of the planning process, which is one of the program's strong points for me. Thirdly, on my system the program's windows (except the home window) sometimes close unexpectedly, so I quickly accept the first decent route on offer in order to get on with the flying (and most of the time, the route on offer is largely ok).

 

Hope this helps.

 

Best wishes,

 

Michael

Thirdly, on my system the program's windows (except the home window) sometimes close unexpectedly, so I quickly accept the first decent route on offer in order to get on with the flying (and most of the time, the route on offer is largely ok).

 

Michael, for me that was fixed by ProATC in the first or second fix issued (which is incorporated in the latest fix). Mourad recommends starting up ProATC as the Administrator especially if you have installed ProATC in the Program Files (x86) folder. I installed mine on another HDD.

 

Best regards,

Jim

Thanks Jim, the 'closing windows' thing never fully went away for me, suspect it is something to do with my running XP. In the grand scheme of irritating FS add-on behaviours, this one barely registers with me! :Yawn:

 

Best wishes,

 

Michael

For me, the closing window still happens when I try to create or edit a flight plan when FSX is already open. Never had this happen when FSX not active.

Apart from that, I have to say that the program still needs a lot of tuning before I'm ready to switch from pfe to pro-atc. Descends come quite early and final descend for landing too late. Asking for lower alt is always negative etc ...

The fake background shatter becomes irritating while it is limited and so I know the messages by heart by now. I'd welcome real communication with AI planes.

I have the default ATC sound always off. Was it Pro-atc that changed that, because all of a sudden, The pro-atc chatter is mixed with the default atc messages.

So, still a lot of questions for me.

 

Jos

win 7 64 bits

Descends come quite early and final descend for landing too late. Asking for lower alt is always negative etc ...

 

That will happen when using a commercial aircraft like the PMDG737. If will not happen with default aircraft. Just continue descending until you are given final clearance for a landing. As far as getting clearance to descend too early, it all depends on how you want to treat your virtual passengers. Do you want a late clearance where you'll have to be descending at a VS of 2200 or do you want to be nice to your passengers by descending at a vs of 1000 fpm? If you are using a commercial aircraft program like PMDG, just follow the FMC's guide. Flying into KSFO, I get TOD clearance before Big Sur (BSR) to descend to 4000 feet (from FL 240) so I bring it down slowly as I know I have plenty of time. And sometimes ATC will tell me to descend to FL 100 before BSR. This should be fixed when they issue the fix for PMDG.

 

Sounds for the default ATC can be turned off in the Sounds page (as I recall it's the bottom slider). ProATC does not turn the default sounds off.

 

Best regards,

Jim

Jim, no event created and memory is configured correctly. This only happens with Pro-ATC and only with this plane after a flight plan has been created. The only sound that plays is Pro-ATC, all other sounds for FSX cease. For example, I can make a flight in Pro-ATC from KLAX to KMIA. I can fly a complete flight with the PMDG MD11 from KJFK to KSEA including programming the MCDU. I can then start a new flight at KLAX and the moment I attempt to program the MCDU FSX freezes although Pro-ATC will continue working. My computer has plenty of good stable working (16GB) RAM with an i5-2500K, heat is no issue, and as I said this problem only happens with Pro-ATC for this one plane. I should mention that I have not attempted to use PRO-ATC with the PMDG 737NGX, the only other PMDG product I own. So, we can safely rule out a memory issue. I greatly appreciate your suggestion though. Please, if you think of anything else I would be happy to hear your advice.

 

Edward,

 

A way to solve half of your problems with this software or give up could be this. Read this thread through.From post #1 all the way down here. then

 

a)pay attention to how many people got this software to consistently work.I mean not just once or twice.

b)pay attention to how many people did not get this software to work.

c)this thread was started a long while ago so now pay attention to how many people (and who this people are) who* still* claim this software works.

 

This will probably help you figure out if your investment was a good one or if it was a "bendoverandsayahhh" kind of purchase.

 

 

Good luck.

Why would I give up? That would be taking a defeatist attitude and that is not my approach to life. I do not see how your comment lends to my question. Clearly you are thinking of someone and I am not that person. I am the guy who went the extra mile and spoke, via private message and emails, to current owners of the software as well as the developer before purchasing. I decided that given all of the pros and cons it was worth the risk. I am still convinced this program was worth the investment despite the current issue I am having You appear to be upset with this software, that is not something I can help with. Please do not feel the need to "solve half" my problems anymore.

 

Thank you,

Ed

Clearly you are thinking of someone and I am not that person

 

Correct.Please disregard.

 

Thanks

Correct.Please disregard.

 

Thanks

Thank you; certainly, Sir.

 

Sometimes we do things in life for the grand adventure not the guarantee of success. I took the plunge knowing full well it may be a total loss; however, the opportunity for an achievement is there too.

I took the plunge knowing full well it may be a total loss; however, the opportunity for an achievement is there too.

 

Yes true if the $$ don't scare you too much :)

I'll keep watching this thread for the time being.

Let us know how it goes Ed!

Steve

PS

I joined the ProATC forum and found it needs cleaning up from dozens of spambot entries....

Yes, Steve, he needs moderators, a captcha, and probably a final approval before activation system. The forums could also stand a touch more organization but that is probably just my obscene level of organization. My family certainly thinks it is insane at any rate; LOL. I strongly suspect this is an error created by the lack of Nav data update. We shall see, patience and an open dialog with the developer is the best thing at this point.

For those interested, ProATC just released Beta 1034 that provides for some support to PMDG aircraft and it modifies the descent rate where you can define for each waypoint an altitude restriction such as:

 

Pass the waypoint at altitude x

Pass the at or above altitude x

Pass the at or below altitude x

 

There are some other changes too but no AIRAC data yet. I haven't had a chance to test it yet but will try a flight some time this week. The list of changes are in the beta download Help section and I had a hardtime pulling that up and had to go to the directory and open it up there. The beta opens the old Help so I deleted the old Help files and kept the new ones in the Help folder. Now when I open ProATC and click on Help, nothing happens. Just a warning in case this happens to someone else.

 

Best regards,

Jim