- User Since
- Dec 8 2018, 12:03 AM (32 w, 12 h)
Wed, Jul 17
Jun 10 2019
No, this was fixed some time ago.
Mar 20 2019
Topology mirror causes other problems, and isn't a work-around;
Mar 17 2019
More follow up, again for the sake of thoroughness/documentation.
Mar 14 2019
Edit: Added debug info
Just a quick follow-up, for the sake of thoroughness.
Mar 13 2019
Excellent, thank you all so much. You're all the best and keep up the great work.
I assume you mean this;
Thank you all for looking into this again. Here's what I did to put the system back into a "broken" state;
So both Nvidia and AMD have the exact same flaws in their drivers, that only are a problem with 2.8, but not with 2.79b? Forgive me if I find that sort of coincidence hard to believe. How is 2.79b getting the OpenGL context to pass where 2.8 isn't? Could it have anything to do with the fact that 2.8 doesn't have an installer? (I assume the stable version will have an installer)
Mar 12 2019
This problem is back. I now have two GTX 1070s and I'm getting the same OpenGL 3.3 error and refusal to launch.
Yes, first thing I did this morning was download the latest build and test it. When I first had the crash, I was using an RX480, now I'm back onto a GTX1070 and it's happened with both, so I can't blame drivers on this one.
Mar 11 2019
I'm not sure why you're only seeing the hood, it's not even a separate element or object. It's only a different place-holder material. I just downloaded the zip file I uploaded here and this is what I saw when I unzipped and opened it.
Feb 28 2019
OK, I basically solved my problem. I gave up on AMD 😛 I put the 1070 back in, and I scrounged up a GT710 for some extra video outputs. It's working flawlessly.
Feb 27 2019
I'm not an experienced programmer at all, that opengl extentions thing is way over my head.
That's perfectly understandable, I've been warned by the game developers I work with to expect AMD drivers to give me issues, so that does seem like a likely culprit. Would it be possible for me to edit the source code for blender in such a way that it just doesn't "ask" for the context? Not that I would know how to do it, but if it's an option, I'll head over to blender artists and/or Level1Techs and see if I can't get some help. I mean this isn't game breaking or anything, just a nuisance, it's just been made more problematic thanks to the crash bug I found recently (and reported) that was causing blender to crash non-stop.
Oof, well that had the effect of breaking my computer for a couple hours. 😛 Took a while and a couple of times reinstalling the drivers for them to work right (2 cards, 6 monitors) but I'm back up and running...and I still get the same error. Got the same Open GL error about six times in a row before blender finally launched.
I had manually removed the Nvidia software previously, but after running the DDU program, I could still see there were traces of it in there. So I ran the DDU program to clean up the NVidia drivers, restarted the computer and now DDU doesn't detect anything Nvidia related, however the intermittent refusal to open problem remains.
Well that's weird it didn't upload the first time, lets try again!
Feb 26 2019
Jan 24 2019
Jan 16 2019
Jan 10 2019
I also noticed today that the vertex weights wouldn't show up with a subsurf modifier visible in edit mode as well. If you untick the visible box, the weights appear, just like with the mirror modifier.
Jan 3 2019
Jan 2 2019
I'm currently using the build from Dec 28th, can confirm this issue. I thought it was something I was doing wrong, made a post about it on blenderartists;
Dec 19 2018
Dec 12 2018
OK, that was my fault. Even though I downloaded the build from Dec 10th, and even overwrote the files in my blender folder with the new ones, the splash screen was showing up as the Dec 6th version, so I'm not sure why, but my shortcut let me astray. Now I just have to figure out where I went wrong with the shortcut.
Dec 10 2018
I apologize in advance for not really know how this system works.