Page 1 of 1
Exporter errors and console log
Posted: Thu Jun 16, 2011 6:32 pm
by kiwimage
Hello,
From time to time, the unofficial Blender Exporter fails to export the .obj and/or .mtl.
It happens. In this case, we get the message, from within the Blender api : "something wrong happened, please check console logs...".
So I open a new blender panel called python Console, to check what 's wrong and... there's nothing in it. Nothing related to the obj export.
Am I doing something wrong here ?
Re: Exporter errors and console log
Posted: Fri Jun 17, 2011 7:37 am
by matej
If I'm not mistaken when you start Blender in Windows a console window pops up. You should check that one for info.
Re: Exporter errors and console log
Posted: Fri Jun 17, 2011 1:43 pm
by kiwimage
Indeed, there's a console popup, but once Blender is launched and running, it's not possible to access it any more .
Not by any mean that I know of. So it doesn't help much.
I thought the console that we can call inside blender panels is an instance of that one you mentioned.
Re: Exporter errors and console log
Posted: Fri Jun 17, 2011 2:21 pm
by matej
Strange, AFAIK that console window is intended exactly for this purposes, so you should be able to minimize Blender and check it...
Anyway, you can start Blender from the console (instead of doubleclicking on icon) - you can find the console program in the menus or in the start menu there is a textbox, write down cmd and hit enter. When the console pops up, browse to where you have Blender installed with cd <whole path to your blender install dir> (like: cd c:\Programs\Blender), and then start Blender with blender command. Now the console is accessible and you'll be able to look up the message.
Re: Exporter errors and console log
Posted: Fri Jun 17, 2011 6:55 pm
by mib2berlin
IIRC the console window could activated on windows in the help menu.
Cheers, mib.
Re: Exporter errors and console log
Posted: Fri Jun 17, 2011 11:43 pm
by kiwimage
Thank you both, i can access it it from the help menu indeed.
I'll do that next time i encounter this error, I hope there'll be something interesting in this console.
cheers