You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Description
Krom Crashes while using world Sky Texture and Shadow Map Atlasing, with the following output at the console:
Uniform envmapStrength not found.
double free or corruption (!prev)
To Reproduce
Link a Sky Texture node to Color in the World panel and check the Shadow Map Atlasing box. Then run it with krom selected as the build runtime.
Expected behavior
No error. No crash.
System
Blender: 3.5 and 3.3.6
Armory: 2023.4.0
OS: Linux
Graphics card: Gigabyte 3060 OC 12G
Test File
I would upload an example blend file, if github allowed uploading blend files this way.
The text was updated successfully, but these errors were encountered:
I would upload an example blend file, if github allowed uploading blend files this way.
Hi, you can zip the project and then upload that. I cannot reproduce the issue from the instructions alone, so please share a file if possible :)
This could potentially be related to armory3d/armorcore#52, although in that case I guess I would be able to reproduce the problem (and the error message is different). Building Krom is pretty straightforward (at least on Windows, but it should be similar on Linux) so feel free to give this workaround a try and then report back.
Thank you for contributing to Armory!
Description
Krom Crashes while using world Sky Texture and Shadow Map Atlasing, with the following output at the console:
Uniform envmapStrength not found. double free or corruption (!prev)
To Reproduce
Link a
Sky Texture
node toColor
in the World panel and check theShadow Map Atlasing
box. Then run it with krom selected as the build runtime.Expected behavior
No error. No crash.
System
Blender: 3.5 and 3.3.6
Armory: 2023.4.0
OS: Linux
Graphics card: Gigabyte 3060 OC 12G
Test File
I would upload an example blend file, if github allowed uploading blend files this way.
The text was updated successfully, but these errors were encountered: