Nice spotting! That very well may be the issue, but thats an auto-generated file at an auto generated path, so its a panda bug if thats the issue. I wonder if there is a nice work around.
rdb, I’ll rerun and check for that directory shortly. I noticed that some of the files that clearly did exist when it was running are not there when its done though (such as the nsis script) so some things are apparently getting deleted when it fails/finishes.
Looking at the source, David fixed this issue a while ago. Can you try pdeploy_dev.p3d from runtime-dev.panda3d.org and see if that works? (Just be sure not to distribute any installers created with pdeploy_dev, it is just for testing!)
Okay. Do I need literally the latest version, or do I need the version that coincides with the pdeploy-dev you linked?
I’m ready to put my game up on Steam’s Greenlight program and I’d really like to be able to include a demo, so if there’s anyway to get pdeploy working properly in the next week or so, I want to pursue it.
I would imagine that you need to get the coinciding version. I’m not sure, though, as I don’t even know why this issue is occurring in the first place.
You can distribute games with pdeploy_dev, as long as you make sure you use the “installer” option with the -s flag so that it doesn’t try to contact the Panda website to try and download the latest development runtime distribution every day.
You could create an installer using 1.7.2, extract its files and recreate the installer for these files manually invoking nsis - you can use the nsi file generated by pdeploy as reference and add the icon instructions to it.
When I was running pdeploy, mine also crashed at the makensis call. As you mentioned, the slashes screw things up on windows, so they need to be changed. You are also correct that the system automatically deletes the required files.
HOWEVER, if you are quick with your fingers, you can copy over the folders that are needed, the .exe, and the .nsi file (All under the TEMP). The nsi file isn’t created until a little later on, so you have to be quick on your toes. Once the application fails, I just copied those files back into the TEMP folder where they were originally created. Then just open the nsi file and fix the slashes. Do a search and replace for all "/"s for ""s. Just be careful that there is a /r option towards the end of the file that needs to stay a forward slash. (as in RMDir /r “$INSTDIR”).
Once I did all that, I just ran the makensis.exe /v2
Okay, now this is weird. The error message was “makensis utility not found”. Oddly, when I went looking, the entire folder was in another directory. WHAT??
I have had problems from day one with the install, had to re-install, not really happy about how oddly things went. This has been an absolute struggle. I just spent eight weeks making a game that should have only taken a couple of weeks, but I chalk a lot up to my inexperience with Panda. Yet, there have been so many things like being unable to change view angles, and not getting textures working and so on…
Anyway, it’s far too late in the process to grouse. I got to the end, but still, why in the world are things in oddball places like this? Something is very plainly screwy. How can we prevent this from happening to other people?
And, where should I place the NSIS folder for things to work and actually make a package? Just want to be certain.