16 replies to this topic

[LordBraxton]

So the graphics used to be far better, and I don't expect PGI to fix it (or anything at this point.) One feature that would make a world of difference to me however, is the old antialiasing. About 2.5 years ago, when MWO's graphics took a nosedive and never recovered, the Antialiasing was the most painful loss for me. Regardless of AA setting, this game looks like a mess of jagged edges, like papercraft models made in a preschool. I can deal with the horrible texture pop-in. I can deal with the vastly inferior lighting and animation. I can deal with the washed out colors. I CANNOT deal with the horrible jagged edges. None of my GPU settings\overrides seem to help. I would love PGI to take responsibility and revert the game to closed beta quality, but failing that.... If anyone has advice on how to fix the AA, either with 3rd party programs or GPU settings. I'm on a Radeon build.

[x Marder x]

All i want is a warhammer.

So you ppl get paid to spam that or you do it as a hobby.

What kind of autism you have and how can i get it too.

Why not posting in sugestion forum and asking about new or imp. Gfx?

[Insects]

Screenshots to compare with others?

[LordBraxton]

x Marder x, on 03 June 2015 - 06:16 AM, said:

All i want is a warhammer.

So you ppl get paid to spam that or you do it as a hobby.

What kind of autism you have and how can i get it too.

Why not posting in sugestion forum and asking about new or imp. Gfx?

It isn't a suggestion, I want advice on 3rd party graphic software. Troll elsewhere.

Edited by LordBraxton, 03 June 2015 - 07:17 AM.

[Joseph Mallan]

x Marder x, on 03 June 2015 - 06:16 AM, said:

All i want is a warhammer.

So you ppl get paid to spam that or you do it as a hobby.

What kind of autism you have and how can i get it too.

Why not posting in sugestion forum and asking about new or imp. Gfx?

You really don't want to be Autistic. You really don't. I see to much of it in my family. You just don't know what you ask for.

[Nightmare1]

x Marder x, on 03 June 2015 - 06:16 AM, said:

All i want is a warhammer.

So you ppl get paid to spam that or you do it as a hobby.

What kind of autism you have and how can i get it too.

Why not posting in sugestion forum and asking about new or imp. Gfx?

You might not be autistic, but it appears you definitely have a case of idiocy.

[LordBraxton]

To further dismiss Marder's post, I am not asking about new graphics, I'm asking about the old ones. However, any 3rd party AA advice would be helpful.

Edited by LordBraxton, 03 June 2015 - 07:18 AM.

[Jetfire]

DX11 and MSAA looks great, no jaggies here.

[Bulletsponge0]

Jetfire, on 03 June 2015 - 07:42 AM, said:

DX11 and MSAA looks great, no jaggies here.

what's your rig set up and what kind of fps do you get in game?

[Goose]

FXAA, ether in-game or from the nVidia driver via nVidia Inspector, is just about optimal; The SMAA Injector I found doesn't work, and SweetFX both has to be the 2.0 alpha bundled with ReShade, and requires you to use the 32-bit client.

Selecting MSAA in game is way punishing, but responds to

r_MSAA_samples = x
r_MSAA_quality = y

where "x" is 2, 4, or 8 for sample, natch, but "y" is this odd-ball protocol for talking about adding Cover Sample to your Mufti-Sample: 0 is off, 2 is "equal," and 4 is "high," as seen on the chart linked. Presumably, nVidia would bounce a 2/2 combo, as that's an ATI-only, which, in turn, can never accept a quality = 4 …

I can't tell if those two r_MSAA_whateves interact with TXAA.

I'm still not clear what PostAA really is, nor have I figured out how to get the SMAA in the engine to fire up (nor if the "T" in half them SMAA modes stands for "stacking on FXAA") …

Good luck, buddy: MSAA means GTX 780s in SLI …

()

Edited by Goose, 03 June 2015 - 09:11 AM.

[Goose]

D'oh

Goose, on 03 June 2015 - 08:16 AM, said:

… and requires you to use the 32-bit client.

Got'a not use FRAPS when trying combos with the 64-bit client.

[Navid A1]

Goose, on 03 June 2015 - 08:16 AM, said:

FXAA, ether in-game or from the nVidia driver via nVidia Inspector, is just about optimal; The SMAA Injector I found doesn't work, and SweetFX both has to be the 2.0 alpha bundled with ReShade, and requires you to use the 32-bit client.

Selecting MSAA in game is way punishing, but responds to

r_MSAA_samples = x
r_MSAA_quality = y

where "x" is 2, 4, or 8 for sample, natch, but "y" is this odd-ball protocol for talking about adding Cover Sample to your Mufti-Sample: 0 is off, 2 is "equal," and 4 is "high," as seen on the chart linked. Presumably, nVidia would bounce a 2/2 combo, as that's an ATI-only, which, in turn, can never accept a quality = 4 …

I can't tell if those two r_MSAA_whateves interact with TXAA.

I'm still not clear what PostAA really is, nor have I figured out how to get the SMAA in the engine to fire up (nor if the "T" in half them SMAA modes stands for "stacking on FXAA") …

