Gray_Lensman

It's more likely an HGS button toggled wrong, NOT a corrupted dll... Toggling the HGS to blank for taxiing is also covered in the 2nd tutorial. Once taxing is finished you HAVE to toggle it back to PRI. see: http://forum.avsim.n...doesnt-working/

Incorrect. Radar Contact (latest version 4.3.38...) allows you to asign a predesignated parking spot on the Controller Info popup which is accessible after you load the flightplan.

My FMC keypad is perfectly clear whether the setting is 1024 or 4096.. I don't think that's his issue. More than likely it's a corrupted installation or his graphic driver/GPU is at fault or corrupted.

I just adjusted the gearing attached to the potentiometers "one notch" and have not had a problem since.

Why bother integrating with dated, very lousy supported software like FSBuild? I gave up waiting for help on their support forum and bought FS Commander instead. FS Build went into my trash can immediately thereafter.

Wrong. You can "arm" VNAV on the ground. In fact Tutorial #1 has you do just that. If conditions are right meaning the 1st waypoint is within just a few degrees of the runway heading you can also "arm" LNAV on the ground. Tutorial #1 also does just that. What might have happened to the OP was that "autothrottle" was/became disengaged for some reason... This has happened to me on more than one occasion and each time results in a stall if not immediately corrected of course.

Wilco CRJ Next Generation was a huge letdown for me. All around poor design and the only addon that was worse than the default FSX version.

Sure... Go into FSX Settings > Sound... then slide the Voice slider all the way to the left to 0. You may or may not have to exit and restart FSX... The first time I tried this before even posting above the first time, it didn't work adding to my confusion and frustration. I thought maybe it was an .INI setting to be changed somewhere. I still have not found where it states to do so in the manual(s) as inferred above. Hope this helps. Regards

Wow! Mister I fought the installation process for over 6 hours, something I never do with other software... then I fight the voice issue for 2 hours and you wonder why my post is somewhat negative? Thanks to your earlier more helpful post, I managed to figure out the necessary change to correct the voiceover, but using the Adobe search function, I have yet to find where it states how to do so in either the RCV4.pdf manual OR the rcv43.pdf manual.

1. Where (what page) in the RC manual does it give instructions to turn off the ATC volume on the Sound screen? 2. I'm using FSX not FS and the Sound screen does not have a specific ATC volume setting on the Sound screen... I tried looking for something like that before I posted in the first place.

After spending several hours getting the MSSTDFMT.DLL issue resolved, I finally got into the first tutorial. As soon as I selected the ATIS report, I heard the normal FSX ATIS information voice being "mixed/overlaid" with the RC4 ATIS information voice. What the heck? Is there a setting somewhere to shut down the FSX ATC voices so that RC4 ATC is all I hear? I must say. my first impressions of this software are not favorable.

According to Microsoft Community support. This file MSSTDFMT.DLL is supposed to be installed by the software being provided... In other words RC4 should have installed this software! Since it didn't install properly how about the software/program developers of RCv4.3 provide a link to the file so we can install it in its proper location, It is not located anywhere on my system nor am I able to find it anywhere on the web. For anyone else considering buying this product, I seriously suggest you determine if you have this .dll file on your system and properly registered within your Windows system BEFORE you even bother to purchase Radar Contact v4.3. This was not meant as a "Yell" but a large attention print for those that follow so that they can avoid some serious inconvenience. Regards

Just an update on my post regarding REX+ above. After numerous restarts of the KSTL to KDEN flight, I finally observed reasonable expected winds aloft out of the west. Whatever made it work correctly I have no idea... Hopefully, going forward, REX+ will be reliable and not a half dozen restarts... Just can't mess with that many restarts with an FSCaptain flight, it's not worth the hassle. I'd rather fly with OPUS's incorrect winds aloft than go thru all that again. Regards

Though the REX+ graphics look great, they still have that checkerboard look when seen from above and even though REX supposedly implements true winds aloft, I have yet to actually see it while flying. Here's a screenshot of an NGX flight at FL360 heading to KDEN from KSTL. At this point in time when the screen shot was taken, the flight was almost directly over KMCI and the weather had been forced to update. Per the REX superimposed screen I should be getting winds mostly from the west direction at approx. 60. Instead, I'm actually getting winds "pushing" me from 40 degrees at 60. http://www.mediafire...b9vqb96a16yxt5s

If it looks like this: http://www.mediafire.com/view/?7vtl9yyot68pcks with the HGS control panel toggled to CLR like this: http://www.mediafire.com/view/?xz7vk4kfvv11y8w then before you go nuts and open a ticket with PMDG you might want to to toggle the CLR button like this to change to PRI mode: http://www.mediafire.com/view/?v85mhzg42ccj3mh and you should end up with this: http://www.mediafire.com/view/?02f08oxa9crboiy Regards

Clarify: Is it dropping down and not displaying any information? Or is it not dropping down at all?l

