Yes I can do that. I'm not sure how or where to upload it though.

I changed units to metric. I changed theme to elysium. Aniso filtering to 8x. VBOs checked. Region Overlap turned on. Images draw method turned to GLSL. The only addon i turned on was yours. cursor depth, auto depth, rotate around selection, global pivot checked.

I use a radeon HD 7870 as my GPU.

It is working just fine for me again. If I start a new blank scene and add a lamp to it before I import any meshes then i get the error again. I have to remove the lamp and add at least one mesh(i.e Legion_Commander_Body.smd) then I can add the lamp back in and continue importing meshes as normal.

Hey Art. I think I figured out the problem if you want to take a look at it. I believe the problem is being caused by a light already being present in the scene when importing. I was importing everything like normal and then I started a new scene and added a light before importing anything because normally i have a hemi lamp present in my blank scene for when i add the textures so they are visible. I removed the lamp and then tried importing again and it worked just fine again. So I reapplied all of my other settings and tried again to import without a lamp already being present in the scene and it still worked. So that is why I believe the lamp already being present is causing the problem. I can add the lamp but not until all the model are imported. I haven't tried any export yet.

Ok I can actually add the lamp after I have added at least one model but not before.

I just moved it to public. I alos had to unzip and manually install the addon because it kept putting it into the IINEWMANII profile.

UPDATE: I completely removed everything related to blender from my computer and reinstalled 2.69 using the installer and then installed the add-on using the .zip and it works. I'm not exactly sure what was causing the problem but thank you for your help and suggestions....especially on a Sunday. Also thank you for taking the time to make this handy add-on.

Is this what you meant by moving it to a different profile?

Traceback (most recent call last):
File "C:\Users\Public\Blender Foundation\Blender\2.69\scripts\addons\io_scene_valvesource\import_smd.py", line 59, in execute
self.countSMDs = self.readSMD(self.properties.filepath, self.properties.upAxis, self.properties.rotMode, append=self.properties.append)
File "C:\Users\Public\Blender Foundation\Blender\2.69\scripts\addons\io_scene_valvesource\import_smd.py", line 1249, in readSMD
if line == "nodes\n": self.readNodes()
File "C:\Users\Public\Blender Foundation\Blender\2.69\scripts\addons\io_scene_valvesource\import_smd.py", line 241, in readNodes
smd.a = self.createArmature((self.qc.jobName if self.qc else smd.jobName) + "_skeleton")
File "C:\Users\Public\Blender Foundation\Blender\2.69\scripts\addons\io_scene_valvesource\import_smd.py", line 301, in createArmature
ops.object.mode_set(mode='OBJECT',toggle=False)
File "C:\Users\Public\Blender Foundation\Blender\2.69\scripts\modules\bpy\ops.py", line 188, in __call__
ret = op_call(self.idname_py(), None, kw)
RuntimeError: Operator bpy.ops.object.mode_set.poll() failed, context is incorrect

location: <unknown location>:-1

It also worked for me until yesterday.

If I do that Blender just stops working. It won't run anymore if I do that. Maybe I should note that when I install blender I just use the installer and have it install the new version of Blender without removing the old version. Thats what the installer does by default. Maybe its causing a problem i don't know really. I tried completely removing blender 2.69 and then reinstalling it and that didn't help. I could try removing every version and then reinstalling Blender 2.69 without using the installer and see what that does.

Hello Art. I did what you suggested. I removed it from Blender and then tried to reinstall it and it gives me the same error. I then completely rmoved it and all other versions i had sitting on my hard drive and then tried re-downloading and installing it and i got the same error. Restarted my computer and tried again and got the same error. Then went back to version 1.8.5 and got a different error but it still didn't work. 1.8.5 was the version I was using before and it worked perfectly. I am using revision 60995 of blender which I believe is the current official version. I will keep trying to see if I can get it working.

Traceback (most recent call last):
File "C:\Users\IINEWMANII\AppData\Roaming\Blender Foundation\Blender\2.69\scripts\addons\io_scene_valvesource\import_smd.py", line 59, in execute
self.countSMDs = self.readSMD(self.properties.filepath, self.properties.upAxis, self.properties.rotMode, append=self.properties.append)
File "C:\Users\IINEWMANII\AppData\Roaming\Blender Foundation\Blender\2.69\scripts\addons\io_scene_valvesource\import_smd.py", line 1249, in readSMD
if line == "nodes\n": self.readNodes()
File "C:\Users\IINEWMANII\AppData\Roaming\Blender Foundation\Blender\2.69\scripts\addons\io_scene_valvesource\import_smd.py", line 241, in readNodes
smd.a = self.createArmature((self.qc.jobName if self.qc else smd.jobName) + "_skeleton")
File "C:\Users\IINEWMANII\AppData\Roaming\Blender Foundation\Blender\2.69\scripts\addons\io_scene_valvesource\import_smd.py", line 301, in createArmature
ops.object.mode_set(mode='OBJECT',toggle=False)
File "C:\Program Files\Blender Foundation\Blender\2.69\scripts\modules\bpy\ops.py", line 188, in __call__
ret = op_call(self.idname_py(), None, kw)
RuntimeError: Operator bpy.ops.object.mode_set.poll() failed, context is incorrect

location: <unknown location>:-1

This is the error I get.

I am using Blender version 2.69 and Windows7 64-bit.