(I realise that rdb is likely not around as of the time of my posting this, but I’d rather leave it here early than risk forgetting later.)
I have a bit more information, perhaps.
I decided to have a shot at using the latest (as of earlier today, my time) SDK version of Panda from GitHub–which, as has been pointed out, shouldn’t have an effect, but seemed worth trying, and I mention it here just in case it’s relevant–and as a result attempted another build.
This time I noticed something in the output of packp3d_dev. It occurs early, and flashes by very quickly indeed, so I may well have missed it previously; I ended up catching it by redirecting the console output to a text file. Here is the text in question:
There are some missing modules: ['Adventuring.footsteps', 'BinsAndTags', 'Combat', 'Common', 'CommonValues', 'Conversation', 'Cutscene', 'GameObject', 'Inventory', 'Level', 'Menus', 'NPC', 'Navigation', 'OptionsMenu', 'Player', 'Town', 'Translation', 'panda3d.bullet', 'panda3d.core']
“Adventuring.footsteps” is understandable–that’s the result of something being accidentally left in, I believe–but all of the others (presumably including “panda3d.core”) are important–it seems somewhat odd that it’s not finding them.
More oddly, I would expect all of my own modules there to start with “Adventuring.”, as in the case of “footsteps”; a quick search of my code using “BinsAndTags” as an example found only importations with the “Adventuring.” prefix, like so: “from Adventuring.BinsAndTags import *”.
I have seen posts mentioning that the inclusion of “panda3d.core” in such messages is the result of a bug–but I believe that I’ve also seen at least one such indicate that said bug was fixed and would be corrected in the next release–since I’m using a dev. version, would I not perhaps have that fix?
As to my own modules, all of those mentioned should be within the directory given to packp3d–or rather, a subdirectory of that directory. To be specific, I build from a directory (simply named “P3D”) outside of my game’s directory, and point packp3d to the appropriate directory via the “-d” parameter. The hierarchy looks something like this:
My Game Projects
|
|----- P3D (from which I build)
|
|----- LevelPrototype (the game directory)
| |
| |----- Adventuring (in which the above-mentioned modules should be found)
I note that it isn’t complaining about modules placed within the “LevelPrototype” directory, but within their own folders instead of the “Adventuring” folder, such as GameSaver or KeyMapper.
Possibly arguing in part against this is that I attempted a minimal test–albeit asking it for the same dependencies: Bullet, MorePy, and OpenAL–it too crashed shortly after opening a black window–but then I’ve had problems with the runtime on this computer (albeit not properly tested), I think, and the fact that it managed a black window (even if it didn’t show anything else) does seem to indicate that Panda is being found, despite there being a similar message in the output of packp3d_dev during building, albeit only including “panda3d.core” this time, I believe.
