Exporter and Blender 2.36?

#1 I got it to appear on the menu in Blender 2.36, and I've successfully exported a static object with it. I had trouble at first because I was using Python 2.4, but once I went back to Python 2.3 it worked fine.

I'm having trouble exporting animated things, but since I've never done animations with blender before, it's more likely that it's something I'm doing wrong and not something wrong with the exporter.

Were there any errors in the blender console window?

EDIT: I just sorted out my animation problems, so the blender exporter works fine with Blender 2.36, as far as I can tell

#2 I can confirm: python 2.4 did not work for me, python 2.3 did.

#3 Odd. I was initially using Python 2.4, and was having trouble, and hoped that rolling back to 2.3 would solve the problem (while using 2.4 the blender console would tell me that it could not find a python installation). I only managed to get the exporter to show up after I rolled back Blender to 2.35a, though.

Drew, Jameson, did you have to do anything funky in addition to the header editing and pythonpath variable in order for the exporter to show up?

#4 Nah, not really. I changed the top of Dts_Blender.py to this:

Name: 'Torque DTS Exporter'
Blender: 233
Group: 'Export'
Submenu: 'Export' export
Submenu: 'Configure' config
Tooltip: 'Export to Torque (.dts) format.'

and I set my PYTHONPATH environment variable to:

C:\Python23;C:\Python23\lib;C:\Python23\Dlls;C:\Python23\lib\lib-tk;C:\Python23\lib\plat-win;C:\Python23\lib\site-packages

I don't think there was anything extra beyond those two things. I also added Python's directory to my path, but looking at it again I misspelled the directory name, so that's obviously not contributing anything.

#5 For me the exporter works correctly with just the change to Dts_Blender.py in 2.35 and Python 2.3, no need to set the PYTHONPATH environment variable (although it won't hurt.) Windows XP SP2.
Upgrading to Python 2.4 breaks the exporter, uninstalling and reverting to 2.3 fixes it.

#6 Can confirm what Mauricio stated

#7 For Clarification:

You shouldnt need to uninstall python 2.4, just set your PYTHONPATH environment variable to point to the python 2.3 libs and bins. Or optionally use a shell script or batch file (win32) to set your PYTHONPATH to point to 2.3 temporarily when you fire up Blender.

#8 So I did a clean install of 2.36 and Python 2.34 on my other computer, and it worked fine after only changing the dts_blender.py header. I guess I might have missed something or broken something in my initial attempts to get the exporter running in 2.36. Cheers, guys! :)

#9 This is OS X 10.4.1 Python 2.35 Blender 2.37a

[url=http://www.garagegames.com/index.php?sec=mg&mod=resource&page=view&qid=4662]Python Exporter Scripts for Blender[/url}

says

Quote:In order to use this exporter, you will need to put it in a place where blender looks for scripts to put on the import/export menu's. The export process can then be invoked via the "Export" option on the exporter menu item, or configured via the "Configure" option.

where does Blender look for scripts to put on the import/export menus?

#10 /.blender/scripts is where you dump the contents of the exporter folder.
Works great for me with no changes on Blender 2.37 and Python 2.3

#11 Where is the .blender directory in OS X, I've only ever seen it on a windows install

#12 Patrick:
I've never seen Mac but on other OSes you do need to unhide folders starting with a '.'

It should be there somewhere - just hidden.


Others:
Make sure you unzip the files in a way that retains the original folder structure amd make sure the folder "DTSPython" is in scripts NOT scripts>Torque_exporter>DTSPython".

It should just be "scripts>DTSExporter"


After unzipping properly it worked nicely for me with Blender 2.37 and Python 2.3

#13 For OSX, the .blender file is inside the blender application package at blender.app/contents/resources. Unfortunately, it is also hidden, so even if you go inside the package, you can't find it. This means you can't just drag them in or anything simple like that. The only way I can think of to get them in there is to use the terminal. I got everything working on my powerbook some time ago, but I can't remember what I did exactly. If I can find out what you have to do I will post here, but if someone has a simpler solution, please post it first.

[Edit]Ok, so the documentation that comes with blender told me that the .blender file was there, but now I can't find it there. I will keep looking, but if you have the answer, please let me know

#14 Ok, got it (I think)
.blender file is inside blender.app/contents/macos

The way to get the files into the folder is to use the move command in the terminal. Open up a terminal window and go to wherever you keep the files for the exporter (you should make copies before doing anything else). The command you need to use is mv and the syntax is as follows: mv dtspython filename to where your blender application is installed (for example /users/username/desktop for me) /blender.app/contents/macos/.blender/scripts. If you have got this right your dtspython folder will disappear from its initial folder and be moved into the .blender folder.
Repeat this step for all the .py files in the exporter folder. Now when you start up blender, .dts should come up in the export menu. I haven't tested in on anything yet on this machine, but I am pretty sure it will work.

Good luck and happy modelling :)