I actually flipped off the Autothrottle to disengage TOGA... I should have been more clear. Pressing the TOGA hidden click spot does not work. Intuitively, you have to get out of the automatic throttle control system mode before any FSX manual throttle control will have any effect. I'm guessing that on the real aircraft, pulling the throttles back would do this automatically, but it's probably an FSX limitation since our SIM throttles are not mechanically connected to a real aircraft.

Works just fine for me. You do have to be above 90 speed, which you stated you were, but you might have to hit F1 to get the throttle to idle depending on the calibration of your throttles. There's nothing wrong with the PMDG logic however. If your throttle is not calibrating correctly to idle then blame your throttle and/or FSX. Also, did you drop out of TO/GA when you pulled back the throttles? If you didn't then the throttles will have no effect... I'm assuming you did disengage TO/GA however. Regards

Then I guess we'll just have to agree to disagree in regards to UHPP. Regards

Simmer2050: When using ADE, check the degrees the runway was constructed to because FSX and FS9 data might be different. I used 338.77 because the FSX UHPP runway was laid out to 338.77. In FS9, the older sim, it might very well have been a slightly different heading... Matter of fact, the Jeppesen charts for FS9 show 343 degrees. Use the same degrees heading for your Localizer correction as the FS9's runway heading... Maybe that is why you are still seeing an offset... Just guessing here. Regards

Again, not knowing about FS9 files, but knowing FSX files, the STOCK internal airport files for FSX are NOT named directly for the airport such as UHPP.bgl, instead they are embedded within the scenery file structure... with UHPP being specifically embedded in a file named APX90130.bgl, but since you have an add-on airport, I wouldn't be sure what would take precedence. You might post a question on the ADEX forums for support for your FS9 question. They are pretty helpful there. http://www.fsdeveloper.com/forum/forumdisplay.php?f=95

In contrast to your example, the 2006 Jeppesen charts for UHPP do not claim to be an offset ILS, in fact they show an ILS in direct alignment with the exact degrees as runway 34R. I would think that if the offset was purposeful, it would show it in the charts the same as your example. see: http://www.mediafire.com/view/?t9vq2rsvf1t9run I made the changes with ADEX for FSX not FS9. Not being familiar with FS9's file layouts, I can only guess that assuming you got the change correct, your FS9 is NOT seeing your edited/changed *.bgl file yet and you are still seeing the stock layout.

Good question... per definition In aviation, a localizer (LOC) is one of the components of an Instrument Landing System (ILS), and it provides runway centerline guidance to aircraft. In some cases, a course projected by localizer is at an angle to the runway (usually due to obstructions around the airport. It is then called a Localizer Type Directional Aid (LDA). However, in this case the chart does not call it an LDA and... If it was meant to guide around obstructions to the airport, then being offset in the direction that it is in stock FSX would actually guide your flight path closer to some higher hills/mountains on the approach path on that side of the approach to runway 34R, a direct contradiction to the purpose of an offset Localizer as described above. If it was offset an equivalent amount to the other side of the approach path, I would be inclined to think that it had such a purpose but as it is to the wrong side, I am inclined to believe it's another FSX airport design goof of which there are many.

especially, when the Navigraph cost is quite acceptable... first the cost... (10 Euros or $13 USD) for 100 credits second ... each AIRAC cycle (13 a year or one every 4 weeks) cost 20 credits which would be 5 cycles worth. BUT Navigraph offers a discount specifically for AIRAC updates (correct me if I'm wrong)... I believe it's 20 Euros (or $26 USD) for a full year (or 13 cycles) instead of just 10 cycles that 200 credits would normally buy) third... If you have several add-on products... for instance PMDG add-ons, along with WILCO add-ons, and Level-D addons. You can download the cycle data for each of those products (all for that cycles' 20 credits) NOT 20 credits for each one... This makes it extremely cost effective for those with more than one company's add-ons. Clarification: The reason for the "credit" system is that Navigraph offers charts and other products that have a "credit cost" so that once you buy some credits, you can pick and choose where you might divide up your purchase. The AIRAC discount mentioned above is an "all at once" allocation of your 200 credits to that particular discounted package. Hope this helps

Easily fixed with ADEX http://www.scruffyduckscenery.co.uk/ The problem is that the stock airport had the Localizer aligned to 337.00 but the corresponding runway was aligned to 158.77/338.77. The further away from the airport you get the worse it aligns especially at distances usually around the FAF. Correcting the Localizer to also be 338.77 corrects the issue. Here's a pic of the stock UHPP airport alignment on my system BEFORE ADEX correction: http://www.mediafire...ixb1a1qulbqfsn4 Here's a pic of the ADEX corrected UHPP airport alignment on my system AFTER ADEX correction: http://www.mediafire...23py5w388y1zcym Regards p.s. I used the Cessna 172 with the Garmin because it best visually shows the Localizer Arc Zoomed in or out... In this case, I aligned to the displayed Garmin localizer arc near the apex then snapped the pics.