All the above is especially true when you realize that the user is most likely using many programs in the pipeline, and each of those have their own particular ways of doing things. So using mouse navigation as an example, I'm sure all of us have run into those times when we accidentally used the mouse buttons and keystrokes that were meant to be used in some other program. That's not a problem when the mistake is not critical, but it seems there should be attention paid to critical types of mistakes that can really ruin your day. We all need some idiot-proofness.
Mouse navigation user confusion
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
Hey, I think there is a really annoying situation in Octane, and I am not so sure what the best solution would be. It has to do with the fact that the usage of the CNTL key to determine whether you are zooming/panning the camera or zooming/panning the image can be very easily confused and especially if you are tired, you can accidentally zoom/pan the camera which immediately restarts the render. After a 15 hour render and counting, to have to start all over again is really bad, especially if you are on a deadline. There is also a situation where even if you have the CNTL key down (using the default preferences settings), accidentally moving the mouse and pressing/scrolling the mouse middle button can cause a change to the camera or its focus. There should be a definite something somewhere that does a better job of preventing accidental changes to the camera when you absolutely don't want it to change, after a render starts. This problem extends to when the mouse is over a slider, thereby handing the focus over to it. It is very easy to screw up and pay for it because there aren't enough checks and balances to prevent common mistakes unless you are always super-human careful.
All the above is especially true when you realize that the user is most likely using many programs in the pipeline, and each of those have their own particular ways of doing things. So using mouse navigation as an example, I'm sure all of us have run into those times when we accidentally used the mouse buttons and keystrokes that were meant to be used in some other program. That's not a problem when the mistake is not critical, but it seems there should be attention paid to critical types of mistakes that can really ruin your day. We all need some idiot-proofness.
All the above is especially true when you realize that the user is most likely using many programs in the pipeline, and each of those have their own particular ways of doing things. So using mouse navigation as an example, I'm sure all of us have run into those times when we accidentally used the mouse buttons and keystrokes that were meant to be used in some other program. That's not a problem when the mistake is not critical, but it seems there should be attention paid to critical types of mistakes that can really ruin your day. We all need some idiot-proofness.
Win7 | Geforce TitanX w/ 12Gb | Geforce GTX-560 w/ 2Gb | 6-Core 3.5GHz | 32Gb | Cinema4D w RipTide Importer and OctaneExporter Plugs.
DoH! Maybe I should.........RTFM.
As for locking the node inspector side, are there any plans in the big list of things to do to support that?
Thanks, Roeland.
As for locking the node inspector side, are there any plans in the big list of things to do to support that?
Thanks, Roeland.
Win7 | Geforce TitanX w/ 12Gb | Geforce GTX-560 w/ 2Gb | 6-Core 3.5GHz | 32Gb | Cinema4D w RipTide Importer and OctaneExporter Plugs.
Once you turn off the material selection preview button (sorry, I can't remember the exact name), then it gets a lot better. That way you can select any material node and you still view your scene as you would expect.
As for middle mouse wheel, I too think they should limit that functionality so that the mouse wheel won't adjust material properties accidently, then that causes a restart of the render and you can't undo the change!
As for middle mouse wheel, I too think they should limit that functionality so that the mouse wheel won't adjust material properties accidently, then that causes a restart of the render and you can't undo the change!
GTX 470 | 16 gigs | AMD 1090T | Win7-x64 | Maya til death!
I agree. And thanks for that tidbit on the material preview part. I keep stepping into these navigation potholes. Can't break the habit! 
Win7 | Geforce TitanX w/ 12Gb | Geforce GTX-560 w/ 2Gb | 6-Core 3.5GHz | 32Gb | Cinema4D w RipTide Importer and OctaneExporter Plugs.

