295 replies to this topic

[Exarch Levin]

Quote

I do not know Goose, I am starting to consistently see MWO assign, (actively) all eight threads on my end since the Dec 22 patch. But I was getting consistent activity across all eight threads, where as before I would get 4 with a good load, 2 with a light load, and 2 ignored.

Sadly I'm still seeing what I've always seen from MWO: 2 cores going between 70-100% usage, 2 cores with a 10-40% load and 4 cores that might as well not be there as they're basically inactive.

What does this

r_MultiThreaded = 1

do? I see it in your CFG file but I know it isn't-wasn't-in mine.

For the triple buffering FPS boost, I am suspecting it was because I had my second monitor displaying 2d readouts and in DX11 mode MWO always interacts weirdly with the second monitor by default (it either freezes the display to whatever it was at when the game is started or makes it display just a black screen), allowing it to work properly only after the ole "3 finger salute" is given.

[Goose]

xWiredx, on 24 December 2014 - 08:39 PM, said:

FWIW, I just tried to manually dole out the threads as described above. Using the original, and using several different assignment configurations, I got the same result: lower performance.

I've been using a Zen-Minimalist set recently, of

r_WaterUpdateThread = 1
sys_TaskThread1_CPU = 0
sys_streaming_CPU = 2

I do have a note writen down to myself about how having Physics and Streaming on one core ("with Task0,") and then Main and Water ("with Task1") on another was a trainwreak of a combo, yealding wildly spiking CPU cores, and tons of GPU stalls; Rotating Physics for Main solved it, and the lesson is there are bad combos to be had.

I still don't know what to make of the new octacore thing; Even worse is half of my cores have stopped hyperthreading like they did before my Big Wipe.

Does it mean my Zen-Minimalist isn't?

Smokeyjedi, on 24 December 2014 - 08:51 PM, said:

[comp sci plus alcohol = ]

Um: You do know them ";" in the user.cfg is basically remarking that whole line out, right? Only

r_WaterUpdateThread = 0
sys_streaming_CPU = 2

are sticking, and that "ca_thread0Affinity = type: int current: 5" is causing a snide remark to show up in the omicron.log, at most.

I do want to see this test result, Because Octacore Patch.

Edited by Goose, 25 December 2014 - 01:37 AM.

[Goose]

Exarch Levin, on 24 December 2014 - 11:01 PM, said:

What does this

r_MultiThreaded = 1

do? I see it in your CFG file but I know it isn't-wasn't-in mine.

I'm being redundant, as I'm positive that "one" is it's default; I suspect it's the same kind'a switch and "multicore rendering" in Source games, and it might be related to the Threaded Optimization switch in nVidia Control Panel … And I've just noticed setting it to "two" will trigger some kind'a auto detect. Huh.

Anyway: Setting it to zero doesn't seem to help nether my big system, nor my little Pentium G620/ GTX 650Ti HTPC box, so I make shore it's set to one all the time.

Exarch Levin, on 24 December 2014 - 11:01 PM, said:

For the triple buffering FPS boost, I am suspecting it was because I had my second monitor displaying 2d readouts and in DX11 mode MWO always interacts weirdly with the second monitor by default (it either freezes the display to whatever it was at when the game is started or makes it display just a black screen), allowing it to work properly only after the ole "3 finger salute" is given.

I seem to have the same issue, only my extra monitors are over an another graphics card.

Edited by Goose, 25 December 2014 - 12:27 AM.

[Exarch Levin]

So the trick is to get the main game thread on its own core, but even that isn't going to solve the problem as that game thread is so bloated that it takes OC'd Intel parts to really handle it? Hmm.

BTW, How do I stop the massive pop-in and terrain morphing? They're killing my performance.

I'm walking along, my FPS is pretty good, and then suddenly MWO decides to load a tree and my FPS tanks for a second. As I walk, foliage pops in and flashes as it fluctuates between (presumably) levels of detail. Rocks flicker and change shape as I walk about. Related to this is low draw distance for certain important game elements: as I approach a capture square on maps, most often Viridian Bog on Conquest, only 3 sides of the square will appear from a ways off and only as I get closer will the 4th and furthest wall appear. This also momentarily tanks performance.

All settings high, all settings low it matters not as the spazing between LOD and pop-in still happens.

[Goose]

Exarch Levin, on 26 December 2014 - 01:12 AM, said:

So the trick is to get the main game thread on its own core, but even that isn't going to solve the problem as that game thread is so bloated that it takes OC'd Intel parts to really handle it? Hmm.

Not sys_main_CPU: ca_thread0Affinity … Until I get a'lot moar testing done under this "22DEC2014 Octacore Patch" …

Exarch Levin, on 26 December 2014 - 01:12 AM, said:

BTW, How do I stop the massive pop-in and terrain morphing? They're killing my performance.

To directly answer you question, there's a couple, like "r_TextureLodDistanceRatio" that never seemed to pan out; To come at your question sideways, I'd a though the four streaming commands, the ones using the "winsat mem" output, were the cure for that.

You could try

r_TexturesStreaming = 1
r_TexturesStreamPoolSize = g
r_TexturesStreamPoolSysSize = h

where "g" is a chunk of your cards' RAM, greater then 128; And "h" would be your normal RAM, greater then 800. How big is your card?

You could also try "r_TexturesStreaming = 0" but I've had bad luck with it.

[xWiredx]

As a heads-up, I haven't run any FRAPS numbers on this yet because it still won't play nice with the 64-bit client and I've been more concerned with grinding stocking stuffers, but I believe turning off in-game AA settings and forcing them with the Nvidia control panel is getting me more AA with less of a performance hit. While this is typical for some games, it didn't appear to be that way with Crysis 3 so I had my doubts. Dunno if it's the same for those with AMD GPUs. I suggested it to Bill Lumbar in a match last night, but he was too busy gloating about how I died (in my defense, I was in my King Crab which doesn't have any efficiencies unlocked, and stock it runs too hot to be effective at anything - it's my worst mech right now). I think he's under the impression that I need fps to be good, but the reason we care about eye candy ON is because we want it to be extra pretty. Usually kids turn DOWN settings to be competitive because it will remove little things like vegetation that make fps easier to gain an advantage on.

So, AA. Try it in the driver control panel instead. I think you'll be happier.

[Smokeyjedi]

Logged in on my old mans Lenovo AMD vision dual core that I have now locked to 1400Mhz cause down clocking to 700mhz was unbearably slow........There will be no testing until later when I grasp the 8400DPI mouse and octocore rig @ home.

**EDIT** did have time to correct drunken mistakes that were pointed out to me. They have been corrected but dint have time to fire the client up to witness said changes.

Edited by Smokeyjedi, 26 December 2014 - 09:04 AM.

[Bill Lumbar]

xWiredx, on 26 December 2014 - 08:20 AM, said:

As a heads-up, I haven't run any FRAPS numbers on this yet because it still won't play nice with the 64-bit client and I've been more concerned with grinding stocking stuffers, but I believe turning off in-game AA settings and forcing them with the Nvidia control panel is getting me more AA with less of a performance hit. While this is typical for some games, it didn't appear to be that way with Crysis 3 so I had my doubts. Dunno if it's the same for those with AMD GPUs. I suggested it to Bill Lumbar in a match last night, but he was too busy gloating about how I died (in my defense, I was in my King Crab which doesn't have any efficiencies unlocked, and stock it runs too hot to be effective at anything - it's my worst mech right now). I think he's under the impression that I need fps to be good, but the reason we care about eye candy ON is because we want it to be extra pretty. Usually kids turn DOWN settings to be competitive because it will remove little things like vegetation that make fps easier to gain an advantage on.

So, AA. Try it in the driver control panel instead. I think you'll be happier.

Lol.... I wasn't gloating about you dieing. We was under the garage on HPG, and I was also in my brand spanking new Thunderbolt with single heat sinks and not one increase in basics unlocked. I haven't got the Crab yet, but I am guessing your mech was running cooler then mine. I could be wrong...but, anyways, I hit two other mechs that was on your team down with you, and then focused on you. One of my teammates ended up taking you down, but I got the most damage on you and almost took the kill as well. My only point and to counter what others have claimed... I have all my eye candy turned up, I get very smooth game play(all things considered with this game engine and not being optimized for any rig) with my Amd system.

It might not be what you and some others consider smooth, (60+ fps at all times) but I have no issues at all playing this game, and neither did my team mates as we took your team out and rather fast I might add. Sure I would love to play this game at 60+ fps steady, but when is enough good enough? Just curious....

I just went back over my rig today, and found that I was running the F5 bios for my Gigabyte 990fx UD3. It was from back around 2012 i think? Well I updated to the new 10e bata one, and now am in the process of re-tweaking my system to see the effects if any. One thing I have noticed for sure already, My core voltage doesn't bounce back and forth as much as it did before, its much tighter, and temps are down on the CPU. This should allow me to push my FX-8350 well beyond the 5.0 ghz mark. Can't wait to find out I am at 4.8 ghz, only 1.35- 1.37 V Core, With the F5 bios from 2011-2012 ish, I was seeing pretty big spikes in my core voltage, even though I had it set to 1.45 it was shooting up as high as 1.55 at times, its not doing that anymore since the new bios update.

Edited by Bill Lumbar, 26 December 2014 - 10:00 AM.

[xWiredx]

I read an article today that I think everybody will find interesting: http://accidentalsci...nny-valley.html

I guess my aim now is ~84fps. I hit it on average, but I think I will want to keep my mins above that line because I'm picky. It probably isn't doable without turning things down or modding certain things in the user.cfg. Oh well. The pursuit of perfection. Drive a Lexus and that's their motto, guess it's mine now, too.

[Bill Lumbar]

xWiredx, on 26 December 2014 - 10:49 AM, said:

I read an article today that I think everybody will find interesting: http://accidentalsci...nny-valley.html

