2024.1 Bugs
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report
Just wanted to report some more bugs I've found in 2024.1!
1. Hardware shade settings are not persistent when opening new file. I can have a file with an environment and certain hardware shade settings applied, and when I open a new file, all of that shifts to the new file's setting, despite having the environment reference selected for the original file in the stage lister. I have to toggle the environment box to the new file and back again, and turn hardware shade off and on again in order to get the environment to read from the original file. I have to do this several times a day, any time I open a new file.
2. Ground plane shadow in hardware shade being on is causing black flashing glitches when modeling, moving CVs, switching stages, etc. This is with the latest Nvidia graphics driver as of December 2023. When ground shadow is turned off, graphic stuttering goes away.
3. Still having lots of crashes relating to what seems to be about using hotkeys too quickly after certain operations. A couple I've noticed - When using the "apply shaders" tool with a hotkey, and swiping up with the right mouse button too quickly will cause the program to crash. I've also seen something like where I use a hotkey too quickly after switching stages, the program will crash. Very hard to replicate, it's very random.
4. When crashing, the Msave and reopen function only works about 50% of the time.
5. The program still fails to remember some of my settings when opening:
-Draw style settings are forgotten when opening program, until I open draw style box and close it, then tumble the model.
-Transform CV falloff box is still bugged, it now shows my last used falloff number, but still effectively is zero when moving CVs, until I move the slider a little, then try again. It will also not remember the choice for linked U and V falloff.
-When I have tools docked in a shelf, some of them don't remember which sub-tool from that group that I've used last is. Particularly for measurement locators in my case. I'd like one of mine to be always "curve-to-curve", but every time I open Alias it reverse back to "closest point", the first tool in that set.
-Saving the user profile does not fix any of these.