Jump to content

Moose4

Members
  • Content Count

    715
  • Donations

    $0.00 
  • Joined

  • Last visited

Community Reputation

0 Neutral

About Moose4

  • Rank
    Member
  • Birthday 09/11/1966

Profile Information

  • Gender
    Male
  • Location
    Kannapolis, North Carolina

Flight Sim Profile

  • Commercial Member
    No
  • Online Flight Organization Membership
    VATSIM
  • Virtual Airlines
    Yes
  1. That's fixed it, Jean-Luc! Thank you very much!
  2. 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!
  3. 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.
  4. 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.
  5. 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.
  6. 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.
  7. 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?
  8. 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
  9. 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
  10. >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
  11. >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
  12. Still can't connect after a reboot. This is most odd. I'll keep trying.Lewis "Moose" GregoryDurham, North Carolina
  13. >Hi Lewis,>>I just checked and both servers are up and running. Could it>be your firewall or anti-virus blocking things?>>Thanks,>JimWell, I haven't run it in a few days, but everything else Internet-related is working just fine, and I haven't recently updated AS6 so ZoneAlarm shouldn't flag it (and it isn't). Maybe it's some sort of glitch with my ISP or something between here and HiFi. I just tried it again and it won't connect, regardless of the primary/secondary force settings. I'll try rebooting to force an anti-virus update and diddle with some things on my end. Thanks Jim!Lewis "Moose" GregoryDurham, North Carolina
  14. 9:00 EST on Sunday 13 January, and my AS6 can't connect to either of the HiFi weather servers. Doesn't matter whether "Force Primary" or "Force Secondary" are checked or unchecked, AS6 just sits at "Connecting to HiFi DataNet" forever. Probably just a momentary glitch, but I thought I'd post on it anyway. :)Lewis "Moose" GregoryDurham, North Carolina
  15. Thanks, problem solved!Lewis "Moose" GregoryDurham, North Carolina
×
×
  • Create New...