stu7708

Oh, that was a blast from the past. If I remember correctly it was an issue at ESSA due to multiple ground stations and "non-standard" naming of the stations. The one I was calling was named GROUND WEST GROUND, and using that failed. The solution was to remove the initial GROUND from the call and just using WEST GROUND, or possibly even using only GROUND, and then it worked fine...

Hello again. Disregard my post above. Last night I was able to fly the flight from ESNN to ESSA without issues, right up to the moment I had to contact Ground at ESSA after vacating the runway. So it looks like there are some kind of issue between VoxATC and Aerosofts Mega Airport Arlanda Scenery. I've decided to contact the guys at VoxATC to see if they can come up with a solution. Kind regards, Mikael Stockfors

Hello everyone. Last night I purchased VoxATC and have it up and running with almost everything working as it should. Did two short VFR flights without issues but when I tried to do a full IFR-flight with SIDs and STARs I encountered a slight hick-up that I want to run by the community, although I suspect I know what's causing it. The flight, as saved in FSX, is a short hop in the Twin Otter Extended from ESSA to ESNN via LUMAX (SID termination point for north departure), DEGAL and OKLEV (Initial STAR Fix for southern arrival), parked at Gate S 72. VoxATC initializes as it should, I can listen in on ATIS, and contact Clearance. Clearance assigned me runway 19L and the expected LUMAX4Q departure after a successful radio check. I then plugged the LUMAX4Q departure into Aivlasoft EFB, thus changing the flightplan in FSX, and after that VoxATC stops responding to my radio calls for push back and engine start. I can also add that the color of the text for my request changes from the initial green color indicating that it picked it up correctly (I assume). VoxATC also responds promptly to any request for push back and engine start or taxi clearance from AI traffic. I also tried to start my flight at ESNN with a plan to ESSA with the appropriate fixes along the route, but on that flight I waited until after receiving clearance for push back and engine start before plugging the departure into the EFB, only to experience a total lack of response to my request for taxi. Am I correct in assuming that it is the fact that Aivlasoft EFB changes the active flight plan in FSX that is causing this issue? Are there any ways to get around this without disabling the function in the EFB to update the flight plan in FSX? Kind regards Mikael Stockfors

Back home, and I can now confirm that disabling SweetFX before starting FSX mended my issue. Once it had ran once I could re-enable sweetFX and all is purring along nicely.. Not much help for the OP sadly though...

I'm in the process of reinstalling FSX and all my Add-ons and ran in to the exact same issue last night. When I start FSX I get the splash screen, I then hear the "Ultimate Traffic Initialized" wave-file play, and then the splash screen disapears and I return to the desktop. Nothing the the Event Viewer and no error messages to give any indication of what's going wrong. It happened after I installed ORBX AU and ORBX YBUD, but the issue remains the same regardeless of the region setting in the ORBX Central so I assume it isn't the scenery but rather something else.. I do seem to recall having the same issue a few years back, and that time it was solved by reinstalling FSUIPC, but last night it was far to late to do any real troubleshooting. But I'm going to check the logbook and DLL.XML parts later on tonight and will report back if I can find a solution. Does anyone know if the EXE.XML file can suffer from the same issues as the DLL.XML by the way?? EDIT: After a quick search in the ORBX-forum it turns out it might be due to my having SweetFX active while installing the ORBX-scenery.. Fingers crossed for a quick fix tonight...

Hi guys I'm afraid Bryan can add one more customer with this issue. Did my first flight with FS2Crew about a week ago. During the pushback I realised I needed to stop it because I was in danger of being pushed into a fence. Using the same commands, apart from the "You're cleared to disconnect and go to hand signals" command, as the OP I got the same result, we stopped, but after setting the parking brake the push back continued. I think that the ground crew said something after I said "Parking brake set", but I couldn't hear what he was saying because ATC was talking to other traffic at the same time. I was flying the 737-600 out of the SWE2011 scenery for ESMS. AES is installed, but not activated in the CFG-panel since the airport isn't supported. Push back was set for 90 degrees left, and a distance of 30 meters if I remember correctly. Can't think of any other programs that would interfere either. The only thing running was REX weahter engine and Radar Contact. Cheers Mikael Stockfors

