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