I'm getting this error when I run the script:

Traceback (most recent call last):
  File "D:e frontierPoser 7RuntimePythonposerscriptsPoserLuxExporter.py", line 219, in ?
    ExportFilm(globalParameters).write(f)
  File "D:e frontierPoser 7RuntimePythonposerscriptsworkersPoserLuxExporter_workers.py", line 570, in write
    if pFilm.hybrid.strip() == "true":
AttributeError: 'NoneType' object has no attribute 'strip'

Laurie

Ups! This future-thing.

The parameter is not found in "dataOut.bbml".

The parameter is ignored now. Please re-download.
 

I fixed it by hand, but I thought it was worth mentioning again...lol.

Thanks adp. You're awesome ;o).

Laurie

"color Ks" [0.4 0.25 0.25]
"bool multibounce" ["true"]

"float d" [.5]

"float index" [.3]

unbiased engines are intended for photo realistic simulation of Light
Toon renders should be done in other biased special effects renderers.

Cheers

Quickie dumb question (I'm due for one...lol):

Firstly, I'm not having much luck getting HDR images to show up in Luxrender with the newest LuxPose build, even though the .lxl file is linking to it.

Secondly - I've made some really nice skies in Vue and Bryce. Is there any way we can, say, use a .bmp image for the sky rather than an .hdr? Inquiring minds wanna know ;o).

Laurie

Quote - Quickie dumb question (I'm due for one...lol):

Firstly, I'm not having much luck getting HDR images to show up in Luxrender with the newest LuxPose build, even though the .lxl file is linking to it.

Just to make sure it works: Can you please use an HDRI delivered with Poser?
Maybe the images you whant to use aren't the right format.

Quote -
Secondly - I've made some really nice skies in Vue and Bryce. Is there any way we can, say, use a .bmp image for the sky rather than an .hdr? Inquiring minds wanna know ;o).

Yes, you can use LDRI also (Low-Dynamic-Range-Images). But probably you have to use additional light in your scene, because a LDR image commonly has not enough "energy" for good contrast.

Quote - > Quote - Quickie dumb question (I'm due for one...lol):

Firstly, I'm not having much luck getting HDR images to show up in Luxrender with the newest LuxPose build, even though the .lxl file is linking to it.

Just to make sure it works: Can you please use an HDRI delivered with Poser?
Maybe the images you whant to use aren't the right format.

Quote -
Secondly - I've made some really nice skies in Vue and Bryce. Is there any way we can, say, use a .bmp image for the sky rather than an .hdr? Inquiring minds wanna know ;o).

Yes, you can use LDRI also (Low-Dynamic-Range-Images). But probably you have to use additional light in your scene, because a LDR image commonly has not enough "energy" for good contrast.

I did use an HDRI from Poser adp...sorry, I forgot to mention that.... I used the Pond scene. While the .lxl file was linking to it, it didn't render in Luxrender. All I got was a blueish sky. I'm not sure what I'm doing wrong...hehe.

Laurie

In the material code examples I see color values higher than 0.8. Doesn't this break an important LuxRender-rule?

Quote - In the material code examples I see color values higher than 0.8. Doesn't this break an important LuxRender-rule?

I haven't had any problems with any I've made....

Laurie

Which version of Vue do you have Laurie ? I'm pretty sure that at least infinite can export as a .hdr image if you turn off all the post processing options

Quote -
I did use an HDRI from Poser adp...sorry, I forgot to mention that.... I used the Pond scene. While the .lxl file was linking to it, it didn't render in Luxrender. All I got was a blueish sky. I'm not sure what I'm doing wrong...hehe.

Laurie

Please look into the *.lxs file for "premultiplyalpha". Set this to "false" if it isn't. 

Make sure there is no other light like sun or sky in your *.lxl file.

Quote - Which version of Vue do you have Laurie ? I'm pretty sure that at least infinite can export as a .hdr image if you turn off all the post processing options

I have lowly version 4....lol. Well, that and Vue 8 Pioneer - the free one. I haven't looked at Pioneer for options yet as I think it puts a watermark or logo or something on the resulting image, which is something I don't want ;o).

Laurie

Quote - Please look into the *.lxs file for "premultiplyalpha". Set this to "false" if it isn't. 

Make sure there is no other light like sun or sky in your *.lxl file.

Will do adp :o). Thanks. I'll let ya know.

Laurie

Ok, there was a typo with premultiplyalpha.  This parameter must be set correctly to true to make environment light work.

Re-download for a corrected version,

Quote - Seems my problem was the metal bars behind her kept throwing all sorts of light sparkles everywhere. After the 3 and a half hours I decided I could post out some of the sparkles and call this one done.

I think you should lower the intensity of this bars. Setting the reflection values to high produces too mutch energy and therefore new lightrays. Even chrome does not 100% reflect.

Ahhh - don't forget to set the camera focus to nearly the same value as it was used to generate the environmental image. Mostly this is something between 18 to 24. 

I only have the one formula for silver, graciously given by LaurieA. I do not know how to change the values or what to change it to.

The silver metal is what it is...it's built into Luxrender.

Laurie

@LaurieA, yes, I sort of thought that it was a Lux preset.

######################

#----->   ball_1/Preview    <-----

MakeNamedMaterial "ball_1/Preview" "string type" ["metal"]

"string name" "amorphous carbon"

"float uroughness" [0.025]

"float vroughness" [0.025]

######################

#----->   ball_2/Preview    <-----

MakeNamedMaterial "ball_2/Preview" "string type" ["metal"]

"string name" "gold"

"float uroughness" [0.025]

"float vroughness" [0.025]

######################

#----->   ball_3/Preview    <-----

MakeNamedMaterial "ball_3/Preview" "string type" ["metal"]

"string name" "silver"

"float uroughness" [0.025]

"float vroughness" [0.025]

######################

#----->   ball_4/Preview    <-----

MakeNamedMaterial "ball_4/Preview" "string type" ["metal"]

"string name" "copper"

"float uroughness" [0.025]

"float vroughness" [0.025]

######################

#----->   ball_5/Preview    <-----

MakeNamedMaterial "ball_5/Preview" "string type" ["metal"]

"string name" "aluminium"

"float uroughness" [0.025]

"float vroughness" [0.025]

######################

#----->   ball_6/Preview    <-----

MakeNamedMaterial "ball_6/Preview" "string type" ["metal"]

"string name" "aluminium"

"float uroughness" [0.1]

"float vroughness" [0.1] 

######################

Don't forget to set Catmul-Clark subdivision to at least 1 for low-res props if you use glossy materials on them.

Copied to a Word document, thank you! Yeah, if only my computer would render something like that in Lux in 15 minutes.....

Hi all, apologies for being MIA for the last week or so, we've all been ill in Lucifer Towers & I can see I have some serious catching up to do. I'll be doing some major reading of this thread before I post anything else.

Strange thing ...

I tried something similar to adp's latest render with the different ball materials.
I loaded some balls into a poser scene and created a Diffuse IBL light.
In the MAT.Room I connected an Image_Map to the Color node of the Light. As image I used the Pond HDR file that came with Poser.

I then exported the scene with LuxPose 1.30a and got this Error Msg. in LuxRender:

• There was an error while checking the size of file 'H:ProgrammeSmith MicroPoser Pro 2010RuntimeTexturesHDRVFXHDRVFX_pond_01_v_002.hdr'

• Unable to open image file 'H:ProgrammeSmith MicroPoser Pro 2010RuntimeTexturesHDRVFXHDRVFX_pond_01_v_002.hdr'

Back in Poser I ran the "TextureReferences.py" and got this:

all texture references:
H:ProgrammeSmith MicroPoser Pro 2010RuntimeTexturesHDRVFXHDRVFX_pond_01_v_002.hdr
wrong references:
wrong after resolving tried:

As if the image just isn't there, even tho I can see being connected to the light in the Mat.Room.

Am I doing something wrong here?

I saw a similar error last night about the size of the hdr image. I just deleted my IBL light and re-exported figuring someone will fix the error soon.

Verify if the imagepath is correct. Can you reach this imagefile with your webserver/explorer?

I have this problem too with P7 sometimes if I use external drives or a serverpath. 

Quote - I saw a similar error last night about the size of the hdr image. I just deleted my IBL light and re-exported figuring someone will fix the error soon.

Seems we have 2 problems.

First, LuxRender has some problems after several re-loading of scene files. Just restart to fix it.

Second, Poser before 8 has it's own understaning of how to handle referenced imagefiles :)

The exporter does nothing more than asking Poser for a path/filename. No chance to work sometimes and sometimes not.

I keep all my V4 and M4 textures in a special runtime in my external drive. The current Luxpose versions have had no problem with this.  The HDRFX folder is within Poser 8 on my C drive, so the exporter not seeing the path to the hdr image should not have been a problem. I should have copied the error message and saved it, but it did have something to do with the size of the HDR image, not it's location. If it is in regards to the focal length of the hdr image and my Poser scene, well then I guess for the moment, I'm not using IBL on export because I render at no lower than 38mm for my camera in Poser. Anything below 38mm is too distorted. I also now use very low level IBL lights with no attached image in Poser, and I don't believe that is supported at the moment on the Luxpose exporter.

BTW, added those metals to the Wiki page.

Hey Liz, I took our names off the built-in Luxrender metals you posted on the wiki since they are built into Luxrender and not something we really came up with a recipe for ;o).

