Closed GoogleCodeExporter closed 8 years ago
Click Help > Toggle System Console, then try to enable the tools again. What
does it say?
Original comment by cont...@steamreview.org
on 25 Jun 2012 at 5:47
Says reloading *the long file name for the add-on* and then I got an: "<!>
Event has invalid window"
Original comment by RDavenpo...@gmail.com
on 26 Jun 2012 at 5:44
Never seen anything like that before. Is there any text above those messages?
Original comment by cont...@steamreview.org
on 26 Jun 2012 at 6:32
Nope nothing besides the standard python message. Nothing I do lets me enable
the SMD/DMX import/export option. Driving me crazy. I've tried to
uninstall/reinstall update/rollback, everything I could think of.
Original comment by RDavenpo...@gmail.com
on 27 Jun 2012 at 6:28
I'm having the same issues.
Original comment by vsem...@hotmail.com
on 1 Jul 2012 at 1:36
I'm a new(ish) blender user and am also having a similar problem. However in
the system console it says the problem is 'ImportError: No module named besh'
Have I just stupidly not installed something? or is there a problem with the
add on?
Original comment by nuri_...@hotmail.com
on 1 Jul 2012 at 7:50
I've downloaded fresh copies of Blender 2.63a 32-bit and 64-bit and don't have
any trouble installing the SMD tools. I have absolutely no idea what could be
causing these problems. :(
Nuri, are you sure the error said "besh"? I'd expect it to say "bmesh", which
probably means that you're using an old version of Blender. (Although Blender
is supposed to pop up a friendly error message if that happens...)
Original comment by cont...@steamreview.org
on 1 Jul 2012 at 8:51
I'm pretty sure it says "bmesh"
Original comment by yagothef...@gmail.com
on 6 Jul 2012 at 12:23
Issue 40 has been merged into this issue.
Original comment by cont...@steamreview.org
on 6 Jul 2012 at 5:45
Yagomus fixed the issue by upgrading to 2.63a. Can everyone make sure you're
using that and not 2.63?
Original comment by cont...@steamreview.org
on 6 Jul 2012 at 5:50
[deleted comment]
[deleted comment]
[deleted comment]
[deleted comment]
After a while it seemed that it didn't work for me. I went to post a forum on
blender.org, but when I decided to check to see the version of the SMD tools, I
noticed mine worked!
It seems that the problem is that you placed the "Blender" file on the desktop
instead of copying it. If you did copy it, maybe reinstall blender. It worked
for me!
Original comment by MCNWunde...@gmail.com
on 31 Jul 2012 at 2:58
Closing due to inactivity. Presumably upgrading to 2.63a fixed the problem.
Original comment by cont...@steamreview.org
on 13 Aug 2012 at 7:43
Apparently same issue, Windows x64. This is the output of the console from
Blender 2.63a double checked and tested both through installer and .zip
Pardon using a screenshot for the console, but Windows's terminal is quite
uncomfortable
Original comment by darthemmanuel2@gmail.com
on 5 Sep 2012 at 8:19
Attachments:
That's a completely different issue that was fixed with the 1.5.1 release.
Original comment by cont...@steamreview.org
on 6 Sep 2012 at 5:25
"Run as Administrator" for the Blender.exe solved this issue for me.
I was getting weird admin privilege blocks when trying to copy the files into
the Blender directory, so I decided to give it a try. Not sure why that was an
issue to begin with though :/
Original comment by fis...@gmail.com
on 5 Feb 2013 at 1:49
Original issue reported on code.google.com by
RDavenpo...@gmail.com
on 25 Jun 2012 at 1:24