Hi,
This is with regards to the Octane demo:
I am a bit confused as to some of the node behavior.
If I start up Octane and import a mesh into the unsaved project (only node on screen), I can adjust its parameters and watch the changes in real time. How is this possible when no other nodes are present except for the nodes in the Preview Config. Macro which I thought was just a macro you could build upon if you wanted to copy its contents into your unsaved project? In other words, aren't the Preview Config and Unsaved Project tabs two separate "realities" that don't talk to one another? My first tests seem to say they DO interact.
Now, if I delete all the nodes in the Preview Config Macro (the only node that can't be deleted is the Render Target node), then my rendering goes black. So I go into my unsaved project and add camera, target, environment, etc., but now I cannot change the mesh parameters in real-time...The render just goes black. I can only watch the render in real-time when the RenderTarget node is clicked, and RMB>"Render".
One last item...If I do not add a Material node to connect with my mesh, but instead just use the material sliders in the Mesh node, If I choose "Specular" as the material type, I find that all of the sliders appear to work correctly except for the Index slider...the Index behaves as if it is always zero. But if I add and connect a Specular Material node to the corresponding material pin on the Mesh node, refraction behaves normally.
Thanks for any help!
Confused about node behavior
Forum rules
For new users: this forum is moderated. Your first post will appear only after it has been reviewed by a moderator, so it will not show up immediately.
This is necessary to avoid this forum being flooded by spam.
For new users: this forum is moderated. Your first post will appear only after it has been reviewed by a moderator, so it will not show up immediately.
This is necessary to avoid this forum being flooded by spam.
regarding your last point: this works as expected with the regular version; might be a bug in the demo...
about your other points: you imo need to dig a little into how rendertargets work/are meant to be used; it is not perfectly obvious in first place, but as far as not covered in the manual already, this tutorial series from a fellow forum member should help: http://www.youtube.com/playlist?list=PL0DBA6671E0A1743B
about your other points: you imo need to dig a little into how rendertargets work/are meant to be used; it is not perfectly obvious in first place, but as far as not covered in the manual already, this tutorial series from a fellow forum member should help: http://www.youtube.com/playlist?list=PL0DBA6671E0A1743B
„The obvious is that which is never seen until someone expresses it simply ‟
1x i7 2600K @5.0 (Asrock Z77), 16GB, 2x Asus GTX Titan 6GB @1200/3100/6200
2x i7 2600K @4.5 (P8Z68 -V P), 12GB, 1x EVGA GTX 580 3GB @0900/2200/4400
1x i7 2600K @5.0 (Asrock Z77), 16GB, 2x Asus GTX Titan 6GB @1200/3100/6200
2x i7 2600K @4.5 (P8Z68 -V P), 12GB, 1x EVGA GTX 580 3GB @0900/2200/4400
This post is specifically about render targets: http://refractivesoftware.com/forum/vie ... =21&t=7300 .
--
Roeland
--
Roeland