Wed, Nov 27, 6:35 AM CST

Renderosity Forums / Blender



Welcome to the Blender Forum

Forum Moderators: Lobo3433 Forum Coordinators: LuxXeon

Blender F.A.Q (Last Updated: 2024 Nov 24 8:44 pm)

Welcome to the Blender Forum!


   Your place to learn about Blender, ask questions,
   exchange ideas, and interact with the other Blender users!


   Gallery | Freestuff | Tutorials

 

Visit the Renderosity MarketPlace. Your source for digital art content!

 





Subject: LightWave exporter is broken - how to rescue my half - year work?!


Silgrin ( ) posted Thu, 30 August 2007 at 3:26 AM · edited Wed, 27 November 2024 at 4:00 AM

file_386608.jpg

I try exporting meshes made in Blender to LightWave. It worked before... But now I only get messages like the attached one [though I have Python installed on my machine], or simply nothing-and Blender just disappears from my screen. This depends of version used [2.44 grumbles about struct module while older vers just crash]. Anyway, I looked at the d/load page and found no info if I should get Python and in what version. Any help needed, or I will loose results of half-year work!! I currently run B 2.41, 2.42a or 2.44a on XP HE PL.

I know... Another question form a series "nothing works and nobody knows why". But this really is how Blender behaves on my puters... I tested it on four totally different machines and it never worked as predictably and usefully as C4D, LW, or even AoI. Now I will be probably buried under a hip of stones thrown by B enthusiasts;) And I suspect this is why its popularity doesnt rise as quickly as it could.


Gog ( ) posted Thu, 30 August 2007 at 4:15 AM · edited Thu, 30 August 2007 at 4:16 AM

Silgrin, from what I can see you don't have python 2.5+ installed, hence the error, you need to download and install any variant of python in 2.5 series, I'm currently using 2.5.1 and the exporter works. You can run python 2.4 series and 2.5 series along side each other with no errors so no need to un-install the old...

----------

Toolset: Blender, GIMP, Indigo Render, LuxRender, TopMod, Knotplot, Ivy Gen, Plant Studio.


Silgrin ( ) posted Thu, 30 August 2007 at 7:41 AM

file_386616.JPG

Thx - it works; seems B 2.44 doesn`t see older Pythons at all - there should be any warning on the download page, like before. Still curious what caused older B`s to crash on a task they performed seamlessly before... Damn.

Now I have another kind of trouble... but should overcome this. Showing just for your fun:)


Gog ( ) posted Thu, 30 August 2007 at 7:52 AM

Lol, looks some strange data stream there!

----------

Toolset: Blender, GIMP, Indigo Render, LuxRender, TopMod, Knotplot, Ivy Gen, Plant Studio.


DramaKing ( ) posted Thu, 30 August 2007 at 10:32 AM

Try exporting to a different location.

It is better to do one thing well, than to do many things and excel at nothing.


Silgrin ( ) posted Fri, 31 August 2007 at 2:43 AM

file_386691.jpg

Heh... I`m afraid it`s caused by the object itself, rather than by the location. I always had problems with C4D->B->LW workflow when it came to non point-modeled geometry. I will just re-model this rather clumsy object in Blender and export it to LW. This will save both polycount and file work trouble:)

Thx for your advices. I havent expected the LW exporter to be a Python script:P ...Though I do have Python installed. Pity Blender page doesnt clearly point out it requires 2.51.


Gog ( ) posted Fri, 31 August 2007 at 3:29 AM

Yeah, there was a fair amount of discussion at a few forums about the need for 2.5 python install - with previous blender drops you could work with 99% functionality and the wrong python...

----------

Toolset: Blender, GIMP, Indigo Render, LuxRender, TopMod, Knotplot, Ivy Gen, Plant Studio.


Privacy Notice

This site uses cookies to deliver the best experience. Our own cookies make user accounts and other features possible. Third-party cookies are used to display relevant ads and to analyze how Renderosity is used. By using our site, you acknowledge that you have read and understood our Terms of Service, including our Cookie Policy and our Privacy Policy.