-
Notifications
You must be signed in to change notification settings - Fork 443
New issue
Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? # to your account
Not Working: "Refresh In-Scene Prefab Instances" #3067
Comments
Hi @zachstronaut, |
NGO 1.9.1 and these are in-scene placed prefabs that had a NetworkObject added to them so they needed to be updated in the scenes that used them so that unique network guids would get generated. Unity 2022.3.10f1, btw. If you are not able to easily repro the problem (problem being: using the context menu from the prefab, seeing the popup load through the scenes, but then not actually have any changed files afterwards) -- like if this requires something else going on to reproduce -- then my one theory for you is that this prefab went from not networked at all to having a new NetworkObject at the top level AND adding a new nested child prefab that was already networked and already had a NetworkObject. |
That is very helpful...just getting back from a short break (needed some rest... 😹 ) and will be looking into this sometime tomorrow. |
Welcome back! |
@zachstronaut Now that I have the steps to replicate it should be relatively easy to figure out. |
@zachstronaut
Let me know if this provides better results on your end too (to verify the issue I replicated on my end is indeed the same issue you are experiencing). If it works for you, then I will open a PR for this update. |
This fix works as far as I can tell! Thanks, Noel! |
Using the "Refresh In-Scene Prefab Instances" contextual menu on a prefab doesn't actually make any changes to the scenes that use the prefab. I have to manually go into the scenes in question and toggle the prefab gameobjects on/off in order to get Unity to recognize the new network guids as a dirty state that can be saved.
The text was updated successfully, but these errors were encountered: