Please dont insult my intelligence with smart ass remarks about magic buttons.
If you have read and understood what I have spoken of in this thread you will know that
I am enthusiastic about working with fully functional software that has the tutorial support to aid in enhanced and accelerated learning. In my experience that is not where Octane is right now.I really hope that it will be in the future.
Language does seem problematic with this product as well. You might want to consider hiring someone with a good grasp of English to assist you with the content, grammar, and spelling in your manuals and also posts here at the web site.
Good communications are key with complicated products like Octane.
Bye bye and good luck.
Trying to like Octane but not succeeding
Forum rules
Please add your OS and Hardware Configuration in your signature, it makes it easier for us to help you analyze problems. Example: Win 7 64 | Geforce GTX680 | i7 3770 | 16GB
Please add your OS and Hardware Configuration in your signature, it makes it easier for us to help you analyze problems. Example: Win 7 64 | Geforce GTX680 | i7 3770 | 16GB
You don't seem to understand what everyone's been trying to say. If you have a good grasp of the C4D interface, learning Octane Standalone is essentially the same as learning the plugin. The same features in Standalone propagate over to the plugin, and behave exactly the same. All you need, then, is the plugin tutorial which tells you where all the buttons from Standalone are in C4D (I'm assuming that's the case, I haven't actually watched the tutorial).
Let's set up a scenario here:
User is attempting to learn Octane for C4D, but things don't work as expected. User tries to learn Octane within C4D, but fails. User spends a short amount of time learning Octane Standalone. User can now use Octane for C4D.
The latter part of that, in my opinion, is what you should be doing.
When you consider the amount of time saved with the speed of rendering with Octane, so long as it doesn't take you an obtuse amount of time to learn (Octane was my first external rendering engine, and I picked it up within days without tutorials), it is well worth learning.
Bottom line: if learning Octane exclusively for C4D isn't working for you, learn Standalone, and the rest will shortly follow. Don't assume that Octane Standalone and Octane for C4D are mutually exclusive. They're both one and the same at heart.
P.S. Your offence taken to a remark about magic buttons is a joke 3D artists tend to make about great renders. Continuing on to insult the English capabilities of that person isn't a good look.
Let's set up a scenario here:
User is attempting to learn Octane for C4D, but things don't work as expected. User tries to learn Octane within C4D, but fails. User spends a short amount of time learning Octane Standalone. User can now use Octane for C4D.
The latter part of that, in my opinion, is what you should be doing.
When you consider the amount of time saved with the speed of rendering with Octane, so long as it doesn't take you an obtuse amount of time to learn (Octane was my first external rendering engine, and I picked it up within days without tutorials), it is well worth learning.
Bottom line: if learning Octane exclusively for C4D isn't working for you, learn Standalone, and the rest will shortly follow. Don't assume that Octane Standalone and Octane for C4D are mutually exclusive. They're both one and the same at heart.
P.S. Your offence taken to a remark about magic buttons is a joke 3D artists tend to make about great renders. Continuing on to insult the English capabilities of that person isn't a good look.
Core i7 950 @3.07GHz | GTX 460 2GB | 12GB RAM | Window 7 x64
(HW) Intel i7 2600k, 16GB DDR3, MSI 560GTX ti (2GB) x 3
(SW) Octane (1.50) Blender (2.70) (exporter 2.02)
(OS) Windows 7(64)
(SW) Octane (1.50) Blender (2.70) (exporter 2.02)
(OS) Windows 7(64)

+1
Don't feed the troll, guys.

Win 8.1 x64, i7-4930K 64GB, 2 x GTX-690
I'm writing for last one to this post.
I'm also a 3d generalist with lot of experience on most 3d software (3dsmax, maya, blender, xsi, Lw, C4d, etc...) and renderers(nearly all of them). I don't think Octane is harder than other renderers. Expecially some of them is much complicated and mysterious. Needs lot of deeper shader and scripting experiences. So learning for wishfull people is not hard and not takes long period. standalone experience is a plus.
I suppose most people give credits about the our work. We are trying to help every people to want use and learn it.
Thanks for taking time
I'm also a 3d generalist with lot of experience on most 3d software (3dsmax, maya, blender, xsi, Lw, C4d, etc...) and renderers(nearly all of them). I don't think Octane is harder than other renderers. Expecially some of them is much complicated and mysterious. Needs lot of deeper shader and scripting experiences. So learning for wishfull people is not hard and not takes long period. standalone experience is a plus.
I suppose most people give credits about the our work. We are trying to help every people to want use and learn it.
Thanks for taking time
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