295 replies to this topic

[Goose]

[Exarch Levin]

Unfortunately I, despite using the memory settings as specified herein, am still getting terrain detail enhancement and building pop-up as I walk about in my mechs. It's like playing a console game

I have environment cranked up to high but, regardless of the setting, terrain detail and many environmental objects don't appear unless my mech is within a few meters of 'em.

[Goose]

Exarch Levin, on 27 December 2014 - 09:38 PM, said:

… many environmental objects don't appear unless my mech is within a few meters of 'em.

MW: O is a battalion scale game, hosted on a pedestrian scale engine; Prophet and Nomad are not as big as Commandos, let alown Atli.

Try setting "e_TerrainTextureStreamingPoolItemsNum =" to something outrageous, like 1024; Or maybe "e_TerrainTextureLodRatio =" to something in the 5~20 range …

[Goose]

I got my Forrest game:
I'd had a set of games, earlier, where core five was not twice as loaded and everyone else, and I was hoping for it to be a breakthrough regrading Object Detail, but alas, restarting the game reverted the core(s) to same-ol' same-ol', as I'd seen it do once ever six months.

At any rate, Forrest doesn't seem to dip into the mid-'30s the way it used to, before my memory upgrade and wipe-rebuild; Conversely, Bog is sending me down to ~36 …

[Exarch Levin]

BTW, I'm noticing (via GPU-Z and HWiNFO64) that my GPU is going into reduced-link width mode on PCI-E, dropping down to PCI 2.0 x1, x16 and then back down again. Presumably it does this because the GPU isn't sufficiently tasked but I've still "gots to know": is this normal behavior, and is it hurting my performance?

>Have added terrain vars to CFG, will test.

[xWiredx]

So far, this is what my system utilization looks like pretty regularly with the 64-bit client. I still can't use FRAPS because it makes MWO crash, but I haven't seen any yellow text at all using F9 yet.



I've got my CPU OC up to 4.3GhZ now, in addition to forcing 8x AA and 8X transparency AA via the Nvidia control panel, and I don't think I've seen any dips in the FPS numbers F9 is showing me. I have seen a couple stutters, though.

Goose is absolutely right about this game engine being built for human scale while the game itself is built on giant robot scale. That probably contributes to a lot of the performance problems, not just the pop-in and terrain issues. Rescaling everything just by a factor of 1/2 would probably bring performance problems down noticeably. In fact, I have no idea why PGI didn't build things that way from the start.

[Smokeyjedi]

xWiredx, on 28 December 2014 - 07:33 AM, said:

So far, this is what my system utilization looks like pretty regularly with the 64-bit client. I still can't use FRAPS because it makes MWO crash, but I haven't seen any yellow text at all using F9 yet.



I've got my CPU OC up to 4.3GhZ now, in addition to forcing 8x AA and 8X transparency AA via the Nvidia control panel, and I don't think I've seen any dips in the FPS numbers F9 is showing me. I have seen a couple stutters, though.

Goose is absolutely right about this game engine being built for human scale while the game itself is built on giant robot scale. That probably contributes to a lot of the performance problems, not just the pop-in and terrain issues. Rescaling everything just by a factor of 1/2 would probably bring performance problems down noticeably. In fact, I have no idea why PGI didn't build things that way from the start.

My good bud/Lance mate pulled the trigger on Asus X99 deluxe 5820 combo. under liquid cooling with a gtx980......he played for 3-4 weeks @ stock clocks......over the last few days we have got him overclocked to 4.3ghz.....needless to say hes very pleased and it crushes MWO.........I can taste the X99 now......Im salivating.........Clockspeed gods save me........

Edited by Smokeyjedi, 28 December 2014 - 08:13 AM.

[Lordred]

wired, if you don't want to do the work yourself, would you be interested in using afterburner to log the performance of a game and just send me the raw data so that I can compile it I would be interested to see.


sent via voice to text from cell phone.

[Exarch Levin]

Quote

Goose is absolutely right about this game engine being built for human scale while the game itself is built on giant robot scale.

That might explain why on the Canyon map the desert shrubs, which resemble plants that would be up to a human's ankle/knee, come up about that high on some mechs.

Quote

My good bud/Lance mate pulled the trigger on Asus X99 deluxe 5820 combo. under liquid cooling with a gtx980......he played for 3-4 weeks @ stock clocks......over the last few days we have got him overclocked to 4.3ghz.....needless to say hes very pleased and it crushes MWO.........I can taste the X99 now......Im salivating.........Clockspeed gods save me........

It is beyond hilarious, though maybe I'm laughing to hide the pain, that the game requires a beastly CPU, which has to be overclocked, to play properly but can run well on a 5 year old GPU, per the devs (which explains why even a laptop-grade Trinity APU's GPU, which is rocking graphics from that AMD gen, isn't breaking a sweat with this game).

...Doesn't X99 force you into DDR4?

Edited by Exarch Levin, 28 December 2014 - 12:17 PM.

[xWiredx]

Latest test. Veridian Bog in a DWF, 1080p, Very High, 8xAA and 8x transparency AA forced in Nvidia control panel. Looks promising.



I don't plan on collecting much more data, if any, unless there are any significant changes to be examined.

[Smokeyjedi]

xWiredx, on 28 December 2014 - 01:13 PM, said:

Latest test. Veridian Bog in a DWF, 1080p, Very High, 8xAA and 8x transparency AA forced in Nvidia control panel. Looks promising.



I don't plan on collecting much more data, if any, unless there are any significant changes to be examined.

[Smokeyjedi]

2014-12-25 00:33:24 - MWOClient
Frames: 24293 - Time: 389128ms - Avg: 62.429 - Min: 36 - Max: 131

