Actions
Bug #1264
open[p3d] [assimp] assimp accepts object names with spaces, p3d doesn't
Status:
New
Priority:
Normal
Assignee:
-
Start date:
2018-09-26
Due date:
% Done:
0%
Estimated time:
Description
When loading a scene (e.g Blender file) with p3d_read_blend, assimp accepts object with spaces in their names.
When creating a scenario (.sce) file from that, p3d writes instructions with that name, which is not supported by the p3d parser, when loading that scenario, hence aborting the loading of the scenario.
We should define the policy for naming objects and enforce it.
Updated by Jules Waldhart about 6 years ago
- Description updated (diff)
If not accepting spaces, we should check after importing assimp models and abort or refuse objects with spaces.
If accepting spaces, and to some extent, any symbols, we should rewrite the parsers.
Actions