Weird Problem + Crash

[dannrees]

If I link an image to a material channel in the graph editor. Then remove the link. I can no longer access those material parameters in the node inspector. If I reattach the image in the node graph it appears again in the node inspector. If I then change it from the channel input from image/floatimage to something else (like rgbspectrum for example) then the application crashes.I tried it a couple of times and it doesnt always crash.

HOWEVER....

Changing parameters in the node editor and in the graph editor dont update between themselves. So for instance if I attach an image to a diffuse (or any) slot in the graph editor. Then in the node editor change it from image to rgbspectrum (or anything else). The link remains in the graph editor. Then removing the link in the graph editor removes the channel from the node editor! If I then reattach the image to the diffuse (or any) slot in the graph editor the node editor shows the channel again but doesn't update with the new input and still thinks it's what it was before, in this case rgbspectrum.

Steps to reproduce problem...

1) Create a material in the graph editor
2) Add a new image texture in the graph editor
3) Select the material in the graph editor (so you can see the node editor)
4) Attach the image texture to the diffuse channel of the material in the graph editor
5) Disconnect the node you just connected (And watch the diffuse channel disappear from the node editor)
6) Re-attach the image texture to the diffuse slot (Diffuse channel reappears in the node editor)
7) Change the diffuse channel input in the NODE EDITOR to RgbSpectrum (Notice the link to the image texture remains in the graph editor)
8) Detach the image texture from the diffuse channel in the graph editor (Diffuse channel disappears again in the node editor)
9) Reattach the image texture to the diffuse channel in the graph editor (Node editor shows diffuse channel again, but still shows it as RGB Spectrum)

!!!!! What the !!!!!!

It would be nice if you could not only fix this, but also if you make changes in the node editor it will make the relevant graph for you. Makes sense to me...

Thanks

[dannrees]

Nobody else familiar with this?

[pixelrush]

Hi,
The demo version that is available atm is a fairly early beta, almost alpha.
As such there were some unfinished bits of code and of course crash producing bugs in it.
The nodes part of the code wasnt really sorted out and functional IIRC.
I wouldnt spend too much time on using nodes in the Graph Editor but rather play around with materials in the Node inspector and decide how you like the navigation, performance etc.
Its really a technology demonstrator ie it gives you a taste of what GPU rendering is about and hopefully gets you interested in buying an introductory license.
There will probably be an update for the Demo version soon if you are still uncertain about the worth of Octane and want to play some more.
Personally I feel we have moved on a fair bit in development in the commercial license version from the present demo in terms of features and stability.
I am not sure that it represents the product to newbies especially well.
I think Refractive would say something similar.
I hope that helps.
If you have any more concerns or questions feel free to post them and someone whether they are a user or from the company will be pleased to answer you I think.
The Refractive guys are pretty hard working and they are progressing well even though being a pioneer is tough going at times
BTW I am a user just helping out others on the forums.

[radiance]

we're working hard on getting public demos out on our videos page of the upcoming customer only 2.3 v5

Radiance