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
ClientSim UI intersects with world geometry #58
Comments
|
Incase any details are needed:
Can't think of any other issues that may be effecting this, I know a few others have ran into this issues on random projects, with the same items I mentioned above. |
|
@MrQ89 , I'm able to reproduce this by removing references to Unity's Not sure what would cause that to happen, but I couldn't find any other way to reproduce the issue. We should be able to fix it by using our own UI material instead of Unity's. |
|
After a lot of messing around it seems the editor extension Awesome Folders is conflicting with ClientSim. Removing it from any of my projects with this issue fixes it and adding it to a new projects creates the issues. |
|
@RackshawGames, were you using any tools such as Awesome Folders? |
|
Tested this a bit more. The canvas background material is still linked for me and the shaders settings look like they are default, also tried making a custom one with the For myself I have just switch over to Rainbow Folders 2, it's doing most of the things I wanted from Awesome Folders. |
|
@Faxmashine That is correct I am using the AwesomeFolders unity plugin as Risky mentioned! |
|
Hah, well there's our solution 😄 I suppose AwesomeFolders interferes with ClientSim somehow. Strange. Thank you @RiskyKen ! |
|
I've done some testing, and have found a good enough workaround for this issue! This is low-priority, and I wasn't able to find a better fix while testing, so we're closing this bug out! |



ClientSim's menu can intersect with world geometry, occasionally making it difficult to interact with.
It should instead be rendered in front of all other objects in the scene.

Thank you Rackshaw from our official Discord server for reporting this issue.
The text was updated successfully, but these errors were encountered: