Undo Command
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
When is the undo function going to be available for the stand alone version of Octane Render?, it's really frustrating to change something and not be able to undo what you just did
Regards
Nehale
Windows 10 x64 | 2x GTX680 | i7 990X | 24GB
Cinema 4D R17 Studio + 3Ds Max 2017
OctaneRender™ for Cinema 4D 3.01 + OctaneRender® for 3ds max® v3.14
Nehale
Windows 10 x64 | 2x GTX680 | i7 990X | 24GB
Cinema 4D R17 Studio + 3Ds Max 2017
OctaneRender™ for Cinema 4D 3.01 + OctaneRender® for 3ds max® v3.14
Or at least a value rest function like the "right click on spinner" in C4D to set it to the default value
Regards
Nehale
Windows 10 x64 | 2x GTX680 | i7 990X | 24GB
Cinema 4D R17 Studio + 3Ds Max 2017
OctaneRender™ for Cinema 4D 3.01 + OctaneRender® for 3ds max® v3.14
Nehale
Windows 10 x64 | 2x GTX680 | i7 990X | 24GB
Cinema 4D R17 Studio + 3Ds Max 2017
OctaneRender™ for Cinema 4D 3.01 + OctaneRender® for 3ds max® v3.14
Yah, I run into that too. I find that I have to be super-careful when my mouse is wandering around the nodes on the far right. If I inadvertently rotate the mousewheel over a parameter, I'm screwed. I have to open an earlier version of the project to remember what the value was supposed to be. So I have a habit of saving many versions of a project so that I can always go back to an earlier version if I mess up.
Win7 | Geforce TitanX w/ 12Gb | Geforce GTX-560 w/ 2Gb | 6-Core 3.5GHz | 32Gb | Cinema4D w RipTide Importer and OctaneExporter Plugs.
I also hate that the mouse wheel changes values - like anyone uses the wheel to set parameters. You either grab the sliders, or input exact values manually. The wheel cant be used to scroll the GUI area and change values at the same time - its bad design, because you can inadvertently change values.
Undo also shouldn't be too difficult to implement - all the work you do in Octane can be represented by a stack of value changes in the node graph == perfect for implementing undo (& very light on memory).
Undo also shouldn't be too difficult to implement - all the work you do in Octane can be represented by a stack of value changes in the node graph == perfect for implementing undo (& very light on memory).
SW: Octane 3.05 | Linux Mint 18.1 64bit | Blender 2.78 HW: EVGA GTX 1070 | i5 2500K | 16GB RAM Drivers: 375.26
cgmo.net
cgmo.net
It's funny because I've programmed for years and it is the easiest thing to implement, but no fun at all. It takes time because you have to gather all the parameters, create the stack and so on, and on....No glory. It's like, if you have a programming team and you yell out, "OK...Who wants to do the Undo System?". Everyone will probably call in sick the next day. 

Win7 | Geforce TitanX w/ 12Gb | Geforce GTX-560 w/ 2Gb | 6-Core 3.5GHz | 32Gb | Cinema4D w RipTide Importer and OctaneExporter Plugs.