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

Unnamed subobjects cause crash when exporting to Collada #7

Open
TRBlount opened this issue Jul 7, 2016 · 2 comments
Open

Unnamed subobjects cause crash when exporting to Collada #7

TRBlount opened this issue Jul 7, 2016 · 2 comments
Assignees
Labels

Comments

@TRBlount
Copy link
Contributor

TRBlount commented Jul 7, 2016

Hades was attempting to export a model to DAE and PCS2 kept crashing. I did some checking and found two unnamed subobjects in the POF (nighthawk.pof from BP). Giving these subobjects names stopped the crash. I think we should make PCS2 auto assign names based on the parent subobject during export to avoid this. Any other suggestions?

@chief1983
Copy link
Member

Are unnamed subobjects something that should be allowed in the first place? I wonder if it would be better to warn the user of unnamed subobjects when a file is opened and prevent export without fixing the problem. Then maybe an 'auto-repair' feature could be presented, but I feel like the user should be notified and given a chance to manually fix the problem.

@TRBlount
Copy link
Contributor Author

TRBlount commented Jul 8, 2016

That is also an option. It would certainly help, especially since it's not able to be ascertained a glance. Just something to think about.

@TRBlount TRBlount self-assigned this Nov 23, 2016
@TRBlount TRBlount added the bug label Nov 23, 2016
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

2 participants