Good luck, buddy: MSAA means GTX 780s in SLI …

()

Well as fa as i remember, FXAA is a very fast non-demanding method. Its a post-process which works on an already rendered image. It simply blurs out thee jagged edges along with textures and everything in the scene. So it gives you less jagginess with almost no performance loss at the cost of blurry textures (a post process can not tell what is an actual edge and what is a texture with an edge in it.

MSAA and TXAA on the other hand force the renderer to render the same scene multiple times in different (usually higher) resolutions and then down sample to your main resolution. Think of it as if you tell the game to render in 4K and use that data in an algorythm to down sample to 1080p to remove jagged edges. It gives good results with no blurry textures at the cost of SIGNIFICANT performance loss.

Unfortunately FXAA in MWO gives a ghosting effect on moving objects which is very unpleasant. And lack of PGI experience in cryengine does not help either.

Edited by Navid A1, 07 June 2015 - 08:45 AM.

[Goose]

I think you've got PostAA mixed up with FXAA

[LordBraxton]

Those screenshots just remind me of how lovely closed beta was... ugghhh it burns.

I'm not gonna lie, the last time I felt knowledgeable about graphics was when we were debating directx vs opengl on counterstrike 1.6

On the radeon catalyst system, what would you suggest I try implementing?

It seems to me none of them actually override the game settings even when set to.

Im also wary of messing with any of MWO's actual files...

I weep for inverse kinematics.

Edited by LordBraxton, 07 June 2015 - 11:06 AM.

[Navid A1]

LordBraxton, on 07 June 2015 - 11:04 AM, said:

Those screenshots just remind me of how lovely closed beta was... ugghhh it burns.

I'm not gonna lie, the last time I felt knowledgeable about graphics was when we were debating directx vs opengl on counterstrike 1.6

On the radeon catalyst system, what would you suggest I try implementing?

It seems to me none of them actually override the game settings even when set to.

Im also wary of messing with any of MWO's actual files...

I weep for inverse kinematics.

Every one weeps for "REAL TIME" IK like the old days. IK is there already... but it only triggers when a mech is killed now (it is released from server key-frame)

Spoiler

Enrique Barahona Ramos, on 28 January 2015 - 06:18 PM, said:

Hey guys, let me address some of the concerns and observations made here.

It’s true that some mechs need a TLC pass, that’s evident in the DWF and WHK, part of the problem stems from the fact that they were released in a pack so there’s less animation man-hours available to work in them, as opposed to other mechs released individually.

The wonky behavior of the DWF in slopes is a mix of code and animation issues, we’re looking into this. Regarding its “prancing and bouncing”, I have to agree that for its weight class is way too much, and the same goes for other mechs mentioned in this thread.
Bear in mind that animators also try to give each mech a distinctive motion where possible, as the more mechs are released the harder it is to make them stand out in the crowd.
Back in the day, it was really easy to spot a Trebuchet out of an incoming lance. Nowadays a distinctive silhouette is not enough to distinguish who is who in a crowded battlefield, so we try to make up for that with animation (to the extent that is possible to do that with a hulking walking tank).
Albeit the DWF weighs 100 tons, you still need to make sure the anim cover the distance when it runs @ 50kph. So the speeding up of the animation compounds the kinks and bounces and makes them all the more evident.
Anyways, we’ll give the mechs mentioned in this thread a good revisiting, so they move and look the part.

The ground detection (a.k.a runtime leg IK) is a source of frustration too for us since the start.
When we first started to implement it, the first hurdle we encountered is that the sheer size of the mechs made the built-in ground detection inaccurate.
Once coders got around it and got it working (as the cool pic of the hunchback shows), the problem became the overhead in raytracing two feet times a dozen plus mechs, which is what you regularly see on-screen in a regular match.

Coders again sought solutions to deal with that bandwidth problem, but then kinks would appear such as legs still flexing after re-entering level ground, which looked a lot worse than not having the IK at all. So it was a matter of choosing the lesser of two evils, which is why IK is off for the time being. This is a bummer (understatement of the year so far), and as animators are very fastidious about their work, you can be sure we’re the first to be very frustrated by this issue.

This doesn’t mean we’re still not looking for a solution. In the meantime, every new mech is still rigged with the bells and whistles needed to detect ground, for when the time comes to flick the switch back on.

Enrique Barahona Ramos

El Señor Animador.

[LordBraxton]

That is HUGE (old) NEWS Navid!

That means there is no excuse for them to not eventually repair real time IK!

They should try slowing down the walking gaits as well, looked a lot better before.

Edited by LordBraxton, 07 June 2015 - 11:22 AM.

[Goose]

LordBraxton, on 07 June 2015 - 11:04 AM, said:

On the radeon catalyst system, what would you suggest I try implementing?

I don't really "speak" Radeon, but as a WAG, you could turn on MSAA, in-game, and set "r_MSAA_quality = 2" and "r_MSAA_samples = x" where "x" is two, four, or eight, depending on what your hardware can pull off.