-
Notifications
You must be signed in to change notification settings - Fork 48
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
LookDev transfer Error #42
Comments
Thanks @CalleHalldin, having a look at this tomorrow morning. Make sure the steps to reproduce does reproduce the problem, that way it'll be much quicker to fix. |
Sorry I haven't gotten into this yet. @LegacyID1991, you might be able to dive into this. The problem must be somewhere in the loader for this family, see here. I would start printing things, and see if you can pinpoint where in the loader the problem occurs. Likely in the |
@LegacyID1991 Did you have a look at this? If not, let me know here so I know whether I should look at it. |
I am sorry to say that I have been so slammed with other work duties that I haven't gotten to this one yet. |
That's ok, I just need to know whether I should look into it so we don't work on it at the same time. Would you like me to take over? |
go right ahead. |
Ok, I've found the problem. The problem is that it assigns to meshes based on the name of the shader group, but if the shader group has the same name in both look dev publishes, such as Putting together a fix now. |
Fixed, @LegacyID1991 is updating the pipeline shortly. |
…le_reversed_order listdir is alphabetically reversed so higher version is first
Example move
Process to get to produce the bug:
Seems like its always the First models and lookDev that you load that transfers the shader to the wrong asset. As can be seen in the video even though I create a completely new scene the bug is still there.
The text was updated successfully, but these errors were encountered: