Remedy : Control PC Game - Need some Help PLS !

"

Schmockla wrote:

...
How can i fix this ?
Is there any line i can add in tweakables to fix it ? or do something in dev menu ?

"

Morkonan wrote:

"

Schmockla wrote:

...
How can i fix this ?
Is there any line i can add in tweakables to fix it ? or do something in dev menu ?

I don't know anything about the specific game/program involved, but that looks like a "smooth shading" issue. And, yes, it's related to Level of Detail, but it could be caused by several things. Basically, the display/game can't figure out "hard edges" on the models in question. They get "balloonified" :) because the method the engine/display is using either does not have enough data to figure out where the edges are (Depending on how it does that), the reference that is supposed to tell it that information at that LoD is missing/borked, or the geometry itself isn't dense enough to confer that information for smooth shading.

First, what GPU are you using?

Next, try turning down "texture filtering."

What I would suggest is to go into your driver settings and create a custom preset for the game's executable. Then, start looking there for possible solutions/workarounds.

AMD often gets the short-end of the stick by game devs because they're generally not optimizing for AMD... Nvidia is the King, atm, and that gets the most attention. Your issue could be related to that if you're running AMD.

Note that what you're seeing is on background objects. Several of these present certain sorts of surface geometry to the engine that is obviously optimized to reduce load. IOW - "They're background objects and such objects don't need a lot of geometry nor do we want that hogging up space."

But, they're relatively complex objects... Round tank with hard-edge overlap, spindly railing, very complex looking stack of pallets, possibly even several combined groups in it that could also have their own materials sets. (Wood pallet, stuff on top of it, either as one object or could be several separate objects, but that it all changes at once means its being subjected to the same problem.)

This is a "developer issue" that may or may not have a suitable work-around on your end. Start with the end-game options focused on dynamic changes, like LoD, Texture filtering, mipmap, etc. Then, set up a custom preset GPU driver setting for the game (so you don't end up changing your driver settings for everything) and start making adjustments there. For AMD, the first thing I'd suggest is lowering or turning off anti-aliasing and checking performance in-game. Then, if it works, adjust settings in-game to suit. If that doesn't yield good results, try other things like texture filtering/lod adjustments before going back to the driver preset to test something else.

"

Schmockla wrote:

...Im also using developer menu for the game that lets me change every little thing in the game, but i cant find anything that changes that.
I think it's categorized as mesh, and yes it might be LoD based....but nothing i do changes that, lowering or maxing up in-game graphics/resolution has no effect.
...

"

Morkonan wrote:

"

Schmockla wrote:

...Im also using developer menu for the game that lets me change every little thing in the game, but i cant find anything that changes that.
I think it's categorized as mesh, and yes it might be LoD based....but nothing i do changes that, lowering or maxing up in-game graphics/resolution has no effect.
...

You're using this? https://www.nexusmods.com/control/mods/28

If so, that could be the issue. It's using a .dll to direct the executable to other places to look for data. That will supersede vanilla sources of data, which means there may be something that is overwriting what is supposed to happen in that rendering process.

For instance, what if during testing the developer figured out that certain mesh objects didn't have very well defined edges and were too lightweight in terms of geometry to tell the renderer it's supposed to be a hard edge there? So, time for the little "fix" before pushing it to publishing. But, since it was just a tiny fix, there weren't any controls put in for it that were accessible outside the executable... or something like that. Some mod that accesses standard setting info to change it may not include that little fix since it's basically "invisible."

Or, it's just the material file and it's looking for something that it can now no longer find.

Or, nobody cares and didn't report it. :)

In any case, I'd uninstall the mod and be sure to remove that .dll file mentioned in the mod's thread, above. Alternatively, you may be able to just rename it with a ".old" extension (don't include the quotes) to temporarily prevent the executable from tying to obey it.

You said these were "mesh" objects, but is that their actual extension? (ie: you can see object files in a directory and they're .msh or .mesh)

Apparently, the game uses the proprietary "Northlight Engine." https://www.remedygames.com/northlight/

Neato... But, that makes "debugging" something like this a bit more difficult.

Like many problems in a game where a mod is being used, the most common answer is always... "It's the mods." :)

"

Morkonan wrote:

...

"

Schmockla wrote:

"

Morkonan wrote:

...

btw just to be sure what dll were u saying to remove ? the devmenu one ?

"

Morkonan wrote:

"

Schmockla wrote:

"

Morkonan wrote:

...

btw just to be sure what dll were u saying to remove ? the devmenu one ?

I was speaking to that mod I linked, above. I don't know that's what was being used or not, but it sounded like the one you were using.

You'll have to refer to that mod's page. I am not familiar with it nor the game "Control." :)

But, I did see where the mod page mentioned that it's .dll was required. That "dynamic linked library" file type is something the executable will look for per "Windows." Such files tell the program "here's stuff you need to know." As long as any third-party .dll files are in the root directory or other directories the executable will access, it's going to "obey" them.

However, it could likely the game has its own .dll files, too. You have to know which ones have been installed by the mod in order to remove those by hand if a typical "uninstall" process won't do it for you. What you can do is "rename" the suspect .dll using an extension neither Windows nor the game will recognize as useable, like .old. If that "breaks something," rename it back to .dll.

If you use an uninstaller or a component that untoggles/unloads the mod, it may not touch that .dll when it does that. If the .dll is still there, the executable will attempt to obey it even if the directories its referring to are now empty.