Reporting a bug(?)

Generic forum to discuss Octane Render, post ideas and suggest improvements.
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
Post Reply
adiarc
Licensed Customer
Posts: 63
Joined: Thu Mar 17, 2011 7:32 am

Sometimes, maybe once out of ten times that I click a material with the material picker, the camera angle changes! The main problem is that if the camera position was not an imported one, that specific position is now gone forever. And no, the camera zoom picking mode was not enabled! This is another reason it would be helpful to be able to undo stuff in Octane.

Another thing (not a bug) is that adjusting the camera angle is a pain in itself. It's very hard to move the camera just a little, say 50cm. I made a large architectural model for a client and tried to get a specific angle the client wanted. The smallest movement of the mouse meant at least 1 meter in the model. I tried the camera position sliders too, but the smallest movement of a slider made the model disappear in the horizon (pos), or turn way too much (target). And what about the numerical coordinates? Well how do you control xyz coordinates, such as -1123.5955056? Or do I have a scale issue here or something?

Anyway, would it be possible to make this somehow more practical, something like, for example to turn the camera around z, you would enter the amount, say 10 degrees, and then you would click a button next to it repeatedly and the camera would turn each time that amount. I think this applies elsewhere in Octane too. Sliders are easy and quick but not accurate, while numerical entries are accurate but slow.

adiarc
User avatar
radiance
Posts: 7633
Joined: Wed Oct 21, 2009 2:33 pm

Hi,

Regarding the navigation speed, this is likely due to importing in the wrong unit system and as a result having a model that is 100 or 1000x too large or too small,
which makes it difficult to navigate.

Regarding the picking/motion, we have planned a rewrite of camera navigation soon, so this is already on our list.

Radiance
Win 7 x64 & ubuntu | 2x GTX480 | Quad 2.66GHz | 8GB
adiarc
Licensed Customer
Posts: 63
Joined: Thu Mar 17, 2011 7:32 am

radiance wrote:Hi,

Regarding the navigation speed, this is likely due to importing in the wrong unit system and as a result having a model that is 100 or 1000x too large or too small,
which makes it difficult to navigate.

Regarding the picking/motion, we have planned a rewrite of camera navigation soon, so this is already on our list.

Radiance
I tried scaling the model but it doesn't make any difference, the camera sliders are useless for me, but the numerical system works better. I think a very practical slider for camera axis would be one which ranges from 0 to 360 degrees, instead of something like -100000 to 100000.

Cool re your plans.

adiarc
Post Reply

Return to “General Discussion”