Open TRBlount opened 8 years ago
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.
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.
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?