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

OgreMeshTool Fails #78

Open
MBetters opened this issue Mar 24, 2021 · 11 comments
Open

OgreMeshTool Fails #78

MBetters opened this issue Mar 24, 2021 · 11 comments

Comments

@MBetters
Copy link

Addon settings:

image

Export settings:

image

Error:

image

@MBetters
Copy link
Author

MBetters commented Mar 24, 2021

The mesh tool is valid. It's from ogre-next (v2):

image

@MBetters MBetters changed the title OgreXmlConverter Fails OgreMeshTool Fails Mar 24, 2021
@MBetters
Copy link
Author

My config.py:

image

@MBetters
Copy link
Author

My exit code for OgreMeshTool isn't 0.

image

@MBetters
Copy link
Author

Disabling both Shape Animation and Shape Normals is what worked. Duplicate of #56

@sercero
Copy link
Collaborator

sercero commented Mar 26, 2021

@MBetters they are actually different issues, the add-on scripts are failing at different instances.

In issue #56 the error is in mesh.py, now the error seems to be in util.py when calling the OgreMeshTool.

Since I'm not using Ogre 2.x, I didn't test this scenario when recommending that you disable only Shape Normals.

@sercero
Copy link
Collaborator

sercero commented Mar 26, 2021

Can you please reopen this issue?

Thanks.

@paroj paroj reopened this Mar 26, 2021
@sercero
Copy link
Collaborator

sercero commented Mar 29, 2021

@MBetters it seems that the problem is trying to use OgreMeshTool with pose animations and the v2 option, I think that pose animations are not supported in Ogre v2 Items.

I will ask @darksylinc in the forums.

@paroj
Copy link
Member

paroj commented Mar 30, 2021

maybe for now we should just gracefully abort with "Pose animations are currently not supported for V2 meshes". This would hint to the workaround instead of a cryptic error message.

@sercero
Copy link
Collaborator

sercero commented Mar 30, 2021

@paroj I was going to ask what do you think about not using an assert if the tool returns non-zero value, but just printing an error in the log and the report saying that the binary mesh will not be generated, just the xml.

@paroj
Copy link
Member

paroj commented Mar 30, 2021

when I added the asserts, exporting XML only was not an option. Should be fine nowadays.

@sercero
Copy link
Collaborator

sercero commented Mar 30, 2021

@paroj another question, I was thinking of adding an option to delete the .xml after conversion. Do you concur?

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

No branches or pull requests

3 participants