-
Notifications
You must be signed in to change notification settings - Fork 30
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
discussion ticket - hatching texture regression #457
Comments
In theory, this should not happen. Only if user change the parameters of the materials on the scene manually. or the component data was changed in the Js code during scene initialization. Because I made a check in json-utils that if the component information is present in the |
But what if the user wants to change the segment elements - any of the components - position, rotaion, material, etc? Then this information still needs to be saved in JSON. |
No, in this case with dividers saving data works correctly. Alternatively, to fix it on older scenes, we could add |
I think it's a good idea to do this. This will eliminate the need for versioning in many cases |
Context:
divider
segment type was incorrect. See hash striping too dense #24instead we want this:
issue:
question:
segment
type
andvariant
s on those segments? that would empower us to make updates to textures or other elements of a segment without needing to modify user scene data to support the updates.workaround:
Here is an example of before and after:
Before:
After:
The text was updated successfully, but these errors were encountered: