...especially when many sliders (like the placement ones) are useless to begin with, because of their insane value ranges...
so, yeah +1 on disabling mousewheel scolling - and while you're at it. scalable slider ranges would be awesome too...
A Special Please
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
-
slimSpencer
- Posts: 6
- Joined: Thu May 31, 2012 12:58 am
- Location: Germany / Aschaffenburg
tonight i came home and wanted to watch the result from a 12-hour-render. I don't exactly remember if it was just a click or an accidential mouse-wheel-touch, but i just lost these 12 hours of rendertime (and energy-consumption) for nothing! 
I really love the fast development and feature-enhancement of octane - but this (a simple confirmation-dialogue) is the most wanted basic feature ever of octane for me! I deeply ask you to introduce a simple solution for this awkward problem.
thanks / br
I really love the fast development and feature-enhancement of octane - but this (a simple confirmation-dialogue) is the most wanted basic feature ever of octane for me! I deeply ask you to introduce a simple solution for this awkward problem.
thanks / br
E3-1230v3 | 8G | gtx 750 Ti | win 8.1 | blender + octane standalone
slimSpencer wrote:tonight i came home and wanted to watch the result from a 12-hour-render. I don't exactly remember if it was just a click or an accidential mouse-wheel-touch, but i just lost these 12 hours of rendertime (and energy-consumption) for nothing!
I really love the fast development and feature-enhancement of octane - but this (a simple confirmation-dialogue) is the most wanted basic feature ever of octane for me! I deeply ask you to introduce a simple solution for this awkward problem.
thanks / br
In the mean time, lock the main window and turn off the buttons that make it render materials when you click on them. This has really saved me.
Intel quad core i5 @ 4.0 ghz | 8 gigs of Ram | Geforce GTX 470 - 1.25 gigs of Ram
-
slimSpencer
- Posts: 6
- Joined: Thu May 31, 2012 12:58 am
- Location: Germany / Aschaffenburg
this was a bit stupid from me - to be honest, i never used/was aware of the "lock this pane"-button... 
It now should safe me from 95% of my accidential render-restarts. Sometimes, one just oversees obvious things.
Thanks for the info!
It now should safe me from 95% of my accidential render-restarts. Sometimes, one just oversees obvious things.
Thanks for the info!
E3-1230v3 | 8G | gtx 750 Ti | win 8.1 | blender + octane standalone
slimSpencer wrote:this was a bit stupid from me - to be honest, i never used/was aware of the "lock this pane"-button...
It now should safe me from 95% of my accidential render-restarts. Sometimes, one just oversees obvious things.
Thanks for the info!
As a final precaution, right above the node inspector, turn off the button for "Enable/diable viewing of material nodes when selected". Its a sphere with an eye over it.
These 2 things have have fully eliminated any accidental restarts from me.
(Now, I have accidentally saved the .ocs file and not the actual image and then closed the program... What I really want is an auto save feature)
Intel quad core i5 @ 4.0 ghz | 8 gigs of Ram | Geforce GTX 470 - 1.25 gigs of Ram