I think since version 2020.1.PolderAnimation wrote:wauw... thanks. just out of curiosity how long is this feature in octane?galleon27 wrote:Press SpacePolderAnimation wrote:I also want to ask again for the functionality to make searching for node (when creating them) faster. For example Nuke and Houdini use the TAB menu. When pressing TAB you can start typing and the node you are searching for appears. This works incredible intuitive and fast and works way better than right mouse button click and looking through a whole menu and finding you nodes.
I already posted this in the feature request and a lot of people like the idea.
https://render.otoy.com/requests/?qa=46 ... how=46#q46
OctaneRender™ 2020.2.3
In theory there is no difference between theory and practice. In practice there is. - Yogi Berra
Yes that works Juan, but I really want to use the nested dieletrics as I can see on tests that it definately produces better results. Do you remember when you fixed this for the Lightwave plugin before, can this easily be done in the standalone code?
Hi,batman911 wrote:Yes that works Juan, but I really want to use the nested dieletrics as I can see on tests that it definately produces better results. Do you remember when you fixed this for the Lightwave plugin before, can this easily be done in the standalone code?
There is one thing I noticed looking at the image you posted, nested dielectric will need the glass to be a single surface, the requirement here is the mesh has to be water-tight (this was mentioned in the release post).
If you absolutely have to model it that way, the only way is to turn off nested dielectric.
Having said that, I have not looked into your scene, so the above is just a guess, are you able to convert it to an orbx? I don't have lightwave unfortunately.
Thanks,
Wallace
OctaneRender crash when dragging the frame slider to frame 4,almost each time it will crash
the animation orbx file is generated by 3dsmax and anima(by axyz design),
I can upload the .abc file since it is small enough to upload
the animation orbx file is generated by 3dsmax and anima(by axyz design),
I can upload the .abc file since it is small enough to upload
You do not have the required permissions to view the files attached to this post.
Supermicro 4028GR TR2|Intel xeon E5 2697 V3| windows 10| revit 2019 |Titan V+ Quadro GV100+RTX 2080 Ti
Hi, team
This release is great! One question:
Does the "Chaos" node behave like the "Displacement" node regarding UV projection? Does it only work with the mesh UV?
Regards,
This release is great! One question:
Does the "Chaos" node behave like the "Displacement" node regarding UV projection? Does it only work with the mesh UV?
Regards,
You do not have the required permissions to view the files attached to this post.
C4D 2025.1.1 Octane 2025.1 Build 0104, <<2 X 3090 + NVlink>>, Windows 10, X399, AMD TR 1950X, 128 GB RAM, NVIDIA SD 552.22
https://www.behance.net/PaperArchitect
https://www.behance.net/PaperArchitect
Yes at the moment it is limited to the Mesh UV projection.Kalua wrote:Hi, team
This release is great! One question:
Does the "Chaos" node behave like the "Displacement" node regarding UV projection? Does it only work with the mesh UV?
Regards,
-
PolderAnimation
- Posts: 373
- Joined: Mon Oct 10, 2011 10:23 am
- Location: Netherlands
- Contact:
Hi Abstrax, I posted this bug a while ago, but I know see I did not post the example file. So here it the post again with the example file attached.
"Octane has an issue with getting the P_FOCAL_LENGTH pin value from an alembic camera.
We use a scripted graph to get all needed camera info from the alembic camera and plug them into a thinLensCamera node so we can adjust other parameters still.
Up to and including octane 2020.2.1 this works perfect, but in 2020.2.3 the focal length does not seem to get updated when skipping through the timeline.
Attached is an example orbx to showcase the issue. The scripted graph code can be read by opening the orbx in a text editor."
"Octane has an issue with getting the P_FOCAL_LENGTH pin value from an alembic camera.
We use a scripted graph to get all needed camera info from the alembic camera and plug them into a thinLensCamera node so we can adjust other parameters still.
Up to and including octane 2020.2.1 this works perfect, but in 2020.2.3 the focal length does not seem to get updated when skipping through the timeline.
Attached is an example orbx to showcase the issue. The scripted graph code can be read by opening the orbx in a text editor."
You do not have the required permissions to view the files attached to this post.
Win 10 64bit | RTX 3090 | i9 7960X | 64GB
Until Abstrax gives a more thorough answer, here is a work around: if you read the FOV and export that instead, it works. I think the issue is happening because the embedded camera inside your Alembic only has an actual animation on the FOV field, not the focal length. In this case the focal length is calculated on the fly from the coupling between these fields.PolderAnimation wrote:Hi Abstrax, I posted this bug a while ago, but I know see I did not post the example file. So here it the post again with the example file attached.
"Octane has an issue with getting the P_FOCAL_LENGTH pin value from an alembic camera.
We use a scripted graph to get all needed camera info from the alembic camera and plug them into a thinLensCamera node so we can adjust other parameters still.
Up to and including octane 2020.2.1 this works perfect, but in 2020.2.3 the focal length does not seem to get updated when skipping through the timeline.
Attached is an example orbx to showcase the issue. The scripted graph code can be read by opening the orbx in a text editor."