- User Since
- Aug 12 2007, 10:08 PM (631 w, 3 d)
Thu, Aug 22
Have found a fix from Noki (amon paike)....
Delete the Outliner chunk from your modified keymap, then it all works nicely :]
Thanks @noki paike (amonpaike), deleting the Oulitner chunk worked for me!
Aug 19 2019
Sorry, didn't try Fac Defs, but did try New File. This has happened in latest build from today too. Hold on, I'll try Fac Defs...
...ah, yes, Defaults works fine.
My Keymap is wildy different from default as I've been Blending >10 years, so have changed loads of stuff. I'll include it here if that's any help?
Also, can confirm that default keymaps work fine, but as soon as I change to my own keymap, Outliner will not expand or collapse.
Thanks Evan, I think it was the same on the build before that, from last week, too, but I'll give it a week and see how it goes.
Aug 18 2019
Jul 20 2019
Ah, makes sense. Thanks for your time!
Hi, Thanks - yeah, so paint on Bro2 or Bro3 textures. then undo and you should see that the painting mode switched you back to Bro01, but you'd rather stay on the texture you are actually painting on.
Jun 5 2019
May 2 2019
Thanks for the confirmation. Shame though - could imagine it would be 'easy' to add one more blur process on a slightly higher res texture to mitigate the effect.
Mar 27 2019
Ok, can confirm that all is well once Factory Settings are loaded. Have deduced that it's something to do with Keymaps. Have been fine with my personal Keymap for years now, but this last update has somehow conflicted with it so that selecting doesn't work in the viewport... One thing I noticed a while ago, and still occurring now is that my keymap does not display the 'Preferences' section at the top, so there is no way to choose L or R select in this section while an older keymap is loaded. Could this be anything to do with it? Second question.. will I have to rebuild my keymap from scratch? :D
Thank you, just running out - will try in about half an hour! ;]
Willing to Factory Reset to test, but apologies, can you suggest a way to FR on OSX without too much poking around?
Hi Brecht, seems present in last night's OSX build, 27th. I say RCS because I still use RCS!
Have reverted back to build from 25th and all is well. I also couldn't use 26th build because of keymaps not responding - couldn't press X to delete!
So, in summary OSX builds 25th - All seems well, 26th - can't X delete, 27th - can't RCS, assuming that you have RCS set up.... have just gone back to 27th build to triple check - no response in 3D Viewport to either mouse button. Also I can't find in Preferences where the option is to change mouse selection, but I'm always RCS!
Jan 18 2019
Oh, yeah, very sorry - totally works in default scene!
Apologies, will double check next time!
Must be my scene :l
Dec 12 2018
Dec 8 2018
Sorry, I should've mentioned that I DO get all the 'trimmings' that alude to the selecting of colour, ie, Sample Colour dialog appears with options - it definitely thinks that it's about to pick a colour, but it just doesn't do it!
Dec 5 2018
Yes, Sergey, that's the one! And yes, re-maximizing the window fixes it.
Sep 1 2018
Jan 3 2018
No prob - weird though - has always been 100% reproducable for me, for literally years, and on multiple versions and operating systems - it's just that it's taken me several years to figure out why it was happening for me (being too 'close' to the object) - but I swear it's been there forever, and still is! XD
No worries though, I'll come back if I have any insights.
Nov 20 2017
Within the file, select any of the multiple objects in the viewport and move it using an axis constraint - you will find that the axis constraints function.
Now, zoom in to any object, with numpad period, or just zoom so that an object fills the viewport, and try using an axis constraint again - for me, the axis constraint disappears and the object's movement is not constrained at all.
Would be interested to see if anyone else can reproduce this?
Nov 6 2017
Here's a vid, hopefully will help explain, but still not how to reproduce :l This is actually happening in the default, non maximised 3d view now - I always thought it was only when in a maximised view, but perhaps it is to do with the wider field of view when maximised that makes it more prone to happen?
Ahah! I've found the cause!! So, happened again this morning, and I was almost considering making a video to show you what I meant, but while playing around with the 'bug' I finally realised that some objects would still constrain - then it dawned on me that those objects were further away - so, I zoomed out to move my problem object further away, and, lo and behold - axis constrain! So, I'm supposing it's a clipping plane thing? If the object is too close to the viewer, it is out of some operational clipping bounds and therefor doesn't get the constrain code?
Would you mind trying to recreate yourself? I am able to 'fix' the problem when it happens (by zooming out), but wonder if you are able to 'create' the problem by zooming in?