Open StellarGame opened 1 month ago
Hello, Thanks for the report. It will be difficult to investigate without a test case. You can either
This function is called for each object of the scene, so you may have to look what object is impacted when the crash happen
Hello, we have an asset we are exporting in blender 4.0 -> 4.2 where NLA tracks ticked is producing a bug in the function __get_nla_tracks_obj. Interestingly, the bug only manifests on the second call to the function during exporting and I'm not sure why it's being called a second time. The first pass appears to handle all the known animations of interest without error; hence the stack trace below shows the path to the second call that causes the bug:
The asset can't be shared at this moment, however playing with the code I can tell you that the length check on track.strips is 0 for the second pass causing current_exported_tracks, and consequently exported_tracks to be empty, finally creating an invalid index access when trying to get the track_names at the bottom of the function. You can also see I added a sloppy fix to just return empty lists on subsequent calls, though I'm not sure that's OK since I still have not reverse engineered what the second pass is designed to do:
Any help on what in our blender setup might be causing the second pass or a track with 0 strips is greatly appreciated! Thank you: