Isn't the conventional wisdom to avoid installing P3D in a subfolder of Program Files (x86)? I've never followed this advise in either FSX nor P3D V2 and I have had no problems w/ anything so far w/ P3D V2. I have the usual cadre of higher resolution mesh, FTXG, REX4, some nice add ons thru the Estonia Migration Tool. Anyway I guess the conventional wisdom doesn't apply to every possible configuration, or perhaps the issue just isn't really that critical most of the time. Or I could just be lucky!

Since a folder with that name on another drive than the system drive won't be a system folder I don't think it would be a problem installing anything into it. The thing about Program Files (x86) is not the name but the fact that it's a system folder looking at the one normally located on C:

Installed clean full 2.1.. with only ftxg+v and rex4 textures as i did with 2.0...

 

With 2.0 i was getting 41-43 fps in fraps, with unlimited frames and the settings i have in my thread here.  (using fsmark07 test)

 

I started off with no tweaks to prepar3d.cfg and only got around 30.53 ..

 

So i thought.. ok, ill add in the tweaks to cfg as i did before and got a nice jump.. NOPE..

 

Fps with cfg tweaks only rose to 31.53.. somewhat studdery..

I'm using the same NI settings (in that thread linked) as before too..

 

Rather unhappy so far with a loss of nearly 11-12 fps all things held equal. 

 

Hopefully its something simple that needs adjusted..

I have to update that fps difference.. i've got it closer to 2.0 fps rates for my system..

 

I found if i toggled ftxg in ftx central from default to au then back.. suddenly my framerate is better (but not better than with 2.0)..

 

I'm hitting 38.50 fps (and removing affinitymask gained 1 fps).. before with same settings i was at 41-43 fps for the same fsmark07.. so with 2.1 thus far.. about 3-5 fps less than 2.0

This was the same type of difference i saw before, when i went from hybrid mode checked (~32 fps) to unchecked at (41 fps) with 2.0.. i have hybrid unchecked, but the toggle boosted things a bit.. i do find the textures to be a bit blurry compared to before.. perhaps some other NI settings need tweaked.

two things just occurred.. not sure if anyone else has ran into this..

 

Again my install.. win 8.1, clean 2.1 full install.. barely anything installed except ftxg+v.. running fsmark07 (KSEA) tests.. 

Went to control C the app.. it crashed with ntdll.dll error on close  (exception code 0xc0000005)... this has happened in with 2.0 with lots of things installed.

 

The other is that I noticed under controls.. only the mouse shows from time to time, even if the joystick is still working (ch flight yoke)... I didnt reinstall fsuipc yet, so perhaps this is related to the joystick fix.. but it also limits the ability to set control buttons in the sim if the joysticks go missing (but still work this time with 2.1).

 

I also noticed on one round of tests, floating buildings above KSEA region on the right hand side.

 

 

Isn't the conventional wisdom to avoid installing P3D in a subfolder of Program Files (x86)?

 

There is no reason to do so. I've never done that with either P3d or FSX.

Just completed a 90 minute flight in 2.1 after reloading my whole system. I used the ESDG CX 2.0 and REX ESS Plus. I'm impressed with the stability and consistent performance of the system. I have less stutters than before and even though the FPS is only slightly better than before, its is definitely smoother. Coming into KFLL in very stormy weather with lots of clouds resulted in the high teens FPS but other than that it was smooth. I'm impressed. My only issue was that the CX 2.0 displays are very dim to the point where I had to use the 2d panel. That's no fault of P3D though. So far, other than the issue I had yesterday with the patch (word of advice, probably better to install 2.1 than patch it), I'm liking it.

 

Good on you LM  B)

 

 

I did have some microstutters but they went away after I twiddled with my basic nvidia control panel.

Would you mind to share your Nvidia settings? I get some blurries since i installed the patch.

I'm getting blurries as well after installing V2. I have a 780 GTX, same settings before the patch I had no issues but with V2 I've had to lower my texture resolutions. The textures don't load at all and I get a blurry mess when I'm above 250knots. I only have AF=14 (non-clocked 4770k) in my CFG file so could it be a possible issue with the NI settings?

