Ack, forgot to mention that the hack was originally made for Miki2, but you should be able to copy and paste it for V4 with no problems.

 Hope all of that helps and makes sense. ^_^

Quote - [
LOL. Nah, Lux files are almost human readable. Some parts of the syntax are strange-ish (I suspect they might make perfect sense to a developer - I'm not one), but if only there were a complete, up-to date documentation it would had been a piece of cake.

Why don't you start writing a documentation for users, not developers?

Quote - In poser 6 I get this error when running the python script.

:758: Warning: 'yield' will become a reserved keyword in the future
Traceback (most recent call last):
  File "", line 157, in ?
  File "workersmanageMaterials.py", line 9, in ?
    import MatNodes5
  File "", line 758
    yield BaseNode(self,n)
                 ^
SyntaxError: invalid syntax

Thanks!

This script file is just an "intermediate" solution and not really needed. I'll remove it in the next version.

i'll second that!  a user-friendly guide, or even a wikipage of code snippets, would be very handy.  i keep my own list but it's getting very disorganized.

Quote - ODF - unfortunately, every hairstyle I've tried (at least 6, from several different sources) gives me the same 'NoneType' error.  I tried loading a hair set by itself, in case being parented to a figure was causing it, but that didn't work.  I tried growing a hairball, and that exported fine.   I'm not sure what's going on.

I think I've found the problem. In the file pydough/from_poser.py, change line 198 from

        if g.Name() == name:

to

       
if g.HairProp().InternalName() == name:

As usual, make sure not to change the number of space at the beginning of the line, since Python is very sensitive about that.

I'm not completely sure yet I understand how Poser handles dynamic hair, but this works with the Izetta hair and looks kind of logical to me.

Quote - In poser 6 I get this error when running the python script.

Updated without changing the version number, because there is nothing new in this version except that I removed an included file that creates an error in P6.

Re-download if you want to give P6 a try. Please report further errors generated by P6 because I want to have P6 support as soon as possible.

Quote - i'll second that!  a user-friendly guide, or even a wikipage of code snippets, would be very handy.  i keep my own list but it's getting very disorganized.

I'll third it, we already have a wiki page ready, the code snippets should be commented to explain what each part does in simple terms though, it's no good just adding the code without explaining what it does & why it does it.

HI poser 6 OSX
latest version of the exporter
getting this error now:

Traceback (most recent call last):
  File "", line 82, in ?
  File "Macintosh HD:Applications:Poser 6:Runtime:Python:poserScripts:LUXPOSE ALPHA:PoserLuxExporter_alpha_1#871987:workers:Parameters.py", line 113, in read
    raise RuntimeError, "configfile not found: %s" % file
RuntimeError: configfile not found: Macintosh HD:Users:EMPERORTAIN:Desktop:AIR/LuxPose/data/dataOut.bbml

Not sure why it seems to be looking for "dataout.bbml file" on my desktop.

Cheers

Quote - (Sorry, a little late, replying to the person looking to make light-emitting textures some pages ago.)...

Note that each light emitting polygon is considered a separate light for Lux's raytracing calculations, so apply Light materials only to simple geometry, lest your render takes ages.

This was I, and I thank you VERY Much! :)
Lots of experimenting to do here :)

The Poser 6 PC version gets the same error as the mac version.

Traceback (most recent call last):
  File "", line 82, in ?
  File "D:Poser 6RuntimePythonposerScriptsworkersParameters.py", line 113, in read
    raise RuntimeError, "configfile not found: %s" % file
RuntimeError: configfile not found: D:Poser 6AIRLuxPosedatadataOut.bbm

Quote - The Poser 6 PC version gets the same error as the mac version.

Traceback (most recent call last):
  File "", line 82, in ?
  File "D:Poser 6RuntimePythonposerScriptsworkersParameters.py", line 113, in read
    raise RuntimeError, "configfile not found: %s" % file
RuntimeError: configfile not found: D:Poser 6AIRLuxPosedatadataOut.bbm

We come closer :)
This error is because P6 doesn't find the folder this script is running from. I've replaced the old function from BB with a function from Dizzi now that works with P6.

If you like to test again, pleae re-download ...

Quote - > Quote - i'll second that!  a user-friendly guide, or even a wikipage of code snippets, would be very handy.  i keep my own list but it's getting very disorganized.

I'll third it, we already have a wiki page ready, the code snippets should be commented to explain what each part does in simple terms though, it's no good just adding the code without explaining what it does & why it does it.

Yes, for me adding something about materials to the wiki is a good idea!

HI just got the same error on P6 is there a new build to download??

Cheers

"Traceback (most recent call last):
  File "", line 81, in ?
  File "Macintosh HD:Applications:Poser 6:Runtime:Python:poserScripts:PoserLuxExporter_alpha_1#871987:workers:Parameters.py", line 113, in read
    raise RuntimeError, "configfile not found: %s" % file
RuntimeError: configfile not found: Macintosh HD:Applications:Poser 6:Runtime:Python:poserScripts:PoserLuxExporter_alpha_1#871987:AIR/LuxPose/data/dataOut.bbml
"

Quote - HI just got the same error on P6 is there a new build to download??

Yes! As before no new version number for this.

Quote - > Quote - > Quote - i'll second that!  a user-friendly guide, or even a wikipage of code snippets, would be very handy.  i keep my own list but it's getting very disorganized.

I'll third it, we already have a wiki page ready, the code snippets should be commented to explain what each part does in simple terms though, it's no good just adding the code without explaining what it does & why it does it.

Yes, for me adding something about materials to the wiki is a good idea!

Added 4 new sections ...

** Editing your .LXM, LXS Files 
****Material Code Line Explanations
**Material Code Line "Hacks"
Lights, Groups and SUN

I get this error in the p6 pc version, now:

Traceback (most recent call last):
  File "", line 202, in ?
  File "", line 178
     return (xfm(x) for x in items)
                      ^
 SyntaxError: invalid syntax

 ::Sigh::

Trying a copy and Paste of "Code" is a nightmare, Wiki thinks you are trying to use a  format on the page... or you get 1 continuous line...

HELP?

WHAT happened to the wiki page? It looks like shit now. I reset it to the older version. sigh

I don't mind someone wanting to add something, but I think one person taking care of the wiki page in this case is enough since it can get really f'd up really fast. If we have 500 ppl adding willy nilly it will be unreadable.

Since I've been taking care (mostly) of the wiki page up to this point, please sitemail me what you want added and I'll add it. Thanks ;o).

Laurie

EXCUSE ME!!

Please stop screwing up the wiki page. Please.

I'm begging. That normally comes just before I grab my 2x4 with nails....

Laurie

 :( sorry... wont happen agin

I don't mind the editing so much, but PREVIEW it before you make a permanent change ;o). If it looks messed up in preview, it will look messed up when you change it permanently.

Laurie

Quote - I get this error in the p6 pc version, now:

Traceback (most recent call last):
  File "", line 202, in ?
  File "", line 178
     return (xfm(x) for x in items)
                      ^
 SyntaxError: invalid syntax

I assume this one is because Python 2.2 can't deal only with arrays for something like this. I replaced it with  return tuple([xfm(x) for x in items]) and hope it works.

Please re-download for another P6 test ...

Quote - I don't mind the editing so much, but PREVIEW it before you make a permanent change ;o). If it looks messed up in preview, it will look messed up when you change it permanently.

Laurie

Maybe it's better to have a separate wiki for material handling?

@adp: please look on the peanut gallery. I got it running under P6 and uploaded the modified files.

All the problems I found looked Python-related, not Poser, so it might be good to try and test things under Python2.2 independently of Poser as much as possible.

I added the new pages as Synpainter has listed them. You may now go in and add to each page what you like. Click the "edit" link by each section and add your copy.

Laurie

Quote -
Please re-download for another P6 test ...

Hi Still no Go On P6 OSX:

"Traceback (most recent call last):
  File "", line 81, in ?
  File "Macintosh HD:Applications:Poser 6:Runtime:Python:poserScripts:PoserLuxExporter_alpha_1#871987:workers:Parameters.py", line 113, in read
    raise RuntimeError, "configfile not found: %s" % file
RuntimeError: configfile not found: Macintosh HD:Applications:Poser 6:Runtime:Python:poserScripts:PoserLuxExporter_alpha_1#871987:AIR/LuxPose/data/dataOut.bbml"

Cheers

Quote - > Quote -

Please re-download for another P6 test ...

Hi Still no Go On P6 OSX:

"Traceback (most recent call last):
  File "", line 81, in ?
  File "Macintosh HD:Applications:Poser 6:Runtime:Python:poserScripts:PoserLuxExporter_alpha_1#871987:workers:Parameters.py", line 113, in read
    raise RuntimeError, "configfile not found: %s" % file
RuntimeError: configfile not found: Macintosh HD:Applications:Poser 6:Runtime:Python:poserScripts:PoserLuxExporter_alpha_1#871987:AIR/LuxPose/data/dataOut.bbml"

Cheers

For me this path looks ok - or I'm blind???
Do you have folder "AIR/LuxPose/data" and the Air config files installed?

I see - it's a Mac problem with path-seperator!

Updated again :)