Laurie

i've had that idl-path problem too (same hdr & same size error message) & changing the backslashes to double-backslashes usually fixes it so lux can find the hdr.  don't have to do that for normal textures, so i don't know what's going on or why that works.

@LaurieA
Cool! Just glad that I figured out how to add to the wiki so other people that aren't diligently following the thread can quickly find these things.

@jancory
Oh, changing them to double slashes will work? Interesting.

You know, I always knew there'd be a reason I kept most of my Poser 4 runtime intact. I'm setting up a scene now with a DM Productions scene and converted some lovely armor by Lory to use. Will see how this turns out. At the moment, Luxpose likes P4 style textures, then I go into the material file and edit in other things like metals that have been posted. I'm going to try the gold posted by ADP.

Quote - I should have copied the error message and saved it, but it did have something to do with the size of the HDR image, not it's location.

LuxRender checks if a file exists while checking the filesize. So the message you got mens: File not found.

Quote - Hey Liz, I took our names off the built-in Luxrender metals you posted on the wiki since they are built into Luxrender and not something we really came up with a recipe for ;o).

Laurie

Yes, I think it makes no sense to duplicate the LuxRender Wiki :)

Quote - i've had that idl-path problem too (same hdr & same size error message) & changing the backslashes to double-backslashes usually fixes it so lux can find the hdr.  don't have to do that for normal textures, so i don't know what's going on or why that works.