:LMAO:Either you have one very understanding wife, or a deathwish :(

And if I was Bryan my answer would be"Not yet but very soon..." :(

Is there any chance of you looking into integrating voice control for Radar Contact (or other 3rd party ATC) into current or upcomming FS2Crew versions? It would add tons to the feel of realism to be able to talk to ATC too.....

I havn't hade this issue with the NGX, but talk about a coincidence.I was watching Air Crash Investigations (Aka Mayday or Air Emergency) on National Geographic last night, and the episode was about two crashes and one incident with the same problem in real world flights, with the difference being that it occured on the -200/300 series.More info here.But I doubt it should happen on the NGX for this reason since the failing part have been remodeled as a cause of the findings of the NTSB.

I'm using the G940 with the NGX without issues so it must be something in your setup. I set it up within FSX and the Logitech profiler, and skipped FSUIPC since I only have the unregistered version.The one issue I've had was similar to what some users have mentioned regarding Saitek pedals, the brakes (not parking brakes) where applied all the time. I solved that by setting the null zone for the toe brake axis to zero, and now everything works.As for the lights on the throttle buttons there's a 3rd party freeware software the can get them working in FSX.You can get it from here. You need to register an account before downloading, but it will allow you to assign those lights.

I have no issues using EZCA 1.17, so unless something is broken on your end that's not the issue. And if you havn't done so already, download the EZCA profile for the NGX from AOA. It's really good, after some small adjustments. http://www.flyaoamedia.com/737/737ngx-ez-camera-setup/

If you need SID, STARS and other charts for all of europe, The Phillipenes and Jordan take a look at EAD. They also require a free registration, but have most of what you will need in the way of charts. http://ead-website.ead-it.com/publicuser/public/pu/login.jsp

I had the same issue, but I solved it my just deleting what I had put in the start up panel state section in the FMC and leaving it blank. The plane now loads with engines running as it did after the clean install.

:( Be careful with your tips, someone might come back and ask you if the wipers will remove it

Looking at the general tone in the PMDG forum concering the 737 NGX at the moment I really fear that some people just won't understand. :( So can fully understand if JD want's to keep his cards close to his chest when it comes to the status of RC v5. Just keep at it, and get it done in your own time. Hopefully sooner than later :(

It's sold separately by Aerosoft toohttp://en.shop.aerosoft.com/eshop.php?action=article_list&shopfilter_category=Flight Simulation&s_design=DEFAULTI think you need to polish your glasses

Is this the one you mean??Holding short of runway 01L @ ESSATook this one while thesting my then new camera at ESSA back in november last year..

Thanks for your feedback Ron.It worked perfectly. Once again I can fly with a competent ATC ;)

Hello everyone.I have a big issue with RC at the moment.Last night after a FSX crash I got the error message IPC request contains bad data when I tried to connect RC to FSX.I found the suggested solution to the problem in you FAQ and followed the instructions there and reinstalled FSUIPC, plus added the latest update to the FSUIPC.DLL-file.After this RC can once again connect to FSX without problems, but I can't see the menu window within FSX. If I press "2" after starting RC I get the ATIS information read to me, so it appears that RC is running and the only problem is displaying the menu..Any thoughts on how to get around this?Kind regardsMikael Stockfors

Want something else to do other than checking this forum while you wait for the release of the NGX?See the qouted press release from Mutley's Hangar below posted last night. For additional information also check out the dedicated forum here.

Hi Howie.I havn't been able to find this within FSX itself either, but I have an external pay ware flight planner called FS Commander that can display the MSA. It won't give you the exact MSA at a specific point on your flight path, but at least you will know the MSA for any given quadrant on the map so you have a rough estimate.There might be free ware flight planners out there that will supply the MSA too, but none that I have tried. One such planner that I've heard great things about is Plan G, but I havn't tried it out yet so I can't confirm that the MSA is available. But since it's free why not give it a try.Hope I could be of some help at least./Micke

Hi PierreI'm using RC with REX2 Overdrive, and have only one minor problem with them working together. On some cases I've seen small differences in barometric perssure when comparing RC ATIS with the value on the FSX map while checking ATIS enroute, but other than that it works great. Kind regardsMicke

Hi Ronzie.Not sure how to put this, but it seems the problem has solved itself. I tried to reproduce it, using the same flightplans as the last time it appeard, and everything works just fine....As for FSS in RC4 it's via Telephone, so no FSS frequency to check... If I recall the issue correctly I got the phone ringing, FSS picked up, I requested my clearence and FSS told me he'd call center and get back to me, and then RC crashed....But now all is fine... should it reappear I'll make a log + a note of the error message and get back to you...Kind regardsMikael Stockfors

Hi all.Since getting RC a few months ago I have been enjoying it alot, a big step up from the default ATC.My only problem has been flying out of uncontrolled airfield. Whenever I try to obtain IFR clearence via FSS RC4 crashes on me. The Wx Breif via FSS works, and obtaining my IFR clearence in the air using the same flight plan also works without issues. The issue have appeared flying in and out of small airports in the ORBX Pacific Fjords scenery and the freeware Netherlands NL2000 scenery package.I have the latest version of FSUICP and MakeRwys installed, and the scenery library has been updated. I don't have the exact error message at hand, but if needed I'll try to reproduce the issue tonight and post it.Any ideas on this? Kind regards, and thanks for a great productMicke