Hello, I am still somewhat new to Panda3D and I was trying to see what method people use to easily display their projects. I turned my project into a P3D, have it on my website, and it seems to be working just like when I run it in terminal. However I noticed that it only seems to work on my computer. (Although I’ve only tested two other computers so far).
Do other people need to have Panda installed to be able to see it? Also I used a self-generated certificate, I’m not sure if that would affect whether or not other people can see it.
I added the first link rdb posted (2 posts up) to the website and tried it from the other two computers I mentioned earlier. Both of them are Max OSX (10.5).
On the first computer I downloaded Panda3d Runtime, installed it, went back to the website and it did nothing in Safari. In Firefox it ran an installation in the browser window and then worked. (It also worked in Safari and Chrome after that Firefox installation).
On the second computer I also downloaded Panda3D Runtime and installed it but nothing seemed to happen in Safari or Firefox.
The installation just happened automatically the first time around, anyone know how to make the installation happen in general?
One last thing, the installation ran in the browser window and it worked on the second computer in Safari but not Firefox. It worked on the first computer’s Firefox though. Are there specific settings in Firefox’s preferences that would block Panda?
How do you define “not work”? Does the window stay blank? Does it display the error image?
Is there any error message in the logfile in ~/Library/Caches/Panda3D/log after trying it in FireFox on the second computer?
I had someone else test it on a Mac OSX in Firefox and it worked without me helping them. Really the goal was just to be able to see it online with little hassle, I’m going to assume that second computer just has some bizarre setting that makes a problem in Firefox.
Ah, there is a bug in Firefox for PPC that causes it not to be able to run the Panda3D plugin. It appears to be a bug in Firefox itself, not in the plugin; our code never even gets called.