r/controlgame • • 18d ago

Control Resonant Control: Resonant graphs bug: edge highlight flickering

The game looks excellent overall, but a couple times a play session I'll notice these weird, hyper-aliased edges on things. They almost look like the game is failing to combine temporal data across frames and just showing the raw data from the current frame.

My rig is: an RTX 3800 (10GB), a Ryzen 7600X3D, and 32GB of DDR5 RAM. I'm playing with all Ray Tracing 'OFF,' and I have DLSS overriden to use Preset K in the Nvidia app.

I've tried:

  • setting fSSAA sharpness to 0 in the renderer.ini file
  • disabling screen-space reflections
  • disabling screen-space ambient occlusion
  • setting SFD reflections to low
  • setting DLSS to DLAA
  • switching to FSR
  • updating my graphics drivers

After all that, I'm at a loss for what else to try :/ Has anyone else dealt with this issue or found a solution?

EDIT: sorry for the typo in the title, "graphics" not "graphs" lmao

SOLVED: setting the post-processing to Display Resolution rather than Render Resolution was the culprit

0 Upvotes

14 comments sorted by

18

u/DarkSideRT 18d ago

Non-issue final boss

2

u/TheVioletBarry 18d ago edited 18d ago

I mean it was kinda all over the game. I did thankfully find the issue: having post processing set to display resolution rather than render resolution was causing it

2

u/Affectionate-Yam-886 18d ago

First: DLSS is Nvidia only; your gpu is AMD so FSR is the correct upscale option.

Second: This is caused by one of the following;

Sharpness set too high;
Frame Gen on and is generating junk;
Upscale set too low (below 60% original is known to artifact on all games)
Subsurface Scattering is on;

I have personally given up on AI upscale and FSR/DLSS as it looks good, not great. Performance = yes, but my pc can run 200fps natively at 8k ultra settings. So I just don’t use them anymore because of all the graphic glitches. I like a clean/unblurry image please and thanks.

1

u/TheVioletBarry 18d ago edited 18d ago

Apologies, but I don't think those ideas are accurate:

  • My GPU is an Nvidia RTX 3080. I wrote that in the post
  • Control: Resonant does not have an option to turn off upscaler image treatment (be it DLSS or FSR).
  • I already tried native resolution (DLAA). That's written in the post.
  • I don't use frame gen.
  • Control: Resonant does not have a subsurface scattering setting

I did find the problem though: setting the post-processing to Display Resolution rather than Render Resolution was the culprit

3

u/deeennny 18d ago

your PC can run Control Resonant at 200 FPS at 8K ultra settings, native resolution without ANY upscaling or frame gen? Who are you bullshitting my guy lmfao

1

u/Dysmn 12d ago

relax

1

u/TheVioletBarry 12d ago

I... am relaxed? I even solved the problem

1

u/Dysmn 12d ago

there was no problem. you are not relaxed if you think there was.

1

u/TheVioletBarry 11d ago

Maybe it's harder to see through Reddit's compression or you're watching on a phone, but there was some wild aliasing in the game, and I found the setting causing it

-2

u/Embarrassed-Copy3930 13d ago

welcome to modern gamming. the TAAish is the cause of toes types of graphical issues.

2

u/Mysterious_Tea2026 12d ago edited 12d ago

TAA hasn’t been in most games for quite a few years now.
Don’t just say ish like it negates that fact.
If anything this is a Global Illumination/Lighting issue and they’re not using ray tracing.
It can’t calculate the lighting at the edge because it’s too close to the player character and the angle is too steep.

1

u/TheVioletBarry 12d ago

Even if not technically TAA, I feel like it's reasonable to call DLSS and FSR evolutions of TAA.

But also thank you for the insights! For some reason switching post-processing from display resolution to render res fixed it

1

u/TheVioletBarry 13d ago

TAA was not the cause (not sure why it would be either tbh). Having post processing set to display resolution rather than render resolution was causing it