The ivy leaves in my above pic all have trans as the leaves are mapped to a flat plane. So I would think transmapped hair would have no problem :o).

Laurie

Now I am almost positive I read in this thread, how to change the Image size, but I am not able to locate that post.

Quote - Same error here with one of my self-made geometries.
Can be downloaded from freebies here, name is "HiTec Trike"

http://www.renderosity.com/mod/freestuff/index.php?user_id=133972

As I thought, there were some corrupted texture polygons (not the same size as the corresponding 'regular' polygons) in that mesh. My code does now test for that and, if it's the case, drops all UV coordinates for that particular material. We'll have to see how often that kind of thing happens, and whether it's in the mesh or in Poser. I'll try to come up with a less drastic solution later.

The new code is in now on http://github.com/odf/pydough, as usual.

open the LXS file in notepad. look for

"integer xresolution" [1024]
 "integer yresolution" [768]

change as required. (eg mine are set to 1024/768 there)

Quote - open the LXS file in notepad. look for

"integer xresolution" [1024]
 "integer yresolution" [768]

change as required. (eg mine are set to 1024/768 there)

THANK YOU! :)

Quote - > Quote - Same error here with one of my self-made geometries.

Can be downloaded from freebies here, name is "HiTec Trike"

http://www.renderosity.com/mod/freestuff/index.php?user_id=133972

As I thought, there were some corrupted texture polygons (not the same size as the corresponding 'regular' polygons) in that mesh. My code does now test for that and, if it's the case, drops all UV coordinates for that particular material. We'll have to see how often that kind of thing happens, and whether it's in the mesh or in Poser. I'll try to come up with a less drastic solution later.

The new code is in now on http://github.com/odf/pydough, as usual.

I think it's in the mesh. All well done meshes do not have problems :)

My geoms are created with C4D, Catmul-Clark subdivided and exported with Riptide. The UV-part is just the "automatic" C4D/Bodypaint is able to do. May be I changed something on the geometry after UV-mapping. Don't remember exactly but I remember there where some problems in Poser I had to deal with. If it helps: I should still have the original C4D model somewhere on my backups. I'll seach for it and send you a copy if this helps.

new SmallLuxGPU video . in the name of god.

www.blendernation.com/smallluxgpu-interactive-demo-with-blender-2-5-videos-tutorials/

Quote -

new SmallLuxGPU video ......

www.blendernation.com/smallluxgpu-interactive-demo-with-blender-2-5-videos-tutorials/

Wow A new Era begins

So I hacked my LuxPose export .lxo and grabbed the sun and sunsky info from the example lux file included with the Luxrender install, replaced that for the light from Poser and WOW!! SOOOOO much more realistic ;o). If we could only get Lux to recognize an infinite light as a Lux "sun" and the background as "sunsky"...this would be awesome ;o).

On the downside...it's slower to render, but for the improved realism I'll wait the extra time...lol.

Laurie

i think its sloveer because of the lux sky.

i think its better to use bagginsbill ENV sphere for the sky lighting.

Quote - i think its sloveer because of the lux sky.

i think its better to use bagginsbill ENV sphere for the sky lighting.

I tried using that, but alas for now, it doesn't work ;o). Maybe soon. Then I'll be using it. But I'd still like to use Lux's sun, which has just a little more something-something ;o). I can hack the files for that, no big deal. Nice thing too is that the xyz coordinates are right there next to it so you can change it's orientation if you want to.

I will post my image as soon as it's done enough to look half-decent ;o).

Laurie

Wow!!!  I cannot wait to see this once it has been developed into a further stage for beta testing, and actual release.  There renders are amazing.- Starkdog

Quote - > Quote - i think its sloveer because of the lux sky.

i think its better to use bagginsbill ENV sphere for the sky lighting.

I tried using that, but alas for now, it doesn't work ;o). Maybe soon. Then I'll be using it. But I'd still like to use Lux's sun, which has just a little more something-something ;o). I can hack the files for that, no big deal. Nice thing too is that the xyz coordinates are right there next to it so you can change it's orientation if you want to.

I will post my image as soon as it's done enough to look half-decent ;o).

Laurie

Poser sun was never ''unrealistic''. so i dont think that the Lx sun is mroe realistic.

Traceback (most recent call last):
  File "C:SmithmicroPoser 8RuntimePythonposerScriptsPoserLuxExporter_alpha_1-10bPoserLuxExporter.py", line 163, in ?
    ExportScene(scene, globalParameters).write(f)
  File "C:SmithmicroPoser 8RuntimePythonposerScriptsPoserLuxExporter_alpha_1-10bworkersPoserLuxExporter_workers.py", line 325, in write
    ExportFigure(fig, self.globalParameters).write(file)
  File "C:SmithmicroPoser 8RuntimePythonposerScriptsPoserLuxExporter_alpha_1-10bworkersPoserLuxExporter_workers.py", line 107, in write
    params).write(file)
  File "C:SmithmicroPoser 8RuntimePythonposerScriptsPoserLuxExporter_alpha_1-10bpydoughgeometry_export.py", line 351, in write
    Subgeometry(self, indices).write(file)
  File "C:SmithmicroPoser 8RuntimePythonposerScriptsPoserLuxExporter_alpha_1-10bpydoughgeometry_export.py", line 103, in write
    self.fix_texture_seams()
  File "C:SmithmicroPoser 8RuntimePythonposerScriptsPoserLuxExporter_alpha_1-10bpydoughgeometry_export.py", line 48, in fix_texture_seams
    tverts = [tpolygons[i][j] for i,j in corners_for_v]
IndexError: list index out of range

Following what the Getting_Started said, I deleted some objects from the scene. This time it ran with No problems.

Ah, but the Poser sun IS quite unrealistic...we're just all used to it...lol. Even in Lux (if you look at that pic of the ivy covered trees I posted) I was still getting hard, overdark shadows, even though the lighting overall was better. Just wait until you see this new one. It's still cooking, but when it's done, I'll post :o).

Laurie

Quote - > Quote - > Quote - i think its sloveer because of the lux sky.

i think its better to use bagginsbill ENV sphere for the sky lighting.

I tried using that, but alas for now, it doesn't work ;o). Maybe soon. Then I'll be using it. But I'd still like to use Lux's sun, which has just a little more something-something ;o). I can hack the files for that, no big deal. Nice thing too is that the xyz coordinates are right there next to it so you can change it's orientation if you want to.

I will post my image as soon as it's done enough to look half-decent ;o).

Laurie

Poser sun was never ''unrealistic''. so i dont think that the Lx sun is mroe realistic.

Really nice to see all those Lux rendered pictures :)

New version to download (see footer).

  Bugfix from odf regarding the geometry exporter.
  Corrected light intensity. Please report if this is good for you.

Folder utilities contains some helper scripts. "NormalizePoserLigts.py" tries to lower all Poser lights to not more than 100% intensity (or any other value; look into the script). Try it and decide if you like to use it. P7/P8 users may "undo" changes made by the script.
 

Quote -
Following what the Getting_Started said, I deleted some objects from the scene. This time it ran with No problems.

Please download the new version. This should fix it (I hope).

Quote - [Poser sun was never ''unrealistic''. so i dont think that the Lx sun is mroe realistic.

To compare Posers light system with Lux is unfair. Don't hurt our little Poser-Toy to mutch.

Quote - Ah, but the Poser sun IS quite unrealistic...we're just all used to it...lol. Even in Lux (if you look at that pic of the ivy covered trees I posted**)** I was still getting hard**, overdark shadows,** even though the lighting overall was better. Just wait until you see this new one. It's still cooking, but when it's done, I'll post :o).

Laurie

Quote - > Quote - > Quote - i think its sloveer because of the lux sky.

i think its better to use bagginsbill ENV sphere for the sky lighting.

I tried using that, but alas for now, it doesn't work ;o). Maybe soon. Then I'll be using it. But I'd still like to use Lux's sun, which has just a little more something-something ;o). I can hack the files for that, no big deal. Nice thing too is that the xyz coordinates are right there next to it so you can change it's orientation if you want to.

I will post my image as soon as it's done enough to look half-decent ;o).

Laurie

Poser sun was never ''unrealistic''. so i dont think that the Lx sun is mroe realistic.

this has to do wit hthe sky. and you dont have the sky in your render since the exporter is nto finished yet.

Quote - open the LXS file in notepad. look for

"integer xresolution" [1024]
 "integer yresolution" [768]

change as required. (eg mine are set to 1024/768 there)

Hm. Image size should be taken from Poser. Does this not work for you?

Quote - > Quote -

Following what the Getting_Started said, I deleted some objects from the scene. This time it ran with No problems.

Please download the new version. This should fix it (I hope).

Thanks, downloading now.

LuxRender says that it is rendering, Statistics 00:09:29 - 108630 S/s -  106101 TotS/s - 242S/px - 143% eff - EV= -7

Should I try importing asomething much smaller/ OR Do i need to modify the LuxRender Settings? So far i left them as the default when i installed it.

nope. I'm getting Lux image sizes like 400/300.... and my poser image has never been that....

Mine always come in at 640/400. That's not what my render size is ;o). I had to hack my .lxo file too to change the size.

Laurie

latest version errors with

Compiling D:PoserSmith MicroPoser ProRuntimePythonposerScriptsScriptsMenuLuxPoseluxmaticnodes.pyc
Compiling D:PoserSmith MicroPoser ProRuntimePythonposerScriptsScriptsMenuLuxPoseluxmaticnodes.pyc
Compiling D:PoserSmith MicroPoser ProRuntimePythonposerScriptsScriptsMenuLuxPoseluxmaticnodes.pyc
Compiling D:PoserSmith MicroPoser ProRuntimePythonposerScriptsScriptsMenuLuxPoseluxmaticnodes.pyc
Version alpha 1.0.3 (exporter: alpha 1.1), exporting Lux files to
D:PoserSmith MicroPoser Pro
Traceback (most recent call last):
  File "D:Program Files (x86)Smith MicroPoser ProRuntimePythonposerScriptsScriptsMenuLuxPosePoserLuxExporter.py", line 166, in ?
    ExportScene(scene, globalParameters).write(f)
  File "D:PoserSmith MicroPoser ProRuntimePythonposerScriptsScriptsMenuLuxPoseworkersPoserLuxExporter_workers.py", line 329, in write
    ExportLight(light, self.globalParameters).write(file)
  File "D:PoserSmith MicroPoser ProRuntimePythonposerScriptsScriptsMenuLuxPoseworkersPoserLuxExporter_workers.py", line 223, in write
    self.convert2Lux()
  File "D:PoserSmith MicroPoser ProRuntimePythonposerScriptsScriptsMenuLuxPoseworkersPoserLuxExporter_workers.py", line 193, in convert2Lux
    pto = dotp(pto, mcol(wm, 0)), dotp(pto, mcol(wm, 1)), dotp(pto, mcol(wm, 2))
UnboundLocalError: local variable 'pto' referenced before assignment

In poser, go to Render/Render Dimensions in the drop down menu.  You should change it there for the script to pick it up.  Or press for windows.

I get the same error now as kaibach.

Quote - In poser, go to Render/Render Dimensions in the drop down menu.  You should change it there for the script to pick it up.  Or press for windows.

Did that. Still comes in at 640x400 ;o).

Laurie

Quote -
UnboundLocalError: local variable 'pto' referenced before assignment

Happend for distance light because I left a line commented out.
Fixed ...

okies. working again

same "IndexError: list index out of range" tho on the figure I had it on before....

If you use point light, scale it up in Poser (make the small circle a big one). Mutch better shadows! 

Quote - okies. working again

same "IndexError: list index out of range" tho on the figure I had it on before....

Mmmm. Mine exports and renders fine now. 
Are you using Alpha_1-10d?

yes I am...
must be that marine figure..

Quote - > Quote - In poser, go to Render/Render Dimensions in the drop down menu.  You should change it there for the script to pick it up.  Or press for windows.

Did that. Still comes in at 640x400 ;o).

Laurie

I have to look into this. 

Quote - > Quote - In poser, go to Render/Render Dimensions in the drop down menu.  You should change it there for the script to pick it up.  Or press for windows.

