Awesome thanks Aoktar ! you rockStudio21 wrote:ohhhh....just found there is a new search bar in the node editor
Test Version 3.07-Test6a
Moderators: ChrisHekman, aoktar
:::::::::::::::::
pxlntwrk.net
pxlntwrk.net
I'm not sure yet but i'll look for a way.Josef wrote: Oh shit, so this is possible ? haha, would love a commander like function in the node editor
Octane For Cinema 4D developer / 3d generalist
3930k / 16gb / 780ti + 1070/1080 / psu 1600w / numerous hw
3930k / 16gb / 780ti + 1070/1080 / psu 1600w / numerous hw
This change is bad for some Mac users with Nvidia cards (obviously all Octane mac users have Nvidia cards).It's now 18.057
That build of Cinema is crashing on every launch (on Mac) with the only version of the Nvidia web drivers that work with 10.12. (It IS possible to launch . 057 with osx Terminal w/o crash, or launch again after crash and use, but something is definitely wrong with that build's compatibility with Nvidia on my system. I'm not at home to double check all of this, but the problem cropped up months ago and I haven't seen an updated Nvidia driver since. I saw the note here and my eyes popped out.
I've been using previous R18 build .041 version only for that reason, and this updated requirement for Octane has me reeling at what to do next. I don't expect much or any further updates to R18, and I don't expect to update to R19 in the immediate future. Kind of bummed about this one. What's the reason for the requirement update?
I had to benefit from some fixes in R18(alpha bug in opengl, etc..).bododge wrote:This change is bad for some Mac users with Nvidia cards (obviously all Octane mac users have Nvidia cards).It's now 18.057
That build of Cinema is crashing on every launch (on Mac) with the only version of the Nvidia web drivers that work with 10.12. (It IS possible to launch . 057 with osx Terminal w/o crash, or launch again after crash and use, but something is definitely wrong with that build's compatibility with Nvidia on my system. I'm not at home to double check all of this, but the problem cropped up months ago and I haven't seen an updated Nvidia driver since. I saw the note here and my eyes popped out.
I've been using previous R18 build .041 version only for that reason, and this updated requirement for Octane has me reeling at what to do next. I don't expect much or any further updates to R18, and I don't expect to update to R19 in the immediate future. Kind of bummed about this one. What's the reason for the requirement update?
This build is running fine on my Sierra(10.12).
Octane For Cinema 4D developer / 3d generalist
3930k / 16gb / 780ti + 1070/1080 / psu 1600w / numerous hw
3930k / 16gb / 780ti + 1070/1080 / psu 1600w / numerous hw
Hi bododge,
about Sierra, R18, and Nvidia drivers, please, have a look at this other discussion:
viewtopic.php?f=30&t=61724
ciao beppe
about Sierra, R18, and Nvidia drivers, please, have a look at this other discussion:
viewtopic.php?f=30&t=61724
ciao beppe
Will try that solution tonight! Thanks for the heads up.bepeg4d wrote:Hi bododge,
about Sierra, R18, and Nvidia drivers, please, have a look at this other discussion:
viewtopic.php?f=30&t=61724
ciao beppe
Hello Aoktar,
Is there a way to ajust the texture of an instance color or apply a transform node to it ?
As you can see in my example screenshot, I have a cloner where "Render instances" is ticked. I need to apply a bitmap on it, and it doesn't work.
Do you have any solution ? Thank you
Is there a way to ajust the texture of an instance color or apply a transform node to it ?
As you can see in my example screenshot, I have a cloner where "Render instances" is ticked. I need to apply a bitmap on it, and it doesn't work.
Do you have any solution ? Thank you
Last edited by FxDesign on Tue Oct 03, 2017 9:56 am, edited 1 time in total.
Hey Aoktar!
Is it possible the Node Editor: Solo mode for textures- feature update has a bug that does not let me un-solo a texture? And does the texture need to be connected to a port on the shader in order to be able to solo it?
Thank you very much in advanced, and thanks for everything you've done so far!
Is it possible the Node Editor: Solo mode for textures- feature update has a bug that does not let me un-solo a texture? And does the texture need to be connected to a port on the shader in order to be able to solo it?
Thank you very much in advanced, and thanks for everything you've done so far!