2014-12-26 20:57:29 - MWOClient
Frames: 15062 - Time: 360000ms - Avg: 41.839 - Min: 0 - Max: 120

2014-12-26 21:21:53 - MWOClient
Frames: 19178 - Time: 298664ms - Avg: 64.213 - Min: 33 - Max: 137

2014-12-27 01:43:18 - MWOClient
Frames: 20893 - Time: 360000ms - Avg: 58.036 - Min: 33 - Max: 133

2014-12-27 01:56:30 - MWOClient
Frames: 16591 - Time: 360000ms - Avg: 46.086 - Min: 28 - Max: 86

2014-12-27 23:55:42 - MWOClient
Frames: 19198 - Time: 360000ms - Avg: 53.328 - Min: 37 - Max: 105

2014-12-28 00:26:42 - MWOClient
Frames: 14015 - Time: 262363ms - Avg: 53.418 - Min: 30 - Max: 113

2014-12-28 00:41:58 - MWOClient
Frames: 21241 - Time: 360000ms - Avg: 59.003 - Min: 32 - Max: 83

-------------------------------------------------------------------------------------
new in game settings....MSAA on 4X(-forced VIA NVIDIA CNTRLPANEL) mostly medium low part. low shaders,low postprocessing. -my own personal user.cfg file.........
2014-12-28 11:35:54 - MWOClient
Frames: 24271 - Time: 360000ms - Avg: 67.419 - Min: 36 - Max: 77

2014-12-28 21:01:53 - MWOClient
Frames: 17539 - Time: 264624ms - Avg: 66.279 - Min: 39 - Max: 118-veridian bog

2014-12-28 22:23:10 - MWOClient
Frames: 25070 - Time: 360000ms - Avg: 69.639 - Min: 38 - Max: 138

2014-12-29 21:47:15 - MWOClient
Frames: 30008 - Time: 360000ms - Avg: 83.356 - Min: 35 - Max: 125


Beautiful smooth gameplay. pretty as all hell and every single one of these matches 7 out of 8 threads are used >80%- verified each match with fresh MSI afterburner
monitor readings...

The last thread works water and particles if Ive done it correctly.......

The last test I will perform before I call er a day is to turn up particles and see if that lonely 8th core can be pegged to 80%...........

after this the only thing left to do is overclock more.......Have to hit 5.0 stable with this mobo(HT+NB @ 2558mhz and ram(2080mhz) and cooler maxed out
(temps ok but blue screen is imminent-guessing vrms just WILL NOT DO IT past 4960mhz)ff

[Exarch Levin]

Forgive mah ignorance but what is the point of OC'ing the NB for MWO?

[Smokeyjedi]

Exarch Levin, on 29 December 2014 - 07:57 PM, said:

Forgive mah ignorance but what is the point of OC'ing the NB for MWO?

Its the link between CPU and RAM, increasing it allows more bandwidth......usually if you are upping NB + HT you are about to or are in the process of FSB OC on CPU + RAM + HT-link + NB freq. they are all linked........

I would benchmark lower and pull less FPS in MWO with identical setups but one having lower NB +HT..............<2600mhz for FX series and 2700-2800 for Denebs or Thubans is the sweet spot.

[Exarch Levin]

Goose, on 27 December 2014 - 10:54 PM, said:

MW: O is a battalion scale game, hosted on a pedestrian scale engine; Prophet and Nomad are not as big as Commandos, let alown Atli.

Try setting "e_TerrainTextureStreamingPoolItemsNum =" to something outrageous, like 1024; Or maybe "e_TerrainTextureLodRatio =" to something in the 5~20 range …

I appreciate the tip. That said, Holy FPS plummet, Batman!

e_TerrainTextureStreamingPoolItemsNum = 1024
e_TerrainTextureLodRatio = 5

Took my FPS from 40-70 with an occasional lower drop to 28-35 with an occasonal drop to 18! GPU was still falling asleep during gameplay.

So how does thie

TerrainTextureLodRatio

work? Do lower numbers = higher detail?

On the plus side, buildings stopped popping in. On the down side, the terrain itself still got obviously more (or less) detailed as I walked around the map, a texture shimmer and update with every step.

Edited by Exarch Levin, 29 December 2014 - 11:53 PM.

[thunderw]

xWiredx

Can you tell me if your posted FPS is with or without vsync enabled? When I enable vsync on one card I cap at 60FPS no matter what. And I pretty much have he same system you do but with 32 gig ram.

I am not crazy tech savvy, but probably better than most. I can follow steps for tweaks. Can you provide some suggestions to get the frames you are posting with your rig?

Thanks!

[thunderw]

Smokey, can you share your config? I can mess with settings and tweak OC and override in game settings, but I am not familiar with mapping processes to threads. Can you provide some guidance?

Thanks

[xWiredx]

Vsync locks your fps to your monitor's refresh rate. Also, if you're running a 5820K like I am, don't bother with the thread assignments. They actually seemed to hurt my performance testing with the 64-bit client.

[thunderw]

Thanks xWiredx. Is it possible to get your optimum spec? Running AA outside the game, using triple threading and reducing post proc, shaders, and particles has pretty much eliminated the tear issues I was having without vsync. I am still running in the yellow for FPS though. Games start off in the 100's then quickly begin to average 25-50 range sometimes dropping into the teens in battle...

I love this game but it is so frustrating to get the best performance out of my rig for it.

Edited by thunderw, 31 December 2014 - 08:30 AM.

[xWiredx]

Are you playing CW or regular matches? I haven't run the numbers in CW because of the performance issues everybody is having (though my dips in CW are also very minimal).

Also, what's your exact hardware? What are your overclocks? I run every setting maxed out, as stated several times throughout the thread. I'm actually doing some user.cfg tweaking this morning to turn on even more eye candy because I have the performance to spare.