Jump to content

Still Unable To Disable Postaa

Bug Report

110 replies to this topic

#1 Lordred

    Member

  • PipPipPipPipPipPipPipPip
  • The 1 Percent
  • The 1 Percent
  • 1,474 posts

Posted 05 September 2014 - 11:39 AM

Setting the AA mode to No AA via the advance options menus still results in Post AA being applied.

Setting 'r_postaa=0' in User config and system override still results in Post AA being applied.

Cryengines Post AA produces an undesirable image effect, for some it is bothersome, for others it is of no concern. For me, it gives me a headache.

PostAA could be disabled up till UI2.0 was released, since then it cannot inless you are using MSAA or TXAA which override postAA.

There must be some errant code forcing the application of PostAA when no AA is selected.



Report:
Unable to Disable PostAA (Cryengines Temporal AA) With out use of higher forms of AA (MSAA/TXAA)

Reproducability: 100% using NoAA/PostAA (When set to No AA, this should not happen.)

Most noticeable:
When a mech is passing through your view when you are not tracking their movement.
High Resolutions.

Less Noticeable:
When you are tracking the movement of another mech.
Low resolutions

Fix:
Find the code which is blocking 'r_postaa=0'

This is an example of what is seen.

Posted Image


I have had a few exchanges with Matthew Craig on the issue.



Transcript from my exchanges with Matthew, who was very helpful in his attempts to peg the problem down.
Spoiler

Edited by Lordred, 06 September 2014 - 06:40 AM.


#2 Wintersdark

    Member

  • PipPipPipPipPipPipPipPipPipPipPip
  • 13,375 posts
  • Google+: Link
  • Twitter: Link
  • LocationCalgary, AB

Posted 05 September 2014 - 11:51 AM

Just to add to this: I have exactly the same problems Mordred has, and have taken all the same steps to rectify it/test.

I am running an AMD Phenomenon 2 X4 965 BE, with a AMD 7850, so its not limited to nvidia.

Its intensely aggravating to me, though it doesn't give me headaches it severely reduces the visual quality of the game. Using MSAA does correct it, but my 7850 lacks the horsepower to do that at reasonable framerates.

This has been a problem for me for a long time, and it affects almost everyone I talk to. While Mr. Craig can't replicate it, he's definitely in the minority - almost everyone I know gets this, across a wide range of hardware, software, and settings.

#3 Flak Kannon

    Member

  • PipPipPipPipPipPipPip
  • Overlord
  • Overlord
  • 581 posts

Posted 05 September 2014 - 11:55 AM

Thank LordRed.

I to am still experiencing this amazingly annoying issue.

I think you and I posted the same day it started occurring.. maybe after the implementation of DirectX11..? I don't remember which patch, I could go back and look at my old posts.


anyway..

Thank you Lordred for staying on top of PGI on this issue.


Your image is exactly what happens to me also.. it usually occurs in the first 60 seconds of a match.


Again.. PGI.. Please, Please, Please... Pretty Please Fix this.


Thank you.

Edited by Flak Kannon, 05 September 2014 - 11:56 AM.


#4 Wintersdark

    Member

  • PipPipPipPipPipPipPipPipPipPipPip
  • 13,375 posts
  • Google+: Link
  • Twitter: Link
  • LocationCalgary, AB

Posted 05 September 2014 - 11:59 AM

I'd like to add: Even if you (PGI) cannot replicate the issue, see the screenshots: we clearly suffer it. Please give us a functioning ability to fully disable PostAA, without having to use a higher cost AA method, as that does fix the issue.

#5 kuangmk11

    Member

  • PipPipPipPipPipPipPip
  • Veteran Founder
  • Veteran Founder
  • 627 posts
  • LocationW-SEA, Cascadia

Posted 05 September 2014 - 12:03 PM

Thanks for posting this (again). it really needs to be fixed.

#6 Koniving

    Welcoming Committee

  • PipPipPipPipPipPipPipPipPipPipPipPipPip
  • The Guide
  • The Guide
  • 23,384 posts

Posted 05 September 2014 - 12:49 PM

AMD Phenom II X950 quad core processor at 3.6 ghz.
16 Gigs ram
XFX AMD Radeon 6870.
Windows 7.
I get the issue with all AA settings except MSAA but the MSAA in MWO is extremely poorly optimized compared to that of ANY Crysis Game, Star Citizen, and virtually any other game I've ever played.


In video you almost can't see it unless cut down to 30 fps.
Still frames however, you can track its history back to closed beta.

#7 Modo44

    Member

  • PipPipPipPipPipPipPipPipPip
  • Bad Company
  • 3,559 posts

Posted 05 September 2014 - 02:10 PM

This started happening when user.cfg was locked down hard to prevent cheating. It seems that nobody bothered to look at it since then to whitelist anything.

