[Bug] 2.43 Windows - Slider value problems

A forum where development builds are posted for testing by the community.
Forum rules
NOTE: The software in this forum is not %100 reliable, they are development builds and are meant for testing by experienced octane users. If you are a new octane user, we recommend to use the current stable release from the 'Commercial Product News & Releases' forum.
Post Reply
User avatar
PolygonPusher
Licensed Customer
Posts: 45
Joined: Fri Feb 04, 2011 4:00 pm
Location: St.Loius
Contact:

I almost thought to report this as a request because though it works, just not the way that makes it functional.

ok heres the way to reproduce the problem:
  • Load any material ball.
  • Goto the camera node
  • Change the pos ("position") on any of the axis.
Problem:
The stepper increments in such great values that it makes the usability of the slider useless. In my example this results in not being able to navigate the camera in a usable way via the sliders with out entering the exact values in by hand.

Solution:
Allow the assignment of the min/max for floats, ints and any other numerical value.
also a bonus would be to allow the assignment of step increments also

This could be accomplished but creating input nodes for setting the min/max and step increments
polyon-pushers.org| Flickr| twitter | vimeo
spec: i7 975 3.33ghz | 12 gigs ram | gtx 260 - 195 cuda cores | win 7 64bit | blender 3d | Octane 2.43
IRC: freenode - #blenderchat - #blendercoders - #octanerender
Post Reply

Return to “Development Build Releases”