Skip to content
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

New CPU Lightmapper crashes with GridMap when baking #45086

Closed
DarkKilauea opened this issue Jan 11, 2021 · 2 comments
Closed

New CPU Lightmapper crashes with GridMap when baking #45086

DarkKilauea opened this issue Jan 11, 2021 · 2 comments
Assignees
Milestone

Comments

@DarkKilauea
Copy link
Contributor

Godot version:

Godot Engine v3.2.4.beta5+lightmapper.official

OS/device including version:

Windows 10 (Build: 19042.685, Arch: x64)
AMD Ryzen 7 3800XT
NVidia GeForce RTX 2080 (running GLES3)

Issue description:

I was testing the new CPU lightmapper proposed in #44628 with a simple GridMap. Whenever I try to bake the lightmap for the scene, I get a crash. Sample scene is attached.

Log:

Godot Engine v3.2.4.beta5+lightmapper.official - https://godotengine.org
OpenGL ES 3.0 Renderer: GeForce RTX 2080/PCIe/SSE2
OpenGL ES Batching: ON

ERROR: get: FATAL: Index p_index = 0 is out of bounds (size() = 0).
   At: ./core/cowdata.h:152

I tested the same scene with the official build of v3.2.4.beta5 and the lightmapper worked fine there.

Steps to reproduce:

  1. Create a scene and add a Gridmap.
  2. Create a MeshLibrary containing a cube as the only item.
  3. Paint a scene with the cube "tiles",
  4. Add some lights.
  5. Add a BakedLightmap node and cover the GridMap in its extents.
  6. Click the "Bake" button.

Minimal reproduction project:

TestGridmapLightmap.zip

@JFonS JFonS self-assigned this Jan 11, 2021
@JFonS JFonS added this to the 3.2 milestone Jan 11, 2021
@JFonS
Copy link
Contributor

JFonS commented Jan 11, 2021

It was a simple error from my side, I already found a fix for it, but I'm waiting to update the PR together with some other fixes. I will keep you posted :)

@DarkKilauea
Copy link
Contributor Author

Confirming that the issue is fixed in 3.2.4 beta 6.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants