Moose4

That's fixed it, Jean-Luc! Thank you very much!

Hi all, got a strange issue with my new RXP GNS 530/430 v2 units. I just purchased them today and have installed them on my new system. I have a number of airplanes from Carenado, Milviz, etc. that have options in their installers, or extra .exe files, to allow the use of RXP gauges, I guess they replace the .mdl files in the VC with GNS 530 and/or 430 bezels. So I went into my Milviz Beaver and selected the RXP 530/430 option in MVAMS. Fired P3D v4.5 up, selected the Beaver, and I see the bezels, but the 530 screen is black and the 430 screen is gray, and they don't have any clickspots. So I went into Add-Ons/Reality XP and configured the 530 and 430 in P3D while sitting in the Beaver, then exited the sim, rebooted, and went back into P3D. The Beaver still does not have the gauges functioning in the VC, though now I have a working pop-up 530 and 430 (which I can't figure out how to close, but I'll cross that bridge when I come to it). Same thing with some of my older Carenado aircraft that have "RXPGNS530.exe" files or similar in their Aircraft folders. I can run those to install the bezels in the VC, but I cannot get the GNS unit(s) to actually work in the VC. Does anybody have any idea what I might have missed? I feel like I must have made a small mistake along the installation somewhere, but the F1 installers are usually pretty word not allowed-proof. So I'm not sure why none of my VCs that are supposed to natively support the RXP GNS units, won't do it. Thanks!

I'm having two odd problems with my B200 (with the RXP GNS 530 in the left-hand slot) in addition to the non-working weather radar and the flickering top third of the VSI/TCAS. I have no clickspots anywhere on the ADF or transponder to tune them. I've moused over every square inch of both instruments, knobs and display both, and the only clickspot on either of them flips the active/standby frequencies on the ADF. There doesn't seem to be a way to tune them. What might I be missing? Other than that, and the fact that it's a little *too* quiet, I love it. The texturing and model are stunning inside and out, and it flies so nicely.

I fixed this issue with nVidia Inspector not forcing anti-aliasing in FSX after a few weeks of off-and-on messing with it. Know all I had to do?Disable DX10 preview in FSX. That's it. I never thought to mess with that setting, until I had to disable it to get texturing to show up on the PIC 737 I'd just reinstalled. When I disabled DX10 preview, voila, instant anti-aliasing. Go figure, huh? I guess I missed that somewhere along the line.

BTW, Ryan, I've tried through nVidia Control Panel with the 266.xx drivers as well; there is an "Override" setting in there, and while they don't list 8xS or 8xSQ as an option, they did list 8xQ. So I tried going through that, and it still didn't make any difference. Jaggies everywhere. I can't really tell if the 16x AF setting is doing anything or not.What's really weird? FS2004 works perfectly. I've got it going with 8xSQ through Inspector and it's doing great, and have also tried 16xS. If I try either one through Inspector with FSX, it doesn't work. It's like it can't "see" that fsx.exe is running or something. Weird.

Well, I tried cleaning out the drivers and upgrading to the latest 266.whatever from last week. I tried a couple different AA settings in Inspector (8xS, 8xSQ, 16xS). I rebooted. Nothing has worked. I duplicated the settings from this thread and when I run FSX, I get no AA. If I turn AA on inside FS, it looks great. If I turn it off inside FS, the drivers don't seem to be overriding FS's selection of "no AA thanks." Don't know if it's a Windows 7 thing (I just installed it so I'm still learning how it's different from Vista) or a permissions thing or what it is. But it's very odd, since Inspector is so simple to use, that I can't get it to work. I'll keep hammering away at it.

I'll give that a shot then, thanks. It's a two-week-old completely clean install of Windows 7 x64 so I haven't had any previous driver versions on it except for whatever W7 installed by default, but who knows what evil lurks in the hearts of registries.

Hi, a question on this...I've got the latest nVidia Inspector, using these settings, and the 260.99 drivers with a GTS 450 1GB, running with FSX w/Acceleration, and I'm not seeing any AA or AF at all when I run (in windowed mode 1680x1050). I have the internal FSX AA turned off and filtering set to Trilinear. Does nVidia Inspector have to keep running in the background while FSX is active, like nHancer did, or are the profile changes permanent and "sticky" so they only have to be made once?

If that's Heavy Weapons Guy in the last row, I think that JS41 is SERIOUSLY out of CG limits! :)(And if the flight doesn't serve food, was he allowed to bring The Samvich along?)These are absolutely amazing screenshots. I've never seen anything like this...almost enough to prompt me to get FSX soon. Almost. :)

Bringing this back to the top because it happened again, with FS2004 and ASA build 355. Flying over Africa with my closest station at FNME (Menongue, Angola), this is the METAR I see:FNME 112143Z 27000KT 16255 SCT033CB 26/20 Q3512 RMK ADVANCED INTERPOLATIONThis is the exact same problem I was having a month ago in certain regions of South America. The METAR pressure reading is totally borked. Does the "RMK ADVANCED INTERPOLATION" mean that ASA is somehow generating this data, or is it receiving garbage data from wherever the METAR data comes from?Forgot to add, it was with a different plane this time than before--the Wilco/Feelthere A340-300.

OK. I'll try a 737 or 747 in the same general area of Chile and see what happens.BTW, Jim, aside from these two pressure glitches, I am very impressed with ASA. B355 seemed to fix the twitchy winds problems I was having in FS2004, and I'm loving the new features and the fantastic cloud depictions.

Hey guys, I don't know if this is a bug report for ASA, but I think it's kind of funny nonetheless...ASA does a very faithful job of reproducing the conditions that the METARs give.Even when the METARs contain the string "Q2340". That does some FASCINATING stuff to the handling of your MD11 at FL370, let me tell you... :( This was from SCRA (Chanaral, Chile), the 2/5/2009 03Z METARs: SCRA 050335Z 22000KT 16255 SCT096 SCT151 19/14 Q2310 RMK ADVANCED INTERPOLATIONAnd here's one even better, the station just north of Chanaral, Las Breas (SCTT): SCTT 050338Z 20101KT 16255 SCT110 20/14 Q3280 RMK ADVANCED INTERPOLATIONI am now closest to the next station south, Caldera (SCCL) and it's showing: SCCL 050339Z 21804KT 16255 SCT064 BKN131 17/14 Q1018 RMK ADVANCED INTERPOLATIONBut my altitude is still completely whacked. My outside pressure appears to be somewhere over 38 inches of mercury; even hitting "B" over FL180 sets my altimeter to 32.01, not 29.92. (May be a PMDG MD-11 oddity?) I'm at FL360 and my altimeter is showing FL270 and slowly descending, cabin altitude is increasing even though the plane is level. And this despite the station showing Q1018. Multiple refreshes haven't helped.EDIT: After running across another station (SCLL) that had a "Q2380" entry for pressure, I've had to shut down ASA and clear all weather settings in FSUIPC in order to finish my flight. I am running Build 355. I've also seen this happen running the original release build of ASA, while flying the Maddog 2008. The Maddog 2008 glitch happened near Memphis, TN and exhibited the exact same symptoms of an insanely high barometric pressure--increasing cabin altitude, altimeter descending even with the plane level according to SHIFT+Z, airspeed all over the place.

Well, against my better financial judgement, I laid down my $80 last night and bought the MD-11. And really, all I can say is this: You guys have raised the bar for Flight Simulator addons with everything you've put out, from the 737-600, to the -800 expansion, to the 747-400--even the B1900s, that proved that inexpensive and simple doesn't mean ugly and tough to fly. With the MD-11, you haven't just raised the bar. You shot that sucker into geosynchronous orbit.Congratulations on a job well done, PMDG, and thank you.

If you have the registered version of FSUIPC, try going into it and looking for "wind smoothing" options. I run FS2004 and not FSX, so I don't know if FSUIPC 4 has different options than FSUIPC 3. I don't think the wind smoothing options work for an unregistered unpaid version of the program, though.Even with wind smoothing turned on, I'm seeing the same thing, occasional areas where winds aloft will shift 90+ degrees from what ASA is showing, and will sometimes "wobble" back and forth over a few minutes--a problem I saw back in the much older days of ActiveSky, and one that AS6 finally fixed. The MD-11 can be a handful when that happens!

I am getting a small amount of flickering as well in the VC. It's only on the ADF2/VOR2 buttons on the pilot's side, and the compass slider on the bottom of the standby instrument. Everything else is rock solid.Core 2 Duo E84004 GB RAMElitegroup Geforce 8800 GTS 512MBnVidia drivers version 175.16 (16xS AA, 16x AF)Vista 64-bit Home PremiumFS2004 9.1

>Hello all,>>>i am just wondering if fs2004 INCLUDING ALL ADDONS are running>under Windows Vista with no problems. This is because my>Flighsim has now seen over six years of modding and I don`t>want to do this again with FSX. If it would be a problem>running FS2004 with the addons on Vista then I will not change>my OS.>>Does somebody know this?>>mixen82The only FS2004 addons I've had trouble with under Vista 64-bit are:Blueprint KRDU v1.1 (.msi installer will not run under 64-bit OS)Reality XP GNS 430 and 530 (Garmin Trainer is a 16-bit app; their new GNS 430W/530W *will* work under a 64-bit OS)Dreamfleet Piper Dakota (there's a gauge that crashes it, don't know which one)I had to get new installers for a couple of things because mine were so old, but once I did, they worked fine.Here's a partial list of what I do have working under FS2004/Vista x64:ActiveSky 6.5Ultimate Terrain USA and UT Alaska/CanadaGround Environment ProFSGenesis mesh (lots) and landclassPMDG 737NG and 747-400LDS 767Wilco/Feelthere 737 PIC, Airbus v.1 and v.2, LegacyEaglesoft Beech 400, Citation II, Citation X, Citation CJ1+, Cirrus SR-22, Columbia 400Digital Aviation Fokker 70/100, PA-31T Cheyenne, Dornier Do 27Carenado planes (lots)Leonardo SH Maddog 2006Dreamfleet Archer, Bonanza, and Baron AFTER replacing the included RXP GNS units with the new GNS 430W or 530W purchased separatelyPSS 757 and 777FSNavigatorFS2004 does tend to crash on exit, but since I'm exiting, I don't worry about it too much.

I'm trying to reinstall my Captain Sim C-130 and the installer is giving me an "error code 11" when it tries to authenticate my order number. Attempting to go to www.captainsim.com doesn't work either, something's blocked between me and their server or else their website is dead. Anybody have any idea what's up?Lewis "Moose" GregoryDurham, North Carolina

Actually I think I may have partially figured it out...it's the taskbar. If I set the taskbar to auto-hide, my frames jump back up to 30+ in the window. As soon as the taskbar pops up, my frames go back in the toilet again. As long as I keep the taskbar hidden, it seems to be working fairly well in a window. That's very odd.Lewis "Moose" GregoryDurham, North Carolina

Hey guys, I've just re-installed FS2004 on my brand new machine, which is a Core 2 Duo E8400 processor, 4 GB RAM, Geforce 8800GTS 512MB video card with the latest nVidia WHQL drivers (175.something). This thing should run FS2004 with everything pushed over to the right quite easily, and it does...in full-screen mode only.I've installed no add-ons at all as of yet, just FS2004, the 9.1 update, and the no-CD mod (to save wear and tear on my disk #4). In the default flight, sitting on the ground at KSEA, if I'm in full-screen mode at my normal resolution of 1680x1050, I get 40 fps (locked at 40). If I switch to windowed mode, still at 1680x1050, I get 8 fps. Anti-aliasing is not turned on in my nVidia drivers yet. Almost all graphic options are maxed out.What's up? My old machine (an Athlon 2500 with a 6600GT) would actually get better frames in windowed than full-screen. I would greatly prefer to run windowed mode since I do a bit of online flying and need the ability to quickly task switch. Thanks!Lewis "Moose" GregoryDurham, North Carolina

I've been playing with this beast for a couple of hours now, and I'm just...speechless. I've mastered every piece of complex payware I've ever tried in virtually no time, and this thing is more challenging than ANY of them. Wow. I did finally get it into the air after working through the excellent step-by-step tutorial, and it flies wonderfully! It's a keeper. How is this possibly free?Those Russian designers sure do love lots of switches, though...Lewis "Moose" GregoryDurham, North Carolina

Thanks Dave! Very interesting stuff.I did figure out my problem...first, I was attempting to use the prop pitch keys to adjust the prop RPM rather than just using the clickspots on the throttle. Then when I did start to use the clickspots, I pushed the levers all the way forward to the "AIR START" position, rather than to the "RUN" position. I did a flight with them in the "RUN" position and everything looked fine, good prop animation, and takeoff power seemed just great. So now I know, just set it and forget it!I just wish they'd put the ground idle speed controls on a popup window, and not exclusively in the VC (same with the interior light controls)--or are they, and I just missed it?Lewis "Moose" GregoryDurham, North Carolina

Hey all...I've been messing around with my Captain Sim C-130, and have a question about the condition levers. If I click the condition levers forward to "run" as the manual (and tutorials I've found) state, the prop RPM just goes to 100% once I put any throttle on it, and stays there, so there's no rotating prop animation. Is this the normal setting for the C-130, just to leave the prop RPM at 100% through all parts of a flight?Also, does anyone have any ideas about typical power settings (ITT, fuel flow, etc.) for climb and cruise? Thanks.Lewis "Moose" GregoryDurham, North Carolina

>Hi,>>See if your Internet Explorer is set to Work Offline. That is>under the File menu. It should not be.That fixed it, Jim! Wow, I would've never thought of that, since I use Firefox 99.5% of the time and only ever use IE for a work website that requires it. Thank you!Lewis "Moose" GregoryDurham, North Carolina

>Hi Lewis,>>I just checked and both servers are up and running. Could it>be your firewall or anti-virus blocking things?Well, this gets weirder. Not only can I not connect to HiFi still after several reboots (with firewall + anti-virus + spyware checker enabled or disabled), I also can't use the Flight 1 wrapper to install some new software I bought (Eaglesoft's Citation II Expansion Pack). It just gets to "connecting to Internet" and exits. But all my other Web stuff--surfing, email, online games--is working fine. Very strange.Thanks for checking the servers, Jim. I've got some debugging to do on this end.Lewis "Moose" GregoryDurham, North Carolina

Still can't connect after a reboot. This is most odd. I'll keep trying.Lewis "Moose" GregoryDurham, North Carolina