Post by Tom/CalClassic on May 23, 2012 14:05:36 GMT -5
Hi all,
From a thread at AVSIM I found out about a modified ATC DLL file that gives you "relaxed" ATC - it is still default ATC, but without the nagging that happens when you fly a propliner and ATC expects you to do more than you can. Also, flying VOR to VOR is a pain because they always tell you you are a little off course.
Well, I just flew a nice little IFR flight in a UAL CV-340 from LAX to SAN, and totally enjoyed it. No nagging, no course correction, etc. The only things that keep it from being true non-radar ATC are the "traffic at 6 o'clock" calls in busy areas. The only other annoyance is the frequent frequency changes. I just quickly said "I see the traffic" and made the frequency changes if *I* wanted to (it won't cancel your IFR clearance if you don't, so sometimes I just didn't bother). Wow!
Now this file has one quirk - if you bust your assigned altitude you will need to go back to it before things get back to normal again, but you shouldn't do that anyway. But once you are at that altitude, you can start your descent any time you like and ATC won't yell at you. And if you cut the corner on their sometimes long ILS approaches ATC will recover and give you ILS intercept instructions. Neat!
I must warn people that I have NOT tested this file extensively, and cannot guarantee that it will work for you. Therefore, make a backup of your ATC.DLL file by renaming a copy ATC.DLL.orig. DO NOT LEAVE YOUR BACKUP FILE NAME ENDING WITH .DLL! It will still be active!
The other thing is that you *must* be using FS2004 with the 9.1 patch, but everyone should have that installed already anyway.
I believe it is Russian in origin, but I scanned it for viruses and it came up clean.
The file has been made available here:
www.mediafire.com/?68bgf92er8x5atf
He suggests using the file in folder "C" for our use (has the fewest nags). Try it out and see if it works for you. Combining this and some Editvoicepack mods to eliminate some of the final nagging (like the "get off the runway" nags) might get us very close.
Read the included readme.txt file for details.
Here is some of what he wrote me:
"1. If you need a bathroom break on those long-haul flights, you no longer have to wait to be handed off to the next center and then do the "don't contact ATC trick". Now
you can leave the "pit" and not fear your IFR plan will be cancelled when you return, because ATC will never cancel it. The way ATC works now, you'll be prompted to
"acknowledge" last transmission or "say again" and then the ATC window will remain up until you action the ATC request. Test it out. After ATC issues your squawk code,
don't acknowledge ATC right away. Set your squawk code and then wait however long you like before acknowledging ATC. In real world you'd acknowledge ATC right away, so
like I said, use ATC as you did in the past. The new ATC.dll's just offer a buffer time zone if needed, and in the example above, gives you time to set your squawk code
before being yelled at (not realistic).
2. When flying VOR to VOR you can now deviate off course or fly direct to the next VOR if you like. ATC will recognize you're off course and will only issue one heading
change to re-intercept your 'exact" flight plan path. If you wish, you can follow ATC heading change to re-intercept you're "exact" flight plan path (just like ATC has
always worked) or, you can continue flying slightly off course and ATC will not nag you to expedite your heading change. Once you re-intercept your "exact" flight plan
path ATC will then issue your on course heading.
3. When flying at cruise flight level, you can now deviate from your cruise FL and not be warned. That said, I don't know why you'd ever want to deviate from your
assigned FL without first requesting a FL change from ATC.
4. ATC will never warn you to expedite your climb or descent. As an example, when ATC initially clears you to descend from cruise altitude, you don't have to start your
descent until you want. ATC won't nag you to descend. Same goes for climbs. One thing to note about climbs/descents with the new ATC.dll in folder "C". While climbing
or descending if you happen to pass through your last cleared altitude before ATC clears you higher or lower, then ATC will never clear you to the next step altitude (same
with the default ATC). You'll have to descend/climb to your last cleared altitude before ATC will clear you higher/lower. I recommend you still use the new ATC as you
would the default ATC to avoid this issue. But, if you do pass though the 500ft zone before ATC clears you higher/lower, you can continue to climb to cruise altitude with
no step climbs from ATC (not realistic). You'll then have to request a higher/lower cruise altitude to get ATC in sync again.
5. ATC will never warn you to expedite you heading changes. This works nice when being vectored for an ILS. With default ATC during ILS vectors, they'll issue you zig zag
headings and if you're greater/lesser than 20 degrees of the assigned heading, ATC will issue you an expedite heading warning. With the ATC.dll in folder "C" you can now
fly headings more "in between" what ATC issues you and make less zig zag heading changes. Often people say ATC has them fly 40nm past the end of the runway before being
told to turn base leg. I've never encountered this issue with default ATC, but have when I used programs such as AI separation or ai smooth. That said, now if you feel
ATC has vectored you to far from the runway end, simply turn base leg and ATC will issue you an ILS intercept heading when you approach the localizer."
Enjoy,
From a thread at AVSIM I found out about a modified ATC DLL file that gives you "relaxed" ATC - it is still default ATC, but without the nagging that happens when you fly a propliner and ATC expects you to do more than you can. Also, flying VOR to VOR is a pain because they always tell you you are a little off course.
Well, I just flew a nice little IFR flight in a UAL CV-340 from LAX to SAN, and totally enjoyed it. No nagging, no course correction, etc. The only things that keep it from being true non-radar ATC are the "traffic at 6 o'clock" calls in busy areas. The only other annoyance is the frequent frequency changes. I just quickly said "I see the traffic" and made the frequency changes if *I* wanted to (it won't cancel your IFR clearance if you don't, so sometimes I just didn't bother). Wow!
Now this file has one quirk - if you bust your assigned altitude you will need to go back to it before things get back to normal again, but you shouldn't do that anyway. But once you are at that altitude, you can start your descent any time you like and ATC won't yell at you. And if you cut the corner on their sometimes long ILS approaches ATC will recover and give you ILS intercept instructions. Neat!
I must warn people that I have NOT tested this file extensively, and cannot guarantee that it will work for you. Therefore, make a backup of your ATC.DLL file by renaming a copy ATC.DLL.orig. DO NOT LEAVE YOUR BACKUP FILE NAME ENDING WITH .DLL! It will still be active!
The other thing is that you *must* be using FS2004 with the 9.1 patch, but everyone should have that installed already anyway.
I believe it is Russian in origin, but I scanned it for viruses and it came up clean.
The file has been made available here:
www.mediafire.com/?68bgf92er8x5atf
He suggests using the file in folder "C" for our use (has the fewest nags). Try it out and see if it works for you. Combining this and some Editvoicepack mods to eliminate some of the final nagging (like the "get off the runway" nags) might get us very close.
Read the included readme.txt file for details.
Here is some of what he wrote me:
"1. If you need a bathroom break on those long-haul flights, you no longer have to wait to be handed off to the next center and then do the "don't contact ATC trick". Now
you can leave the "pit" and not fear your IFR plan will be cancelled when you return, because ATC will never cancel it. The way ATC works now, you'll be prompted to
"acknowledge" last transmission or "say again" and then the ATC window will remain up until you action the ATC request. Test it out. After ATC issues your squawk code,
don't acknowledge ATC right away. Set your squawk code and then wait however long you like before acknowledging ATC. In real world you'd acknowledge ATC right away, so
like I said, use ATC as you did in the past. The new ATC.dll's just offer a buffer time zone if needed, and in the example above, gives you time to set your squawk code
before being yelled at (not realistic).
2. When flying VOR to VOR you can now deviate off course or fly direct to the next VOR if you like. ATC will recognize you're off course and will only issue one heading
change to re-intercept your 'exact" flight plan path. If you wish, you can follow ATC heading change to re-intercept you're "exact" flight plan path (just like ATC has
always worked) or, you can continue flying slightly off course and ATC will not nag you to expedite your heading change. Once you re-intercept your "exact" flight plan
path ATC will then issue your on course heading.
3. When flying at cruise flight level, you can now deviate from your cruise FL and not be warned. That said, I don't know why you'd ever want to deviate from your
assigned FL without first requesting a FL change from ATC.
4. ATC will never warn you to expedite your climb or descent. As an example, when ATC initially clears you to descend from cruise altitude, you don't have to start your
descent until you want. ATC won't nag you to descend. Same goes for climbs. One thing to note about climbs/descents with the new ATC.dll in folder "C". While climbing
or descending if you happen to pass through your last cleared altitude before ATC clears you higher or lower, then ATC will never clear you to the next step altitude (same
with the default ATC). You'll have to descend/climb to your last cleared altitude before ATC will clear you higher/lower. I recommend you still use the new ATC as you
would the default ATC to avoid this issue. But, if you do pass though the 500ft zone before ATC clears you higher/lower, you can continue to climb to cruise altitude with
no step climbs from ATC (not realistic). You'll then have to request a higher/lower cruise altitude to get ATC in sync again.
5. ATC will never warn you to expedite you heading changes. This works nice when being vectored for an ILS. With default ATC during ILS vectors, they'll issue you zig zag
headings and if you're greater/lesser than 20 degrees of the assigned heading, ATC will issue you an expedite heading warning. With the ATC.dll in folder "C" you can now
fly headings more "in between" what ATC issues you and make less zig zag heading changes. Often people say ATC has them fly 40nm past the end of the runway before being
told to turn base leg. I've never encountered this issue with default ATC, but have when I used programs such as AI separation or ai smooth. That said, now if you feel
ATC has vectored you to far from the runway end, simply turn base leg and ATC will issue you an ILS intercept heading when you approach the localizer."
Enjoy,