@Lukas Stockner (lukasstockner97) , @Brecht Van Lommel (brecht) feels like a codegen bug, in a compiler we're soon gonna drop anyhow, not sure if it's worth spending time tracking it down.

I can only seem to reproduce this with msvc2013 and avx2, @Falk Müller (xharthok) can you try a build from the bot marked with 'New Compiler' (has vc14 in the filename) and see if it works for you without having disable avx2?

Thank you for the report. Currently we are aware of many issues in 2.8 and actively working to fix them. But since replying to reports takes time, we have decided to limit bug reports to module team members.

Thank you for the report. Currently we are aware of many issues in 2.8 and actively working to fix them. But since replying to reports takes time, we have decided to limit bug reports to module team members.

oh wow , there was quite a bit more of the pbuffer stuff left, thanks for the cleanup @Germano Cavalcante (mano-wii) !

• Merge remote-tracking branch 'origin/blender2.8' into glrefactor_blenfont
• Updated enable/disable function with Boolean.

Committed! thanks for the patch!

looks like the bots are back online though, i see builds coming in as we speak.

not in my control, sorry.

It's already migrated, you can find it here https://wiki.blender.org/wiki/Process/Bug_Reports

i have no idea why it did this and if i broke anything or not, @Clément Foucault (fclem) , @Campbell Barton (campbellbarton) help?

• Updated with feedback.

• feedback: remove now unneeded pbuffer

• feedback: replace uint8_t with uchar.

I used uint8_t mostly out of habit (i like exactly knowing what i'm getting) . I could make the argument that the C specification has some ambiguity in the char-type (it can be larger than 8 bits, and it has been seen in the wild on some obscure architectures) while uint8_t * is guaranteed to be 8 bits, but i'll be honest, that's not why I chose it, and the crazy architectures that break this rule are so uncommon it really doesn't matter.

In D3481#80493, @Germano Cavalcante (mano-wii) wrote:

I don't quite understand the importance of setting a PixelFormat to dummy contexts or offscreen contexts (or even to the context used in Blender).

Poor title, it kinda took over the text from the diff, my bad sorry!

Thanks for the report, but this add-on is not developed by Blender, please report the bug to the original author.

Please follow our submission template and guidelines and make a complete, valid bug report, with required info, precise description of the issue, precise steps to reproduce it, small and simple .blend and/or other files to do so if needed, etc.

is this still an issue with the latest buildbot versions?

it always has to be a complete diff that can applied to master or 2.8 (or better use arc since it adds all contextual information)

looks like an incremental from the last diff now.. still not good.

Is this still an issue with 2.79b?

Since last asking for information it has been 7 or more days, due to the policy of our bug tracker we will have to archive the report until the requested information is given.

the diffs you send replace the previous ones completely, they don't add up, so now it's just a header change ,may i suggest switching to arc?

Please follow our submission template and guidelines and make a complete, valid bug report, with required info, precise description of the issue, precise steps to reproduce it, small and simple .blend and/or other files to do so if needed, etc.

Any chance you can check your event log for any TDR related events around the time of the crash?

Thank you for the report. Currently we are aware of many issues in 2.8 and actively working to fix them. But since replying to reports takes time, we have decided to limit bug reports to module team members.

Thank you for the report. Currently we are aware of many issues in 2.8 and actively working to fix them. But since replying to reports takes time, we have decided to limit bug reports to module team members

From the bug report page.

That appears to be a gcn 1.0 card, Blender only supports graphics cards with GCN architecture 2.0 and above).

fixed in rBaca403c819c4fc9e1e7197bbe3027d43d114bfd6

This broke command line renders/ctest.

Thank you for the report. Currently we are aware of many issues in 2.8 and actively working to fix them. But since replying to reports takes time, we have decided to limit bug reports to module team members

Hi, while we love to hear these ideas, this is not the right place for them. This website is mainly used to track bug reports and not feature requests. But luckly, there are some other nice solutions you can take, so please use one of the other forms of communication listed below:

Thank you for the report. Currently we are aware of many issues in 2.8 and actively working to fix them. But since replying to reports takes time, we have decided to limit bug reports to module team members.

from the bug report page

osl is not supported in material mode, osl is not capable of emitting a gsgl shader.

Its highly likely that this bug is specific to your hardware/driver configuration. These kinds of display issues are often caused by OpenGL driver bugs.

Thank you for the report. Currently we are aware of many issues in 2.8 and actively working to fix them. But since replying to reports takes time, we have decided to limit bug reports to module team members.

Thank you for the report. Currently we are aware of many issues in 2.8 and actively working to fix them. But since replying to reports takes time, we have decided to limit bug reports to module team members.

• fix typo / add support in make.bat for asan for easy access.

You had a rather strong opinion last time i tried adding a configuration, any objections here ? (again, will only add it when windows+clang are in play)

doesn't look like that fix ever made it into 2.79b, and daily build shouldn't even list the fermi card as available anymore since support was dropped for it. so yeah.. that's kind of a rough spot to be in.

Thank you for the report. Currently we are aware of many issues in 2.8 and actively working to fix them. But since replying to reports takes time, we have decided to limit bug reports to module team members.

Thank you for the report. Currently we are aware of many issues in 2.8 and actively working to fix them. But since replying to reports takes time, we have decided to limit bug reports to module team members.

I gave you exactly the commands you needed to type, in the order you needed to type them in, i'm not sure what else to tell you.

• Disable clang for X86.

• Include lib patches needed