Major_V

If you run Win7, go to "C:\Users\...\Documents\EZCA Profiles" and delete its contents.

stelios: The first step I would take is to delete (or rename or move) the fsx.cfg file. When you then start FSX, it will rebuild the fsx.cfg with original settings. This is standard maintenance for many of us and easily reversible if you renamed or moved the file. Give it a try and see if that helps. Good luck! MajorvV

Thanks for the suggestion, but the VRS Support forum has been spectacularly unhelpful to this point. Like many others, I have been trying to get the Superbug to work in P3D for some time now, with no success. The problem appears to be that the Superbug's Aircraft Configuration Manager calls for a specific version of SimConnect which is different than the version reported by P3D. If you ignore this and just try to load the aircraft in P3D, you get nothing but a blank screen. I have posted on the VRS Support forum and asked them to address the issue (even indicating that I would be willing to pay for a P3D home/personal use "license"), but so far they have ignored my post: http://forums.vrsimulations.com/forums/phpBB3/viewtopic.php?f=23&t=8453 As for the statement that "Superbug has been got to work in P3D," I see no evidence of that in any public forum (but would be happy if someone would prove me wrong). Major V

cassis:You can assign a joystick key, but this will zoom in/out only one increment. To have continuous zoom in/out, you need to add a "repeat" line after the "EYEPOINT" entries for your assigned joystick button in the standard.xml (located in "C:Users[your user name]AppDataLocalMicrosoftFlightPlayers[your code]CareerControlsstandard.XML") as I have done below:<SimControls.Map><MapName>CH Pro Throttle USB{3889DD70-0D9D-11DF-8003-444553540000}</MapName><MapVersion>6</MapVersion><Entry><Index>0</Index><Down><EventName>Avatar.ToggleAttach</EventName></Down></Entry><Entry><Index>1</Index><Down><EventName>CAMERA_CYCLE</EventName></Down></Entry><Entry><Index>5</Index><Down><EventName>EYEPOINT_FORWARD</EventName><Repeat>32.000000</Repeat></Down></Entry><Entry><Index>7</Index><Down><EventName>EYEPOINT_BACK</EventName><Repeat>32.000000</Repeat></Down></Entry>Good luck.

Marc:My guess is that you are using Bojote's shader mod and your new fsx.cfg is missing the following line:[GRAPHICS]ALLOW_SHADER_30=1I would add it in and see if that fixes it. If not, try to revert back to one of your saved fsx.cfg's. Good luck.

How exactly did you uninstall it? I can think of at least four things you may not have done properly:1. You need to revert back to the original "ShadersHLSL" folder in your FSX directory;2. You need to revert back to the original "WaterConstants.Xml" file in your FSX directory;3. You need to change your fsx.cfg as follows:[GRAPHICS]...ALLOW_SHADER_30=1 ----> change this to "ALLOW_SHADER_30=0"4. You need to flush your shader cache by changing the following entry in you fsx.cfg:[GRAPHICS]...SHADER_CACHE_VERSION="X" (where "X" is some number) ----> change this to SHADER_CACHE_VERSION="X+1" (i.e., the next number - if X was 2 then change it to 3, etc.)Then start FSX - everything should be back to normal. If you have not done all of the above, then that probably explains why you are having problems. Good luck.

Ricardo:You need to make sure you have the following entry in your fsx.CFG for wide screen display:[Display]...WideViewAspect=TrueHope this helps.Major V

Wow, great find McDan. I guess that is what a flight simulator is supposed to look like - almost didn't recognize it without the stutters, spikes, anomalies, blank textures, etc. that we have come to know and love. It is amazing what they can do with computers nowadays (and a little bit of optimized code).Only problem - looks like it's not yet available for sale in the U.S. I did see that they are selling it in Germany for 39.99 GBP - 2 DVD set, no download delivery option. Looks like the company's main product line is RC simulation (those appear to be the only products available for sale in the U.S. at the moment). I will be the first in line to grab it when it hits the States.

When you UNinstall the Shader 3 mod, you need to make sure you make a conforming change to your fsx.cfg file. You need to REMOVE the following entry under [GRAPHICS]:ALLOW_SHADER_30=1(or change it to ALLOW_SHADER_30=0).Major V

Frank:Thanks for the detailed run down on your system and set up. Right off the bat, I noticed you have Matrox Triplehead2Go - I do not, and I will defer to others who are familiar with it who might know if this is a possible source of the problem. You say you are running Bojote's Shader mod but you "can't remember what the suggested cfg setting is." Please check your fsx.cfg file and make sure you have the following entry under the [GRAPHICS] section:[GRAPHICS]ALLOW_SHADER_30=1If you try to use Bojote's shader mod without this entry, this can interfere with your preview display. This entry is added automatically by Bojote's installer, but it is unclear to me whether you may have tried to re-build the fsx.cfg file after installing the mod, which could have deleted the entry. Also, you should change the number that appears in the following entry by 1:[GRAPHICS]SHADER_CACHE_VERSION=[some number]In other words, if the [some number] is 13728, then you should change it to 13729. If it is 3, then you should change it to 4, etc. This will rebuild your shader cache the next time you start FSX.Of course, it might be something else entirely, but this is worth a check. Good luck.

Ulf B is right on - tell us a little something about your set up and maybe some of us can lend a hand. That is the trouble with re-installing when you run into a technical glitch, which unfortunately can be quite frequent with FSX - reinstalling is just a laborious and time-consuming shot in the dark, and you never figure out what the problem was in the first place. Aside from Ulf B's question about which scenery you installed, which is obviously important, some other possibilities also come to mind - are you running DX10 preview? What is your bufferpools setting? Are you using D3D Overrider or ATI Tray Tools? Do you have updated drivers installed for your graphics card? Do you have the latest Direct X? Are you using Bojote's Shader mod without the proper fsx.cfg setting? Etc. All of these things could affect the preview display.

Thank you, bkeske. You helped me fix the same problem on my F33! Cheers,Major V

Hirgab:I have an ATI 4870X2 and find that I get the best performance by checking the AA box in FSX settings and selecting "application controlled" for AA in CCC. You may get slightly better image quality by enhancing AA in CCC as well, but in my case the slight image improvement is not worth the performance hit (particularly in cloudy areas). Your 5870 is a more powerful card, so it may do a better job than mine with AA enhanced in CCC. You should try out both settings and see which one works best for you.Major V

*******:Thanks for yet another excellent tip! I prefer this to the other limiter because you can set the buffer value and do not have to open the Java GUI each time, as you noted. I am running an ATI 4870X2 and this limiter does NOT break the vsync (of course, I do have your ForceFullScreenVSync=1 line in my fsx.cfg -- greatest tweak ever for ATI users!). The only downside is that I do get a black screen when I end the flight, as others have reported. I have to hit ESC twice to end FSX, after which I see my desktop again.Regards,Major V

Thanks for the heads up, JeffG. Would not have known about it otherwise.Major V

Thanks, fisheye. I tried your approach but unfortunately I could not get it to work for some reason. I did remove the quotation marks like you said, but Alacrity would not start up FSX (even though it did start the FPS_Limiter.exe with the command line inserted). I am still able to use it with FPS Limiter, however, using another workaround. I run an ancillary program, Voice Activated Commands (which is excellent, by the way), as the "monitored" program and then direct Alacrity to start the actual fsx.exe.limited.bat as a "program to start after." The only downside is that I have to manually close the FPS Limiter dialogue box when I am done with FSX, but this is a relatively minor inconvenience.Major V

Steve:No problems here, mate (Win7 64-bit; i7; ATI 4870X2). I actually think that the Overdrive textures run more smoothly (but the REX folks seem reluctant to claim this - your mileage may vary!). Do make sure that you follow the installation instructions to the letter, though.Good luck.Major V

Thanks, David. Worked for me!Major V