Quote - > Quote - I don't mind the editing so much, but PREVIEW it before you make a permanent change ;o). If it looks messed up in preview, it will look messed up when you change it permanently.

Laurie

Maybe it's better to have a separate wiki for material handling?

I added the sections specified by Synpainter in his forum post. So far, no one has either sent me any copy that I can add or has added anything themselves. But the sections are definitely there ;o).

I apologize if I hurt your feelings Synpainter. I just woke up to a jumbled wiki page mess and my pissy component kicked in ;o). You may now edit to your heart's content. All I ask is that you preview what you've done before you make it live to avoid any further messes. And if you need syntax help, just examine a section that's already been done to see how the wiki likes the code to be.

To make a new section, set it up like this:

==Name Of Your Section==

...then add what copy you want beneath it. That adds a new section and also adds that section to the contents block.

Laurie

Quote - I see - it's a Mac problem with path-seperator!

Updated again :)

Hi here where we are P6 OSX:
**
Traceback (most recent call last):
  File "", line 79, in ?
AttributeError: 'module' object has no attribute 'sep'**

Thanks

Quote -
Hi here where we are P6 OSX:
**
Traceback (most recent call last):
  File "", line 79, in ?
AttributeError: 'module' object has no attribute 'sep'**

Ok, the classic way ...
I think we are close - would be nice if you could try again!

Quote -

Ok, the classic way ...
I think we are close - would be nice if you could try again!

Hi here is the new error:

Traceback (most recent call last):
  File "", line 202, in ?
  File "Macintosh HD:Applications:Poser 6:Runtime:Python:poserScripts:PoserLuxExporter_alpha_1#871987:workers:PoserLuxExporter_workers.py", line 3, in ?
    reportcomments = True # comments written to outputfiles
NameError: name 'True' is not defined

Going to Lunch now will back be online after 1:30 pm New York Time

Cheers

Quote - > Quote - > Quote - I don't mind the editing so much, but PREVIEW it before you make a permanent change ;o). If it looks messed up in preview, it will look messed up when you change it permanently.

Laurie

Maybe it's better to have a separate wiki for material handling?

I added the sections specified by Synpainter in his forum post. So far, no one has either sent me any copy that I can add or has added anything themselves. But the sections are definitely there ;o).

I apologize if I hurt your feelings Synpainter. I just woke up to a jumbled wiki page mess and my pissy component kicked in ;o). You may now edit to your heart's content. All I ask is that you preview what you've done before you make it live to avoid any further messes. And if you need syntax help, just examine a section that's already been done to see how the wiki likes the code to be.

To make a new section, set it up like this:

==Name Of Your Section==

...then add what copy you want beneath it. That adds a new section and also adds that section to the contents block.

Laurie

I won't have the time to do anything worthwhile for the wiki until tomorrow, when I get time I'll have a look at what's been done then try adding something, I'd rather not mess it up by rushing it, you're too scary for me to get on the wrong side of you.  :b_tonguewink:

Quote - > Quote - > Quote - > Quote - I don't mind the editing so much, but PREVIEW it before you make a permanent change ;o). If it looks messed up in preview, it will look messed up when you change it permanently.

Laurie

Maybe it's better to have a separate wiki for material handling?

I added the sections specified by Synpainter in his forum post. So far, no one has either sent me any copy that I can add or has added anything themselves. But the sections are definitely there ;o).

I apologize if I hurt your feelings Synpainter. I just woke up to a jumbled wiki page mess and my pissy component kicked in ;o). You may now edit to your heart's content. All I ask is that you preview what you've done before you make it live to avoid any further messes. And if you need syntax help, just examine a section that's already been done to see how the wiki likes the code to be.

To make a new section, set it up like this:

==Name Of Your Section==

...then add what copy you want beneath it. That adds a new section and also adds that section to the contents block.

Laurie

