Closed GerryArk closed 2 years ago
Some things to check:
setParam
deduces the OSPDataType
from the 2nd argument via type traits. Thus, is e.g. st.turbidity
of type float
? And is a trait defined for Vector
to map to OSP_VEC3F
? For types from glm
or rkcommon
those are defined in headers in https://github.com/ospray/ospray/tree/master/ospray/include/ospray/ospray_cpp/ext (which need to be included).World
(directly, or indirectly via Group
+Instance
?pathracer
renderer.Another quick check you might try. OSPRay will set default values for all parameters. If you comment out your parameters and simply create the sunSky
light, do you see anything then?
Thanks guys, Yes I have found one problem, the sun position, now the sun light and shadows are Ok, I do not see the sky background, anything to know about this ?
You might check the horizonExtension
. Anything below the horizon is not part of the sky background. But, you can stretch the sky dome with this value. Or, make sure that you are looking above the horizon.
Lights need to be visible
, but this is the default. Which renderer do you use? SciVis needs to additionally have visibleLights
on (which is off by default), the Path Tracer will show it always (if the light is visible
). Also, if you have a bright / white backgroundColor
set in the renderer then the sky will be "hidden".
I am using the pathtracer , the background is always white in the rendering. I have set backColor to (0,0,0) One thing to underline is that my environment has Z upvector , X-Y plane of Horizon, how does the software get this info ?
Ok, sorry I have found again that the up vector was still wrong. Now it works fine. thanks for your effort.
I am a beginner with OSPray so putting all at work requires more than reading the docs
Here is my SunSky
No error, but in the rendering I do not see the sun light , nor shadows, so something is wrong Any hint on how to detect the issue ?