In UE4.16 and 4.18 (we have modified the engine for our game though)
We have started to see this issue with shipping builds of our game. The screen goes Green and flickers at 60FPS
• Black shows as Green
• Yellow shows as Pink.
• Only occurs in Fullscreen (but that’s the default so the first thing you see).
• Visible with or without VSync, although Vsync ON exacerbates the problem.
The issue can be resolved locally by changing from Fullscreen to Windowed. Changing to borderless also solves the problem and means you don’t have to play in a window.
However this is a very problematic issue.
Drivers:
Latest Windows update
Latest Nvidia Drivers
(as of Wed 29th Nov 2017)
There are a few simple things I would like you to try first and if these do not work we can dig deeper.
First and foremost, the approved driver for Nvidia 9 and 10 series GPUs is the 388.00 driver. If you could try rolling back to that and see if it solves your problem. Second, could you check and see if Nvidia Shareplay is running if so disable it as this could potentially be causing problems as well. Hopefully this will fix your issue and if not just let me know and we will keep trying. Thank you.
I am getting this as well. I held off on the windows update until about 2 days ago, and the next build I made had this problem. My fix is actually different though, In my graphics options menu in my build, If I set the overall scalability settings to anything, from low to cinematic, the green flicker goes away, and i dont have to touch any of the fullscreen/windowed/fullscreenwindowed settings…
edit* i realized after switching overall scalability that the windowed setting auto changes to full screen windowed and that might be what actually solves the issue… ive gone from 4.16 to .17 to 4.18 and still have this issue… .
Jeff, with all due respect to EPIC, this isn’t really resolved. You can see the pattern here with all UE4 games from PUBG to Fortnite to our(ue4 community) various development builds…
Just because WE found a solution, it doesn’t really make this resolved as the end-user trying out our game for the first time is going to be like - what is this broken piece of software that I just bought?!
*edit, i realize this is mostly MICROSOFT’s fault, as the latest update has been causing all kinds of wreckage across various different software/hardware setups… but the problem is still there, and you can’t deny that end users are going to get frustrated at the software, not at microsoft or Epic… and we as the devs will suffer… just because there is a hacky workaround it doesn’t mean the issue is resolved… this is going to affect EVERYBODY that makes a new build in this current time until someone fixes this issue (microsoft, nvidia, or epic)…
Hi Jeff, has there been an update from Unreal on this? We are still getting the issue and we did an open Beta this weekend and it is turning a lot of customers away as they assume it’s a bug with our game. Games like PUBG can get away with this but this could really destroy our player base.
Is there a patch incoming or a fix in 4.19? Even anything speculative at this stage?
Hi Jeff, has there been an update from Unreal on this? We are still getting the issue and we did an open Beta this weekend and it is turning a lot of customers away as they assume it’s a bug with our game. Games like PUBG can get away with this but this could really destroy our player base.
Is there a patch incoming or a fix in 4.19? Even anything speculative at this stage?
Have you tried the link posted above by J.C Smith? This has seemed to fix the problem for most people. I have not been able to reproduce this on my end so if you have a way to consistently reproduce the issue please let me know.
Players on Steam have been intermittently reporting this issue with my game as well. I agree with the comments above that the root cause needs to be addressed This forum thread has some hardware data from players (for various games) which may be useful in reproducing the issue.
My game’s feedback dashboard concurs with the comments above, that players who encounter this glitch conclude it’s an issue with the game; the workaround is posted on my game’s discussion board, however most players don’t visit the forums, they will simply move on to another game which works for them.
This is concerning for any game trying to grow its player base like others have said above!
It would great if Epic could take a closer look into this. Regardless of where the root-cause stems from, the fact is only UE4 games seem to be affected by this, so please help, Epic!
Myself and most of my friends are having this issue in every game that has frequent updates on UE4, such as pubg, redout:enhanced edition, squad, foxhole etc. I find it hard to believe you can’t replicate it but are there any log/debug files or anything I could send to help?
I think its honestly appalling that we are expected to follow this ‘fix’ which severely degrades the visual quality by limiting the range of colour, due to an issue solely from UE4,
I need a way to consistently reproduce this on my end in order to go any further with it. Also looking into that Thread that you posted it only looks like it is happening on Nvidia GPUs and only on certain Driver versions. This leads me to believe that it is an issue on Nvidias end not ours. However if you find a way to successfully reproduce this I can bug it.
I found an Nvidia knowledge base article which discusses this issue and the workaround. According to that article the issue is with the Windows 10 fall creators update and apparently Microsoft has fixed this issue in a preview build.
I’m not sure whether that preview build is out or not going by the build numbers, though I’m guessing it hasn’t as new players are continuing to report it for my game. Will probably need to add some mechanism to make players aware of the workaround, that’s the best I can think of until an actual fix arrives. Any other ideas or suggestions are welcome as well!
Here is how to fix screen flashing issue in Windows 10
Open Task Manager – There are many ways in which you can do that.
Method 1- Right click on any blank space in your taskbar and select Task Manager.
Method 2- Press Ctrl + Alt + Del. From there select Task Manager.
Click on the File tab. If you are unable to see File tab then click ‘More details’ at bottom left corner.
Select ‘Run new task’.
Type ‘msconfig’ without quotes.
Click on the ‘Services’ tab.
Scroll down and find two services named ‘Problem Reports and Solution Control Panel ‘and ‘Windows Error Reporting Service’. If you have difficulty finding these two services then you click on ‘Service’ column header in the table. This will alphabetically arrange all the services.
Uncheck these two services. Press ‘OK’.
If Windows prompts you to restart the system then restart the system and your problem will be solved.
Windows 10 machine with any nvidia gpu, multiple monitors, make sure your primary display is NOT your left most monitor or “display 1” and have a shipping build of any project made with UE4.18 that boots to fullscreen.
For some reason 4.18 will never boot to your primary display and will always boot to “display 1” unlike previous versions of the engine, display 1 in fullscreen when it isn’t set as your primary display seems to always have the green flashing going on.
This