New LFexport (FINAL:Apr 4)

[eeshlo]

(Apr. 4-2003, final update,
http://www.elysiun.com/forum/viewtop...?p=85998#85998)
(Nov 11, update, various bugfixes)
(Nov 2, updated with extra render preset and a correction in install.blend)
(Nov 1, Updated everything, including the blendfile converter)
(Oct 31: Update for both Linux and windows, links changed below)
(Oct 24, temporary update for Linux)
(Oct 23 UPDATED)

Well, there it is then, far too late, after seven months of work...

For anyone who did not use any python script at all and want to try this script, once again I advice you to try any of the other exporters first like POVAnim or Blenderman, these are much easier to use than this script, POVRay also can be a lot faster than Lightflow.

It is rather big at 1.7Mb, and for me iptic is VERY slow (less than 2kb/s download), so I could not test the download myself without waiting for 30-45 minutes, so I hope for others downloading is faster than that.

PLEASE READ THE DOCUMENTATION, BEFORE RUNNING THE INSTALL.BLEND, READ THE GENERAL INFORMATION FIRST.

Windows:
http://mysite.iptic.com/eeshlo/LFexportGUI_W.zip

Linux:
http://mysite.iptic.com/eeshlo/LFexportGUI_L.tar.gz

For any other export writers who might be interested in the Blendfile import (alhtough probably not, I posted this more than a month ago without any response from anybody), here is the improved Blendfile to Python converter script with documentation:

http://mysite.iptic.com/eeshlo/BF2PY.zip

Of course, that would have been useful maybe a year ago, but now it is only a matter of time before all of that is standard in Blender...

[paradox]

Thank you eeshlo for your work. It is always good to see what new thing or script you come up with. I've found in the past your scripts are always worth the time to learn how to use because they add so much to the use of Blender (like HDRI, IBL, Toon shading, ect.) Please keep up the good work and know that you are appreciated.
Now a question for anyone who has used Virtualight and Lightflow. I'm using Virtualight now with pretty good results and was wondering how the two programs compare, speed, quality etc. Thanks
Paradox

[ray_theway]

WOOOOOW. . This looks great. The major deterrent I had at first to LF was that it didn't have a GUI for export, but now I have no excuse to try out LF. The only problem, though, comes with the render. I get this in the console:

Traceback (most recent call last):
  File "LFRENDER_GUI.py", line 6159, in rd_bevent
    def rd_bevent(evt):
  File "LFRENDER_GUI.py", line 6066, in StartLightflow
    def StartLightflow(wait=0):
OSError: [Errno 2] No such file or directory

Then the script crashes.
Also, when I first start the script, I get this in the shell:

Could not import Blendfile reader

Could this be a problem?
Thank you so incredibly much eeshlo. When I saw that there was an error in the 6000th line, that means there were at least 5999 lines of good code .

[eeshlo]

Originally Posted by ray_theway This looks great. Then the script crashes.

Well, that's good news... Didn't you get any errors when running the install blendfile?

Also, when I first start the script, I get this in the shell: Could not import Blendfile reader Could this be a problem?

Well, again, this should be handled by the install script, try to run it again, and tell me what errors you get. The blender directory as reported by the script is correct?
I guess it is, otherwise you would have answered 'No' to stop the script since it asks you if it is correct. Or did you just load the script directly into Blender? You really should try to at least read the GeneralInfo.html page, I know, nobody reads (or wants to read) documentation, but sometimes it is really necessary unfortunately...
I'm not accusing you that you didn't read it of course, I just can imagine that some people won't.

[ray_theway]

I did read through all the docs at least once (except the MATSpiderLF notes - I'm not that far along yet). I ran the install script from the blend included in the installation directory. It correctly detected my blender directory. However, it did not copy the BFREAD.py file to the blender directory. When I did this manually, the Blender file reader error went away. However, now I get this error at the time of rendering:

Traceback <...>:
  File "D:\Blender\LFExport\caustics\caustics_0001.py", line 1, in ?
    from lightflowPM import *
ImportError: Module use of python15.dll conflicts with this version of Python.

The script does not crash, but the rendering fails nonetheless.

[Kikko]

Hey Eeslho... thanks for announcement !!!

Good Job!!!

(now i'm testin'YAFRAY)
regards Kikko

[mad3d]

eeshlo for PRESIDENT!
thank u eeshlo...

[jms]

Originally Posted by eeshlo ... For any other export writers who might be interested in the Blendfile import (alhtough probably not, I posted this more than a month ago without any response from anybody), here is the improved Blendfile to Python converter script with documentation: http://mysite.iptic.com/eeshlo/BF2PY.zip Of course, that would have been useful maybe a year ago, but now it is only a matter of time before all of that is standard in Blender...

Sorry, very busy a month ago (beginning of "french year school") and I didn't really understand the interest of this work.

[wiensta]

finally ,

thanks for all your hard work!!

now to try it...

[mad3d]

after i clicked on Render now i get this error :x :x in the dos wind. (under xp)

traceback <most recent call last>:
File "C:\BlenderPublisher\LFRENDER_GUI.py", line 6159, in rd_bevent
def rd_bevent<evt>
File "C:\BlenderPublisher\LFRENDER_GUI.py", line 6066, in StartLightflow
def StartlightFlow<wait=0>:
OSError: [Errno 2] No such file or directory

tha

[kino]

Hi eeshlo

under linux (suse 7.3 too) it fail to find the TOdir path

Install script for LFRENDER_GUI
Copying files...

Files will be copied to: 
This should be the Blender directory.
Is this OK?
Enter Y(es) or N(o), don't forget the enter key! ->

with 2.23 and 2.25 publisher , python 2.1

ther's a env var for blender executable?

can i change the TOdir to fit my need without problem

thank's

kino

[eeshlo]

Ok, last first...

Originally Posted by Kino under linux (suse 7.3 too) it fail to find the TOdir path Install script for LFRENDER_GUI Copying files... Files will be copied to: This should be the Blender directory. Is this OK? Enter Y(es) or N(o), don't forget the enter key! -> with 2.23 and 2.25 publisher , python 2.1 ther's a env var for blender executable? can i change the TOdir to fit my need without problem

This is correct, this is like '.' from './' which means it is the current directory, which should be (if you started from a terminal) the blender directory, it works for me anyway. But if you want to change it, go right ahead. There is no environment variable for Blender, but it is possible to get the path to the running python interpreter with the sys.executable function, that is used in the script.

Originally Posted by mad3d after i clicked on Render now i get this error in the dos wind. (under xp) traceback <most recent call last>: File "C:\BlenderPublisher\LFRENDER_GUI.py", line 6159, in rd_bevent def rd_bevent<evt> File "C:\BlenderPublisher\LFRENDER_GUI.py", line 6066, in StartLightflow def StartlightFlow<wait=0>: OSError: [Errno 2] No such file or directory

Like for ray_theway, I suppose there might be something going wrong with both the BFREAD.py & lightflowPM.py module. What should happen is that both should be copied to the Python lib dir, not the blender directory.
Look at the output of the install script, it might be installing it somewhere else.

Originally Posted by jms Sorry, very busy a month ago (beginning of "french year school") and I didn't really understand the interest of this work.

Well, this wasn't directed to you really, and of course it is not necessary to get any response, I just though it might have been useful at the time. Now it really isn't useful anymore.

Originally Posted by Kikko (now i'm testin'YAFRAY)

Well, after all the bugfixes for this, I will start working on YafRay again, I haven't heard from Jandro for some time, development seems to have stopped, but he told me he would have other things to do at some point, so I suppose he doesn't have much time any more.

Originally Posted by ray_theway However, it did not copy the BFREAD.py file to the blender directory. When I did this manually, the Blender file reader error went away. However, now I get this error at the time of rendering: Code: Traceback <...>: File "D:\Blender\LFExport\caustics\caustics_0001.py ", line 1, in ? from lightflowPM import * ImportError: Module use of python15.dll conflicts with this version of Python. The script does not crash, but the rendering fails nonetheless.

That is one of the things that might have been hidden a bit in the LFPROBLEMS.txt, the lightflow python module is now emulated with a python script, which will clash with the REAL lightflowPM.dll if you did not delete that from the python1.5 dll directory. In any case, like I said in the docs, if you only installed python1.5 for Lightflow, you can just uninstall it, since it is not used anymore, if you don't want to do that, then at least remove the lightflowPM.dll from the python1.5 dll directory.
For linux this file is renamed.
Also, like I said above, the BFREAD.py should not be copied to the blender directory but the python lib directory instead, this should be handled by the install script.
Where does the script say it is copying the BFREAD.py and lightflowPM.py modules to?
The LFArender utility should end up in the main Lightflow directory.

Originally Posted by paradox I'm using Virtualight now with pretty good results and was wondering how the two programs compare, speed, quality etc.

Well, there are quite a few people who consider Lightflow dead and buried long ago, so I suppose you should just keep using VirtuaLight. I think dotblend might tell you VL is far superior to LF and at least it is actively developed.

[Kikko]

Originally Posted by eeshlo Originally Posted by Kikko (now i'm testin'YAFRAY) Well, after all the bugfixes for this, I will start working on YafRay again, I haven't heard from Jandro for some time, development seems to have stopped, but he told me he would have other things to do at some point, so I suppose he doesn't have much time any more.

Ok.. Jandro has already sent me yours exporter for yafray, and it seems run well to part the fact that the camera finds in one various position that is in Blender :-?
I have asked Jandro:
K> Do u think to create a material editor as in eeshlo newscript for Lightflow or
K> in calypso?

J> That is a good idea. But now I cannot do that, I have no time. Maybe
J> someone could do it. I'll ask
----------
PS... I had the same problem of Kino for newest LFexporter (ciao Kino)

[wiensta]

hmm

its still using the lightflowPm modules for me.

it says its conflicting with my current version of python,
"Traceback (most recent call last):
File "E:\Library\untitled\untitled_0002.py", line 1, in ?
from lightflowPM import *
ImportError: Module use of python15.dll conflicts with this version of Python."


then when i delete the modules, it says

"Traceback (most recent call last):
File "E:\Library\untitled\untitled_0002.py", line 1, in ?
from lightflowPM import *
ImportError: No module named lightflowPM"

any ideas??

[eeshlo]

Originally Posted by wiensta its still using the lightflowPm modules for me. any ideas??

Yes, the script has a 'fake' lightflowPM module to render without python, like I said above, this lightflowPM.py module should be copied by the install script to the python lib directory of whatever python version you are running. Nobody has told me yet what the install script is doing exactly on their system, so I'm waiting for that before I can do something about it (IF I can do something about it), I need to know where it ends up, if it says it is copying to the python lib directory, check that it actually has copied the file.

Everything worked so well before, but this was all untested stuff (except by me), I suppose I should have sent it to the testers first, but that would have meant more delay.

Reading some comments here on elysiun and blender.org about Lightflow (even by Montz himself, the original script author) really makes me think I wasted seven months I could have better spent on something else (like Dynamica maybe). But I am a bit stubborn I guess, if I start something I want (or at least try) to finish it too.
But it is all S68's fault really, he send me the initial GUI which started it all...

[eeshlo]

I just updated the zipfile, I have corrected some mistakes in the docs. There was also a small script error that made the export fail if a WORLD_LIGHT was used with the texture set to 'None'. I had actually corrected that before, so it seems I have somehow overwritten the corrected file (which might have had more bugfixes) with another one... so all of that is lost.. I hope that was the only difference though...

Anyway, I also included the Blender Logo blendfile which I used to render the picture for the script documentation, it might be useful as an example maybe.

[kino]

sorry to bother again but i have the same error

i have changed line 53

TOdir = "/my/blenderbindir"

and line 155

LFE_DOCS to Lfe_docs

and the install work


but when i exec

LFRENDER_GUI.py", line 89, in ?
from select import select
ImportError: No module named select

all the path and env var are correct

Kino

[eeshlo]

Originally Posted by Kino sorry to bother again but i have the same error i have changed line 53 TOdir = "/my/blenderbindir" and line 155 LFE_DOCS to Lfe_docs and the install work but when i exec LFRENDER_GUI.py", line 89, in ? from select import select ImportError: No module named select all the path and env var are correct Kino

First, I really think it was not necessary to change the script at all, like I said "." is not an error, it is the current directory which is the Blender directory when started from a terminal.

Anyway, the script uses a number of 'exotic' python modules which are not always installed by default, not in Linux anyway. The array module is another one that is used which I could not import at first without re-compiling and installing python. As this was bound to happen for others too I created a work around for that in the script so that it would use an alternative method if it can't import that module. You probably also get a message like 'Fast display, no array' or 'Slow display, no array'.

I forgot about the select module though, it is used to detect keypresses in the terminal. I can't think of any other way to do it really. But I'll see if I can create another workaround like for the array module somehow...

[kino]

Originally Posted by eeshlo First, I really think it was not necessary to change the script at all, like I said "." is not an error, it is the current directory which is the Blender directory when started from a terminal.

sorry we (me and kikko) have every time the same error
if i write

import Blender
import sys, os
print os.path.split(sys.executable)[0]

in the terminal it print nothing not . or ./

ok 4 the rest no prob just want to try your script
after reading the doc about bug and problems
i prefer to concetrate to other renderer
any news from jandro

thk's

Kino

[jms]

Originally Posted by eeshlo Originally Posted by wiensta its still using the lightflowPm modules for me. any ideas?? Yes, the script has a 'fake' lightflowPM module to render without python, like I said above, this lightflowPM.py module should be copied by the install script to the python lib directory of whatever python version you are running. Nobody has told me yet what the install script is doing exactly on their system,...

On my system, win98, the install script fails after the copy of the pyds.

The paths:
SET PYTHONPATH=F:\PROGRAMSFILES\PYTHON;F:\PROGRAMSFILE S\PYTHON\DLLs;F:\PROGRAMSFILES\PYTHON\LIB;F:\PROGR AMSFILES\PYTHON\lib\LIB-tk

"F:\PROGRAMSFILES\PYTHON" becomes "F:\P"