Tue, Nov 19, 8:32 AM CST

Renderosity Forums / Poser 11 / Poser Pro 11 OFFICIAL Technical



Welcome to the Poser 11 / Poser Pro 11 OFFICIAL Technical Forum

Forum Moderators: nerd

Poser 11 / Poser Pro 11 OFFICIAL Technical F.A.Q (Last Updated: 2024 Nov 17 7:07 pm)

banner

Welcome to the Poser Forums! Need help with these versions, advice on upgrading? Etc...you've arrived at the right place!


Looking for Poser Tutorials? Find those HERE



Subject: I couldn't see the color preview anymore......


RAGraphicDesign ( ) posted Wed, 13 November 2024 at 1:49 PM · edited Tue, 19 November 2024 at 8:30 AM

Hi everyone!
Today for the first time, while I was organizing a scene, I couldn't see the color preview anymore. Up to a certain point I could see it perfectly. I managed to render as I wanted, but every time I open this specific document I still see it like this.
Did I do something wrong? and I didn't notice?
Thanks for the advice.

skqzz8ztABxHXhNu1JyAjtnDk4TsYZnXeeeDG1wQ.jpg

My Store

My Freestuff



hborre ( ) posted Wed, 13 November 2024 at 3:11 PM
Online Now!

Lights?


RedPhantom ( ) posted Wed, 13 November 2024 at 4:10 PM
Site Admin Online Now!

I agree. It looks like a lights issue. Usually when I see something like this, the lights were setup in a later frame but the scene is loading to the first. If I move to the end, the lights are fine and the scene looks right.


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


hborre ( ) posted Wed, 13 November 2024 at 5:36 PM
Online Now!

My overall assessment indicates that the lights are off, and the snowy ground and background emit an ambient glow that is not apparent at full render. Please verify if any lights are present throughout the scene and whether they are activated.  


RAGraphicDesign ( ) posted Thu, 14 November 2024 at 2:43 AM · edited Thu, 14 November 2024 at 2:43 AM

Actually the view is of the last frame (the one I rendered). The problem is the lights: they are rendered but I can't see them in the scene. The lights window, an IBL and the Sun, appear black. It never happened to me and so I don't know how to change this state...

XDwqUfzU5CHcniZztoQxGW7keUkJy5tJ3yaoaVyk.jpg

My Store

My Freestuff



RedPhantom ( ) posted Thu, 14 November 2024 at 6:55 AM
Site Admin Online Now!

That's showing no lights, or lights the lights are all off and at zero position.


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


RAGraphicDesign ( ) posted Thu, 14 November 2024 at 7:19 AM

RedPhantom, But the render came out like this......


I'm afraid of touching something I shouldn't: I would like to keep the file to be able to use the scene for other things....

My Store

My Freestuff



Y-Phil ( ) posted Thu, 14 November 2024 at 9:23 AM · edited Thu, 14 November 2024 at 9:23 AM
RAGraphicDesign posted at 7:19 AM Thu, 14 November 2024 - #4491331

If you click on "Light Controls", you should see a list of lights, example:

vfyhFfb1e95a2mupc80BkIM6XGvhOtqyzzpLqpfk.png

That being said, if you set your light's material this way (diffuse and specular color):

uIQTbGX5u0V4DXHdrr3wVWX5e5amjLXqKxYOqqAi.png 

it should light the scene only in the preview, not at render time, which can be either useful or confusing


𝒫𝒽𝓎𝓁


(っ◔◡◔)っ

👿 Win11 on i9-13900K@5GHz, 64GB, RoG Strix B760F Gamng, Asus Tuf Gaming RTX 4070 OC Edition, 1 TB SSD, 6+4+8TB HD
👿 Mac Mini M2, Sonoma 14.6.1, 16GB, 500GB SSD
👿 Nas 10TB
👿 Poser 13 and soon 14 ❤️


hborre ( ) posted Thu, 14 November 2024 at 9:53 AM
Online Now!

RAGraphicDesign posted at 7:19 AM Thu, 14 November 2024 - #4491331

RedPhantom, But the render came out like this......


I'm afraid of touching something I shouldn't: I would like to keep the file to be able to use the scene for other things....

Overwriting the original file is safe provided you do not resave your scene. Initially, verify the presence of lights in the scene at render time. If lights are present, examine the Properties for each to ensure they are active, as indicated by an 'On' checkbox, signifying the emission of rays. Next, confirm that the light intensities are set above zero.  Lastly, if there are no lights, add one to monitor its effect.

As mentioned earlier, if you're using a dome, scene illumination can come from the ground and background. This can be verified in the Material Room. When using Firefly rendering, navigate to the Material Room and examine the Ambient settings on the PoserSurface node. If the value exceeds 1, then the background is contributing to the scene lighting.


RAGraphicDesign ( ) posted Thu, 14 November 2024 at 11:03 AM

I have an EnvShere that I use with the lights of vincebagna. The lighting in question is given by an IBL and the Sun. The render was done in SuperFly. I checked again - referring to a previous version of the file - and I moved the intensity values ​​of IBL and sun. Even the colors of the lights in the small window had to be changed anyway.....It remains a mystery how they were reset....

Thanks to all:)

My Store

My Freestuff



hborre ( ) posted Thu, 14 November 2024 at 12:21 PM
Online Now!

IBL fails to render in Superfly. As previously noted, the Envsphere prop and the snow emit ambient light; without it, the scene would be entirely dark. This can be confirmed in the Material Room.


nerd ( ) posted Sun, 17 November 2024 at 1:27 AM · edited Sun, 17 November 2024 at 1:27 AM
Forum Moderator

If you use a sky dome it must be the light emitter. The much easier way is to use one of the IBL pre-built scenes that come with Poser 13.

Load the "Wide Street" scene from the included content. The scene looks like it's just a simple light dome. It's way more.

This scene is built so the dome is visible in preview. So, you can see what you're doing with the dome and pose the scene relative to the environment.

When it renders is uses some Stupid Poser Tricks (tm) to hide the visible environment sphere the render is using Cycles native environment. (which isn't normally visible) The orientation of the preview dome and the HDRI environment are linked. You shouldn't really be able to tell it switched.

If you want to use a different IBL just use the same HDRI on both the light and the dome. You can do this in one act from the Texture Manager by "Replacing All ... In scene"


How the magic works ... You absolutely don't need to know how this works to use it. But if you want to build your own here's the secrets ...

The first stupid trick is that the Environment Preview only shows in Preview. It doesn't render.

The environment preview is only there for composing the scene. It's orientation is linked to the BG Environment node in the material room. That make the Cycles native HDRI environment line up with the Preview. Just to make it more interesting the BG Environment Rotation is in Radians.

The orientation of the preview IBL light is setup the same way. Just like the Preview Background the Preview IBL doesn't render. It's just there so you're not stumbling around in the dark. Just for nerdly fun this one is UVS to Degrees. Ewwww math!

So every thing you can see in that scene in preview, none of it renders. Not the light or the environment sphere. They're just there so you can see what you're doing. All that actually renders is the BG Environment node. It creates the light and the environment.,

BUT WHYYYYYYY!

The cycles BG Environment simple isn't capable of not casting shadows. Took me a while to wrap my head around that too. But it's not a "light" so it doesn't have shadows. It's a diffuse emitter and stuff that's occluded simply can not receive light.

So at the end of this we get to the point. If you use an environment sphere Image Base Lights will not shine through it. Period, Full stop. Ain't happenin'. The "environment must go into the Cycles BG Environment node. The "dome" must the hidden when rendered. Also absolutely none of this apples to FireFly. It's not a physical based render. That means it's allowed to break the laws of physics.


hborre ( ) posted Sun, 17 November 2024 at 5:33 AM
Online Now!

This is a nice presentation, but the OP is running P11.  It may be beyond his understanding of how it is done in P13.


nerd ( ) posted Sun, 17 November 2024 at 7:07 PM · edited Sun, 17 November 2024 at 7:11 PM
Forum Moderator

The only thing missing from P11 would be an environment sphere mapped to match the "Equirectangular" mapping of the Cycles BG Environment. The preview sphere is mapped with an equirectangular projection (AKA Mercator projection). But, none of this is really necessary for anything except the preview. The complexity in the template scenes is all for the sake of previewing the HDRI.

The setup below is for P11. There's no magic preview sphere but it will render the same.

For a SuperFly render in P11 just plug the HDRI from the environment dome into the BG Environment node and connect that to the Background root node. Same setup as post above except you don't need the dependencies. You do need the Mapping and TextureCoordinate nodes to make the environment display correctly..

Hide the dome in the scene. Then set the background shader up like shown below. The Rotation input on the mapping node will control the rotation of the background. Remember it's in radians. A value of 0.0, 1.57, 0.0 will rotate the background 90deg. The background will not be visible in the preview. Now you probably see (or really don't see) why I made that template scene for this.

You may want to add a plane at ground level setup as a shadow catcher. The OP scene doesn't look like it would actually need that though.




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.