Quote - Hi!

 

I need a little assistance...

Where can i find this back-pack (jet pack) from Maccha? ( A viewer wants to know...)

(see image) http://fav.me/d2wxlhl

It's been in my runtimes for years...; but I'm not sure where I found it, or if it is still available.

:)

Try here -

http://cid-fc1d202961aade39.skydrive.live.com/browse.aspx/.Public?uc=5&sa=707386573

Cheers.

Quote - Aziqo has released a Deidara character from Naruto with clothes, props, hair etc.   Yay!

I think it may be for M3RR, haven't installed yet.

Thanks for the heads up.

If you look at the store I think Naruto is an original character not a morph of another character. Could be completely wrong but that's the way I'm reading it.

Quote - Experimental Version 1.42 Download here

This version has experimental skin, velvet, mattetranslucent, metal, mirror and glass support. Please give feedback after experimenting.

(1.40 is still downloadable from my footer if this version does not work for you).

Base is a glossy-shader. Other shaders are mix-ins. 

Poser translucence -> Lux mattetranslucent
Poser Refraction -> Lux Glass

Would be nice if someone could play with this. Maybe some parameters are better changed.

Getting a 'file not found' for 1.42.

I was getting the same as stewman. Tried deleting all lights and now get this -

Loading  pydough.geometry_export
Loading  pydough.poser_extractor
Loading  pydough.geometry
LuxPose Version alpha 1.22, exporting files to C:Program FilesSmith MicroPoser 8RuntimePythonposerScriptsPoserLuxExportertoLux3test2.lxs

Using sampler metropolis
Using integrator bidirectional
Using accelerator kdtree

GEOMETRY EXPORT
Traceback (most recent call last):
  File "C:Program FilesSmith MicroPoser 8RuntimePythonposerScriptsPoserLuxExporterPoserLuxExporter.py", line 222, in ?
    ExportScene(scene, globalParameters).write(f)
  File "C:Program FilesSmith MicroPoser 8RuntimePythonposerScriptsPoserLuxExporterworkersPoserLuxExporter_workers.py", line 478, in write
    ExportFigure(fig, self.globalParameters).write(outfile)
  File "C:Program FilesSmith MicroPoser 8RuntimePythonposerScriptsPoserLuxExporterworkersPoserLuxExporter_workers.py", line 158, in write
    params).write(file)
TypeError: init() takes at most 4 arguments (5 given)

Something broke.

Quote - Runtime Error!

Program: C:Program Files LuxRenderluxrender.exe

This application has requested the Runtime to terminate it in an unusual way. Please Contact the application's support team for more information. 

As ADP001 said, check for IBL in the scene. The only time I have ever had that error was due to IBL. I just deleted it from the .lxl file to save having to re-export everything.

Quote - > Quote -

If you want to have several projects on the go at once here is what I rename to keep order.

  It's easier to add the following code to PoserLuxExporter.py, to get asked to choose the filename:

search for globalparm["filename"] = filename = "poserscene_%s" % version

Add the following two lines after that (make sure the blanks before the text are the same number as the line before): dlg=poser.DialogTextEntry(None, "Enter filename (without extension, cancel for default)") if dlg.Show(): filename=dlg.Text()

I am sure all this will become redundant as the GUI gets released but for now I thank you for this, most useful.

Quote - I do know how to save .flm files, but I don't know how to suck eggs.  Might be interesting.  :lol:

I tell you what - give it a go, take a picture and post it. Now that would be interesting  :lol:

Apologies if I was covering old ground with my post above.

If you want to have several projects on the go at once here is what I rename to keep order.

Open the .lxs file in the text editor of your choice.

Rename "poserscene_alphax.xx" in "string filename" ["poserscene_alphax.xx"] to "your file name" . This changes the name of the output png.

Scroll to the bottom and change -  Include "poserscene_alpha x.xx.lxm"  to Include "your file name.lxm"
Repeat for Include .lxo and .lxl.
Save the file.

Now change the name of all 4 files in the toLux folder to your file name.

Choose your file from LuxRender by name and render away.

Attached is a copy of the files in my toLux folder with two projects on the go.

Does everyone know how to save the 'flm' file so you can open it again and resume rendering or will I be teaching people to suck eggs here?

Quote - The front point light was scaled to 500% in size. The brightness on the front light is 200%. For the rear light (which is exactly opposite to the front in coordinates) it's the same size in scale (500%) but it's only at 5% brightness. I just wanted to fill in the shadow so that it wasn't so dark.

That's pretty much it :o).

Laurie

Thanks, time to experiment a bit more :)

Quote - Ok, here is my favorite nekkid standin (yet again...sorry ;o)).

The particulars are on the image.

I have no idea why I'm getting that ring on the floor and there are still a few blank pixels, but overall, I'm satisfied with the skin. At least she's not shiny...lol.

This particular skin does have a bunch of burned in highlights, but I only have two and it's the lesser of two evils. The Daz texture is horrible ;o).

Laurie

Laurie,

Excellent image.

Thanks for the LuxRender settings you used. If you still have the scene could you please post your Poser light settings prior to export?

Until we get some 'official' test secenes I am trying to recreate this image and it would greatly help me get a handle on how the exporter treats Poser lights.

Many thanks.

Looks like saanzi has put a direct download link to the file on the page infinity10 posted above.

Ah well, I wil still have fun looking round artistside, never knew it existed.

Quote - > Quote - Right at the top on the page with weekly Lux builds we find:

*The LuxRender team is pleased to bring you the third (and last?) pre release of the upcoming 0.7 version.

Based on feedback from the first 2 pre releases, we've fixed a whole lot of bugs and polished the GUI and LuxBlend exporter. I want to thank the whole dev team for its commitment to improving LuxRender. We're not aware of any major bug left, please report any in Mantis. 

So we can assume the way how Lux works now is "the last word" (especially this camera problem)

Now you have completely confused me as well.

LuxRender 0.7 RC3 was published June 6. Well BEFORE 0.7 was released.

LuxRender 0.7 (official) was published July 9.

http://www.luxrender.net/forum/viewtopic.php?f=12&t=4209

I could be wrong, as I don't have time to chase down everything that looks wrong to me, but your info about RC3 looks wrong to me.

The 0.7 official July 9 announcement also says (confusingly)

Quote - Changes since v0.7RC3:

• bug fixes (mostly to reduce fireflies)

I say confusingly because it looks like you're telling us RC3 is newer than the released 0.7, while the Lux site tells us the opposite.

Agree with BB here. When choosing what to download a while ago I looked at the files quite carefully. Official 0.7 seems to be the latest build with the weekly release moving on from there.

rty - glad someone was able to be more scientific than me :)

The problem I get is shown in the image attached. On the left is the Poser render and on the right is the LuxRender render. The file is exported to the same dimensions (checked in the .lxs file). The LuxRender one appears to be 'zoomed out' a little bit.

Have no idea if this is to do with the render dimensions but it has done it for each file I have exported in all versions of the alpha.

Poser 8, SR3, Display units = Feet

Quote - Oh, that's too bad.   Does he give any explanation for this decision?  And if we were to email him, can we do so in English or should we try using a translator?

A quick google translate states redistribution and commercial use which was forbidden. Can't find anything about the emails though.