BTW, some documentation on what actually works when in user.cfg would be nice. There is no point in looking for CryEngine tweaks when most will not work/will work randomly.

#8 Lordred

    Member

  • PipPipPipPipPipPipPipPip
  • The 1 Percent
  • The 1 Percent
  • 1,474 posts

Posted 06 September 2014 - 05:47 AM

Additional testing.

All settings = LOW
Frame rate limit of 100 used.

@720p noticeable
Posted Image
@2160p VERY noticeable
Posted Image

Low-Spec simulation frame rate limit set to 33fps.
Posted Image

#9 Lordred

    Member

  • PipPipPipPipPipPipPipPip
  • The 1 Percent
  • The 1 Percent
  • 1,474 posts

Posted 07 September 2014 - 10:05 PM

Very shameless bump to keep the topic visible, as most of the current 'feedback' is related to complaints about heat changes, and not about bugs.

#10 Zero Verniers

    Member

  • Pip
  • Shredder
  • 14 posts
  • Locationin the sky, parachuting in an ejector pod.

Posted 08 September 2014 - 07:47 AM

I have experienced blurs as well but not as bad as what u guys posted here. i also have all the settings related to blur turned off.

Been a while too since this bug has been in place yet it hasnt been addressed yet.

#11 Cyberiad

    Member

  • PipPipPipPipPipPip
  • 342 posts

Posted 08 September 2014 - 11:25 AM

Setting the antialias setting to MSAA removed ghost/frame-blending for me.

#12 Cyberiad

    Member

  • PipPipPipPipPipPip
  • 342 posts

Posted 08 September 2014 - 12:23 PM

Heat vision doesn't work in MSAA mode, just like TXAA. When antialiasing is off the ghosting/blending is still there.

#13 Lordred

    Member

  • PipPipPipPipPipPipPipPip
  • The 1 Percent
  • The 1 Percent
  • 1,474 posts

Posted 10 September 2014 - 05:55 AM

Bump

#14 Lordred

    Member

  • PipPipPipPipPipPipPipPip
  • The 1 Percent
  • The 1 Percent
  • 1,474 posts

Posted 11 September 2014 - 05:55 AM

bump till there is an acknowledgement.

#15 Cyberiad

    Member

  • PipPipPipPipPipPip
  • 342 posts

Posted 11 September 2014 - 06:18 AM

Lordred you can submit a support request and they will most likely tell you if it's a known issue/currently tracked in their system (Jira?).

#16 Wintersdark

    Member

  • PipPipPipPipPipPipPipPipPipPipPip
  • 13,375 posts
  • Google+: Link
  • Twitter: Link
  • LocationCalgary, AB

Posted 11 September 2014 - 07:35 AM

View PostSiliconLife, on 08 September 2014 - 11:25 AM, said:

Setting the antialias setting to MSAA removed ghost/frame-blending for me.
as Lordred said in the OP. However, MSAA comes with a heavy performance cost in this engine.

#17 Cyberiad

    Member

  • PipPipPipPipPipPip
  • 342 posts

Posted 11 September 2014 - 08:53 AM

View PostWintersdark, on 11 September 2014 - 07:35 AM, said:

as Lordred said in the OP. However, MSAA comes with a heavy performance cost in this engine.


Not only that but heat vision does not work when MSAA or TXAA is selected as the AA option, making these settings entirely unusable.

#18 Lordred

    Member

  • PipPipPipPipPipPipPipPip
  • The 1 Percent
  • The 1 Percent
  • 1,474 posts

Posted 12 September 2014 - 01:19 PM

Bump for a dev acknowledgement of issue.

#19 Cyborne Elemental

    Member

  • PipPipPipPipPipPipPipPipPip
  • 3,983 posts
  • LocationUSA

Posted 12 September 2014 - 02:10 PM

Yeah this it the Motion blur bug, been there since that first patch when they setup DX11 support.

Its happening on Nvidia, Its happening on ATI, its happening in DX9, its happening in DX11.

Lower fps seems to accentuate the issue.

Seems to be mostly on moving objects within the render scene, but I'm willing to bet that its a full pass on every frame, some shader effect w/e.

Might be an undefined line of code, so the engine is just defaulting the effect.

Figure it out and I'd bet there is a big bump in FPS across the board.

Needs to be fixed, hopefully soon, preferably very very soon.

Edited by Mister D, 13 September 2014 - 12:13 AM.


#20 Tahribator

    Member

  • PipPipPipPipPipPipPipPip
  • Fire
  • Fire
  • 1,565 posts

Posted 13 September 2014 - 08:26 AM

It happens to me too with an NVIDIA card. Here's an example:

Posted Image

As Mister D said, this problem is present since months.





1 user(s) are reading this topic

0 members, 1 guests, 0 anonymous users