Hey Vincent, at 11:00, for HDRI, you can open the Node editor and put a 'Colour Correction' node in between the 'Image Texture' and 'Environment' nodes. You will also have to add a 'Transform' node to your 'Image Texture' and rotate your HDRI by adjusting the 'T.X' slider (transform by X axis), as the 'RotX' and 'RotY' in Environment controls will not work after this
At 20:50 you mention the limitations of multiply/add/mix nodes. I was having the same frustration with it too today until I realized that you're supposed to use composite texture node for anything more advanced than a quick mix. The composite and layer system gets pretty nutty.
Octane has got a lot more stable from 4 years to now. Other things also reduce number if crashes: example:set to use no multi thread of CPU for Octane processes helps a lot.
When you lock your liveviewer, there a two numbers on the side "1" and "1". This are your scale values for the liveviewer. The first number scale your renderview just as you did in your rendersettings but keeps your rendersettings not touched. The second one scales just the window size of your liveviewer but not changing the actual rendersize and rendertime. Sounds strange but I hope this is a little help.
Hi there, Im an amateur!! I have a project that was built on Redshift. My PC has a buit-in card which means a GPU si out of question. A few questions: Can Redshift work exclusively with CPU? Can Octane work exclusivly with CPU? Is it possible for the Redshift project to swich "automatically/easy" to Octane? Thank you guys!!
Good decision to go back to octane redshift is way to overhyped because its speed.but it also looks like a cheaper solution.... Octane looks awesome even without an hdri and materials on ur stuff. But i can agree that it is more stable than ever before. I also switched because of that way back. But i was always disappointed of redshift because its only good for small product viz stuff but it always has this lack of realizm. Anyways welcome back to the octane Family buddy 🔥😄
hmm I don't think it's true. Redshift is much more robust and production-ready. If you dig in VFX Behind-The-Scenes and you'll find Octane is mostly used for Pre-production and Look dev only. TBH even Redshift is not quite used in the final rendering for big blockbuster films but Arnold/Renderman/Vray, or mostly CPU-based. But I gotta say this random walk SSS from Octane is HOT.
![SahBabii - Viking [Official Music Video]](http://i.ytimg.com/vi/D37cL92JX0I/mqdefault.jpg)
Hey Vincent, at 11:00, for HDRI, you can open the Node editor and put a 'Colour Correction' node in between the 'Image Texture' and 'Environment' nodes. You will also have to add a 'Transform' node to your 'Image Texture' and rotate your HDRI by adjusting the 'T.X' slider (transform by X axis), as the 'RotX' and 'RotY' in Environment controls will not work after this
thanks☺
This doesn't work for me, the only rotation axis that works is Z and this is just distorting it, X and Y don't do annything
At 20:50 you mention the limitations of multiply/add/mix nodes. I was having the same frustration with it too today until I realized that you're supposed to use composite texture node for anything more advanced than a quick mix. The composite and layer system gets pretty nutty.
So glad to see this video, more people coming back to Octane, it is still my fav, thank you.
Would love to have more videos on Octane from you!
Just bought the course! I was so surprised by the discounted price for it. Your tutorials are fantastic so I look forward to taking the course.
Octane has got a lot more stable from 4 years to now. Other things also reduce number if crashes: example:set to use no multi thread of CPU for Octane processes helps a lot.
Hit the lock, then roll your middle mouse wheel. You can have it look just like redshift does for the IPR part.
thanks
@@vincentschwenk No problem, I'm moving back to octane myself. My #1 complaint is redshift won't let me see transparency in the ipr.
Finally!! Time to become a patreon
When you lock your liveviewer, there a two numbers on the side "1" and "1". This are your scale values for the liveviewer. The first number scale your renderview just as you did in your rendersettings but keeps your rendersettings not touched. The second one scales just the window size of your liveviewer but not changing the actual rendersize and rendertime. Sounds strange but I hope this is a little help.
I had to switch to redshift. Octane is just crashing too much on mac (metal). They also discontinued metal support. M1/2 might be a different story.
One question. How fast is the Octane team to listen to user's feedback and implement new features or correct bugs?
Hi there, Im an amateur!! I have a project that was built on Redshift. My PC has a buit-in card which means a GPU si out of question. A few questions: Can Redshift work exclusively with CPU? Can Octane work exclusivly with CPU? Is it possible for the Redshift project to swich "automatically/easy" to Octane? Thank you guys!!
Good decision to go back to octane redshift is way to overhyped because its speed.but it also looks like a cheaper solution.... Octane looks awesome even without an hdri and materials on ur stuff.
But i can agree that it is more stable than ever before. I also switched because of that way back. But i was always disappointed of redshift because its only good for small product viz stuff but it always has this lack of realizm. Anyways welcome back to the octane Family buddy 🔥😄
hmm I don't think it's true. Redshift is much more robust and production-ready. If you dig in VFX Behind-The-Scenes and you'll find Octane is mostly used for Pre-production and Look dev only. TBH even Redshift is not quite used in the final rendering for big blockbuster films but Arnold/Renderman/Vray, or mostly CPU-based.
But I gotta say this random walk SSS from Octane is HOT.
Is Octane faster in rendering than Redshift?
-Nvidia user here
:)