Sometimes when I open the editor, something will cause it to make my screen go completely white whenever I click down. It will flash white if I simply click, or stay as I long as I have the cursor held down if I hold it. It is my entire screen, not just the editor itself. It seems random when this happens, but it is frequent, and an expense of time as I have to keep reopening the editor until it does not do this. Is this a known issue? Is there something I can do to stop it?
Can you reproduce this in a newer version of the engine? Engine version 4.7.6 is our most recent public binary release and I am curious to see if this also occurs in this version.
If you do not wish to update your engine version that is totally fine, but be aware we made some really great improvements as well as added some powerful new features which could also resolve the issue you are experiencing.
Hi Andrew, I apologize for the late reply. As best as I can tell, this does not occur in 4.7, but I’ve encountered some problems converting my project to it, so I’d like to continue in 4.6.
To answer your questions, my graphics drivers are up to date. I’m on Mac so I can’t get you a DXdiag- if I understand correctly- but here is my system information:
When changing to 4.7, did you use the convert-in-place option or the open a copy?
And no worries, thank you for providing me with the requested information. I will tell you now that your memory (RAM) as well as your GPU are below the minimum recommended specs for what we suggest when using the editor.
Yeah, it’s all I’ve got to work with for now, so if that’s the nature of the problem I can live with it. So far I’ve only tried opening it as a copy in 4.7.
Open a copy is the safer option. Just wanted to double-check, but I would definitely recommend lowering your ‘Engines Scalability Settings’ to increase your performance while working with the editor.
Let me know if this helped at all. There are also other options within this same dropdown menu that will help your performance a bit. Try changing the ‘Material
Quality Level’ also.
I see this marked resolved, I am using 4.7.6 to match a Tutorial I am using, having same issue, I see no solution here.
I have used lower and higher editor versions without this issue, so that would seem to indicate it is related to the 4.7.6 build I have, any solution to getting it resolved with this version?
The only change in my setup since using unreal is updating to El Capitan.
Current-
iMac
OS X El Capitan ver10.11.4 (15E65)
3.1GHz i5
4 Gig men
AMD Radeon HD 6970M 2048 MB
Not the best specs for running the editor, but never had this particular issue outside 4.7.6
We were not able to reproduce this issue internally, so that was the initially problem. This is going to be an issue with lower end spec machines on this build specifically. Since this version is over a year old, we won’t be going back to fix this issue. We will ask that you try this out in the most recent version of the engine, and if the issue still occurs there, then we can move forward with the troubleshooting process.
I downloaded UE4 Editor a year or two ago for my Mac and it worked fine with all of the high spec demo scenes. I haven’t been using it since then but just updated to 4.7.6, and I’m getting the pure white screen showing with every hold of the mouse button.
Mac Pro late 2013 3.0 8-core xeon, dual d700 GPUs w/ 6GB VRAM each, 64GB RAM.
Please see my earlier response about this issue. This issue is being reported on an engine version over a year old, and we will not be going back to fix it. Would you test this on a more recent version of the engine to see if it occurs there as well?
If it does occur there, we can continue forward with this report.
I need help with this. I am running 4.6.1 and i have to use that version for the tutorial i am doing. But everything turns white when i hold down the cursor. Wat should i do?
Specs
Macbook Pro 13 inch 2012,
i5 2.5ghz,
, Intel HD Graphics
, 16gb 1600mhz ddr3 ram.
We have not been able to reproduce this issue internally, and the fact you are working on an engine version that is over a year old, it is not likely we will return to fix this.
Would you try testing in a more recent version of the engine, and providing me with steps to reproduce the issue on my end?
