Exclude the conversion of the model to .bam, at the stage of building the application

General Discussion
,
1

https://docs.panda3d.org/1.10/python/distribution/list-of-build-options#list-of-build-options

According to these application building options, the user has the opportunity to develop an application using the .egg, .glband .gltf formats. Which, in my opinion, is of questionable usefulness, since this issue of choosing the format of models is essentially attributed to the export stage. Postponing it to the packaging stage introduces confusion and inconsistency, since the default-model-extension option from the .prc file helps to organize the loading of such models at the development stage.

Which in itself is absurd for C++ users, I don’t think explanations are needed here. It breaks the logic for python users, since users can place such files in a .mf, anywhere else. Then they may come up with the idea that some files should not be converted to a format .bam, there will be no limit to this fantasy.

Aren’t there too many scenarios for an application building tool? It may be easier to abandon this mega features in favor of rationality.

2

What exactly are you suggesting? I’m not sure I understand what you are saying exactly.

3

My thought is in the title of the post. I suggest not converting models to .bam during the application build phase. I think you need to think about this at the stage of exporting the model. Leaving this process at the final stage gives rise to many logical surprises.

4

The model always gets converted to .bam when loading (for caching), so I’m not sure what surprises you expect to suddenly encounter during the final export.