Node editor broken again

Wed Mar 01, 2017 12:34 pm

A -Win 8.1
B- 2 x GTX 1080, GTX TITAN
C - 64 GB
D - 376.53
E, F - 3.05.3
G - R18.041

If I drag & drop a texture to the Image Texture node it looks like it's loaded but if I select the node again, the texture is gone. If I drag it from the Content Browser nothing happens.

Wed Mar 01, 2017 12:50 pm

It's a C4D window. And i have no control over this. All operations as drag&drop are handled by C4D CORE not plugin. So you have to ask to MAXON.

Wed Mar 01, 2017 11:29 pm

aoktar wrote:It's a C4D window. And i have no control over this. All operations as drag&drop are handled by C4D CORE not plugin. So you have to ask to MAXON.

So I should ask Maxon why your plugin's not working correctly? Maybe they'll say something about making proper use of their API or something..
This is yet another simple thing that's only a problem with Octane, nowhere else and in no other plugin.

Wed Mar 01, 2017 11:54 pm

preciousillusion wrote: This is yet another simple thing that's only a problem with Octane, nowhere else and in no other plugin.

Neither of them are using this dialog. Most are on xpresso interface and gui controls of xpresso and Octane plugin is not based on. You can drag images over icon's of ImageTextures. It will replace.

Thu Mar 02, 2017 2:41 am

aoktar wrote:
preciousillusion wrote: This is yet another simple thing that's only a problem with Octane, nowhere else and in no other plugin.
Neither of them are using this dialog. Most are on xpresso interface and gui controls of xpresso and Octane plugin is not based on. You can drag images over icon's of ImageTextures. It will replace.

Then how is your solution not inferior?
How much workflow crippling are we supposed to endure?
Where, or rather, when can I find a single benefit from this?

Thu Mar 02, 2017 3:56 am

How about you being more polite? I should not even bother but the way the Octane node editor is build allows for a much faster workflow and by not using the standard API it also allows for greater development in future releases, compare it to the one that Arnold uses which is built with the C4D API and you will see the Octane solution is faster and nicer to work with, well if you are willing to admit it that is. Also you can always go back to a version of the plugin that was working for you while you properly report the problem and lastly when you open the node editor if you can read it it says "WIP" in the title bar.

Thu Mar 02, 2017 6:55 pm

Terryvfx wrote:How about you being more polite? I should not even bother but the way the Octane node editor is build allows for a much faster workflow and by not using the standard API it also allows for greater development in future releases, compare it to the one that Arnold uses which is built with the C4D API and you will see the Octane solution is faster and nicer to work with, well if you are willing to admit it that is. Also you can always go back to a version of the plugin that was working for you while you properly report the problem and lastly when you open the node editor if you can read it it says "WIP" in the title bar.

Me not being polite enough might have something to do with mostly getting weird/contradicting/untrue/unrelated/plain stupid/incomprehensible or even rage bursts, derived from god-knows-what pile of personal problems, as answers from Otoy. Feel free to pick a category for the “ask Maxon.." answer for example.
Or, you know, 10 months after release the documentation is still not complete.

From my, somewhat limited, experience with Arnold I would argue quite the opposite. And it works.
I've read “WIP”, it's been there forever..
Speaking of “WIP”, ever since Aoktar said that the node system is the foundation of the plugin on top of which everything relies, I’ve been waiting for an answer on how it’s possible that the whole plugin’s not considered “WIP”?