- Home /
I updated my unity project and started getting these errors, anyone know how to fix this?
This is the same problem as described in this forum post.
Please, try to do some research first on google.
Uhm this is actually not the same problem as in the forum thread. In the forum thread there was a bug in Unity that caused that
An element with the same key already exists in the dictionary
error caused by the UNetWeaver assembly postprocessor that handles the automatic code generation for the UNet attributes.
This is a completely different error which states that the code has a variable of type "Shader" which is marked as sync var (or otherwise serialized across the network) but the UNetQeaver couldn't create the appropriate wrapper code since the "Shader" type can't be serialized / send over the network.
So this is actually more likely a user error. Unfortunately the error doesn't tell us on which Behaviour it was currently working on since the error has to be in that class.
Though UnityAnswers is not an error / stacktrace analyzing service. This "question" can't be answered / solved as the error is somewhere in the user code which has not been included in the question.
Well what I don't understand is it was working in a previous version of unity just fine, so I was wondering if anyone was aware of shader dependencies that were deprecated or something strange like that, I have a very $$anonymous$$imal understanding of shaders and this error is co$$anonymous$$g from an asset I downloaded through the asset store.
Sorry, I was googling around and never found that, thank you for the link.