Fri, Apr 20
@Christian Hoffman (Dramock) : is this still relevant? Has above link solved this?
Thu, Apr 12
Woah, I found the file you were talking about and removed it. Everything seems to be running fine now. I have no idea how that file was in there if it was not supposed to be.
I don't believe so, I've been having this problem since I first download blender yesterday, I'll check if I can find that file.
Looks like you're running on mesa? did you by any chance drop a opengl32.dll in your blender folder?
Alright, I've attached the file and I will look at the information displayed from the debugging, thank you.
Let's see what graphics card blender is using on your computer.
In the Help tab click on Save System Info and then share the file generated here. (Maybe that gives some clue of what's going on).
Another thing that would help investigate would be by opening blender from the Command Prompt adding the arguments --debug-gpu. The prompt will display some information that may be useful.
This occurs with a standard cube (about 2-5 fps). If I load in a character model it gets even worse( below 1 fps)
Wed, Apr 11
Is this with the standard cube or with a very large scene?
Fri, Apr 6
I also encountered this problem. My mechanical keyboard has some broken switches and I made a new windows keyboard layout for german and replaced the letter "Ö" with "L", as "L" and I didn't need "Ö".
Mon, Apr 2
I've also had the same problem.
Blender would load, and then when clicking on the splash screen, it would be "disabled"/"locked".
After some time, Windows notifies the software is taking to long to respond.
Yes! That fixed the problem entirely, thank you.
I think we've seen this before, if i remember i saw someone resolve this by right clicking the blender shortcut and selecting what gpu to launch on, but since i don't have this setup i really can't offer any more details than that.
I apologize for not including complete information.
My computer is running Nvidia GEFORCE 940MX, and the Intel Core i7 Gen. 8 (UHD 620).
Hi, thanks for the report.
Sun, Apr 1
Mar 18 2018
Mar 17 2018
Feb 8 2018
Since the commit rBe0597baed57f Carve library was removed from Blender. Since these boolean problems are related to issues within the library, the task can be closed.
Feb 7 2018
Feb 6 2018
Feb 4 2018
Workaround: I'm using v2.79 and experiencing same problem as described, where regardless of which monitor I was using as my main display, Blender was always opening up in the secondary monitor. I forgot to do a diff on the startup files, but this is how I worked around it: In Windows 10 I have a single video card with multiple monitors, but I think the problem is in the settings somewhere and doesn't matter the setup:
- I had to right-click on the Desktop and select Display Settings.
- Under "Multiple Displays" I changed it from "Extend These Displays" to "Duplicate These Displays"
- I opened Blender and with it selected in the primary display I Saved Startup File and then Close Blender.
- Under "Multiple Displays" I changed it from "Duplicate These Displays" back to "Extend These Displays"
- Reopen Blender, and it opens in the primary display as selected.
If I get a chance, I'll try to experiment to see exactly what is happening here, but in the meantime I hope this helps!
Feb 1 2018
Just as a clarification, cmake silently removed the runtime dlls for 2.79a, i didn't do this deliberately, This patch retains the old functionality (include all needed dll's), and no longer silently fails when build with newer cmake.
If this never impacts users (only CMake maintenance), then I don't see anything against applying the patch.
actually it does, i accidentally shipped the 2.79a-rc without the runtime dll's due to this issue, just nobody has noticed it yet...
I brought that up earlier today on irc, the BF stance was blender should work on a clean install, no extra downloads needed, so we're gonna keep shipping the runtime dll's (even though they ballooned from 3-4 to about 45 files)
@LazyDodo (LazyDodo) from your last comment I don't see why we wouldn't apply this patch (if it really does work as intended).
Jan 31 2018
@Hans Chnuspi (chnuspi1234) : Hi Hans, thanks for your video, now I understood!
@Hans Chnuspi (chnuspi1234) : thx for making that clearer :)
@Alberto Giorgi (AlbertG) : left hand side of your screenshot the face is also 'back' (you just see right through in wireframe)
reg. missing faces: I think that video makes it clear?
I believe you have been tricked by an optical illusion - I hope this short video clarifies it for you :)
This patch description is quite vague,
Jan 30 2018
Hi Philips, thanks for your answer!
Jan 29 2018
I am not sure if I understand correctly:
Jan 28 2018
Jan 23 2018
I have the same issue. Blender starts up with a white screen. I have an Windows 10, 64bit, intel i7 (1.99GHz), 16GB RAM, NVIDIA GEFORCE. I don't know much about computers, but the way that I was able to get Blender to work was to right-click on the start up icon, and choose "Run with Graphics Processor > integrated graphics". I don't know what implications this has on renders, etc., but it is the onl way I could get Blender to work.