Fun times of considering if I want to wipe my computer and start over on Big Sur before doing the most simple thing to fix it. you have to click away and then click back onto the window.Ī restart and Eevee runs smooth again on my M1. visually the shading on the top bar is your only clue, and you can in fact tumble the viewport in this deselected state, but then other inputs won’t work, and more infuriatingly, you can’t seem to just click the window to make it active. about 50% of the time, with no clear cause that I can identify, blender launches with its window in a deselected state. My brain misses the red highlight too often - not to mention the navigation of folders and performing the actual save is the exact same click / return key input, so a bit of disk lag causing you to accidentally click an extra time because you thought the first click didn’t register… file overwritten.Īnother macOS integration beef I have is that blender’s window management is really wonky. it desperately needs a confirm overwrite, at least as an option. ![]() it is WAY too easy to accidentally overwrite something. That said, I’m with you on blender’s file dialog needing some more love or a native OS option. ![]() type / for the root list, ~/ for the home folder, and // for the path relative to the blend file if its been saved. Blender’s file dialog does in fact implement essentially the same thing.
0 Comments
Leave a Reply. |