In T57843#554108, @William Reynish (billreynish) wrote:

Hmm, to add further flavour, changing the 3D Cursor to Click makes it so it doesn't move under your mouse cursor. This may be a bit more difficult to fix than I thought.

Hmm, to add further flavour, changing the 3D Cursor to Click makes it so it doesn't move under your mouse cursor. This may be a bit more difficult to fix than I thought.

Thanks for the fix! Now the rendering is ok.

Ok, I've located the issue. For the 3D Cursor tool keymap, Set 3D Cursor (view3d.cursor3d) is set to Press rather than Click. If changed to Click, the D key now works again.

Sorry about the video issue. looks it is working on my safari browser but not on other browsers :/

The D key for annotate does work if you use any of the other tools, other than the 3D Cursor tool. It's probably a keymap issue.

What key map are you using and what editor type are you trying to annotate on?

I can see in the buildbot logs it's now using 9.1. So I'll consider this resolved, thanks!

Update done and buildbot restarted.

@Francesco Siddi (fsiddi), can you uninstall CUDA toolkit 9.2 and install CUDA toolkit 9.1 instead? That is what we use for other platforms.

Someone installed cuda 9.2 on the buildbot.. which is known bad.

Yes, drivers are up to date.
OctaneRender and Cycles from 2.79b work fine. This issue is with latest experimental 2.79 and 2.8 builds.

Cannot reproduce on linux (but @pan beep (beep) already tagged as Mac only)

Same bug here on High Sierra 10.12.6.

@Isaiah McCurdy (Helium234) cannot find that option on my 2.79b instalation, could you show me where you change it? Thanks!

I had the same issue and fixed it by unchecking the integrated graphics in user preferences

Interesting informations from iTerm : https://gitlab.com/gnachman/iterm2/issues/6608

Ok, so it seems to be a bug in macOS for which a workaround exists, I don't think we should consider this a bug to solve in Blender then.

Another forum : https://github.com/SublimeTextIssues/Core/issues/2250
They say the problem is fixed in 10.13.5 but apparently not completely ;)

Same problem with "The Elder Scroll Online" and 10.13 : ESO

I have exactly the same problem on High Sierra (10.13.6), with 2.79 and also with 2.8. As previously said, a possible fix is to increase the cursor size in macOS "System Preferences > Accessibility > Display > Cursor size" from Normal to any higher value.

In T56332#551951, @Brecht Van Lommel (brecht) wrote:

World volumes were broken for a bit, this should be fixed now.

yes it's working. big job. I had hope a such work in the interface. but it's not so sure about that...for instance modifications in keys are strange and often useless! I have to restored shift C cursor to center, ctrl alt shit c set origin. I added shift RMB to move cursor and shift alt RMB to move it on surfaces ^^ it's already possible in the key configuration. why not present in their tool menu. border select have a bug in object mode: it doesn't add several selections. it's cool to work on such mysterious keys like alt E to add several color in the ramp node but there is more logical things to do first. ctrl t and alt t back! no way. why all this is still present but was substract from the settings. ctrl u is back no way...
and in the interface if they don't understand how much faster is a crtl t I dont have to explain many other things...

I think we fixed this issue for everyone now. Closing.

World volumes were broken for a bit, this should be fixed now.

hello i just download the nov 7 blender this time it didnt show purple background :)

There is some information on that here:
https://docs.blender.org/manual/en/latest/render/workflows/command_line.html?highlight=terminal#macos

In T56332#544830, @Bastien Montagne (mont29) wrote:

@wahhaj (wahaj) we are not talking of python interactive window, but system console from which you’ll have launched Blender (using debug option, so something like blender --debug).

It's fixed.
Something along the way must have been fixed, it don't crash at that point any more.
closed.

I believe this was fixed last week along with various other macOS bugs.

It happens on both my own as well as the daily builds.
It goes away when I set my "screens have separate spaces" off so I did that in the meantime, but it's not the solution I know.

@Clément Foucault (fclem) Ambient Occlusion and SSR are looking fantastic.

Videos are working in firefox for me.

I want to know if you are seeing the videos I'm submitting. It seems like they are broken so If you can't see it please tell me and I will add them to another source first.

@Clément Foucault (fclem) Yes, This is happening with all hdri's, the only differences is that some of them produce dark glitches. All in Lookdev Mode.

@Oscar Orlando Caballero Moreno (oocaballerom) Is the problem happening with other HDRIs? does it happen in lookdev mode?

I have further conclusions about why this is happening. If I open the application not just on the whole screen, I will only scale it, everything works smoothly. The problem only occurs if the blender is displayed on the full screen.

Not sure if this might be fixed already by recent commits, but I guess this is something for @Clément Foucault (fclem) to look at?