Factorio Forums

I have noticed when playing the latest update that most textures pop bright and have somewhat of a outline to them. I personally narrowed it down to Gsync.

Moving it to my other monitor or turning off gsync fixes it. I am not too sure if it is because I have a freesync monitor with gsync enabled (new feature from nvidia) or what. This is the only game I have seen to have this issue so far.

Not sure if this can be fixed because I currently would rather not disable gsync while playing the game everytime or having to play on my other monitor.

Maybe a logfile could be useful.
Also if the issue can be screen captured, it could be helpful

Log file here: https://pastebin.com/VdpPLntW

So I tried screen capturing it and nothing. I assume because of how gsync works.

Here is the gif of how it looks which looks fine on this end. Which is def not the way I am seeing it.


So what I did instead is took a really bad camera pictures lol.
Standing still and Moving

Basically the best way to describe is everything gets very darkened edges almost like phantom textures when moving or something like that. Borderlandish. But really disorienting. I have tried fooling around with every setting and force-d3d. The only way I have solved this turning off gsync.

Screen flickering when moving by foot or vehicle.

I attach 4 files, screen shot, photo when moving(flickering), photo when not moving(normal), and log.

I cant find no flickering on screen shot, so I attached photo.
On the photo when moving, i draw red circle where you can see flickering clearly.
And if you see the photo carefully, you can see flickering occurs horizontally and screen wide.

I think this is another problem.

I use Radeon 5770, so I cant use G-sync.
I changed radeon setting, such as wait for vertical refresh(on, off) and frame rate target control(off, 60fps), but nothing changed.

So, I cant find any way to avoid this problem.

Can anyone tell me why my game is looking like this?

https://imgur.com/a/CGdqM3i

Please Help!

Hello, is this still an issue in 0.17.48?