110 replies to this topic

[Lordred]

DavidHurricane, on 11 October 2014 - 08:58 AM, said:

Please, just once, tell us why we can't photograph your beautiful Mechs! At least tell us why we can't disable PostAA at this time!

It was because the command r_postaa=1 was stuck on, somewhere in the build, it was just simply over-riding the command so it would always be on.

Alexander Garden, on 10 October 2014 - 06:54 PM, said:

Okay, pre-Thanksgiving weekend update time. It's a good news/bad news kind of update.

The 'forced PostAA' bug has been squished, and if all goes well the fix should roll-out with the October 21 patch.

[Cyberiad]

Hmm.. The ghosting is still actually happening for me although it is no longer appearing in screenshots.

This is what I still see even with the workaround + MSAA (screenshot with postAA):


The new screenshots with MSAA + workaround don't show this but I do see it in game.

These are my graphics settings:


This is my user.cfg:

r_HDRRendering = 0
r_MotionBlur = 0
gp_option_ShowCockpitGlass = 0
r_DepthOfField = 0
r_HDRGrainAmount = 0.0
cl_fov = 105

On a side note, if you toggle the motion blur option from off to high while the general graphics setting is custom, you get real motion blur back again:


It would be nice if we can just set it to high and just have motion blur enabled and not have to toggle it off and on every time the client restarts if we want it.

[VagGR]

bump...and while youa re at it..please...pleeeaaaase make another optimization pass on the game...

[Lordred]

Does it still look like the fix will make it in for the 21st?

Thanks.

[Alexander Garden]

Just confirmed the PostAA fix in the patch build, so it'll be rolling out tomorrow.

To clarify:

PostAA will not be forced On when dropping into a match or the Testing Grounds.

PostAA will still produce ghosting when On.

Heat vision is not yet functional under MSAA/TXAA. That fix is ongoing, and will not roll out with the fix tomorrow.

[Koniving]

Lordred, on 10 October 2014 - 12:42 PM, said:

Yes, AMD/ATI users experience the IR bug, Koniving will post the relitive proof for you, but I can port the game to my APU unit to do it in a few hours for you.

Alexander Garden, on 10 October 2014 - 12:50 PM, said:

Adding r_HDRRendering = 0 to your User.cfg should restore IR under MSAA.

Lordred, on 10 October 2014 - 01:05 PM, said:

Tested: Worked.

Great find Alex!

I didn't get around to this before Lordred gave me Alex's fix for the IR bug... but I have to do this fix, brand new, every single time. (Not entering the code, but for some reason I can't get DX-11 to stay on... I'll be deleting the system override.cfg [where I forced it over to DX-11 + MSAA so I didn't have to open the game, do it, restart, etc. when I closed the game and put in the code in user.cfg] to see if maybe there was something wrong with that.).

On a side note, looking forward to not getting motion sickness from temporal AA!

Edited by Koniving, 20 October 2014 - 10:09 AM.

[Diffusion9]

Very much looking forward to the patch today because of this. Hoping the fix is good, and I can start playing regularly again!

[Galland]

I've been testing the r_HDRRendering = 0 workaround for Thermal vision in MSAA and it appears to be completely disabling AntiAliasing. I see jagged edges on a Summoner in Mech Bay, for example, as well as the radar dish in Forest Colony.

[Cyborne Elemental]

Definitely working.
Its soooooo nice to have that bug finally solved.
Also getting a nice fps boost too, averaging about 15-20 fps higher now.

Good bye drunk vision, good bye

[kuangmk11]

So happy this got fixed!

[Cyberiad]

Any idea when heat vision will be fixed in TXAA/MSAA?