After upgrading a project from 4.6.1 to 4.7.1 I have two blueprints that are not working. Attempting to debug them in the blueprint debugger produced the image below. If I run the blueprint editor in a smaller window the command ribbon can also be corrupted making impossible to see the buttons such as “step” and “stop”. Upon stopping the game rendering returns to normal.
The top left corner works, can be panned, and updates with execution. This is reproducible on multiple different machines.
Hey rjsams,
You say you can reproduce this on multiple machines. Would you mind providing me with reproducible steps so I can test this issue on my end as well?
Thank you,
I’m trying to simplify the repro steps but it only seems to happen with a moderate interaction with C++. It does still repro on 4.7.2.
Hey rjsams,
Are you changing or setting the resolution of your windows within your code?
Have you set the DPI or Scaling of the Engine anywhere in your ‘Editor Preferences’?
Could you also provide me with your ‘dxdiag’ and whether or not you are running a laptop to external monitor set up?
Thanks,
Reproduced on 2 monitor desktop system. Tried blueprint editor on both monitors. Also reproduces on a laptop with the single integrated monitor and integrated gtx 770m.
What makes this blueprint different from the others that still work is it dynamically adds and removes widgets. Both blueprints which do this are showing problems.
[dxdiag][2]
Hey rjsams,
I am going to test this issue soon and wanted to clarify.
The problem only occurs when you are dynamically spawning/removing a Widget?
I have a laptop with the same integrated graphics cards so will test using that set up.
Cheers,
Yes, this is what I am seeing. I’ve seen it with two different GFX cards and configurations, both NV.
If there is a way to privately upload a repro case, I could give you the full project where it occurs.
Hey rjsams,
You can send me the project via a dropbox link through a private message on the Forums.
Thank you,
Hello rjsams -
This issue should be corrected in 4.7.3. If you are still experiencing this issue please let us know and we will continue to help you on a solution.
Thank You Again for your report and help in tracking the issue down.
Eric Ketchum