I guess my aim now is ~84fps. I hit it on average, but I think I will want to keep my mins above that line because I'm picky. It probably isn't doable without turning things down or modding certain things in the user.cfg. Oh well. The pursuit of perfection. Drive a Lexus and that's their motto, guess it's mine now, too.

Lexus and Bmw's are nice and all, but I have drove both of those, and I still prefer A 2002 Nissan Maxima Jet black/ all black leather interior 3.5 6-speed manual Transmission with 153,000 miles on it that is paid off in full.

Edited by Bill Lumbar, 26 December 2014 - 10:59 AM.

[Smokeyjedi]

xWiredx, on 26 December 2014 - 10:49 AM, said:

I read an article today that I think everybody will find interesting: http://accidentalsci...nny-valley.html

I guess my aim now is ~84fps. I hit it on average, but I think I will want to keep my mins above that line because I'm picky. It probably isn't doable without turning things down or modding certain things in the user.cfg. Oh well. The pursuit of perfection. Drive a Lexus and that's their motto, guess it's mine now, too.

I have been DL as much 48+FPS videos since I purchased my VG248QE and went nuts on ultra high refresh in all ways. It tickles my eyes. I described it as entering my brain in a new way when Ive subjected friends and family to 48FPS video...and beyond..

[Exarch Levin]

Goose, on 26 December 2014 - 07:49 AM, said:

Not sys_main_CPU: ca_thread0Affinity … Until I get a'lot moar testing done under this "22DEC2014 Octacore Patch" …

To directly answer you question, there's a couple, like "r_TextureLodDistanceRatio" that never seemed to pan out; To come at your question sideways, I'd a though the four streaming commands, the ones using the "winsat mem" output, were the cure for that.

You could try

r_TexturesStreaming = 1
r_TexturesStreamPoolSize = g
r_TexturesStreamPoolSysSize = h

where "g" is a chunk of your cards' RAM, greater then 128; And "h" would be your normal RAM, greater then 800. How big is your card?

You could also try "r_TexturesStreaming = 0" but I've had bad luck with it.

Card has 4096 MB of VRAM.

[Goose]

Exarch Levin, on 26 December 2014 - 03:07 PM, said:

Card has 4096 MB of VRAM.

Goose, on 24 December 2014 - 01:01 PM, said:

Did forget to mention "sys_budget_videomem = y" to you? I'm sorry; "y" is the meg on your card.

[Lordred]

Goose, any results from testing 8 thread loads on your end?

Here is my most recent with a 'meager' overclock


As always, Test performed at 1080p with the Very High preset used for the video settings.

http://valid.x86.fr/5biyn8




It is kinda odd, the further along I push the system, the more it starts to use the last two cores. Any ideas?

Edited by Lordred, 26 December 2014 - 04:07 PM.

[Goose]

Hadn't been on, really, for two days; I do have it in my head to rem out my last three "thread-placement" lines, see what happens …

I also have this bad habit of not logging every last map: Waiting for Origianl Forrest & and Frozen (Day) cuts the sample size way down, but I think the quality of punishment make up for it … and my derpy record keeping.

How River City (Day) fell off the list of Hard Maps, I don't know …


… Well: I did record one game after the Octacore Patch; Forrest Snow

Teh framerates strike me as same ol' same ol', but the CPU loads are real different, even with my "normal" set of three "thread-placement" lines.

Point of order: Hyperthreading is invisible to Cryengine, and I'm "just" a hexacore.

[Exarch Levin]

Forest Colony is a more demanding map than most?

I still have trouble with the concept that the game is CPU limited when yet no CPU cores ever hit 100% utilization during gameplay.

Your GPU is also barely utilized by this game. Seeing these low-GPU-utilization charts helps me wrap my head around why my mighty 290 hasn't been giving me a sizeable FPS boost over my jury-rigged Radeon HD 68XX Crossfire setup that I'd been using previously, and why my FPS in-game is much the same regardless of resolution.


BTW, is that a CRT monitor in your setup?

[Catamount]

Yes, Forest Colony is a brutal map on your CPU. AFAIK no map produces lower minimums for me. Even CW runs don't seem to produce mins as low as just a random Forest Colony drop.

[Goose]

Exarch Levin, on 26 December 2014 - 07:47 PM, said:

BTW, is that a CRT monitor in your setup?

Over on the left …

So I just got off Frozen!


I'd rem'd out the three thread-placers, like I said; Got the expected Core #5/ ca_thread0 load, and the others are sort'a "normal", but I don't remember seeing ca_thread0 ever react like that to my death.

I think I'll move Water and Task1, again, as Core #1 just looks lonely.

But moar importantly, I'm now inspired to jack most of my setting back up, 'cept Object Detail, and Glow: I think them two are on ca_theard0, the rat ******** …

[Goose]

So I CtD just as I'm thanking my lucky stars for putting me on Forrest.

FML

[Lordred]

Goose, on 26 December 2014 - 08:24 PM, said:

Spoiler

Over on the left …

Goose, your Gouf is showing.....