Download latest LuxPose version www.poserprofis.de/PoserLuxExporter_Alpha
Tracking Page sites.google.com/site/luxposedevelopment/

Have At It!

General Lux Pose Questions
LuxPose Wishlist
Original Thread

Someone should write a short description what it is and why it is great!

Here you can read how and why the project is started just a few weeks before ...
http://www.renderosity.com/mod/forumpro/showthread.php?thread_id=2807395

Quote - Tracking Page sites.google.com/site/luxposedevelopment/

I'll need to bone up on my Latin... :lol:

I was planning a Getting Starter Package

• Includes a sample scene using primitives
• A method creating a scene in Poser and going through the steps to have LuxRender render it.
• Links to LuxRender

It will be a very basic load-and-go primer. It WILL not go into editing the .lx* files to add sunlights, portals and such as I never got clear on how to do this myself as like some folks we are awaiting the complete version.

If someone would like to take somethings from the initial thread and make a "Moving on to Advanced Lux" Package" That will be cool, (and greatly appreciated).

Very good for early stage,  I will have to figure out hair transparency later on.
It is faster than current method I use of breaking scene down and running through Blender.
But with LuxBlender, you can tweak materials that are exported

please remember Medzinatar, this is an Alpha. Materials are still only on a very basic level.

The google wiki page is out. So if anyone with a smidge of html knowledge wants to start a page on the RO Wiki, please volunteer :o). With the google wiki, I was just trying to make things easier for folks who have zilch or nearly zilch in html skill like myself ;o). Oh well :o(.

Laurie

I just stepped in here. Can someone point me to right place / page how to install the diff parts. thks a million

Quote - I just stepped in here. Can someone point me to right place / page how to install the diff parts. thks a million

So far, it only resides here in the monster thread ;o). If you click on the link in adp001's signature, you should be able to get the instructions in the zip file. You'll need to install Luxrender as well.

Laurie

thks laurie and have great weekend all

Quote - I just stepped in here. Can someone point me to right place / page how to install the diff parts. thks a million

First go to www.luxrender.net and download Lux. Lux is a "stand alone render engine" with an own GUI to set some things up (probably you want to read a bit in Lux documentation on the same site).

Second, go download Adobe AIR if you havn't installed it yet. [www.adobe.com/products/air

](http://www.adobe.com/products/air)Third, download Alpha Exporter package LuxPose from my footer.

Extract the zip file as described in "starter.txt" contained in the package.

Don't be frustatated if not all materials are exported now. This will come soon.

Quote - Very good for early stage,  I will have to figure out hair transparency later on.
It is faster than current method I use of breaking scene down and running through Blender.
But with LuxBlender, you can tweak materials that are exported

Transmaped hair should work. 

Transmapped hair does work - at least with Poser 8 vanilla it does ;o). And it looks better than in Poser.

Laurie

Quote - So if anyone with a smidge of html knowledge wants to start a page on the RO Wiki, please volunteer

No need for any HTML-knowledge at all... The editor is quite easy to use... I just started a page:

http://www.renderosity.com/mod/rrwiki/index.php/LuxPose

Quote - > Quote - So if anyone with a smidge of html knowledge wants to start a page on the RO Wiki, please volunteer

 

No need for any HTML-knowledge at all... The editor is quite easy to use... I just started a page:

http://www.renderosity.com/mod/rrwiki/index.php/LuxPose

Awesome! Thanks Dizzi ;o).

Laurie

I was hasty in checking Transmapped hair status.
The one I first used had a "Noise Node" attached to bump input and material failed to convert.
All others tried after seem to work fine

adp, would you please fix the exporter to tell where it actually exports to? (line 157, outputpath)
Makes it less confusing when used for the first time ,-)

Quote - adp, would you please fix the exporter to tell where it actually exports to? (line 157, outputpath)
Makes it less confusing when used for the first time ,-)

Pretty good idea.

Package updated without to change version.

.

Better yet, and only a suggestion, allow the user to define the folder for LuxPose Export.

I wrote this as a separate script:

Set LuxPose Export Folder

import poser,os

Setup Folder Preference File

try:
    luxSvPath = os.path.join(poser.PrefsLocation(), "LuxPose")
except:
    luxSvPath = os.path.join(os.path.dirname(poser.AppLocation()), "LuxPose")

make directory if doesn't exist

if not os.path.exists(luxSvPath):
    os.makedirs(luxSvPath)

luxSvFile = os.path.join(luxSvPath,"LuxPose_SceneFolder.ini")

Choose Directory

filePath = os.path.join(os.path.dirname(poser.AppLocation()),"Runtime")
msg = "Please Select a Folder For Lux Scenes"
dlg = poser.DialogDirChooser(message=msg, startDir=filePath)
if dlg.Show():
    dir = dlg.Path()
    fp = open(luxSvFile, "wt")
    fp.write(dir)
    fp.close()

and then in PoserLuxExporter changed

outFolder = os.path.join(myFolder, 'toLux')
if not os.path.isdir(outFolder):
    try: os.mkdir(outFolder)
    except:
        raise Exception, "Folder 'toLux' can't be created in path %s." % myFolder +
                         "Check if a file named 'toLux' exists already."

to:

try:
    luxSvFile = os.path.join(poser.PrefsLocation(), "LuxPose","LuxPose_SceneFolder.ini")
except:
    luxSvFile = os.path.join(os.path.dirname(poser.AppLocation()), "LuxPose","LuxPose_SceneFolder.ini")

if os.path.exists(luxSvFile):
    fp = open(luxSvFile, "rt")
    outFolder = fp.readline()
    fp.close()
else:
    outFolder = os.path.join(myFolder, 'toLux')
    if not os.path.isdir(outFolder):
        try: os.mkdir(outFolder)
        except:
           raise Exception, "Folder 'toLux' can't be created in path %s." % myFolder +
                        "Check if a file named 'toLux' exists already."

Of course, it could all be integrated in and additional code could also allow users to name the export file.  I don't know what kind of GUI you have going in the future, so if you already will have it covered, that's cool :)

pokeydots, do you know that you can just use [subscribe] at the bottom of a page to get notified of replies? :-) 

I do now! lol Had a brain fart! Forgot I could just subscribe!

The windscreen also doesn't really seem to clean up completely, still fireflies on it.

Will go try Path instead of Bidirectional setting.

Quote -  This is still a work in progress; as you can see I lost Vicky's head, I guess that's the refraction of the windscreen glass in action.. :p

The windscreen also doesn't really seem to clean up completely, still fireflies on it.
Will go try Path instead of Bidirectional setting.

That will look better once the materials are fully sorted out and integrated ;o).

Laurie

I guess dynamic hair's not going to transfer over. I tried dynamic clothes, which do, but I spoke to someone who tried hair and it's no-go....ah well... Something about just the guide hairs show up, just in case anyone was wondering ;o)

Laurie

If you enable "Show populated" in the styling controls of the hair, then the exporter will export that and not just the guide hairs. 

Hmmm...I'm no good with dynamic hair, but I'll pass that on ;o)

Laurie

I added that to the wiki page's new FAQ section together with scripts to turn that on/off (Poser 6+ only). Too bad that it's got the same problem as the forum: no .py upload :-(.

Quote - I added that to the wiki page's new FAQ section together with scripts to turn that on/off (Poser 6+ only). Too bad that it's got the same problem as the forum: no .py upload :-(.

Dizzi, you're awesome! :o)

Laurie

Flenser, the problem with most of the glass made for Poser props is that it is only single sided.  That will throw off the refraction in a huge way.  If the windows on that car only have one layer you would be better off setting the material to Lux's architectural glass, or setting the IOR to 1 so it won't refract.

That's going to be something to keep in mind for most of the glass items we use in Poser.

Quote - I guess dynamic hair's not going to transfer over. I tried dynamic clothes, which do, but I spoke to someone who tried hair and it's no-go....ah well... Something about just the guide hairs show up, just in case anyone was wondering ;o)

Laurie

That's not a problem. We'll generate the actual hairs from the guide hairs, just like Poser does. Patience, patience. This project isn't even a month old.

Apropos of nothing, working with Lux made me finally get off my butt and go get a new desktop computer. I just set it up. I'm now getting 285K samples per second versus the 20 to 30K I was getting.

Woo hoo. And that's not even the GPU version. For the graphics card I got the ATI 5770 - I hope that wasn't a mistake. I already have problems with Poser OpenGL on it. Have to update drivers I think. I've always avoided ATI.

But I sure like 8 threads cranking on Lux or Poser.

Quote - > Quote - I guess dynamic hair's not going to transfer over. I tried dynamic clothes, which do, but I spoke to someone who tried hair and it's no-go....ah well... Something about just the guide hairs show up, just in case anyone was wondering ;o)

Laurie

That's not a problem. We'll generate the actual hairs from the guide hairs, just like Poser does. Patience, patience. This project isn't even a month old.

Well, I wasn't actually being impatient...lol. Dynamic hair is something I don't use myself, at least not yet...hehe. If there's a way it can be done, I'm sure you guys will pull it off ;o)

Laurie

Quote - Apropos of nothing, working with Lux made me finally get off my butt and go get a new desktop computer. I just set it up. I'm now getting 285K samples per second versus the 20 to 30K I was getting.

Woo hoo. And that's not even the GPU version. For the graphics card I got the ATI 5770 - I hope that wasn't a mistake. I already have problems with Poser OpenGL on it. Have to update drivers I think. I've always avoided ATI.

But I sure like 8 threads cranking on Lux or Poser.

Whoa, must be nice! Congrats ;o).

Laurie

Did a little messing with Lux settings and tweaking this and that. I'm up to 430K samples per second. That's really acceptable.

Unbiased rendering is a totally different experience when you get into the order of magnitude of million samples per second. In a few more years we'll have 32 cores, not 4, and then it will be near realtime.

