Mac OS X platform support.
Release Builds: @Arto Kitula (akitula)
Developer Members: @Arto Kitula (akitula) @Brecht Van Lommel (brecht) @jens verwiebe (jensverwiebe) @Ton Roosendaal (ton) @Dalai Felinto (dfelinto)
Mac OS X platform support.
Release Builds: @Arto Kitula (akitula)
Developer Members: @Arto Kitula (akitula) @Brecht Van Lommel (brecht) @jens verwiebe (jensverwiebe) @Ton Roosendaal (ton) @Dalai Felinto (dfelinto)
The blender render has been removed from blender 2.8 and will not receive any more updates.
Therefore I will close this issue.
@Kent Davis (mac4kent): I've noticed in all your bug reports that you attribute any and all your bugs to be Mac-specific. While there may be issues that only manifest themselves with a certain OS, GPU or driver, most bugs in Blender are not platform-related.
Cool thanks
OK, thanx for getting back.
Not familiar with font rendering, maybe @Bastien Montagne (mont29) has an idea? or @Clément Foucault (fclem)?
I just found out recent. Not worry about THEME.
I think so yes Mac but some time have Windows too I guess.
Interface on Resolution Scale
When drag become small text from big text cause appear "J" when become big text from small text cause disappear "J"
I show you on youtube.
When you see my mouse drag please look out on "J" on Object menu you will notice.
https://youtu.be/b7h8S6g-Vc0
Not a problem here, might be MAC only?...
the same issue (black shader on eevee) is happening on my mac pro (2012).
Well you have the issue explained here.
Hello Clément,
Here is the output of the Terminal window.
thanks{F6527363}
If this is a shader compilation problem, generally it should say something in the system console output.
Hello,
I confirm the rendering bug with Eevee. With the official wanderer.blend, the character is rendered purple (strictly as shown in images & movie posted above).
I can reproduce the problem with 2 machines:
Is this still an issue with the latest blender beta?
I belive this bug was solved some months ago.
I believe this bug was solve some months ago.
Yes. let's close ticket.
so it's fixed?
They fixed I am going show you youtube.
Is this still an issue with the latest blender beta?
It's a bug in an add-on that we do not maintain, so it's up to the author of that add-on to fix. The bug being platform specific does not mean it is a bug on the Blender side.
As you can't reproduce this without the addon, can you contact the hardops devs and ask them to create a small test example for us that doesn't rely on having the addon?
I haven't tested extensively, but at first glance, this seems to fix my problem (though, I rarely change window size and usually use Blender maximized).
Yes, you GPU is really old (12 years) and the mac drivers is buggy.
We can't support hardware this old really, so unless you manage to find an easy workaround that we can put in, we can't do anything.
I just built it locally too with 33dcf9fa71c7 . This is still not working. The blender-2.80.0-git20190129.957b4547aeeb-x86_64 downloaded beta build does not work for me either.
I built locally and it works brilliantly now. Thanks! The native pixel stuff on MacOS is quirky. Ironic that I just found a workaround 3 days ago.
Ah, I will try tomorrows build.
@John Ostrom (macnib) Try with tomorrows build. It was fixed today and the builds are only updated once a day.
If I moved the blender window to the center of the display, then the black offset happens when I login from sleep.
Hmm, I still am not sure it's working for me.
At my end, things are working the way it should now! Thanks
I was able to reproduce this issue now when opening a particular .blend file. I've committed a fix for that case.
Archiving old report, this macOS version is no longer supported and DoF in 2.8 is different.
Complementing what I can find in memory and relations.
Im not a programmer but i do know how to use the terminal XD
Still a problem. But I have a workaround for my particular system at the moment.
Official releases are signed, but daily builds are not.
Have you tried stable releases?
I believe they are signed.
Also --debug-gpu-force-workarounds doesn't solve the issue for me.