Forum Coordinators: RedPhantom
Poser - OFFICIAL F.A.Q (Last Updated: 2024 Nov 08 7:07 am)
Quote - I was looking for the IOR for latex earlier today, seems to vary from what I found, between about 1.42 and 1.59. I was playing with one at an IOR of 1.5 (splitting the difference). Think I need to bring the roughness down a bit but am getting close.
Mind you, Laurie is far more familiar with how materials go together and would probably get it done much faster than I will. I admit I am still plinking away trying to figure out what everything does in the various materials definitions.
Yes Rhionnon, I looked everywhere for a latex IOR and finally found 1.535 for patent leather, which is close. Since natural rubber is about 1.519 and plastic 1.460 I'd put it somewhere between 1.460 and 1.535 ;).
And your shoes mat looks really good! :D
Laurie
What ice-boy is trying to say cough, is that not only are point lights and Poser lights harsh, but that emitters give a more natural lighting effect with softer shadows ;). Point lights are also infinitesimally small and don't spread out much of a highlight ;). For indoor lighting, it's best to use an emitter :). And even better, an emitter with real-world IES data. It will take some time to unlearn some of the things we did that were necessary for Poser but not with Luxrender :). Baby steps...lol.
Laurie
I've included the textures for the hearts and stars just for fun..in case you wanted to use 'em on fingernails or whatever. Wouldn't look so great on a car though I wouldn't think ;). You can put the textures anywhere you like.
NOTE: this material will only work in the very latest versions of Pose2Lux! (Pose2Lux 1.0.1 and Pose2LuxPro 0.3.0)
Laurie
If you get IES Generator v.4 you can actually see how each of the IES files casts its light. The site is Russian, but you can easily find the download link at the bottom of the article. You can also generate your own IES data in the program. Handy to have if you don't quite know how your IES files are casting it's light.
In the emitters tab:
Highlight an emitter and use GRAB to copy its paramters to the controls and find the IES file you want to use. Use ASSIGN to apply the control values to the emitter(s). You can highlight more than one emitter at a time. There's also an IES folder that's been added to the Paths panel so that you can keep all your IES files in one place for getting to easily ;).
Laurie
I think there is a huge problem with the newest Pose2LuxPro 0.30. I just tried a render using that, and when I did, only a small portion actually rendered. The scene was a car on a pier. The car top was the only thing that rendered. I then used an earlier version and everything rendered like I was expecting. I did not change any of the materials that were auto-assigned in either render.
No insult taken, and no point lights involved. One spot and an emitter. Just snagged the lights from my test pic in gallery to save time.
Latex IORs are really only listed for its spherical pre-final state, the raw material. I looked at patent too. And yes the IORs are darned close.
Well I have ten set up now with the colours sampled off a variety of examples of latex and will upload a sample and the .xml shortly. Just getting caffeine into me quick while I get the file zipped up. Want to try making some of the patterned ones next.
Added the bump map bit, thanks Snarly.
And I will look at the IES Generator, just probably not today.
Quote - Thanks Laurie :D
Another quick silly question, in the viewer is it a top down view of the light
Nah, I think it's a side view...what it looks like up and down. I could be wrong about that though, but I don't think so...lol. I think that most lights are heavier on one side than another because a lot of IES files are for lights with a reflector and the lighter side is just light that bleeds behind. Anyway, even a bare bulb will cast more light from the sides that are totally glass and less back in the direction of the bulbs base.
Laurie
Well it kept me busy last night instead of stressing, which is a good thing. Got word my grandfather (who raised me) is in congestive heart failure. Waiting to find out more and if I am going to be packing up stuff to go up to stay there for a bit. Maybe I should get an extra external HD today for Poser and Lux.
Anyways, remove the .txt and extract it to where your Lux materials are.
Quote - I think there is a huge problem with the newest Pose2LuxPro 0.30. I just tried a render using that, and when I did, only a small portion actually rendered. The scene was a car on a pier. The car top was the only thing that rendered. I then used an earlier version and everything rendered like I was expecting. I did not change any of the materials that were auto-assigned in either render.
Is anybody else experiencing issues?
I have been unable to reproduce this problem - a selection of scenes that I've just tested have all rendered as expected.
That doesn't mean that there isn't a problem, but I need more information to be able to track down any bugs. Can anybody throw any more light on this (no pun intended)?
Free stuff @ https://poser.cobrablade.net/
Quote - And here's the image:
These are textures and colors straight from Poser with the car paint material applied in the exporter.
Oh my. You're producing some lovely materials Laurie. I now have more of your materials in my Pose2Lux folder than I have of my own!
One day I'm going to have to coerce you into rewriting the Pose2Lux built-in libraries ;-)
Free stuff @ https://poser.cobrablade.net/
I'm not having any problems with the Pose2LuxPro beta so far either. I just used it to export a scene and it works fine.
My suggestion? Break down the scene to see what it is that's in it. Are you using displacement? - questions of that nature.
I'm going to try a scene that I know for sure has displacement next.
Laurie
I'm getting this
"Traceback (most recent call last):
File "L:Poser developmentPloppose2luxpro.py", line 5694, in ?
File "L:Poser developmentPloppose2luxpro.py", line 3133, in init
File "L:Poser developmentPloppose2luxpro.py", line 3888, in init
AttributeError: pageLights instance has no attribute 'varGroup'"
from the pro version when I try running it with no lights in the scene.
I broke it again, YAY! :lol:
Windows 7 64Bit
Poser Pro 2010 SR1
Quote - I'm getting this
"Traceback (most recent call last):
File "L:Poser developmentPloppose2luxpro.py", line 5694, in ?
File "L:Poser developmentPloppose2luxpro.py", line 3133, in init
File "L:Poser developmentPloppose2luxpro.py", line 3888, in init
AttributeError: pageLights instance has no attribute 'varGroup'"
from the pro version when I try running it with no lights in the scene.
I broke it again, YAY! :lol:
Ha! You did!
I'll fix this in the next update. In the meantime just make sure you have a light in your scene :-) You must need one to see what you're doing in the Preview room?
Remember, if you name your light "ignore:Light name" (or whatever) then it is automatically put into the 'ignore' group and not exported, so there's ne especial reason to not have a light in the scene.
Still, it'll be fixed next time around anyway!
Free stuff @ https://poser.cobrablade.net/
Quote - Ha! You did!
I'll fix this in the next update. In the meantime just make sure you have a light in your scene :-) You must need one to see what you're doing in the Preview room?
Remember, if you name your light "ignore:Light name" (or whatever) then it is automatically put into the 'ignore' group and not exported, so there's ne especial reason to not have a light in the scene.
Still, it'll be fixed next time around anyway!
I'd forgotten about the ignore function, make it idiot proof & you can be sure some idiot (me) will come along & break it. :D
Windows 7 64Bit
Poser Pro 2010 SR1
Quote - Well, I just tried the scene again, and this time checked the 'no displacement' checkbox and it renders fine.
I should add that I didn't change the chrome materials in the 0.30 scene which is why the chrome is white in that and not in the earlier version of the exporter.
Did the Lux log give any useful diagnostic information?
It's the entries marked with a red triangle that are generally the most useful.
Free stuff @ https://poser.cobrablade.net/
Quote - Ok, I just tried a prop I made that uses displacement. The kind of the displacement on the prop is -0.5 to +0.5 and done with a subtract node. What kind of displacement map is in yours jcleaver? Just a plain 0-1.0? FWIW, mine exported fine.
Laurie
Actually, I can't find that I am using any displacement. I checked all of the materials, and displacement is not attached on any of them. Mind you, I could be missing something obvious. That is known to happen from time to time.
Thank you LaurieA and Rhionon so much for the lovely materials! I'm also going to give the pointlight trick a try on a test render.
"A lonely climber walks a tightrope to where dreams are born and never die!" - Billy Thorpe, song: Edge of Madness, album: East of Eden's Gate
Weapons of choice:
Poser Pro 2012, SR2, Paintshop Pro 8
Attached Link: http://vimeo.com/21139061
A video worth watching to understand Luxrender sample settings better and goes over the Luxrender glass2 material. The author of the tute is using Blender, but the materials and Luxrender settings still apply.Laurie
Ok, so we're narrowing down the range of possibilities a bit! Useful stuff.
I still can't reproduce the problem though.
In the attached image is a scene rendered with microdisplacement switched on. The green square has a displacement map attached, with the word 'displacement' running from bottom left of the square to top right.
The scene appears to have rendered fine.
Is it feasible for you to zip up the 'broken' version of the .lxs file output by Pose2Lux and send it to me? That would give me more data with which to get to the bottom of this.
And thank you, for helping debug Pose2Lux - this is exactly what we need to be doing to make it a robust script!
Free stuff @ https://poser.cobrablade.net/
OK, I loaded the scene again and deleted the car. It now renders fine with micro-displacement enabled. So it is something about the car.
To verify that, I started a new scene with the car only, and it has problems by itself. So, it is the car that is causing my problem. Just what, I'm not sure yet. I'll see if that is small enough to send if I zip that up, if that's OK. It is also too big, at about 11 MB.
Attached Link: HJSplit
> Quote - I will have to find a way to send it. The zipped file is still 22 MB, and my email won't send that large of a file. Let me know where to send it also.You can use HJSplit to split a file into more manageable parts. I have HJSplit too, so I can reassemble them when I get them.
Any files can be sent to roystonpaul@btinternet.com, removing the asterisks of course.
Free stuff @ https://poser.cobrablade.net/
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.
One way is this:
"texture bumpmap" [USE_BUMPMAP]
Another is to use a line:
etc.
....
I'd recommend the approach because it is more robust in cases where no bump map is found.
Free stuff @ https://poser.cobrablade.net/