Slap me with a trout and call me stupid!!

(BgDM) #1

OK. I have a very basic question. How the hell do I run my Lightflow .py file from the Command Line?

I have looked through the python literature, etc. with no help, (I probably saw it, but I just didn’t understand what I was looking at cause I am no coder/programmer). Can someone just give me the line to do this, please!!

Thanks for your continued support of my stupidity :stuck_out_tongue:


(gowen) #2

Assuming your blender file eas called “test” try:

cd c:\LFExport est

provided the python 1.5.2 directory is in your path.

If windows explorer shows the .py file with a snake icon next to it, try double clicking the filename.

(BgDM) #3

Thank you!


(eeshlo) #4

If you can wait a few days (a week at most), I’m almost done with the new LF script, I only need the Blender source code to check the texture mixing code, after that is corrected I will release it. You won’t need python1.5 any longer, you can use material/textures as normal, MATSpider materials can be directly imported, you can export metaballs & nurbs/surfaces without converting to mesh, and render directly from blender with the image displayed while rendering, etc…
Of course all of this doesn’t work perfectly all the time (Lightflow is not a Blender emulator), but it might be worth waiting instead of trying to use the old script.

(Bapsis) #5

Bapsis slaps BgDM with a trout…“Stupid!!!”

Does that help you any? :wink:


Blend on, and blend well!!!

(BgDM) #6

That is the answer I have been waiting for!!! Thank you. Now duck!!!

/me slaps Bapsis back with a bigger and wetter trout! :wink:


(Bapsis) #7

Shouldn’t have told me to duck, 'cuz you missed!!! :wink:

Why dont we just call this one a draw, peace brother!!!

Let’z toss these trout on the bbq and show the rest of the trout slappin’ community what they are really supposed to be used for…no, not that, sheesh, i ment the bbq thing. :wink:

Anywayz, goona quit before this gets stupid hehe :wink:


Blend on, and blend well!!!

(Jamesk) #8

eeshlo: That sounds very crispy indeed! When you’re done with lightflow, why not give VirtuaLight a good spanking? That script could use some eeshlo magic as well…

:smiley: :smiley: :smiley: :smiley: :smiley: :smiley: :smiley: :smiley: :smiley: :smiley: :smiley: :smiley:

(eeshlo) #9

Just to put everything in perspective again: Lightflow WILL crash at random, anytime you change a material setting you will HAVE to save, some will still find it IMPOSSIBLE to get the whole thing to work at all, ‘Cube’ mapping has no Lightflow equivalent, ‘Tube’ mapping (‘cylinder’ in LF) doesn’t work in Lightflow (LF bug), etc… so it still has it’s limits that might reduce the whole thing to a bit of a useless toy to some, it really is not that great at all.

As for VirtuaLight, this was asked by dotblend as well, and what I said was that I don’t modify/change/rewrite other people’s scripts without permission, and I think with all the rapid changes that might occur soon, it probably is better to wait for things to get a bit more stable anyway. I also still have quite some work to do for YafRay, Jandro’s raytracer. And besides that, this took almost seven months to complete, of course all the Lightflow bugs and the blender python API limits did a lot to slow things down.