Since I have tessellation disabled while using a 560ti-448 (i7-3820 OC 4.6), most of the work is on the CPU. I have found that I run better with affinity mask 84 in 2.3. Tessellation enabled using the Norfolk scenery (fantastic) from 1.4, put too much work on the video card and it occasionally became a stuttering mess. Probably due to the 1.2 gb memory. With scenery maxed and autogen on normal, cloud shadows enabled (10,000) and quality set to low, I'm getting 35-60 frames in high detail areas.

Not sure if anyone noticed this, but Cloud Shadow distance of 80,000m (max) increase my fps by 2 over 0 (and 10,000 - 60,000) ... don't ask me why as I don't understand why, but I have confirmed this many times.

 

Cheers, Rob.

Not sure if anyone noticed this

 

Yes, I see the same, which is odd, but I'm not complaining... I wish all the other sliders had the same affect ^_^

 

Something I found is setting pop free autogen to 0 in the cfg, and therefore turning it off, only affects buildings, with trees remaining 'pop free'... if you only tend to fly in rural areas, but sometimes stray close to large urban areas, this can help maintain performance; and with lots of trees, a few buildings popping is less of an issue.

 

I also tweak the tree settings in the cfg, taking the tree draw distance to the max of 12,000 and the tree to distance LOD upto the max of 9500... this gives amazing tree coverage, for very little loss of fps.

Rob is right.   Process Lasso isn't about FPS improvement per say.  It's about not contaminating the cores your P3D runs on.   On my beast rig, for whatever reason, running P3D on ALL cores is bad for my FPS because the cores are getting contaminated by one or more processes my computer runs.   When I pushed all other programs away and isolated P3D on core 11, 9, 7 and 5 (6 core HT CPU) it made my FPS go from a dismal 29 FPS avg to pegged at 60 (my refresh rate of my monitors) in the default aircraft.   With PMDG 737NGX running my FPS on average is now 25 but because my P3D is not contaminated that 25 FPS is smooth as glass, even at payware airports in moderately craptastic weather.   SteveW and Rich really saved my bacon with their help about core contamination. 

 

I've been experimenting with process lasso..

 

For version 2.2, i found i was able to gain about 9 fps by locking things to certain cores on my 4930k hex core.. it didnt seem to matter whether i turned HT on or off.. as long as i chose certain cores, even with HT on I achieved a 10 fps boost.

 

For version 2.3.. no joy so far.. my experience is about 10 fps weaker no matter what.. and previously v2.2 was about 7 fps worse than 2.1 etc.. (and with my 780ti and v2.3, my gpu load never exceeds 49% as well)

 

Curious.. it seems to me that i have to set the processes to "always" for cpu affinity then relaunch p3d to see any change. has this been everyone else's experience with process lasso.. that is.. i can change the current affinity and see a benefit.. i must relaunch my saved flight and start over each time after setting the "always" affinity (and making sure the AM is set to use all cores in v2.2 or no setting in v2.3).

 

I also dont think i'm suffering from any certain core contamination, because at any given time, out of all my other processes they are generally 1%, but usually 0.5% cpu usage or less.

While fixing another issue, I deleted the cfg and began with new settings in 2.3 which I had drastically changed. As I mentioned above, I used affinity mask = 84. I took a quick flight with default settings and a clean cfg and was surprised at how much better it looked and performed than the settings that I had come up with. Only moved frames to unlimited, increased scenery complexity to max, checked cloud shadows and set to low. Left all the other settings alone, kept the tessellation, left traffic at none, forget 4096, left it at 1024. Now it's smoother and looks better than before, 35-60 frames with my 560ti-448. This is what I got with tessellation disabled before, and without it, the water looks terrible. So hopefully, in time, I'll forget where the hell the cfg file is even located!

While fixing another issue, I deleted the cfg and began with new settings in 2.3 which I had drastically changed. As I mentioned above, I used affinity mask = 84. I took a quick flight with default settings and a clean cfg and was surprised at how much better it looked and performed than the settings that I had come up with. Only moved frames to unlimited, increased scenery complexity to max, checked cloud shadows and set to low. Left all the other settings alone, kept the tessellation, left traffic at none, forget 4096, left it at 1024. Now it's smoother and looks better than before, 35-60 frames with my 560ti-448. This is what I got with tessellation disabled before, and without it, the water looks terrible. So hopefully, in time, I'll forget where the hell the cfg file is even located!

 

P3D has a cfg file ? lol - those days are over

P3D has a cfg file ? lol - those days are over

 

I have to add texturemanload=30 and change TEXTURE_BANDWIDTH_MULT= to 400 or else some object textures will turn black when I am not looking and take a couple seconds to load back in when I look which absolutely kills immersion. I don't understand why P3D has to remove textures from VRAM when they aren't being looked at when I have 1000MB of memory free. It's like the engine isn't optimized for 3GB+ GPUs.

Hello captains,

most of those settings (jobscheduler, highmemfix...) written in first post of this thread are automatically saved into .cfg file when installing FSDT/Flightbeam sceneries. You can manage them by Addon Manager menu.

What do you suggest to do about it?

Bye.