-
Notifications
You must be signed in to change notification settings - Fork 71
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Complete viewscene state #2285
Complete viewscene state #2285
Conversation
Not loaded yet
Please provide some saved network files that demonstrate those settings not loading correctly. |
Tested on macOS 11.4 and 10.15.7. Same behavior. Settings that did get saved:
Settings that did not get saved:
|
Hmm, not sure why MacOS version is a factor here. Anyway, I can test on 11.3 now. I don't think I hooked up the light settings yet, I'll check. And clipping state is a little flaky, as you found. |
Oh, one problem with the screenshots--you're not using the updated version, that's the milestone build. |
I was finally able to test this. I'm getting a build Error:
|
Also the lighting is different in the artifact that was generated. I'll investigate it some more tomorrow |
Oops never built tetgen. I'll fix that today. |
looks like the light color doesn't initialize properly in a previously saved network. Once I click on the change light color button it fixes the lighting. without doing it, it only shows the ambient component |
OK I moved some lighting init code around so maybe it's working differently. But the code I changed should not have been correct before. Was it working completely on master? |
It works fine on master, but the color was not save in the state. It works fine if it's a new network, of if the network has been saved with the newest version. It's only a problem with a network saved in an old version (master) and loaded in this (branch), so it's a pretty narrow case, albeit one that most people will see. |
This fixes the save from a new model, but it still sets to 0,0,0 with an old network. One thing I noticed is that an old module sets the colors as an int 0-255, but the new one is a float 0-1. I'm not sure I'd want to sacrifice accuracy, but this may be a problem for users |
maybe we can add a note somewhere obvious? like the red viewscene thing? |
Can you attach a network with int colors saved? All of mine seem to be float. |
I believe that was a change made a long time ago, like years. |
test_light_color_save.srn5.zip This network was made on the branch, so the ints probably don't matter. It appears the color selector is returning ints, but the module handles it ok. One thing I noticed is that I have to toggle the meta layer to get it to update the state info |
with old modules loaded in this branch, it is still defaulting to 0,0,0. Why would that be? |
Right the metadata layer doesn't update until execute. That should be an easy improvement but do make an issue for it. |
Can you provide an old network that does this? Or just use any old one with headlights turned on...hard to search for that in the xml files... |
test_light_color_save_II.srn5.zip Here is a test case for the default settings that probably should be reverted to white |
test_light_color_save_III.srn5.zip multiviewscene. One with non default that should be left alone |
Closes #1939
Also made the change to scoped enums. #1381
And M1 mac build works, at least headless.