That's interesting. Did you try to replace the (single) backslashes with (single) slashes? I'm using LuxRender with Linux, so I can't test it by myself.

I wish the exporter kept the set intensities of the Lights from Poser. When I get a scene into Lux, I have to turn the light groups down.

Quote - I wish the exporter kept the set intensities of the Lights from Poser. When I get a scene into Lux, I have to turn the light groups down.

You can (have to) set "Sensivity", "Exposure" and "FStop" to values a real camera would need for your scene. If you found a set you need for your typical image, you may set your values as the default ones (dataOut.bbml).

No need to push lightgroups down except to finetune.

Note: Lux handles light different than Poser. Exporting light 1:1 is not easy - and probably not what you want. If you're after a Poser-look, render with Poser.

single forward slash worked; just checked it. 

Can someone test please if  LuxRender for Windows and/or Mac understands slashes insteed of backslashes in (texture/material) filenames? If yes, I can change this in the Exporter for all filenames used.

i just ran a quick test on an antonia & the textures all loaded ok in lux with single slashes.  i'm  running Windows XP. 

I made a version with double-backslashes for environment-images.

Version 1.30b

Quote - i just ran a quick test on an antonia & the textures all loaded ok in lux with single slashes.  i'm  running Windows XP. 

That's good news and may help to exchange materials more easily.
I'm sure Mac understand this as well.

 Ran into a problem in Poser 6:

Traceback (most recent call last):

  File "", line 203, in ?

  File "C:Program FilesPoserLuxExporter_alpha_1-30cworkersPoserLuxExporter_workers.py", line 62, in ?

    from BBLuxMat import MatConverter, clearCache

  File "C:Program FilesPoserLuxExporter_alpha_1-30cworkersBBLuxMat.py", line 61, in ?

    reload(luxmatic.matcore)

AttributeError: 'module' object has no attribute 'matcore

Seems to work perfectly fine in Poser 7 though.

On a side note someone added a shadow/reflection catcher to LuxRender. The code is not merged to the main branch yet though.

background picture

IBL + shadow-catcher plane aligned with table

Rendered on a lowly AMD Turion 64 1.8Ghz CPU with 1.406GB of available memory WinXP 32 bit laptop with 256 S/px after 6 hours and 40 minutes.

I just tried jancory's tip, of using double-backslashes.
With this, it works for me, too.

Before I had an error msg in LuxRender, saying:

• There was an error while checking the size of file 'H:ProgrammeSmith MicroPoser Pro 2010RuntimeTexturesHDRVFXHDRVFX_pond_01_v_002.hdr'

• Unable to open image file 'H:ProgrammeSmith MicroPoser Pro 2010RuntimeTexturesHDRVFXHDRVFX_pond_01_v_002.hdr'

After altering the path, in the *.lxl file, from: ["H:ProgrammeSmith MicroPoser Pro 2010RuntimeTexturesHDRVFXHDRVFX_pond_01_v_002.hdr"] to ["H:ProgrammeSmith MicroPoser Pro 2010RuntimeTexturesHDRVFXHDRVFX_pond_01_v_002.hdr"] I get the following msg. in LuxRenders log:
"Loading FreeImage Texture: 'H:ProgrammeSmith MicroPoser Pro 2010RuntimeTexturesHDRVFXHDRVFX_pond_01_v_002.hdr'"

And all is working perfectly.

Sometihng "steals" a backslash, during the export =)

Updated Version 1.30d

Pathes now all changed to forward slashes. 

To make CC-subdivision more useful, I added seperate scripts to the utility folder:

addParameters2CurrentActor.py

    Adds parameter dials to the currently selected prop.

addParameters2AllActors.py

    Adds parameter dials to all props in a scene.

Additionally there is a script to delete the parameters: deleteParametersFromAllActors.py

Important note: This parameters are only used if the subdivision-level in dataOut.bblm is set to 0.

 So... I am kind of lost... What is the Subdivision for? I know what it is, just not sure what it is being used for in this situation.