Did that. Still comes in at 640x400 ;o).

Laurie

Strange.  Mine works fine that way.  What do you have it listed as in LuxPose?  Do you have the override button checked?  That defaults to 600x400.  If it is checked in there, uncheck it and try again.

Two pointlights in this scene. One far away (50,1000,100), scaled to 500. The other in front scaled to 1000.

Like others, it isn't rendering at the size i had Poser 8 setup for. 768 x 808
Render Dimensions: Match Preview Window.

It shows:
Resolution: 490 x 500
Zoom Factor: 100%
Viewportsize: 696 x 793

14 mins rendering SM1 Mad Hatter exported from P8 with default lights.

 click fit in preview window and hit match document window
then it works!

Quote - > Quote - > Quote - In poser, go to Render/Render Dimensions in the drop down menu.  You should change it there for the script to pick it up.  Or press for windows.

Did that. Still comes in at 640x400 ;o).

Laurie

Strange.  Mine works fine that way.  What do you have it listed as in LuxPose?  Do you have the override button checked?  That defaults to 600x400.  If it is checked in there, uncheck it and try again.

I'm sorry...override button? In Lux or in Poser? Color me stupid today....lol.

Laurie

Quote -
  Do you have the override button checked?  That defaults to 600x400.  If it is checked in there, uncheck it and try again.

OK, where is The Override Button please?
I see an "Auto" Radio Box and and "Apply" radio Button.

In the luxpose program on the Film tab.  Although mine says 800 x 300 for Poser Dimension, it is really 1600x1000 which is picked up by the exporter. 

..what film tab?
looks all over Lux render and finds no film tab

Um, my Luxrender doesn't have a film tab...lol.

Laurie

Oh...the LuxPose GUI you mean? I haven't even set that up yet...lol

Laurie

Yep, soory.  I should have emphasized the LuxPose GUI program, and not LuxRender.  If you do run that, it should be run prior to exporting to Lux as the results are what is used by the exporter.  It is possible that if you hadn't run it before then the defaults were used instead; which may mean 600x400 dimensions.

Quote - > Quote - > Quote - In poser, go to Render/Render Dimensions in the drop down menu.  You should change it there for the script to pick it up.  Or press for windows.

Did that. Still comes in at 640x400 ;o).

Laurie

I have to look into this. 

I think it probably picks it up from the dataout.bbml file, there is dimensions defined there, those get read by the exporter.

If you don't use the GUI:

Please look into file AIR/LuxPose/data/dataout.bbml
Search for "overwriteDimensions" and set it to "false" or "true". 

"true" means the dimension ("width", "height") in the same file is used as render dimension.
"false" means the script tries to get the dimension from Poser.

Quote - If you don't use the GUI:

Please look into file AIR/LuxPose/data/dataout.bbml
Search for "overwriteDimensions" and set it to "false" or "true". 

"true" means the dimension ("width", "height") in the same file is used as render dimension.
"false" means the script tries to get the dimension from Poser.

I think I need to actually install the GUI first...lmao. I was so ready to test Lux that it slipped my mind completely...lol.

Either way, it was simple enough to change :o)

Laurie

Quote - Oh...the LuxPose GUI you mean? I haven't even set that up yet...lol

Laurie

Is the LuxPose GUI  another file to download?

Like others, I see no Film tab.

Quote - > Quote - Oh...the LuxPose GUI you mean? I haven't even set that up yet...lol

Laurie

Is the LuxPose GUI  another file to download?

Like others, I see no Film tab.

If you have downloaded recently, you should already have the install files.  They are located in the AIR subdirectory.  There is a readme.txt there, which i would suggest reading first.  Pay attention to the file it will ask you to locate.

Quote - Yep, soory.  I should have emphasized the LuxPose GUI program, and not LuxRender.  If you do run that, it should be run prior to exporting to Lux as the results are what is used by the exporter.  It is possible that if you hadn't run it before then the defaults were used instead; which may mean 600x400 dimensions.

Thanks, I see now. That would BB's LuxPoseUI 0.1.2.

As BB suggested, did you place this in your Poser Python Poserscripts folder?