LuXSI

[miga]

sure!

Just found out how lightgroups work






At the moment every light is a own group



But I will use the Softimage internal groups to make real luxrender groups!


Is that normal?:

it's the same scene but left one has no lightgroups (so just "default") and the right scene has one (the sunlight 'XSI_Physical_Sun' + 'default')

[ignore the bad image quality, this is just to show the lightgroups]

[Radiance]

nice

it's a small bug in RC1, just disable the 'premultiplyalpha' in the film parameters.

Radiance

[miga]

Edit:
Got the Lightgroup definition the wrong way. The sun is now shining in

[Zikco]

Hello, new guy here.
Might as well say hello here & get straight to buisness .

I stumbled upon this renderer on my quest for an alternative to Mental Ray in XSI (7.01), and was eager to dip my toes.
But, I found out the hard way that the current version of LuXSI is 32bit only.
I'm running the 64bit version of XSI and therefore can not get the thing installed, much less running...

So; my question: Will there be a 64bit version of LuXSI released in the near future?

[miga]

Hi,
yes there will be. I'll try to get access to a 64bit system this week to compile the latest LuXSI version for 64bit. As soon as I have it I'll let you know!

[Zikco]

That sounds Great!
I can hardly wait.
In the meantime, I'm gonna try to set something up for my first Lux (test) render...

Thank you!

[miga]

Try this one please: LuXSI 64bit test

[Zikco]

Hi.

I've tried it. It was a bit iffy when I installed it, wouldn't stick, until I stuck it into my 'user\application\plugin\' folder manually and loaded it from there.
It exports most all without problems (objects w/subdivision (the '+/-' kind), camera and shaders. Haven't tried lights yet (next on the list)...), except I think it forgets to put backslashes in paths, at least the path to the HDRI file (.exr format, of course). The log displayed the path without slashes and said it couldn't find it.

Could you check it out, please?

I'll let you know if I snag on something else...

EDIT: I just noticed that it doesn't put backslashes in saved image output paths either!
I'm attaching the log from Lux.
Hmm... the forum won't let me attach .txt files...
Nevermind, I'll just paste it in here, then. Prepare for Wall of Text :

[log start]
2009-Jul-15 19:42:45 Error: (3) Unable to open image file 'D:3D stuffHDRIExrennis.exr'
2009-Jul-15 19:42:45 Warning: (24) Missing end to luxAttributeBegin()
2009-Jul-15 19:42:45 Warning: (0) Parameter 'write_tonemapped_exr' not used
2009-Jul-15 19:42:45 Warning: (0) Parameter 'write_untonemapped_exr' not used
2009-Jul-15 19:42:45 Warning: (0) Parameter 'write_tonemapped_tga' not used
2009-Jul-15 19:42:45 Warning: (0) Parameter 'write_tonemapped_igi' not used
2009-Jul-15 19:42:45 Warning: (0) Parameter 'write_untonemapped_igi' not used
2009-Jul-15 19:42:45 Warning: (0) Parameter 'maxdepth' not used
2009-Jul-15 19:42:45 Info: (0) Applying 4 levels of loop subdivision to 96 triangles
2009-Jul-15 19:42:45 Info: (0) Subdivision complete, got 24576 triangles
2009-Jul-15 19:42:45 Debug: (0) Mesh: accel = none (global), triangles = 24576 wald, quads= 0 quadrilateral
2009-Jul-15 19:42:45 Info: (0) Applying 4 levels of loop subdivision to 384 triangles
2009-Jul-15 19:42:45 Info: (0) Subdivision complete, got 98304 triangles
2009-Jul-15 19:42:45 Debug: (0) Mesh: accel = none (global), triangles = 98304 wald, quads= 0 quadrilateral
2009-Jul-15 19:42:45 Info: (0) Applying 4 levels of loop subdivision to 384 triangles
2009-Jul-15 19:42:45 Info: (0) Subdivision complete, got 98304 triangles
2009-Jul-15 19:42:45 Debug: (0) Mesh: accel = none (global), triangles = 98304 wald, quads= 0 quadrilateral
2009-Jul-15 19:42:45 Info: (0) Applying 4 levels of loop subdivision to 384 triangles
2009-Jul-15 19:42:45 Info: (0) Subdivision complete, got 98304 triangles
2009-Jul-15 19:42:46 Debug: (0) Mesh: accel = none (global), triangles = 98304 wald, quads= 0 quadrilateral
2009-Jul-15 19:42:46 Debug: (0) Mesh: accel = none (global), triangles = 128 wald, quads= 0 quadrilateral
2009-Jul-15 19:42:46 Info: (0) Applying 4 levels of loop subdivision to 384 triangles
2009-Jul-15 19:42:46 Info: (0) Subdivision complete, got 98304 triangles
2009-Jul-15 19:42:46 Debug: (0) Mesh: accel = none (global), triangles = 98304 wald, quads= 0 quadrilateral
2009-Jul-15 19:42:46 Info: (0) Applying 4 levels of loop subdivision to 96 triangles
2009-Jul-15 19:42:46 Info: (0) Subdivision complete, got 24576 triangles
2009-Jul-15 19:42:46 Debug: (0) Mesh: accel = none (global), triangles = 24576 wald, quads= 0 quadrilateral
2009-Jul-15 19:42:46 Info: (0) Applying 4 levels of loop subdivision to 96 triangles
2009-Jul-15 19:42:46 Info: (0) Subdivision complete, got 24576 triangles
2009-Jul-15 19:42:46 Debug: (0) Mesh: accel = none (global), triangles = 24576 wald, quads= 0 quadrilateral
2009-Jul-15 19:42:46 Debug: (0) Building KDTree, primitives: 467072
2009-Jul-15 19:42:56 Info: (0) Preprocess thread uses seed: 40
2009-Jul-15 19:42:56 Info: (0) Thread 0 uses seed: 41
2009-Jul-15 19:42:57 Info: (0) Thread 1 uses seed: 42
2009-Jul-15 19:42:57 Info: (0) Thread 2 uses seed: 43
2009-Jul-15 19:42:57 Info: (0) Thread 3 uses seed: 44
2009-Jul-15 19:42:57 Info: (0) GUI: Updating framebuffer...
(repeat that 12 times...)
2009-Jul-15 19:44:41 Info: (0) GUI: Updating framebuffer...
2009-Jul-15 19:44:46 Info: (0) Writing Tonemapped PNG image to file C:UsersZikcoDocumentsMy ArtLuxDoing.png
2009-Jul-15 19:44:49 Info: (0) GUI: Updating framebuffer...
(repeat that some more...)
2009-Jul-15 19:45:37 Info: (0) GUI: Updating framebuffer...
[end of log]

[miga]

will check the paths! Nice to see that you got it working. Just implementing the "run luxrender from luxsi" function in windows.
Got some problems with the UVs at the moment. Have to digg into that again.

[Zikco]

I did some digging in the .lxs file, and noticed that all the filepaths had one backslash.
I tried putting double backslashes instead and Voilá! it works!

So, bottom line; the exporter is only putting single backslashes in file paths, when there should be double.
Shouldn't take long to fix .

Until then, I'll just have to remember to edit the .lxs file by hand, as a workaround.