I feel that adding these features as options to Blender that the user could enable would make Modelling faster and more intuitive. The user Right-Clicks to exit out of Tweak-Mode. Tweak-Mode enables quick modifications to a mesh by manipulating one piece of geometry at a time. Instead of using a keyboard-shortcut to trigger the Translate, the user simply click and drags to move the Preselection-Highlighted Vertex, Edge or Face and releases the mouse to Confirm.
The Ability to Use Preselection-Highlighting as a Temporary-Selection is also enabled. The user clicks to finish the Mesh-Operation and the Temporary-Selection is cleared resulting in the user being back in Preselection-Highlighting Mode.Ĥ) Tweak-Mode: A mode where Preselection-Highlighting is enabled with the default mesh-operation being Translate. If the user clicks a Vertex, Edge or Face to select then that is the Selection but if the user instead presses a keyboard-shortcut for a Mesh-Operation (such as Extrude, Translate, Rotate, Scale, etc) then the Geometry that is Highlighted is taken as the selection for the Mesh-Operation. This option is especially useful when combined with Preselection-Highlighting.ģ) The Ability to Use Preselection-Highlighting as a Temporary-Selection for Mesh-Operations: After Deselecting-All with Preselection-Highlighting enabled, the Closest Edge, Face or Vertx is temporarily Highlighted. The first piece of geometry that the user Selects becomes the Mesh-Select-Mode.
The user can then click to Select Geometry with the knowledge of exactly what is being Selected.Ģ) The Ability to have Mesh-Select-Mode set to the type of the first piece of geometry selected after a Deselect-All: After Deselecting-All in Edit-Mode, the user can Select a Vertex, Edge or Face. I think it would be a good idea to implement Preselection-Hightlighting into the Blender Modelling Tools:ġ) Preselection-Highlighting: Preselection-Highlighting is the ability to hover the mouse over a Mesh in Edit-Mode and continuously have the Closest Edge, Face or Vertex temporarily Highlight.
And granted, this is a gross, oversimplification, but I hope that it is apparent why a CPU might not be as fast as a GPU even when it seems like the CPU is huge. if we can only do one of the 1024 things at a time, the CPU blazes past the GPU (still slower overall because only 1 core can be used). If we start adding more things to compute, it will only take longer!īut the key is is that we can do each of those 1024 things at the same time, which is not always the case. By comparison, you CPUs will do it in over 10 seconds! (1024 things / ( 24 cores*4 times as fast)). Computing 1 thing a second (intuition!) your GPU will do it in 8 seconds (1024 things/128 cores). Now, lets say you need to computer 1024 things, and we can do any combination of them at the same time. For your GPU, you have 128 cores, but again, each slower than the CPU. Take for instance, a general case where a CPU core is 4x faster than the GPU core (not accurate but this is for intuition again!). Current hybrid accelerations don't work well due to overhead of communicating between the GPU and CPU, but hopefully that paradigm is changing.īut anyway, for an intuitive idea of why a GPU might be faster than a CPU, let me give a quick example (I know you might already understand this but some other people who read through here might not, so I hope to help them too). Actually, a GPU might still outpace a CPU even with 24 cores (my understanding of virtual cores is that they do not contribute to faster computations, they just divide the use of a core's time between two processes more easily, correct me if I'm wrong as I tend to be).
0 kommentar(er)
