Renderosity Forums / Poser - OFFICIAL
Welcome to the Poser - OFFICIAL Forum
Forum Coordinators: RedPhantom
Poser - OFFICIAL F.A.Q (Last Updated: 2025 Jan 03 1:41 pm)
Subject: General questions about LuxPose
Quote - Dizzi,
I think we sould go with this talking about compatibility things to another place. What about Laurie's Forum at her "Peanuts Gallery"? She offered a closed forum for dev-talk to the Lux developers. Or just open another thread here.
If that's what she wants, I'll add her to the list of users :o).
Laurie
Quote - Maybe I will try to test this out. But, if I download and install Lux and the alpha or beta of LuxPose, will I be able to uninstall it or delete it if it proves too much for me? How easy is it to get rid of?
You just have to delete the newly installed folder(s) to remove the Python scripts.
To uninstall Lux and/or AIR you may use your Windows service (Software). I'm sure you'll find help here if you have trouble with uninstalling. As far as I know there are no leftovers after uninstalling the packages (even Adobes AIR :) ).
On the other side: Air is used by other software, too. So having it installed may be useful anyway.
Lux has it's own installer and can be uninstalled.
LuxPose alpha is just unzipping somewhere, if you unzip it into its own folder and not directly into the PoserScripts folder, you can just delete the folder if you don't like it, otherwise you have to hunt down multiple folders and files :-)
Adobe Air and the LuxPose UI using Adobe Air can be uninstalled like any other application, too.
Quote - I should have mentioned I'm on a Macintosh, running 10.6.4. Would that change anything as far as uninstalling goes?
When Dizzi says to unzip LuxPose into its own folder, would that be within the Python folder?Or, could I just place it within the Runtime folder?
You have to put the script in your Python/poserscripts folder, like the instructions that come with .zip file instruct. "Getting Started.txt"
I think it may be in your best interest to have a look at the LuxPose wiki page, go over everything there, as well as read up on LuxRender a little and then test.
Laurie
Hello
-
To deal with textures which shows as missing in LuxRenderer there is simple solution. In material room just clik on "Image_Source" of problematic texture if it's path starts with :Runtime, then just press OK - you should notify that name changed to texture's name. Now do export to Lux.
-
Fireflies on the renders - it's a bug in 0.7 release of LuxRenderer (here is tread about that on Lux's forum: http://www.luxrender.net/forum/viewtopic.php?f=16&t=4374). To get rid of it you can find one of the new weekly builds which almost eliminates this.
-
If you plan to use net rendering (i've set up a pair - win xp and imac with 10.5) you have to have the same version of Lux (unfortunatelly compatible pair for win and macos - 0.7 stable - contain fireflies).
hope this helps a bit
Attached Link: http://www.renderosity.com/mod/forumpro/file.php?fileid=458329
For missing textures, you can also run the script from the attached link. It should let Poser fix all links it can. Alternatively (but way more tiresome): use texture shaded preview for all elements, that lets Poser fix the references, too (Poser 7+).If that doesn't fix the references: what cubek said ;-)
Please tell me, if the first two methods work for anyone else, not just me ;-)
Quote - Yes, it's advisable you put it in it's own folder in /poserscripts...lol. Makes it easy to get rid of if you don't want it on your machine anymore ;o). Is that in the "Getting Started.txt" file? If not, maybe we should add it.
Laurie
Laurie,
you do such a good job with the wiki, couldn't you write something for the "starter.txt"?
Quote - OK, thanks, LaurieA. I'm interested, but, yes, I don't want to jump in and drown.
I think you will easily find someone here who can help you with anyone to get you rendered :)
Or to delete what you don't want anymore.
Anything used with this project is available for Windows, OS-X and Linux/Unix and open source (or at least free like Adobes AIR). So nothing is hidden or leads to something a user can easily manage.
At the moment AIR is not really required. If you just want to see if Lux/Poser is good for your images, leave AIR aside. You can install it later if you want.
Quote - > Quote - Laurie,
you do such a good job with the wiki, couldn't you write something for the "starter.txt"?
Me??!
Write something? I make little enough sense as it is....lol. But if it doesn't hurt Flenser's feelings, I'll give it a go.
Laurie
I cklicked on history in the wiki and saw mostly "LaurieA" :)
ANYBODY WHO CONTRIBUTED TO THE WIKI: Thank you for spending your time and know-how to the project!
OK, I downloaded the Poser Lux Exporter Alpha from the signature in ADP's posts, Adobe AIR, and LUX RENDER v.07, using the Macintosh versions of the latter two. Now, I'm pausing. Can I get rid of each one of these easily, if I decide to? I'm not going to install today. I think I'll back up and check out my HD before doing that. But, these are the only three components I need, right?
Oh, yes, I'm running PoserPro2010 on an Intel Macintosh, running 10.6.4, an iMac Core Duo 2 Extreme, with 4 GBs of Ram. The graphics card is an ATI Radeon HD 2600 Pro with 256 MBs of VRAM. Anybody see any problems with this system?
Quote - OK, I downloaded the Poser Lux Exporter Alpha from the signature in ADP's posts, Adobe AIR, and LUX RENDER v.07, using the Macintosh versions of the latter two. Now, I'm pausing. Can I get rid of each one of these easily, if I decide to? I'm not going to install today. I think I'll back up and check out my HD before doing that. But, these are the only three components I need, right?
Oh, yes, I'm running PoserPro2010 on an Intel Macintosh, running 10.6.4, an iMac Core Duo 2 Extreme, with 4 GBs of Ram. The graphics card is an ATI Radeon HD 2600 Pro with 256 MBs of VRAM. Anybody see any problems with this system?
Anything is fine for you. You downloaded correctly. You really don't need to backup. Nothing you have on your hd is in danger in any way.
This might be a silly question, but where can I get luxpose?
Available on Amazon for the Kindle E-Reader Monster of the North and The Shimmering Mage
Today I break my own personal record for the number of days for being alive.
Check out my store here or my free stuff here
I use Poser 13 and win 10
ok, i think my question was either misinterpreted or not fully understood.
right now, most people are not using IDL. by far, more people are still using IBL alone to fake indirect lighting. but LuxRenderer already computes indirect lighting. so most IBL lights used with real indirect lighting might blow out the scene because they're designed to compensate for its absence.
for your basic outdoor scene in Poser, you might have an infinite for the sun and an IBL for the light from the ground, sky, and surrounding props. but in something that calculates actual indirect lighting, i'd only need IBL for what isn't actually there. sure, if it's a closed box, the light light from the IBL won't get in. and if something's right next to something else or really big, the only light will be the correct reflected light. but if the spacing is greater, the space isn't enclosed, or the item is smaller, then what you're going to have is indirect light supplemented by IBL in an unrealistic way.
now maybe i'm wrong and this isn't an issue at all. but renders being too bright were a problem with a lot of people's first attempts with IDL.
not to mention, when IBL is used only to fake indirect light from surrounding items (which is true of a lot of studio style renders and indoor renders in general), it's just wasted information.
i wanted to know if anyone had any solutions or general advice about how to handle the lighting adjustment, especially considering you might want to retain the original lighting for Firefly. if there's not, that's cool. it sounds like it hasn't really been considered yet. but i wasn't wondering whether IBLs existed in Luxrender. it would actually be better for about 99% of my renders if they weren't brought over.
Quote - Back to 0 and 1?
And the export path is not the correct path. Poser 8's last path is the one where the script was run, Poser 6's last path is the one the pz3 was loaded from...
It would be nice if Poser 6 remembered where you last saved a PZ3 file to and where you last ran a Python script from.
www.youtube.com/user/ShawnDriscollCG
As I understand what is planned, you can set up any light groups you wish inside LuxPose, including not exporting them. Then you can adjust lighting anyway you want inside Luxrender on the light tab. You can leave all lights in your scene and turn off what you don't want at any time during the render.
The "correct" way to do it with Lux is to use an environment (something like a "skyglobe"). Lux has a special light for that. Loaded with one HDR image the light creates the environment and uses the same image as IBL. So you hardly can avoid correct lighting :)
Converting "correctly" set Poser IDL/IBL to get a matchable result is ... hard. The other question is: Do we want it matchable? I think no. If you want, you can quit Lux and use Firefly.
The goal is to get really good images at the end. Converting things defined in Poser helps a lot to get a startpoint. For some Poser setups it may be the correct result. Other automatic convertions may need help. Especially if complicated nodesets hide what the result should be.
After the conversion the GUI is there to support you getting the finals done. Even setting IBL or an environment. At the end and with a bit luck this can be done in (nearly) realtime.
Quote - > Quote - Back to 0 and 1?
And the export path is not the correct path. Poser 8's last path is the one where the script was run, Poser 6's last path is the one the pz3 was loaded from...
It would be nice if Poser 6 remembered where you last saved a PZ3 file to and where you last ran a Python script from.
At least the location of the running script can be evaluted. If we assume this is Posers Python path, we know a lot already.
Quote - The "correct" way to do it with Lux is to use an environment (something like a "skyglobe"). Lux has a special light for that. Loaded with one HDR image the light creates the environment and uses the same image as IBL. So you hardly can avoid correct lighting :)
Converting "correctly" set Poser IDL/IBL to get a matchable result is ... hard. The other question is: Do we want it matchable? I think no. If you want, you can quit Lux and use Firefly.
The goal is to get really good images at the end. Converting things defined in Poser helps a lot to get a startpoint. For some Poser setups it may be the correct result. Other automatic convertions may need help. Especially if complicated nodesets hide what the result should be.
After the conversion the GUI is there to support you getting the finals done. Even setting IBL or an environment. At the end and with a bit luck this can be done in (nearly) realtime.
I'm sorry adp (and perhaps I'm just not understanding...lol) but are you saying that we should try to mimic Poser's lights in Lux rather than pitch the Poser lights and use the closest matching Lux light?
I thought the point was to use Lux because of it's strengths? Forgive me if I've misunderstood.
Laurie
Quote - As I understand what is planned, you can set up any light groups you wish inside LuxPose, including not exporting them. Then you can adjust lighting anyway you want inside Luxrender on the light tab. You can leave all lights in your scene and turn off what you don't want at any time during the render.
All light switched off aren't exported anyway. Same with props and figures.
You can lightgroups now if you rename your light. Better: Add a group-prefix followed by ":".
If you want to make "Light 1" and "Light 2" go into one lightgroup, rename:
Light 1 to: "group 1:Light 1"
Light 2 to: "group 1:Light 2"
Quote -
I thought the point was to use Lux because of it's strengths? Forgive me if I've misunderstood.
You are right, Laurie.
I answered kobaltkween's question if it is possible to get a Lux render close to that one has done in Poser the heavy way with IBL and such.
I asked the same as you do with "Is this really what we want?"
Oh....lol. I misunderstood then.
For me personally, I want to use Lux because it has better lighting, detail, etc. I'd like to be able to use those strengths to my advantage. Otherwise, I might as well just stick with Firefly.
As for folks who are saying that they haven't seen renders that really look any better from Luxrender than they do Firefly, I think we'll see that for awhile until ppl unlearn Poser's hacks for lighting and material behavior. Then we'll start to see better images ;o).
Just my two pennies ;o).
Laurie
Quote - I'd suggest to move to the coding thread ;-)... At least a place odf and bb will read the posts, too, even if odf doesn't care for compatibility at the moment... I've got some code ready for the path checking before exporting soon...
Well, I wouldn't say I don't care for compatibility. It's just that I can't be bothered testing my code in Poser 6 at the moment. If someone else did the testing, I would definitely make an effort to fix any problems that came up.
-- I'm not mad at you, just Westphalian.
Quote - ok, i think my question was either misinterpreted or not fully understood.
right now, most people are not using IDL. by far, more people are still using IBL alone to fake indirect lighting. but LuxRenderer already computes indirect lighting. so most IBL lights used with real indirect lighting might blow out the scene because they're designed to compensate for its absence.
for your basic outdoor scene in Poser, you might have an infinite for the sun and an IBL for the light from the ground, sky, and surrounding props. but in something that calculates actual indirect lighting, i'd only need IBL for what isn't actually there. sure, if it's a closed box, the light light from the IBL won't get in. and if something's right next to something else or really big, the only light will be the correct reflected light. but if the spacing is greater, the space isn't enclosed, or the item is smaller, then what you're going to have is indirect light supplemented by IBL in an unrealistic way.
now maybe i'm wrong and this isn't an issue at all. but renders being too bright were a problem with a lot of people's first attempts with IDL.
not to mention, when IBL is used only to fake indirect light from surrounding items (which is true of a lot of studio style renders and indoor renders in general), it's just wasted information.
i wanted to know if anyone had any solutions or general advice about how to handle the lighting adjustment, especially considering you might want to retain the original lighting for Firefly. if there's not, that's cool. it sounds like it hasn't really been considered yet. but i wasn't wondering whether IBLs existed in Luxrender. it would actually be better for about 99% of my renders if they weren't brought over.
IBL does not contain 'bounce light information'. It is just another source of direct illumination so there is no conflict with IDL. In nearly every other renderers, they are used together.
Using IBL alone to light a scene get adopted into poserverse because IDL came late. If an IBL scene gets too bright when IDL is added, it is likely due to an incorrect setup such as high HDRI intensity to compensate for the lack of IDL.
As others have mentioned, if you want to retain the original lighting of Firefly, use Firefly.
adp001 - i think you should probably just ignore my questions or points, because you're so busy deciding i don't know what i'm talking about and trying to correct me that you don't get what i'm saying and end up just pontificating about stuff that's completely beside the point. it doesn't help me, and i'm pretty sure it doesn't help you.
nightfall - you aren't getting it either.
Jcleaver - thank you very much. being able to adjust your lights in LuxPose is exactly what i wanted to know more about and discuss. i'd ask more questions, but i don't have time to sift through and correct defensive rhetoric.
to try to clarify the actual use cases:
your average Poser user decides to try Luxrender. they start with a scene they designed for Firefly. they are an average Poser user, so they do not use IDL. they do not use linear workflow for that matter. they use IBL and other lights to fake bounced light. if they just rely on a straight translation, no adjustment, of their lights, it will look like crap and they won't bother to go further (see GC threads for examples).
your average content maker or merchant decides to support Luxrender and show off their work there. but since most of their users will be using Firefly, they need to have Firefly previews, too. they don't want to maintain two sets of lights as they tweak things like directional light color, intensity, and spread, especially when it just means making the same tweaks to translate over and over.
i could go on and on. the point is that most people will start with a notion of lights for Firefly, they will probably not want to design their scene to be Luxrender only, especially with only Poser tools. you've actually discussed some of the necessary translations for spot and point lights within LuxPose in the other thread, but i hadn't seen any discussion about IBL. especially one that addressed the problem of how IBL needs to be different when used with real bounced light..
yes, IBL can be used with IDL. but it will mess things up if it includes things it shouldn't. like, say, faked bounced light. which is how most people use IBL right now. calling that setup incorrect when it accounts for at least 80% of current use doesn't make sense. and it's not just intensity, it's what's actually in the source. most uses of IBL i'm aware of actually fake bounced light from things that are in the scene.
either way, i'm not suggesting anyone try to get the same exact look as in Firefly. but that's OK, i'm not asking any more questions.
Quote -
either way, i'm not suggesting anyone try to get the same exact look as in Firefly. but that's OK, i'm not asking any more questions.
I just said (and tried to declare) that both systems are very different. So a lightset in Poser using IBL may or may not work in Lux.
But setting up a good environment based setup (and automatic IBL) in Lux is easy. Just selecting an image and switching off some lights in Poser. Not so much work for a merchant and understandable for a Poser novice (at least after a few tests).
On the other side: Anything we guess here can be wrong if it is implemented.
Hi, I'm back: I discovered that, as I have Photoshop CS5 Extended, there are, in my Applications/Utilities (Macintosh), both an Adobe AIR Installer and an Uninstaller for the same. Now, I don't know if, when I installed Photoshop, the Adobe AIR component was installed. Does anyone know?
If so, I guess I don't need the downloaded version of Adobe AIR, as the version that came with Photoshop CS5 is only a couple of months old.
So, I could get rid of Adobe AIR, if I wanted to uninstall it.
Now, for LuxPose: I could place a folder containing all of the LuxPose files within the Runtime/Python/PoserScripts folder, I think. Is this correct?
Now, for LuxRender: I unzipped the file, I have the installer. But, what if I want to uninstall this? I don't see an uninstaller.
Sorry, if this has been explained to me before. I know i've already asked about it. But, I don't want to goof anything up and get stuck with an app I can't get rid of. Does LuxRender put files all over the HD? Or, do the files go (except for Preferences, maybe) into one folder? Do any files go, for example, into Library/Application Support? If I knew where the files were going to be placed, then I could manually delete them.
Hope someone can answer these questions. Then, I'll go ahead to the next step: namely, installing.
i think you don't even need to 'install' LuxRender anywhere. i run it right out of the unzipped folder, which is just in my downloads folder. just doubleclick & go. (i'm on XP; don't know if this is true for other OS)
don't know anything about AIR, sorry. i don't use BB's interface anyhow yet, waiting/hoping for the final version.
lost in the wilderness
Poser 13, Poser11, Win7Pro 64, now with 24GB ram
ooh! i guess i can add my new render(only) machine! Win11, I7, RTX 3060 12GB
Quote - Ah, thanks: Now, what about Adobe AIR? Would it have been installed along with Photoshop CS5 Extended? Anybody know?
And, lastly, LuxRender: Where do the files go so that I could manually delete them if I wanted to do so?
Have you read Getting Started.txt? I really need to rewrite that I think. Ok with you Flenser?
You can uninstall the script by just deleting that folder you made in your poserscripts folder. You can uninstall the GUI and Adobe Air and LuxRender however you uninstall any other program thru whatever interface you use to do that. Then they're gone.
The generated .lxs files (for now) go into a folder inside your script folder called "toLux". If you haven't run the GUI yet, it won't be there yet because it's created when you run the GUI for the first time. I'm unsure about this last bit, but I think that's the case - I'll check and make sure.
Edit: looking at the contents of the latest exporter script zip file, I do not see the "toLux" folder, so I assume it's created when the GUI is run for the first time.
Laurie
Quote - " Ah, thanks: Now, what about Adobe AIR? Would it have been installed along with Photoshop CS5 Extended? Anybody know?
And, lastly, LuxRender: Where do the files go so that I could manually delete them if I wanted to do so?"
Yes "toLux" is created from the script if not there.
Lux needs only this few files you see in the downloaded zip To remove Lux, just delete the folder you unzipped to. No spreaded other files.
You didn't need the actual GUI for a first test. Install Lux, install the script and try out.
If you are satisfied and ready to use the GUI to set some parameters, look into the scripts install path and find a folder named "AIR". Doubleclick on the file "LuxPose.air". If a GUI comes up, your AIR installations works. If not, you have to install the other (but I think you're fine with what you have installed).
I think I know why some people cannot create the toLux folder.
We used my script hack to find "myFolder". That does not work for compiled modules and packages. It only works for the main script being run by Poser.
For compiled modules and packages, the information about the original file structure and location is embedded in the .pyc files.
This is why when an error occurs, it describes source code folders on the machine owned by the DEVELOPER, not the USER.
As a consequence, unless the USER unzips the package into the exact same folder structure as the DEVELOPER, the software doesn't work.
Or, it works, but not for the reasons you think. If the user unzipped the first version, and ran it, and then unzipped the second version in a NEW folder, the second version will be writing into the "toLux" folder of the first version.
I will correct all of this in my setup.
Renderosity forum reply notifications are wonky. If I read a follow-up in a thread, but I don't myself reply, then notifications no longer happen AT ALL on that thread. So if I seem to be ignoring a question, that's why. (Updated September 23, 2019)
When I tried to start the export, I got what's shown in the Screen Shot:
Nothing happened, though. I tried selecting first one than the other, of "data" and of "ui." Next, I went to the File Menu, and selected "Run Python Script." I navigated to the "PoserLuxExporter.py" script and chose it. A blank box opened and the spinning beachball commenced. Nothing. Checking the App, I got the message that Poser (2010) was not responding. I had to quit the app in order to get out of it.
I'm not giving up, though. Can anyone please help? The PoserLuxExporter is "alpha_1-12," just downloaded yesterday. The LuxRender is "_v07-Install_OSX_universal_intel," just downloaded yesterday. AdobeAIR is version 2.0.3, the current version. (The Photoshop v and the v downloaded yesterday are the same.) My Intel iMac Computer is running OS 10.6.4. It's a Core Duo Extreme, with 4 GBs Ram, and an ATI Radeon 2600 Pro graphics card with 256 MBs of Ram.
Anyway, what should I try next?
Quote - OK, I installed everything. Adobe AIR was, as I suspected, already installed with Photoshop CS5 Extended. (Remember, this is on a Macintosh.)
When I tried to start the export, I got what's shown in the Screen Shot:
Nothing happened, though. I tried selecting first one than the other, of "data" and of "ui." Next, I went to the File Menu, and selected "Run Python Script." I navigated to the "PoserLuxExporter.py" script and chose it. A blank box opened and the spinning beachball commenced. Nothing. Checking the App, I got the message that Poser (2010) was not responding. I had to quit the app in order to get out of it.
I'm not giving up, though. Can anyone please help? The PoserLuxExporter is "alpha_1-12," just downloaded yesterday. The LuxRender is "_v07-Install_OSX_universal_intel," just downloaded yesterday. AdobeAIR is version 2.0.3, the current version. (The Photoshop v and the v downloaded yesterday are the same.) My Intel iMac Computer is running OS 10.6.4. It's a Core Duo Extreme, with 4 GBs Ram, and an ATI Radeon 2600 Pro graphics card with 256 MBs of Ram.
Anyway, what should I try next?
adp - This is something else I did not have time to talk about but here it is. Because you tell people to put the whole Python tree inside the Poser Scripts menu, they think they can and should navigate down into the parts.
This is not a good structure and I'm changing it.
I'm referring to the screen shot above where we see the user navigating through the internal folders of LuxPose.
Renderosity forum reply notifications are wonky. If I read a follow-up in a thread, but I don't myself reply, then notifications no longer happen AT ALL on that thread. So if I seem to be ignoring a question, that's why. (Updated September 23, 2019)
OK, well, what should I do, bagginsbill? I tried accessing from the scripts menu, which is what the screen shot shows, and I then tried choosing the py file from the File Menu. Both seemed wrong.
I hope I don't come across as snotty or anything: just telling what I did. I'm glad to try something else, but what?
Quote - I think I know why some people cannot create the toLux folder.
We used my script hack to find "myFolder". That does not work for compiled modules and packages. It only works for the main script being run by Poser.
Creating the "toLux" folder is the first action the main script does. This part is no module.
After this "outputpath" is provided to any module interested via Parameter. But actually modules must not know about the path. They should write to the allready existing stream "file".
Actually, if somebody helps a person like me, who is not a "geek" (no offense at all -- it's just that I don't understand the code and can't write any aps), this might actually help to develop a program that almost anybody could use.
Privacy Notice
This site uses cookies to deliver the best experience. Our own cookies make user accounts and other features possible. Third-party cookies are used to display relevant ads and to analyze how Renderosity is used. By using our site, you acknowledge that you have read and understood our Terms of Service, including our Cookie Policy and our Privacy Policy.
Thanks - and shit, I assume some trouble with what I wanted to do :)