Yes i know the title sound ambitious but believe me it is the single best tip you will ever see regarding 3D apps!
I lost an hour trying to figure why the darn uv were not updating in the 3d viewport when i was moving them in the uv editor window!
Do you want to know now what is that fabulous tip? Well are you correctly seated?
Restart Blender and it usually do wonder!
Next time you have an issue before Googling for 2 days and getting to sleep frustrated simply restart the darn software and 90% of the time it will simply work!
It happen to work for many other small issues i was having but often we think it’s more complicated and we go for the frantic search to find a solution while restart will save you time and your sanity!
This has been true in my case a couple of times. I’ll unknowingly thwack a toggle key I didn’t mean to on the keyboard. Blender behaves oddly. Restart reloads that sweet, sweet startup file and Bob’s your uncle.
Well, yeah. That’s pretty much the default quick fix for all things computer. The usual troubleshooting steps start with trying to turn it off then on again. If that doesn’t work, then reinstall Windows. If that fails, then try kicking your computer. If whatever is giving you problems still doesn’t work by that point, then just go and buy a new computer, cuz your current one is just godawful terrible, and it’s broken forever, cuz you kicked it.
…unless you’re on a Mac. If a Mac doesn’t work right, it’s because of something you did, and you should really be ashamed of yourself.
It would be better to find what is really the problem… Restarting might be a fix, but sure is not a solution!
I suppose it might be some flaw in some addon, as the API has changed a bit; but a full diagnostic is needed to correctly find out what’s causing the issues.
After 18 years and using so many 3d app i can honestly say that they all need to be restart at some point to fix issues with their various components.
3ds max was notorious for this behavior and when i start with Blender it was refreshing to see this happening a lot less.
My main point was to make people realize that sometime we lose precious production time when a simple restart could have fix the issue.
I know identifying the issue is better but some time there is some of these issues that are very hard to pin point and when you are under time constraint you need to find a quick way.
When you move UV meshes and they don’t update in the3d viewport, usually is just because you unchecked the lock icon on the header, which serves this purpose. Just saying.
First: I can understand your solution, as I also did the same when I made the jump… But I found out that restarting Blender is most of the times not even needed… Also, I never experienced a level of crashing in Blender similar to the CrashKing from Autodesk. And by your description, it’s probably more a setting issue than a bug (as @sourvinos sugested).
Second: Blender is OpenSource, which means that I can look at the source to figure what happened wrong and try to fix it. With 3dsMax, I could only report a bug, hopefully (never happened) receive a fixed version while still working in the same project.
Agree that Blender crashes very very seldom, sometimes it sticks for a while and I’m tempted to force quit it, but usually, if if I have the patience to wait, it suddenly springs up again.
Luckly, the Developers Team, and all the others that also contribute, are quite accessible… If you think you found a bug, or something is not working as it should, you can contact the DT per email, chat or in the devtalk… If know the steps to reproduce the error/crash, you can directly report a bug… You’d be surprised how most of errors are quickly solved.
For me in 2.80 and 2.81 I had this problem a few times and I didn’t have to reset the program. In workbench mode switching back and forth to another viewing mode (lookdev, eevee) fixed it. Also the workbench mode with textures will only display the UV mapping coordinates, not other such as generated, object, normal, etc…
