Feature request: WASD navigation keys

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
Rikk The Gaijin
Licensed Customer
Posts: 1528
Joined: Tue Sep 20, 2011 2:28 pm
Location: Japan

Can we have a keyboard navigation system like most 3D engines have? I would especially copy the Unreal Engine 4 one, in my opinion it's the best.
For the ones unfamiliar with it, it's a navigation system that mimics the way you move in First Person Shooter games.
W = move forward
A = strafe left
S = move backward
D = strafe right
E = move up
Q = move down
RMB = free look
RMB + wheel = increase/decrease movement speed.

This is particularly efficient when navigate environment scenes.
User avatar
Goldorak
OctaneRender Team
Posts: 2321
Joined: Sun Apr 22, 2012 8:09 pm
Contact:

This can be done (sort of) through lua script nodes, with the timer callback. We used this to test a dummy GL viewport that shadowed the current Octane RT, and reflect any changes made to the node graph in the Octane UI. Conversely, the GL window could capture input events and change the camera node.

We may need to clean up some of how this works before we make lua nodes 'non-experimental'. In the ORBX viewer you can set up a lua script node to process user/device input for custom navigation schemes.
Rikk The Gaijin
Licensed Customer
Posts: 1528
Joined: Tue Sep 20, 2011 2:28 pm
Location: Japan

Goldorak wrote:This can be done (sort of) through lua script nodes, with the timer callback. We used this to test a dummy GL viewport that shadowed the current Octane RT, and reflect any changes made to the node graph in the Octane UI. Conversely, the GL window could capture input events and change the camera node.

We may need to clean up some of how this works before we make lua nodes 'non-experimental'. In the ORBX viewer you can set up a lua script node to process user/device input for custom navigation schemes.
Does this mean is it basically done and it only needs to be included in the next version? :twisted:
Post Reply

Return to “General Discussion”