The top and left hand side of the screen seem to get previous frames added on to them. Switching to FXAA didn’t solve the issue either. here’s a screenshot.
I tried testing your issue with different types of blank projects following with your reproducible steps, but was unable to see what you are reporting.
Can you reproduce this in a new blank project?
Also, try closing all of the applications aside from the Engine and see if they could be affecting the issue as well. Have you set the resolution in code somewhere for your project? This could be clamping the overall fullscreen effect of your game, and displaying it improperly on your monitor.
Let me know what you discover and if you have further questions.
Not had a chance in a blank project yet, but here’s a video if it makes it any easier to debug! Only occurs in 4.7, older versions of the project never had this.
My window/resolution settings are all at the default, and it happens on all PC’s I’ve tested it on.
We have not heard back from you in a few days, so we are marking this post as Resolved for tracking purposes. If you are still experiencing the issue you reported, please respond to this message with additional information and we will offer further assistance.
I was able to reproduce this in the SillyGeo content example on the Learn tab. All i did was create a new project in 4.7, and play in fullscreen PIE. You have to play in the editor viewport.
Thank you for the extra information on where to reproduce this issue. I will return with my findings after testing. Since it is a straightforward and easily reproducible issue, I am pretty sure I will report back with an entered bug report.
Would you mind removing any Widget you are rendering to the screen and pressing play again to see if you are still experiencing the issue. I noticed the factor that unifies the issue is they are all using a Widget Blueprint.
Let me know what you discover if this changes anything or if you need more help.
I was able to reproduce this issue in 4.10.4 and added more information to a bug that was generated for this issue, which is currently unresolved. We are working to track down this issue (UE-11109) and get a fix in place, and we appreciate your patience while we do so.
Once the issue has been resolved either myself or another staff member will return with the updated information. Let me know if you have further questions or need additional assistance.