Hi, I had a custom decal shader for needle 3.3 and it was working fine and when i updated the needle to version 4.2 the custom shader is not working the decals are not visible in the web build , I even tried changing the shader to unlit still it did not work .
Hello Team Imersive,
The issue you’re experiencing with custom decals not rendering correctly after updating to Needle Engine version 4.2 could be related to several factors, particularly because shader behavior can change between versions.
Here are some steps you can take to troubleshoot:
Check Shader Compatibility: Ensure that your custom shader is compatible with the new version. In the documentation, it is mentioned that using custom shaders or materials could lead to objects appearing white, meaning the properties did not map to glTF compatible names (see faq). Double-check the shader properties and ensure they are correctly set up for glTF export.
Modify Material Properties: If the shader is not adapting well, try reverting it to a simple material and see if that works. After testing a basic material, you can gradually introduce your shader properties and settings to identify what might be causing the issue.
Check the Decal Mesh: Ensure that the decal meshes themselves are correctly configured and that their shaders are being correctly applied. Check if there are any changes in the way the engine handles decals compared to version 3.3.
Inspect Export Settings: Verify your export settings. Changing the shader to “unlit” should normally work, but ensure that the material is correctly assigned in Unity and that it is marked for export.
Review Documentation: Consult the Needle Engine documentation, especially updates between versions 3.3 and 4.2, for any relevant changes related to shaders and rendering (see releases).
Log Errors: Look for any console errors or warnings during the build process or in the browser’s developer console. This could provide valuable clues about what is going wrong with the shader or the decal rendering.
If the issue persists, consider creating a minimal reproducible example or check if the issue is resolved in newer versions beyond 4.2, as updates might have patched compatibility issues.
Please let me know if you need further assistance, and feel free to share any logs or specific error messages you encounter!
1 replies left - Get a PRO license for more AI replies.
thread_Rp21De6mQipSGBByF1ckDeVm
Reply to this message to continue the conversation
Hi, do you see any error in the browser console? Needle 4 updated to three 169 instead of 162
That error is from your code? When is that logged?