Rex247:Have you added the following lines to your fsx.cfg?[GRAPHICS]ForceFullScreenVSync=1 // Fixes vSync natively (Fullscreen)ForceWindowedVSync=1 // Fixes vSync natively (Windowed mode)If so, which driver are you using? I am using the latest Catalyst 10.9a (hotfix) and it works great with my 4870X2 (try at your own risk):10.9a hotfixMajor V

Stanner:It is possible that your firewall is preventing the REX weather engine from downloading the weather reports, so it would be a good idea to exempt its file directory from the firewall. However, I am not sure you have REX properly installed. When you click the REX icon, you should get a REX 2.0 load screen followed by the REX Main screen, which has a bunch of buttons across the top (like "Main", "Theme Creation", "Options", "Configuration", etc). Also, when you first installed REX, you were supposed to tell it where your fsx.cfg is located and where the FSX directory is on your system - did you do this or not? You may need to go to the REX website and ask them for help. Good luck.Major V

Stanner:If you have checked "Enable REX Weather Engine" on the REX Options screen, then this is exactly what you are supposed to see when you start FSX:This is NORMAL. Next, you click the "Minimize" button. Then you load your flight. Once the flight is loaded, only then does REX know what weather to load. It does this automatically, and you will see green bar messages telling you this in the sim. Hope this helps.Major V

I am, yallu. Totally agree with your sentiments--the market seems to be saturated with multiple good or excellent P51s, Spitfires, Cessnas, etc. What we really need is a good, up to date, FSX-native ATR. The F1 ATR looks excellent and is well regarded, but I will not purchase an FS9 port over. I think an FSX-native ATR would generate a great deal of interest - I would be the first in line with my credit card.Major V

Jeff:This is what I hate the most about the Aerosoft Twin Otter (I don't have the Kodiak). It is a recognized problem with Aerosoft's turbojet flight model (others have noted this problem on their forum), but Aerosoft is unable or unwilling to do anything about it. I bought the Twotter because everybody said it was great - apparently, they don't mind the fact that it jumps over the airport fence when you first start up the engines! The other selling point was that it comes with both floats and skis. Only trouble is, you can't start the darn thing on water or snow becuse it will spin around uncontrollably after the first engine starts! (I know there are ways to try to counteract this through manipulation of the throttles into reverse, etc., but this is maddening and unrealstic.) To me, the Twotter's unrealistic startup behavior is completely unacceptable and is the main reason why I never, ever fly it (not to mention its low-quality cockpit textures and invisible float rudders).PMDG showed everyone the right way to model turboprop start up behavior with their JS4100 (which is great) - the engines are started unfeathered, I believe, so they do not generate unrealistic thrust upon start up. I enjoy FSX but I spend more time with higher quality flight simulators (IL2 1946, LOMAC, DSC Black Shark, Rise of Flight), all of which tend to have much more realistic flight modeling than the included FSX planes and most payware for FSX (of course, the very best FSX payware planes do have excellent flight models, such as PMDG, A2A, RealAir, Carenado, VRS and Lotus--those are the only ones I will fly). It is amazing to me that so many FSX users seem willing to accept the lack of realism in so many of the lesser-brand payware models (maybe they just don't know how much better some of the other flight sim modeling is?). Then again, so many FSX users seem to like flying with 2d cockpits (it's a cartoon, people!) or dumbed down procedures (Ctrl E is a good way to spoil the fun) or flight dynamics. To me, that is a complete waste of time (but I have no problem with others' enjoyment of it!).Major V

Marc:Are you running in DX10 mode? Cockpit tool tips do not work in DX10.Major V

*******:Brilliant work once again! The performance 3.0 shaders work great with my ATI 4870X2. In fact, they have improved my performance so much that they have allowed me to switch back from DX10 to DX9, which I prefer for several reasons (cockpit tips, taxi arrows, proper aircraft lights, no flashing runways). Thank you once again for all of your tremendous contributions to this sim - I am very appreciative of your time and efforts!Regards,Major V