Thu, Nov 28, 5:28 AM CST

Renderosity Forums / Poser - OFFICIAL

All Forums

Welcome to the Poser - OFFICIAL Forum

Forum Coordinators: RedPhantom

Poser - OFFICIAL F.A.Q (Last Updated: 2024 Nov 27 5:12 pm)

Poser Gallery - Poser Freestuff

Subject: VSS and Custom Gamma value?

Whichway opened this issue on Feb 21, 2010 · 6 posts
Back to Forum Print
Whichway ( ) posted Sun, 21 February 2010 at 4:09 PM · edited Thu, 01 August 2024 at 3:23 PM

Under Poser Pro (2010 beta, in this case) Image Maps have the option to set a Custom Gamma Value in order to do Displacement, Bump, Transparency, etc. properly when using Linear Color Space, i.e., letting Poser Pro do the GC globally rather than with each material. My question is, is there any way to set up something like a template Displacement Map in a VSS template material so that the substituted image map uses a Custom Gamma value of 1.00? I don't seem to be able to set the option on an Image Map node without picking something other that None as the map source. Any help will be appreciated. Thanks.

Whichway

bagginsbill ( ) posted Sun, 21 February 2010 at 4:18 PM · edited Sun, 21 February 2010 at 4:19 PM

Strangely, the configured gamma value for an image is not stored in the material.

It is stored in some hidden lookup table that Poser remembers. They never told me where this info is kept. It is stored based on the file name.

So - the first time you configure XYZBump.jpg to be custom gamma 1.0, it is that way forever, even if you open a new scene. It is that way in every material, even if you only made the change in one particular material.

There is nothing VSS can do, or you can do in materials, that would alter that. As far as I know, this mapping between exact file names and specific gamma values is completely hidden from Python so VSS can't do anything about it.

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)

hborre ( ) posted Sun, 21 February 2010 at 4:29 PM

file_448494.jpg

Unless BB can make a suggestion into hacking your VSSProp, my recommemdation would be to change the map source prior to applying synchronize,  The image above shows how to set the node up for template skin.

Whichway ( ) posted Sun, 21 February 2010 at 5:20 PM · edited Sun, 21 February 2010 at 5:31 PM

Hmm. Ok, thanks guys. Setting the GC value by hand before applying the VSS Prop is what I've been doing, but was looking for an automated way. Maybe Bagginsbill knows off the top of his head if the file property table is preserved across invocationns of Poser Pro; Then I'd only have to set it up once in the lifetime of the file. If he doesn't know, I suppose I could force myself to check.

Whichway

P.S. - I checked and the table is not preserved across invocations. Not surprising, I suppose, but it means I have to fiddle the GC value once each time I use the file in any Poser Pro session. sigh

Whichway ( ) posted Sun, 21 February 2010 at 5:42 PM

However, if I save out a Material Set with the changed GC values, they remain set to the value I picked when reapplied in another Poser Pro invocation. So, if I sort out my workflow properly, it shouldn't be too bad.

Whichway

hborre ( ) posted Sun, 21 February 2010 at 7:17 PM

That would probably be the best way until some other method is discovered.

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.