Seems to be something wrong with Vega 64 (and newest divers?), there are other (more specific issues reported, see e.g. T57832)
Fri, Nov 2
That may well be, but i'm not gonna change a legal text on my own without explicit instructions to do so.
It is actually correct to be GPL3, from https://www.blender.org/about/license/
I can change it into whatever, but i'm gonna need some guidance from @Ton Roosendaal (ton) what he wants
@Robert Guetzkow (rjg)
The major part of the "source code" is under GPL2+, but Cycles is Apache2.0 that's incompatible with GPL2.
Consequently, the Blender "binary" built with Cycles becomes GPL3+ automatically.
COPYING file is not included in the binary distribution.
Yep! I can confirm that manually disabling CMAA ( "Conservative Morphological Anti-Aliasing" ) in Intel driver's settings is fixing the problem. No more crashing at maximizing and restoring Blender ! 8-)
Unless I'm mistaken it is GPL2 according to https://developer.blender.org/diffusion/B/browse/master/GNUmakefile
Thu, Nov 1
Just to say, that Blender is still crashing with the latest 2.80 Alpha 2 version (downloaded on 31.10.2018)
Also, I'm unable to move the Blender window to a second monitor - the moment I try to drag it to the other monitor it crashes and disappears.
The only way to work on a second monitor is to open a new Main window, which automatically appears on my second display.
Wed, Oct 31
@Jaimi McEntire (Jaimi) Thanks for the heads up. We have our own AA methods and if Intel's option is crashing blender, it's not really our fault.
Update: Latest 10/21/2018 drivers from Intel fix several rendering errors on Intel chipsets.
Tue, Oct 30
Mon, Oct 29
Works great in the latest update.
Wed, Oct 24
If you drop in an software opengl implementation, things are gonna be slow, If blender doesn't run without it you either have an old video card, or have driver issues.
Tue, Oct 23
this can be closed. I retried this every once in a while - in the version from 21.10.2018 I can now open my files again ( build: blender-2.80-13cfb641c6d-win64 ) thank you!
- Give us your exact Blender, OS and GPU (including drivers) versions, as requested in the template!
- Ensure both your OS and drivers are fully up-to-date (and use official GPU drivers, not those provided by windows or tablet/laptop maker or open source ones in linux distributions).
- If your GPU driver is already to latest version, try down-grading to a few previous versions (sometimes newest versions introduce bugs…).
- Try to start Blender in factory settings (--factory-startup commandline option) (this will ensure whether this is a userpref or addon issue or not).
- Try to tweak OGL settings in UserPreferences, System tab.
- Try to tweak your GPU driver settings (e.g. try different values between 'performance' and 'quality' if you have such slider, etc.).
- Attach as text file here the report generated by Help -> System Info (do not paste it directly in comment).
- Launch Blender from the command line with --debug-gpu option and attach as text file here any error printed out in the console (do not paste it directly in comment).
Please follow our submission template and guidelines, also read these tips about bug reports, and make a complete, valid bug report, with required info, precise description of the issue (only ONE issue per report!), precise steps to reproduce it, small and simple .blend and/or other files to do so if needed, etc.
The latest build should already have a fix for this.
In this case i'm closing this task. feel free to reopen if the problem persists.
Its cool no worries :) Thanks for getting back to me. I would like to give you an answer but that computer needs to be repaired. It is not working so that error could have just been because of that. If I get that computer running again I will try the new build and post back. Thanks again!
@Prabesh Aryal (Prabesh) Sorry for not responding for a long time. I would like to know if the issue is still present in the latest builds? And if you can still reproduce, paste the output of the console (window's CMD) when launching blender with the --debug option.
Mon, Oct 22
OKi, closing as resolved then
More than a week without reply or activity. Due to the policy of the tracker archiving for until required info/data are provided.
Sun, Oct 21
As of Now
version blender-2.80-8e3a680ebe3 released on 20th oct 2018
seems to have fixed this problem.
Sat, Oct 20
Fri, Oct 19
problem solved on HD5770 !
Will actually mark this as incomplete until we either have confirmation it works in new builds (or problem still persists...)
Can confirm in 2.79b (official release), but not in 2.8 nor 2.79 master.
Yes, if i save before step 11, close blender and load it up again - no crash. But why it crashes if i not saving, closing and loading?
First off all, thank you all for helping me now even though it has become something different than a blender problem. Before I'm reinstalling windows probably on the weekend I wanted to leave this here maybe it makes sense to someone. I tried investigating it a bit more, so I took a closer look at what Daz3d was telling me and It had a crash log for me.
Thu, Oct 18
And I'm guessing that's the only thing left for me to do. I know for sure if I clean install an older version of windows with all my old drivers blender is going to work, if i get the same problem after I update everything, that's going to probably give me a stroke. I'll report back once I did that.
your card supports it, but the drivers are causing a stink, it looks like gpu-z is a little better at not crashing and burning when it encounters that, you could give nvidia support a try, but they'll probably tell you to go reinstall your computer.
No this is with the dlls