Not Game Ready?

[Ryan]

Hi,

I purchased the Mountain Valley - HDRP - Game Ready Level as I wanted to use something that is game ready, however after setting everything up I can see that the combine mesh colliders are not working correctly. I was later informed that if I purchased the Scene Optimizer that I could fix them, so I did and I followed the steps and the issue still remains in the current version 1.0.7. I'm also seeing the rocks, path and the fence from different layers getting combined together, which seems very strange? Another issue I have is a load of the prefabs are missing after installing the Fantasy Kingdom - Spawner Pack, e.g

SM_Item_Broom_02
SM_Item_Broom_03
SM_Item_Pouch_01
SM_Item_Goblet_01
SM_Item_Goblet_02
SM_Item_Dish_04
SM_Item_Bottle_Clear_Labelled_01
SM_Item_Bottle_Clear_Labelled_03
SM_Item_Cheese_Slice_01

Please help!

[Peter]

Hi @Ryan, we were able to reproduce the issue after you reported it yesterday, we are working on an updated version of the levels. Getting the scene optimizer was a suggestion and re-applying the optimizations yourself was meant mostly as a suggestion if you do not want to wait for us until we publish the fixed version of the level.
It is strange though that you still see the issue after running the optimizer yourself - the game ready levels were made with an very early version of the scene optimizer so we were assuming that was a bug with collider scaling that was fixed until then - we need to see what the results are from the colleagues who are looking into this issue.

We looked into the other issue with the missing prefabs - it looks like the original Synty POLYGON Fantasy Kingdom package was updated since we built the spawner pack, and now there are some prefabs missing in there. For example if looking at the prefab "SM_Item_Broom3", in an earlier version of the synty pack this is a prefab sitting under 
Assets\PolygonFantasyKingdom\Prefabs\Items


In the latest version of the package, this prefab does not exist anymore, although the model/mesh files still exist:





We believe that might potentially be an issue in the original synty package - we could fix this in our spawner pack by creating those prefabs ourselves and including them in our pack, this might however create issues if synty decides to later include the prefabs back in again. We will try to contact synty to see if this is an intended change or if it is an accidental mistake.

[Manny]

Hey @Ryan,

I also found a solution to your other issue about the Scene Optimizer making incorrect scaling issues on colliders. This has been fixed in the newer upcoming version of the Scene Optimizer (v1.0.8). The tool basically ensures that the default lookup for the colliders are correct. 

If you can't wait for the latest version, there's a way to fix this manually yourself. Simply do the following 3 steps:

1. Go to the 'Scene Optimizer' Scriptable Object located in Procedural Worlds > Scene Optimizer > Resources.
2. Switch to 'Debug' mode in the Inspector and locate the section that shows 'Primitive Meshes'.
3. Replace the last two with the correct colliders.

If you're still unsure of what to do, here's an image that shows how to get there:

Let me know if this works! 🙂

[Ryan]

When I press cancel on the optimised scene button I get errors.
Okay, this is when clicking on the resources one, I guess I should not click there?

[Ryan]

I followed your steps and I have the same broken result after pressing the optimize scene button.

[Bryan]

These errors are basic Unity errors that happen regardless if Procedural Worlds products or any publishers products are in Unity are not. 

I believe this error has to do with Unity's GUID system. 
There is nothing we can do about this error. 

[Ryan]

After updating to version 1.08 the colliders are now working as expected. Thank you for that fix.

[Manny]

Hey @Ryan,

Could you try pressing the "Reset to Default" button in the Scene Optimizer window and try again?