I won't have the time to do anything worthwhile for the wiki until tomorrow, when I get time I'll have a look at what's been done then try adding something, I'd rather not mess it up by rushing it, you're too scary for me to get on the wrong side of you.  :b_tonguewink:

I'm harmless...lol. Just make sure you preview before making it permanent. Otherwise I'll cut you off at the knees...lmao.

I am JUST KIDDING!! LOL But I am a little pissy for my own good sometimes, I freely admit it ;o).

Laurie

@ Laurie

My skin is pretty thick so, No hurt feelings... It's all good. 

People get pissy, so be it, we all have our moments...

Still stumped with trying to paste a code line in Wiki..... 

For instance:

# start light "Sun & Sky"

AttributeBegin

* LightGroup "Sun"*

* LightSource "sunsky"*

* "vector sundir" [-0.6 0.5 0.7]*

* "integer nsamples" [3]*

* "float gain" [0.020]*

* "float turbidity" [3]*

AttributeEnd

# end light "Sun & Sky"

All becomes one continuous line, I "Think" the punctuation is seen as a format code of sorts by wiki.
Not sure... someone confirm?

Quote - @ Laurie

My skin is pretty thick so, No hurt feelings... It's all good. 

People get pissy, so be it, we all have our moments...

Still stumped with trying to paste a code line in Wiki..... 

For instance:

# start light "Sun & Sky"

AttributeBegin

* LightGroup "Sun"*

* LightSource "sunsky"*

* "vector sundir" [-0.6 0.5 0.7]*

* "integer nsamples" [3]*

* "float gain" [0.020]*

* "float turbidity" [3]*

AttributeEnd

# end light "Sun & Sky"

All becomes one continuous line, I "Think" the punctuation is seen as a format code of sorts by wiki.
Not sure... someone confirm?

It very well might...let me give it a shot... I'll let you know what I find out and you can do the edits then :o).

Laurie

Ok Synpainter...I think there's a sort of workaround....

I added your copy and code above to the wiki. I made it permanent so that you can see what I did and make any further additions using it as a guidline. After you make your changes, feel free to delete what I added when you no longer need it.

What I did puts everything in a box, but at least everything in the box looks like it should.

If there's anything you aren't sure of or if you can't quite tell what I did to make it look that way or if you feel uncomfortable adding it yourself, sitemail me with questions or copy to add. I'm always hanging around ;o).

Laurie

Quote - [**
    reportcomments = True # comments written to outputfiles
NameError: name 'True' is not defined**

Going to Lunch now will back be online after 1:30 pm New York Time

Cheers

This line was just too high ... moved it downwards

Quote -
I'm harmless...lol. Just make sure you preview before making it permanent. Otherwise I'll cut you off at the knees...

Can I see a render pretty please?

:)

Quote - > Quote -

I'm harmless...lol. Just make sure you preview before making it permanent. Otherwise I'll cut you off at the knees...

Can I see a render pretty please?

:)

I'm not into virtual blood and gore. Only the real thing....lmao.

I am STILL kidding...lol

Laurie

Here are two more interesting Links about Lux textures/materials:

http://www.luxrender.net/wiki/index.php?title=LuxRender_Textures
http://www.luxrender.net/wiki/index.php?title=LuxRender_Materials

Quote -

This line was just too high ... moved it downwards

Hi latest error poser6 OSX
**

"Traceback (most recent call last):
  File "", line 210, in ?
Exception: Make sure all files from the package are installed into the same directory.
cannot import name radians"**

Cheers

Cheers

Quote - Anyways had a slow afternoon so the graphic Designer in me
got inspired to create the "official" LUXPOSE Logo.

I LIKE! :D

Laurie

Quote - > Quote - Anyways had a slow afternoon so the graphic Designer in me

got inspired to create the "official" LUXPOSE Logo.

I LIKE! :D

Laurie

ME TOO!

Thanks for creating the subsections for material hacks LaurieA! I'll see about posting some of the ones I've made into that section. Hopefully, they'll be more readable than the one(s) I've posted here. Also, is there a way to add images to the wiki so they don't mess up the formatting of the page?

And Wolf, I like the logo and can totally see it working for the exporter app. ^_^

Quote - **
cannot import name radians"**

Added a replacement function for radians and the constant PI because the math lib from Python 2.2 has none.

Another try?

headache

Go ahead and everyone do what you want with the wiki....

I can't (and won't) clean up after more than one or two persons. I resign...lol.

Laurie