Resonite: Normal Maps Bug After Uploading
Hey guys! Today, we're diving into a peculiar issue in Resonite that some users have been encountering: normal maps looking wonky after uploading and then bringing them back out. It's like your carefully crafted textures decide to take a vacation from reality for a bit. Let's break down this bug, how to reproduce it, and what the expected behavior should be.
Describe the bug?
So, here's the deal: when you save an object or world in Resonite that has a normal map applied, and then you immediately spawn it out, the version hosted on the cloud sometimes looks, well, mangled. The original normal map seems to go through some kind of bizarre transformation until the correct variant is computed. It's like the cloud server is playing a practical joke on your textures.This issue, while self-correcting after a few hours or days as the cloud variant is processed, can be quite alarming. Imagine you've just finished tweaking your avatar, world, or a single object, save it with pride, and then, bam, the textures look like they've been through a digital washing machine. The inconsistency between the local and cloud versions can lead to confusion and frustration, especially when you're trying to showcase your creations or collaborate with others. The temporary nature of the problem doesn't diminish its impact, as first impressions matter, and a mangled normal map can certainly leave a lasting impression. Furthermore, the uncertainty of when the correct variant will be computed adds another layer of annoyance, as users are left wondering when their creations will finally look as intended.
To Reproduce
Alright, if you want to try and replicate this issue, here’s what you gotta do:
- Open the testing world: Head over to this Resonite record:
resrec:///U-ohzee/R-8f27dd1c-76e0-4eda-935b-ad0b88d8d3c9. - Check the screenshots: Take a look at the screenshots provided to see the visual differences we're talking about.
- Inspect the object: Focus on the object with the normal map applied.
- Cross your fingers (maybe): Hopefully, you'll notice that it looks different from the original before saving.This testing is a bit fickle, so the variant system might generate the correct variant by the time you check it out. If you're feeling adventurous, try testing with a raw normal map and performing a destructive operation to save it to the cloud, which should prevent deduplication. This can help ensure that the issue manifests more reliably. Additionally, experimenting with different normal map settings, such as compression and mipmapping, may also influence the outcome. The key is to try and isolate the factors that contribute to the incorrect rendering of the normal map in the cloud version.
Important Note: Keep in mind that this issue can be a bit inconsistent, as the variant system might generate the correct variant by the time you review it. To increase your chances of reproducing the bug, try testing with the raw normal map and performing a destructive operation to save to the cloud, which should prevent deduplication.
Reproduction Item/World
resrec:///U-ohzee/R-8f27dd1c-76e0-4eda-935b-ad0b88d8d3c9
Expected Behavior
Ideally, the normal map should look pretty much the same as the local version, even if it’s in a non-optimized variant. We're not expecting perfection, but a reasonable resemblance would be nice, right? The whole point of using normal maps is to add intricate detail to surfaces without bogging down performance with excessive geometry. When the cloud version of a normal map deviates significantly from the local version, it undermines this purpose and can lead to visual inconsistencies that detract from the overall user experience. Furthermore, the discrepancy can make it difficult for creators to accurately assess how their creations will appear to others, hindering the collaborative process. Therefore, ensuring that normal maps are rendered consistently across local and cloud environments is crucial for maintaining visual fidelity and fostering a seamless creative workflow in Resonite.
Screenshots
Before saving:
Applied to object:
After saving and loading from cloud:
Applied to object:
Here's the testing normal map I'm using:
Resonite Version Number
- Beta 2025.9.23.1237
What Platforms does this occur on?
- Windows
What headset if any do you use?
- Desktop
Log Files
Additional Context
Initially, there was a thought that the format of the normal map might be the culprit. However, it's tough to say for sure. So, the focus shifted to the normal maps simply looking wrong. This issue might be related to the bit depth of a texture, but more testing is needed to confirm this. It doesn't seem to happen to all normal maps. The example used here has a bit depth of 32. The normal map issue can indeed be frustrating, but hopefully, with more information and testing, the Resonite team can squash this bug and ensure that our creations look their best, no matter where they're loaded from. Keep experimenting, keep reporting, and let's make Resonite even better together!
Reporters
- Ohzee
- reviver.noon
- raidriar796
- draycethevoidangel
- Hayden