On my new computer I'm getting the camera disparity that others reported. Poser is doing something different in 64-bit version maybe? This is the first time I had access to 64-bit Poser.

Nah, I'm getting it too in Poser 8 on my 32 bit system ;o). It's occurred to me that it's contained to Poser 8 and 2010, since users of earlier versions don't seem to be having the problem.

Laurie

Well it will be a while until it is sorted out, unless somebody else pursues it. I'm going to bed, and then I'm going sailing all day tomorrow. Realistically, I probably won't work on Luxpose until Monday.

As Laurie said.

congrats on new puter BB. That is magic!
 I'm saving up for the 12 core mac pro, so I will be eager to try all sorts of interesting stuff like this once I get it.  I just have to do lots of extra shifts at work.  Pretty tired because of that.
Love esther

Quote - I'm going sailing all day tomorrow.

Sailing huh? I've been sailing since the age of 7...
What are you sailing on?

I have updated the wiki page with all the wishlist items suggested in the wishlist thread thus far.

Laurie

odf: to solve my problem, it was sufficient to adjust your code like that (the other code from the other thread wasn't really necessary):

        nr_tpolys = sum([len(actor.Geometry().TexPolygons())
                         for actor in actors if actor.Geometry().TexPolygons()])

This prop just returns 'None' for TexPolygons() (and 0 for the NumTex... methods).

you may want to check the camera view code.
the view is not matching up in poserpro (not 2010) either.. I hadn't noticed it till it was pointed out.

Quote - odf: to solve my problem, it was sufficient to adjust your code like that (the other code from the other thread wasn't really necessary): nr_tpolys = sum([len(actor.Geometry().TexPolygons()) for actor in actors if actor.Geometry().TexPolygons()])

This prop just returns 'None' for TexPolygons() (and 0 for the NumTex... methods).

D'uh! I should have been using NumPolygons() and NumTexPolygons() all along.

But actually, this issue is a bit more complicated than it may look. If some actors in a figure have UVs and others don't, I can either throw away the UVs for the whole figure, or else I have to make sure that the texture polygons are still in correct correspondence with the regular ones. Apparently broken or partially missing UVs crop up every once in a while, so it would be good if I came up with a strategy for dealing with them and tested that properly. I guess the lesson here is to use the Num.. methods Poser provides rather than len().

Quote - I have updated the wiki page with all the wishlist items suggested in the wishlist thread thus far.

Good idea! I was just about to suggest that.

I have a question regarding the Catmull-Clark subdivision wish. I think it was ADP who suggested that, but since I had already implemented it, I'm not sure I understand what he meant.

The Catmull-Clark subdivision wish is about having it in accessible in the GUI I think.

Can't get rid of those last fireflies.

Quote - odf: to solve my problem, it was sufficient to adjust your code like that (the other code from the other thread wasn't really necessary): nr_tpolys = sum([len(actor.Geometry().TexPolygons()) for actor in actors if actor.Geometry().TexPolygons()])

This prop just returns 'None' for TexPolygons() (and 0 for the NumTex... methods).

This should now be fixed in the latest version up on http://github.com/odf/pydough.

If you could test it with the object that gave you trouble before, that would be very much appreciated.

Quote - this is with the refraction index at 1.1, down from the default of 1.5. The glass became opaque when the index got down to about 0.5.

pardon, but isn't there a glass specifically for windows in Lux?

Quote - > Quote - this is with the refraction index at 1.1, down from the default of 1.5. The glass became opaque when the index got down to about 0.5.

pardon, but isn't there a glass specifically for windows in Lux?

Yes he's using that I think, but the Lux glass still asks you to say what is the IOR.

Note that nobody should be using "glass". There is a new "glass2" that is more sophisticated.

Herein is a lesson. Lux is not finished. LuxPose isn't either.

The LuxRender blurbs will tell you this is phyically accurate rendering. But the contradiction, then, is that they tell you not to use the "glass" material that was being offered as part of the "physically accurate" framework, but now is identified as not so much.

In other words, the goal is correctness, not the actuality, and further if you have the freedom to put parameters in any of it (other than color) than you have the freedom to force the program to depart from physicall correctness.

I also think the fireflies point to a fundamental flaw. I don't believe it should be necessary to render 2500 samples in order to get rid of such an obvious rendering artifact. The notion of unbiased rendering as being unable to produce clean results until a huge number of samples is produced is a different notion than unable to produce accurate results until a huge number of samples is produced.

Let me clarify:

Unbiased rendering needs thousands of samples per pixel for accuracy - I agree.

Unabiased rendering needs thousands of samples per pixel to avoid artifacts - I disagree.

I think they have something wrong. If not that, then I think they have been thinking with too narrow a mindset. I think that a clean image should be possible in 50 samples no matter what in the kinds of images I've been doing. There is no refraction or caustic effect, and all light sources are large. With the bidir path integrator, it is easy as pie to find paths from camera to light source, and after 50 such paths, every pixel should be within 10% of its final accurate value.

When I have time, I will look into this problem.