I have made a scene in blender, and now i want to export to panda3d with plugin, i’m not sure if this plugin is well installed (do i must to install it in " blenderdirectory/scripts "?),
Well, i try first to export the scene to egg extension:
The i got a warning, system tells me that i must to check console:
And this is the console error:
Reading the console text, i think there is another way to export from a terminal windows, and convert it like pzip, but the plugin is a .py file, then i don’t know how to export…
Maybe this is a novice error, please excuse me if its…
The correct directory should be C:\Program Files\Blender Foundation\Blender.blender\scripts, though with program files in your native language - note the ‘.’ in front of blender. I’m curious that the plugin loads with it in that directory though - your at least the third person to report this problem in the forums and I’m wondering if all are making the same mistake. Could you confirm that moving it to the correct directory works? If it does I should be able to modify chicken to print a big fat warning when this happens, as its obviously very frustrating for all involved.
OK !, its works now, the problem basically is the blender package style…
Since in Blender homepage are two ways of download it, zip or exe install, the zip one brings those directories you just mentioned “./blender” and “./blender/scripts”, such in exe one does not contain (i dont know why, strange…), but now i copied all Chicken’s content into .blender/scripts and it ran well… at least the script… now i’m going to export the scene…
Just for thread completeness, I think when you install the .exe version of blender it lets you choose whether to put the .blender directory in the blender directory (As for the zip version) or in the user application data directory, with the default being the latter. Which means that when you used the .exe installer the directory you should of used was something like C:\Documents and Settings<username>\Application Data\Blender Foundation\Blender.blender\scripts
A note for future reference more so than anything else - as you have it working now there is no point to further fiddling.
Still, the fact that you can install the script into this other directory and get a partially working system is a problem I will have to work on - I might just put a big capital letter warning in the installation guide.
