Game Engine-style Right Mouse Viewport
Navigation Just like unreal, engine and source film maker
33.3%
Development Status:
Open
Upvote1Downvote2
t
the_corruption
27 Feb 2025
2 Comments
L
Lauloque
I'd avoid bluntly calling to copy a proprietary software. That's potential for troubles (see
this post
for more context on that), and in the first place it doesn't make a good feature proposal since it assumes that both community members and developers are already familiar with what you refer too, which you can't guarantee.
And to begin with, we don't really have to "copy" anything or add new systems, we can also just make our current tools better. Which is also simpler to implement and maintain.
Instead, I would advise you to flesh out your proposal so that anyone can understand the idea and its potential benefits, and developers passing by should also be able to assess its feasibility without needing to conduct extra research.
Start by describing the current need:
What’s lacking in Blender?
Blender already have quite a bunch of navigation tools, including fly/walk ones.
How are current solutions falling short?
What do they not provide, isn't it possible to customize the keymap to get what you want out of them, ...
What’s the impact?
Highlight how this limitation affects your workflow.
Then, outline potential solutions:
What feature(s) could solve these specific problems?
What it is, what it does, how...
Why is it better?
Compare the proposed feature to Blender’s current tools, explaining how it would improve usability or outcomes.
Integration and usability:
Suggest how this could fit into Blender’s existing interface and workflows.
Mockups or examples:
If possible, create a visual example of how this could look and work in Blender.
1
p
pablovazquez
When proposing ideas, always assume the reader has never used those tools. Describe how it works, what are the shortcuts, etc.
2 Comments
I'd avoid bluntly calling to copy a proprietary software. That's potential for troubles (see this post for more context on that), and in the first place it doesn't make a good feature proposal since it assumes that both community members and developers are already familiar with what you refer too, which you can't guarantee.
And to begin with, we don't really have to "copy" anything or add new systems, we can also just make our current tools better. Which is also simpler to implement and maintain.
Instead, I would advise you to flesh out your proposal so that anyone can understand the idea and its potential benefits, and developers passing by should also be able to assess its feasibility without needing to conduct extra research.
Start by describing the current need:
Then, outline potential solutions:
When proposing ideas, always assume the reader has never used those tools. Describe how it works, what are the shortcuts, etc.