On my system, I found removing any cfg tweaks (AM, TML, etc) and running with frames set to unlimited fixed the blurries.

 

You can also experiment with vsync and triple buffering on/off for what works best on your rig.

I'm getting blurries as well after installing V2. I have a 780 GTX, same settings before the patch I had no issues but with V2 I've had to lower my texture resolutions. The textures don't load at all and I get a blurry mess when I'm above 250knots. I only have AF=14 (non-clocked 4770k) in my CFG file so could it be a possible issue with the NI settings?

 

I had blurry issues.. turned out somehow both fsx and in my NI settings FXAA was set to on.. turning either of these to on resulted in blurries as below in my image.. Only issue with turning FXAA OFF is that you end up with some object flashing.. like distant cars, planes etc.. I find the SuperVCAA 64X 4V12 or 4xBias options to work well..  I run with AA set to 8 samples in the sim itself.  I live (for now) with flashing distant objects so i can gain that added level of sharpness.  Vsync is on both in prepar3d and in NI.  Triplebuffer off (no change in fps either way).. FTF 0.2 (0.1 about the same too).. bufferpools=0.

 

Here are my current NI settings.. i've tried a bunch.. this results in 40 fps with fsmark07 using the other settings including AM=1364 found here.

FSDT has updated their installers for 2.1 FYI...their airports now work

After some long hours of testing, I was able to solve the bad case of stutters.

 

Items very hard on frame rates were AutoGen vegetation > Dense, Water Detail = Ultra  (High was actually better on fps than medium), Shadows - Terrain = cast ... these were the big stutter producing setting for my setup.

 

As others have suggested ... adding an AffinityMask setting seemed to make matter worse so I left it out.

 

Most of my testing was done in the MJC Q400 with cloud layers, I monitor flight at "Unlimited" check the lowest value then subtract 6 fps from the lowest value and Lock to that -- in my case 30.9 fps was worst case so locked at 24 fps.  Initial entry after a complete wipe using default settings at 2560 x 1600 res was around 67-70 fps.

 

My settings, I hope they help anyone else that might have a case of the stutters (used Rendi's NI settings):

 

http://robainscough.com/images/ae9f92bc5a2aa005ee280b6759803b75.jpg

 

http://robainscough.com/images/0140bce0afe4bf3abbc3d1d7e915d89f.jpg

 

http://robainscough.com/images/ed32ecb2da847024d17ea8087d72882a.jpg

 

http://robainscough.com/images/bfeb162cf9bf70377d696c7b9bff8ef4.jpg

 

http://robainscough.com/images/79984e35910d01cd68b19282b036a76f.jpg

 

http://robainscough.com/images/184028d07fea645a414f89ccb419a1e3.jpg

 

Rob

There is no reason to do so. I've never done that with either P3d or FSX.

But it doesn't hurt you if you avoid to install into "program files(x86)"?

Spirit

Spent ages installing, loading aircraft, tweaking and sorting errors. Finally got the Airbus X into the air. An hour into the flight I clicked the right mouse (by "accident"). The whole program exits? No error or anything, just closes. Any right click closes the whole program. Seriously?? Back to FSX for a while.

Spent ages installing, loading aircraft, tweaking and sorting errors. Finally got the Airbus X into the air. An hour into the flight I clicked the right mouse (by "accident"). The whole program exits? No error or anything, just closes. Any right click closes the whole program. Seriously?? Back to FSX for a while.

 

 

Same problem here. I've doing test flights trying to fix the blurry issues, good suggestions in post 188 and 189 which seem to have addressed that issue. Now, after flying for 15 minutes P3D just exits. No error message, nothing similar to the issue you're having. I was really expecting much more with this fix but it seems like one issue after another.

Spent ages installing, loading aircraft, tweaking and sorting errors. Finally got the Airbus X into the air. An hour into the flight I clicked the right mouse (by "accident"). The whole program exits? No error or anything, just closes. Any right click closes the whole program. Seriously?? Back to FSX for a while.

Agreed. Total fail.