- User Since
- Tue, Dec 4, 6:09 PM (2 w, 10 h)
Tue, Dec 11
I looked up that guide and I've tried what it said from that one. But nothing different happen.
However I was trying out settings too see why the option to specifically select graphic device was disabled or non existent in this case. I then checked if there was something wrong with the hardware. For my pc setup I use two monitors, and I've just noticed that one of the monitors was hooked to the gpu output but the second one was hooked up to the motherboard output. I switched both to the gpu outputs and the...
IT WORKED!! The problem is now resolved for me. Everything now works in Blender 2.8. It was very weird for me as I was using the monitors like this for years and using blender all the time yet I had not problems like this ever.
Mon, Dec 10
Okay, here is the current situation. I have downloaded the driver for intel from the site and installed only to get up an error that it said "This driver is not compatible with this computer cpu." something like that. Then I have downloaded their Intel Driver & Support Assistant program which eventually did properly installed to the latest driver.
I tried to open up Blender hash ver: e79bb957fc3 and got a black screen. Then I've tried to go in edit mode, and then it showed the cube. Tried to view it in LookDev mode and it did not crash this time, but the colors of the cube and the grid keep glitching in weird colors. Sometimes when I switch back and forth from edit mode it shows the model in the right colors, but then it starts glitching back again. Tried to switch up to cycles mode but the grid and the mesh keep glitching in weird colors. After playing with the settings with only rendering with cpu˛only, cpu & gpu, gpu only. I got the same weird colors every time. But now it doesnt crash at all. Here is the newer gif of my current situation.:
Ive looked up the intel card on my device manager and it checked all the updates and came back as it is up to date.
Fri, Dec 7
My bad, I have now retried it with the workaround and copied the error text to this file.
Tried the one with the --debug-gpu-force-workaround, but it crashed straight away. hash: 606223f6a6
The blender hash is: 606223f6a61