-
Notifications
You must be signed in to change notification settings - Fork 74
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
Oot map importer segments are bugged (FOUND WORKAROUND) #252
Comments
can you be more specific? I never got a crash with the importer, ideally provide the errors in the console (but it can be annoying if it's crashing), are you importing a vanilla map when the issue occurs? |
its when launching the map in game. fast64 doesnt error. it also is a vanilla map yes |
update it seems to be assuming that everything on the draw config is used on all materials as an example in spot00 8 and 9 are used exclusively for xlu on the water and A is only used on a specific window to light it at night any other use case crashes in spot00 |
Work around
|
here is a python script for
import bpy
for mat in bpy.data.materials:
for attr in (*(f"segment{n}" for n in "89ABCD"), "customCall0", "customCall1"):
for propGroup in (mat.ootMaterial.opaque, mat.ootMaterial.transparent):
setattr(propGroup, attr, False) |
that works |
Oot map importer enables segments 8 9 and A for all materials on import causing crashes without spending 30 minutes figuring out the correct settings by hand.
The text was updated successfully, but these errors were encountered: