Shortcut for setting origin to vertex












5












$begingroup$


I find myself doing the following quite often:




  1. go into edit mode

  2. select a single vertex

  3. press Space to enter the search menu

  4. type cur


  5. select Set cursor to active



    Set cursor to active



  6. leave edit mode

  7. press Shift+Ctrl+Alt+C to get the set origin choices


  8. Choose Set origin to 3D cursor



    Set origin to 3D cursor




This seems like a very tedious process to me. I'm sure there's a shorter version of setting the origin to a vertex. Please tell me how to make this process more efficient.



I am open to installing an Addon if necessary.






shortcut 3d-cursor origin







share|improve this question











$endgroup$








  • 2




    $begingroup$
    OK, but I hope somebody will give a more complete answer, because i do this steps quite often too and a way to automate it would be handy.
    $endgroup$
    – thibsert
    yesterday










  • $begingroup$
    I don't think there is any built-in way as of 2.79. There were talks it will be In 2.8. With addons it can be made faster, like with Dynamic Context menu (built-in one), see blender.stackexchange.com/a/71319/1245. There are also some 3-rd party addons as well though their workable state is to be checked
    $endgroup$
    – Mr Zak
    yesterday






  • 1




    $begingroup$
    Related: blender.meta.stackexchange.com/questions/2387/…
    $endgroup$
    – batFINGER
    yesterday










  • $begingroup$
    lol, don't be sorry.. I love that question (and especially the deleted answer) it appeals to my warped SOH. Post it whenever I'm given the opportunity.
    $endgroup$
    – batFINGER
    yesterday
















5












$begingroup$


I find myself doing the following quite often:




  1. go into edit mode

  2. select a single vertex

  3. press Space to enter the search menu

  4. type cur


  5. select Set cursor to active



    Set cursor to active



  6. leave edit mode

  7. press Shift+Ctrl+Alt+C to get the set origin choices


  8. Choose Set origin to 3D cursor



    Set origin to 3D cursor




This seems like a very tedious process to me. I'm sure there's a shorter version of setting the origin to a vertex. Please tell me how to make this process more efficient.



I am open to installing an Addon if necessary.






shortcut 3d-cursor origin







share|improve this question











$endgroup$








  • 2




    $begingroup$
    OK, but I hope somebody will give a more complete answer, because i do this steps quite often too and a way to automate it would be handy.
    $endgroup$
    – thibsert
    yesterday










  • $begingroup$
    I don't think there is any built-in way as of 2.79. There were talks it will be In 2.8. With addons it can be made faster, like with Dynamic Context menu (built-in one), see blender.stackexchange.com/a/71319/1245. There are also some 3-rd party addons as well though their workable state is to be checked
    $endgroup$
    – Mr Zak
    yesterday






  • 1




    $begingroup$
    Related: blender.meta.stackexchange.com/questions/2387/…
    $endgroup$
    – batFINGER
    yesterday










  • $begingroup$
    lol, don't be sorry.. I love that question (and especially the deleted answer) it appeals to my warped SOH. Post it whenever I'm given the opportunity.
    $endgroup$
    – batFINGER
    yesterday














5












5








5


1



$begingroup$


I find myself doing the following quite often:




  1. go into edit mode

  2. select a single vertex

  3. press Space to enter the search menu

  4. type cur


  5. select Set cursor to active



    Set cursor to active



  6. leave edit mode

  7. press Shift+Ctrl+Alt+C to get the set origin choices


  8. Choose Set origin to 3D cursor



    Set origin to 3D cursor




This seems like a very tedious process to me. I'm sure there's a shorter version of setting the origin to a vertex. Please tell me how to make this process more efficient.



I am open to installing an Addon if necessary.






shortcut 3d-cursor origin







share|improve this question











$endgroup$




I find myself doing the following quite often:




  1. go into edit mode

  2. select a single vertex

  3. press Space to enter the search menu

  4. type cur


  5. select Set cursor to active



    Set cursor to active



  6. leave edit mode

  7. press Shift+Ctrl+Alt+C to get the set origin choices


  8. Choose Set origin to 3D cursor



    Set origin to 3D cursor




This seems like a very tedious process to me. I'm sure there's a shorter version of setting the origin to a vertex. Please tell me how to make this process more efficient.



I am open to installing an Addon if necessary.






shortcut 3d-cursor origin




shortcut 3d-cursor origin






share|improve this question















share|improve this question













share|improve this question




share|improve this question








edited yesterday







Thomas Weller

















asked yesterday









Thomas WellerThomas Weller

656617




656617








  • 2




    $begingroup$
    OK, but I hope somebody will give a more complete answer, because i do this steps quite often too and a way to automate it would be handy.
    $endgroup$
    – thibsert
    yesterday










  • $begingroup$
    I don't think there is any built-in way as of 2.79. There were talks it will be In 2.8. With addons it can be made faster, like with Dynamic Context menu (built-in one), see blender.stackexchange.com/a/71319/1245. There are also some 3-rd party addons as well though their workable state is to be checked
    $endgroup$
    – Mr Zak
    yesterday






  • 1




    $begingroup$
    Related: blender.meta.stackexchange.com/questions/2387/…
    $endgroup$
    – batFINGER
    yesterday










  • $begingroup$
    lol, don't be sorry.. I love that question (and especially the deleted answer) it appeals to my warped SOH. Post it whenever I'm given the opportunity.
    $endgroup$
    – batFINGER
    yesterday














  • 2




    $begingroup$
    OK, but I hope somebody will give a more complete answer, because i do this steps quite often too and a way to automate it would be handy.
    $endgroup$
    – thibsert
    yesterday










  • $begingroup$
    I don't think there is any built-in way as of 2.79. There were talks it will be In 2.8. With addons it can be made faster, like with Dynamic Context menu (built-in one), see blender.stackexchange.com/a/71319/1245. There are also some 3-rd party addons as well though their workable state is to be checked
    $endgroup$
    – Mr Zak
    yesterday






  • 1




    $begingroup$
    Related: blender.meta.stackexchange.com/questions/2387/…
    $endgroup$
    – batFINGER
    yesterday










  • $begingroup$
    lol, don't be sorry.. I love that question (and especially the deleted answer) it appeals to my warped SOH. Post it whenever I'm given the opportunity.
    $endgroup$
    – batFINGER
    yesterday








2




2




$begingroup$
OK, but I hope somebody will give a more complete answer, because i do this steps quite often too and a way to automate it would be handy.
$endgroup$
– thibsert
yesterday




$begingroup$
OK, but I hope somebody will give a more complete answer, because i do this steps quite often too and a way to automate it would be handy.
$endgroup$
– thibsert
yesterday












$begingroup$
I don't think there is any built-in way as of 2.79. There were talks it will be In 2.8. With addons it can be made faster, like with Dynamic Context menu (built-in one), see blender.stackexchange.com/a/71319/1245. There are also some 3-rd party addons as well though their workable state is to be checked
$endgroup$
– Mr Zak
yesterday




$begingroup$
I don't think there is any built-in way as of 2.79. There were talks it will be In 2.8. With addons it can be made faster, like with Dynamic Context menu (built-in one), see blender.stackexchange.com/a/71319/1245. There are also some 3-rd party addons as well though their workable state is to be checked
$endgroup$
– Mr Zak
yesterday




1




1




$begingroup$
Related: blender.meta.stackexchange.com/questions/2387/…
$endgroup$
– batFINGER
yesterday




$begingroup$
Related: blender.meta.stackexchange.com/questions/2387/…
$endgroup$
– batFINGER
yesterday












$begingroup$
lol, don't be sorry.. I love that question (and especially the deleted answer) it appeals to my warped SOH. Post it whenever I'm given the opportunity.
$endgroup$
– batFINGER
yesterday




$begingroup$
lol, don't be sorry.. I love that question (and especially the deleted answer) it appeals to my warped SOH. Post it whenever I'm given the opportunity.
$endgroup$
– batFINGER
yesterday










2 Answers
2






active

oldest

votes


















6












$begingroup$

Steps 3/4/5 can be replaced by Shift+S (for Snapping) / O.



Step 8 can be replaced by T. In general, you can look for underlined letters in such menus.



I also wrote an add-on to automate the process: OriginToSelection.py.



Install the add-on via User Preferences / Add-ons / Install from file, don't forget to activate it (check the box before its name). Press Spacebar and search Origin, then select Origin To Selection.



Be careful, I'm new to publishing add-ons and I'm pretty sure it can cause crashes. Save your work before using!






share|improve this answer











$endgroup$













  • $begingroup$
    The plugin is cool. Works fine so far.
    $endgroup$
    – Thomas Weller
    yesterday










  • $begingroup$
    It works but is insecure (ie, it drops an error if used in Object mode), and i can't guarantee it won't crash Blender. Using Dynamic Context as suggested by Mr Zak seems way better (and it's build-in).
    $endgroup$
    – thibsert
    yesterday










  • $begingroup$
    I wonder why the bother with the context overriding in your addon. Consider having it poll only when in 3d view and edit mode. As it is it will fail silently when run when no 3d views in screen.
    $endgroup$
    – batFINGER
    yesterday










  • $begingroup$
    I still don't understand that context thing really well. Before packing it as an addon I was running it trough the script window, so the overriding was necessary (I think?). You say it's safe to remove it ? Edit : it works well without it, thank you!
    $endgroup$
    – thibsert
    yesterday












  • $begingroup$
    Can override going the other way when testing in the text editor, ie if __name__ == "__main__": bpy.ops.my_new.operator(ctx, 'INVOKE_DEFAULT')
    $endgroup$
    – batFINGER
    yesterday



















3












$begingroup$

Little bmesh helper script.



The process to move the origin involves making the new point the origin by subtracting it from all other verts, then translating the matrix world of the object such that the global location stays the same



Run in edit mode. Moves origin to selected geo.



import bpy

import bmesh

from mathutils import Vector

context = bpy.context



ob = context.edit_object

mw = ob.matrix_world

me = ob.data

bm = bmesh.from_edit_mesh(me)



selverts = [v.co for v in bm.verts if v.select]

if len(selverts):

    pt = sum(selverts, Vector()) / len(selverts)

    #T = Matrix.Translation(-pt)

    bmesh.ops.translate(bm, vec=-pt, verts=bm.verts)

    mw.translation = mw @ pt # replace @ with * for 2.7x

bmesh.update_edit_mesh(me)


As an addon for 2.80



enter image description here






share|improve this answer











$endgroup$













  • $begingroup$
    does it work for blender 2.78a,2.79?
    $endgroup$
    – Michael Ben David
    yesterday






  • 1




    $begingroup$
    Without testing (library upgrades for 2.80 have bombed my 2.79 build, too lazy to fix atm) Pretty sure the required changes to make it work for 2.7x is replacing any @ with * and change the version accordingly in bl_info
    $endgroup$
    – batFINGER
    yesterday












  • $begingroup$
    well anyways the other addon works for me too
    $endgroup$
    – Michael Ben David
    yesterday






  • 1




    $begingroup$
    Yes this one is by no means better, simply more "mesh-centric". The other addon in theory will also work for other types like curve and armature too. Script wise wanted to show how to do this without toggling edit mode, which can mean death to an edit bmesh.
    $endgroup$
    – batFINGER
    yesterday












  • $begingroup$
    bmesh means blender mesh isnt?
    $endgroup$
    – Michael Ben David
    yesterday











Your Answer





StackExchange.ifUsing("editor", function () {
return StackExchange.using("mathjaxEditing", function () {
StackExchange.MarkdownEditor.creationCallbacks.add(function (editor, postfix) {
StackExchange.mathjaxEditing.prepareWmdForMathJax(editor, postfix, [["$", "$"], ["\\(","\\)"]]);
});
});
}, "mathjax-editing");

StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "502"
};
initTagRenderer("".split(" "), "".split(" "), channelOptions);

StackExchange.using("externalEditor", function() {
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled) {
StackExchange.using("snippets", function() {
createEditor();
});
}
else {
createEditor();
}
});

function createEditor() {
StackExchange.prepareEditor({
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: false,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: null,
bindNavPrevention: true,
postfix: "",
imageUploader: {
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
},
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
});


}
});














draft saved

draft discarded


















StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fblender.stackexchange.com%2fquestions%2f134440%2fshortcut-for-setting-origin-to-vertex%23new-answer', 'question_page');
}
);

Post as a guest















Required, but never shown

























2 Answers
2






active

oldest

votes








2 Answers
2






active

oldest

votes









active

oldest

votes






active

oldest

votes









6












$begingroup$

Steps 3/4/5 can be replaced by Shift+S (for Snapping) / O.



Step 8 can be replaced by T. In general, you can look for underlined letters in such menus.



I also wrote an add-on to automate the process: OriginToSelection.py.



Install the add-on via User Preferences / Add-ons / Install from file, don't forget to activate it (check the box before its name). Press Spacebar and search Origin, then select Origin To Selection.



Be careful, I'm new to publishing add-ons and I'm pretty sure it can cause crashes. Save your work before using!






share|improve this answer











$endgroup$













  • $begingroup$
    The plugin is cool. Works fine so far.
    $endgroup$
    – Thomas Weller
    yesterday










  • $begingroup$
    It works but is insecure (ie, it drops an error if used in Object mode), and i can't guarantee it won't crash Blender. Using Dynamic Context as suggested by Mr Zak seems way better (and it's build-in).
    $endgroup$
    – thibsert
    yesterday










  • $begingroup$
    I wonder why the bother with the context overriding in your addon. Consider having it poll only when in 3d view and edit mode. As it is it will fail silently when run when no 3d views in screen.
    $endgroup$
    – batFINGER
    yesterday










  • $begingroup$
    I still don't understand that context thing really well. Before packing it as an addon I was running it trough the script window, so the overriding was necessary (I think?). You say it's safe to remove it ? Edit : it works well without it, thank you!
    $endgroup$
    – thibsert
    yesterday












  • $begingroup$
    Can override going the other way when testing in the text editor, ie if __name__ == "__main__": bpy.ops.my_new.operator(ctx, 'INVOKE_DEFAULT')
    $endgroup$
    – batFINGER
    yesterday
















6












$begingroup$

Steps 3/4/5 can be replaced by Shift+S (for Snapping) / O.



Step 8 can be replaced by T. In general, you can look for underlined letters in such menus.



I also wrote an add-on to automate the process: OriginToSelection.py.



Install the add-on via User Preferences / Add-ons / Install from file, don't forget to activate it (check the box before its name). Press Spacebar and search Origin, then select Origin To Selection.



Be careful, I'm new to publishing add-ons and I'm pretty sure it can cause crashes. Save your work before using!






share|improve this answer











$endgroup$













  • $begingroup$
    The plugin is cool. Works fine so far.
    $endgroup$
    – Thomas Weller
    yesterday










  • $begingroup$
    It works but is insecure (ie, it drops an error if used in Object mode), and i can't guarantee it won't crash Blender. Using Dynamic Context as suggested by Mr Zak seems way better (and it's build-in).
    $endgroup$
    – thibsert
    yesterday










  • $begingroup$
    I wonder why the bother with the context overriding in your addon. Consider having it poll only when in 3d view and edit mode. As it is it will fail silently when run when no 3d views in screen.
    $endgroup$
    – batFINGER
    yesterday










  • $begingroup$
    I still don't understand that context thing really well. Before packing it as an addon I was running it trough the script window, so the overriding was necessary (I think?). You say it's safe to remove it ? Edit : it works well without it, thank you!
    $endgroup$
    – thibsert
    yesterday












  • $begingroup$
    Can override going the other way when testing in the text editor, ie if __name__ == "__main__": bpy.ops.my_new.operator(ctx, 'INVOKE_DEFAULT')
    $endgroup$
    – batFINGER
    yesterday














6












6








6





$begingroup$

Steps 3/4/5 can be replaced by Shift+S (for Snapping) / O.



Step 8 can be replaced by T. In general, you can look for underlined letters in such menus.



I also wrote an add-on to automate the process: OriginToSelection.py.



Install the add-on via User Preferences / Add-ons / Install from file, don't forget to activate it (check the box before its name). Press Spacebar and search Origin, then select Origin To Selection.



Be careful, I'm new to publishing add-ons and I'm pretty sure it can cause crashes. Save your work before using!






share|improve this answer











$endgroup$



Steps 3/4/5 can be replaced by Shift+S (for Snapping) / O.



Step 8 can be replaced by T. In general, you can look for underlined letters in such menus.



I also wrote an add-on to automate the process: OriginToSelection.py.



Install the add-on via User Preferences / Add-ons / Install from file, don't forget to activate it (check the box before its name). Press Spacebar and search Origin, then select Origin To Selection.



Be careful, I'm new to publishing add-ons and I'm pretty sure it can cause crashes. Save your work before using!







share|improve this answer














share|improve this answer



share|improve this answer








edited yesterday









Community♦

1




1










answered yesterday









thibsertthibsert

1,9691311




1,9691311












  • $begingroup$
    The plugin is cool. Works fine so far.
    $endgroup$
    – Thomas Weller
    yesterday










  • $begingroup$
    It works but is insecure (ie, it drops an error if used in Object mode), and i can't guarantee it won't crash Blender. Using Dynamic Context as suggested by Mr Zak seems way better (and it's build-in).
    $endgroup$
    – thibsert
    yesterday










  • $begingroup$
    I wonder why the bother with the context overriding in your addon. Consider having it poll only when in 3d view and edit mode. As it is it will fail silently when run when no 3d views in screen.
    $endgroup$
    – batFINGER
    yesterday










  • $begingroup$
    I still don't understand that context thing really well. Before packing it as an addon I was running it trough the script window, so the overriding was necessary (I think?). You say it's safe to remove it ? Edit : it works well without it, thank you!
    $endgroup$
    – thibsert
    yesterday












  • $begingroup$
    Can override going the other way when testing in the text editor, ie if __name__ == "__main__": bpy.ops.my_new.operator(ctx, 'INVOKE_DEFAULT')
    $endgroup$
    – batFINGER
    yesterday


















  • $begingroup$
    The plugin is cool. Works fine so far.
    $endgroup$
    – Thomas Weller
    yesterday










  • $begingroup$
    It works but is insecure (ie, it drops an error if used in Object mode), and i can't guarantee it won't crash Blender. Using Dynamic Context as suggested by Mr Zak seems way better (and it's build-in).
    $endgroup$
    – thibsert
    yesterday










  • $begingroup$
    I wonder why the bother with the context overriding in your addon. Consider having it poll only when in 3d view and edit mode. As it is it will fail silently when run when no 3d views in screen.
    $endgroup$
    – batFINGER
    yesterday










  • $begingroup$
    I still don't understand that context thing really well. Before packing it as an addon I was running it trough the script window, so the overriding was necessary (I think?). You say it's safe to remove it ? Edit : it works well without it, thank you!
    $endgroup$
    – thibsert
    yesterday












  • $begingroup$
    Can override going the other way when testing in the text editor, ie if __name__ == "__main__": bpy.ops.my_new.operator(ctx, 'INVOKE_DEFAULT')
    $endgroup$
    – batFINGER
    yesterday
















$begingroup$
The plugin is cool. Works fine so far.
$endgroup$
– Thomas Weller
yesterday




$begingroup$
The plugin is cool. Works fine so far.
$endgroup$
– Thomas Weller
yesterday












$begingroup$
It works but is insecure (ie, it drops an error if used in Object mode), and i can't guarantee it won't crash Blender. Using Dynamic Context as suggested by Mr Zak seems way better (and it's build-in).
$endgroup$
– thibsert
yesterday




$begingroup$
It works but is insecure (ie, it drops an error if used in Object mode), and i can't guarantee it won't crash Blender. Using Dynamic Context as suggested by Mr Zak seems way better (and it's build-in).
$endgroup$
– thibsert
yesterday












$begingroup$
I wonder why the bother with the context overriding in your addon. Consider having it poll only when in 3d view and edit mode. As it is it will fail silently when run when no 3d views in screen.
$endgroup$
– batFINGER
yesterday




$begingroup$
I wonder why the bother with the context overriding in your addon. Consider having it poll only when in 3d view and edit mode. As it is it will fail silently when run when no 3d views in screen.
$endgroup$
– batFINGER
yesterday












$begingroup$
I still don't understand that context thing really well. Before packing it as an addon I was running it trough the script window, so the overriding was necessary (I think?). You say it's safe to remove it ? Edit : it works well without it, thank you!
$endgroup$
– thibsert
yesterday






$begingroup$
I still don't understand that context thing really well. Before packing it as an addon I was running it trough the script window, so the overriding was necessary (I think?). You say it's safe to remove it ? Edit : it works well without it, thank you!
$endgroup$
– thibsert
yesterday














$begingroup$
Can override going the other way when testing in the text editor, ie if __name__ == "__main__": bpy.ops.my_new.operator(ctx, 'INVOKE_DEFAULT')
$endgroup$
– batFINGER
yesterday




$begingroup$
Can override going the other way when testing in the text editor, ie if __name__ == "__main__": bpy.ops.my_new.operator(ctx, 'INVOKE_DEFAULT')
$endgroup$
– batFINGER
yesterday













3












$begingroup$

Little bmesh helper script.



The process to move the origin involves making the new point the origin by subtracting it from all other verts, then translating the matrix world of the object such that the global location stays the same



Run in edit mode. Moves origin to selected geo.



import bpy

import bmesh

from mathutils import Vector

context = bpy.context



ob = context.edit_object

mw = ob.matrix_world

me = ob.data

bm = bmesh.from_edit_mesh(me)



selverts = [v.co for v in bm.verts if v.select]

if len(selverts):

    pt = sum(selverts, Vector()) / len(selverts)

    #T = Matrix.Translation(-pt)

    bmesh.ops.translate(bm, vec=-pt, verts=bm.verts)

    mw.translation = mw @ pt # replace @ with * for 2.7x

bmesh.update_edit_mesh(me)


As an addon for 2.80



enter image description here






share|improve this answer











$endgroup$













  • $begingroup$
    does it work for blender 2.78a,2.79?
    $endgroup$
    – Michael Ben David
    yesterday






  • 1




    $begingroup$
    Without testing (library upgrades for 2.80 have bombed my 2.79 build, too lazy to fix atm) Pretty sure the required changes to make it work for 2.7x is replacing any @ with * and change the version accordingly in bl_info
    $endgroup$
    – batFINGER
    yesterday












  • $begingroup$
    well anyways the other addon works for me too
    $endgroup$
    – Michael Ben David
    yesterday






  • 1




    $begingroup$
    Yes this one is by no means better, simply more "mesh-centric". The other addon in theory will also work for other types like curve and armature too. Script wise wanted to show how to do this without toggling edit mode, which can mean death to an edit bmesh.
    $endgroup$
    – batFINGER
    yesterday












  • $begingroup$
    bmesh means blender mesh isnt?
    $endgroup$
    – Michael Ben David
    yesterday
















3












$begingroup$

Little bmesh helper script.



The process to move the origin involves making the new point the origin by subtracting it from all other verts, then translating the matrix world of the object such that the global location stays the same



Run in edit mode. Moves origin to selected geo.



import bpy

import bmesh

from mathutils import Vector

context = bpy.context



ob = context.edit_object

mw = ob.matrix_world

me = ob.data

bm = bmesh.from_edit_mesh(me)



selverts = [v.co for v in bm.verts if v.select]

if len(selverts):

    pt = sum(selverts, Vector()) / len(selverts)

    #T = Matrix.Translation(-pt)

    bmesh.ops.translate(bm, vec=-pt, verts=bm.verts)

    mw.translation = mw @ pt # replace @ with * for 2.7x

bmesh.update_edit_mesh(me)


As an addon for 2.80



enter image description here






share|improve this answer











$endgroup$













  • $begingroup$
    does it work for blender 2.78a,2.79?
    $endgroup$
    – Michael Ben David
    yesterday






  • 1




    $begingroup$
    Without testing (library upgrades for 2.80 have bombed my 2.79 build, too lazy to fix atm) Pretty sure the required changes to make it work for 2.7x is replacing any @ with * and change the version accordingly in bl_info
    $endgroup$
    – batFINGER
    yesterday












  • $begingroup$
    well anyways the other addon works for me too
    $endgroup$
    – Michael Ben David
    yesterday






  • 1




    $begingroup$
    Yes this one is by no means better, simply more "mesh-centric". The other addon in theory will also work for other types like curve and armature too. Script wise wanted to show how to do this without toggling edit mode, which can mean death to an edit bmesh.
    $endgroup$
    – batFINGER
    yesterday












  • $begingroup$
    bmesh means blender mesh isnt?
    $endgroup$
    – Michael Ben David
    yesterday














3












3








3





$begingroup$

Little bmesh helper script.



The process to move the origin involves making the new point the origin by subtracting it from all other verts, then translating the matrix world of the object such that the global location stays the same



Run in edit mode. Moves origin to selected geo.



import bpy

import bmesh

from mathutils import Vector

context = bpy.context



ob = context.edit_object

mw = ob.matrix_world

me = ob.data

bm = bmesh.from_edit_mesh(me)



selverts = [v.co for v in bm.verts if v.select]

if len(selverts):

    pt = sum(selverts, Vector()) / len(selverts)

    #T = Matrix.Translation(-pt)

    bmesh.ops.translate(bm, vec=-pt, verts=bm.verts)

    mw.translation = mw @ pt # replace @ with * for 2.7x

bmesh.update_edit_mesh(me)


As an addon for 2.80



enter image description here






share|improve this answer











$endgroup$



Little bmesh helper script.



The process to move the origin involves making the new point the origin by subtracting it from all other verts, then translating the matrix world of the object such that the global location stays the same



Run in edit mode. Moves origin to selected geo.



import bpy

import bmesh

from mathutils import Vector

context = bpy.context



ob = context.edit_object

mw = ob.matrix_world

me = ob.data

bm = bmesh.from_edit_mesh(me)



selverts = [v.co for v in bm.verts if v.select]

if len(selverts):

    pt = sum(selverts, Vector()) / len(selverts)

    #T = Matrix.Translation(-pt)

    bmesh.ops.translate(bm, vec=-pt, verts=bm.verts)

    mw.translation = mw @ pt # replace @ with * for 2.7x

bmesh.update_edit_mesh(me)


As an addon for 2.80



enter image description here







share|improve this answer














share|improve this answer



share|improve this answer








edited yesterday

























answered yesterday









batFINGERbatFINGER

25.6k52876




25.6k52876












  • $begingroup$
    does it work for blender 2.78a,2.79?
    $endgroup$
    – Michael Ben David
    yesterday






  • 1




    $begingroup$
    Without testing (library upgrades for 2.80 have bombed my 2.79 build, too lazy to fix atm) Pretty sure the required changes to make it work for 2.7x is replacing any @ with * and change the version accordingly in bl_info
    $endgroup$
    – batFINGER
    yesterday












  • $begingroup$
    well anyways the other addon works for me too
    $endgroup$
    – Michael Ben David
    yesterday






  • 1




    $begingroup$
    Yes this one is by no means better, simply more "mesh-centric". The other addon in theory will also work for other types like curve and armature too. Script wise wanted to show how to do this without toggling edit mode, which can mean death to an edit bmesh.
    $endgroup$
    – batFINGER
    yesterday












  • $begingroup$
    bmesh means blender mesh isnt?
    $endgroup$
    – Michael Ben David
    yesterday


















  • $begingroup$
    does it work for blender 2.78a,2.79?
    $endgroup$
    – Michael Ben David
    yesterday






  • 1




    $begingroup$
    Without testing (library upgrades for 2.80 have bombed my 2.79 build, too lazy to fix atm) Pretty sure the required changes to make it work for 2.7x is replacing any @ with * and change the version accordingly in bl_info
    $endgroup$
    – batFINGER
    yesterday












  • $begingroup$
    well anyways the other addon works for me too
    $endgroup$
    – Michael Ben David
    yesterday






  • 1




    $begingroup$
    Yes this one is by no means better, simply more "mesh-centric". The other addon in theory will also work for other types like curve and armature too. Script wise wanted to show how to do this without toggling edit mode, which can mean death to an edit bmesh.
    $endgroup$
    – batFINGER
    yesterday












  • $begingroup$
    bmesh means blender mesh isnt?
    $endgroup$
    – Michael Ben David
    yesterday
















$begingroup$
does it work for blender 2.78a,2.79?
$endgroup$
– Michael Ben David
yesterday




$begingroup$
does it work for blender 2.78a,2.79?
$endgroup$
– Michael Ben David
yesterday




1




1




$begingroup$
Without testing (library upgrades for 2.80 have bombed my 2.79 build, too lazy to fix atm) Pretty sure the required changes to make it work for 2.7x is replacing any @ with * and change the version accordingly in bl_info
$endgroup$
– batFINGER
yesterday






$begingroup$
Without testing (library upgrades for 2.80 have bombed my 2.79 build, too lazy to fix atm) Pretty sure the required changes to make it work for 2.7x is replacing any @ with * and change the version accordingly in bl_info
$endgroup$
– batFINGER
yesterday














$begingroup$
well anyways the other addon works for me too
$endgroup$
– Michael Ben David
yesterday




$begingroup$
well anyways the other addon works for me too
$endgroup$
– Michael Ben David
yesterday




1




1




$begingroup$
Yes this one is by no means better, simply more "mesh-centric". The other addon in theory will also work for other types like curve and armature too. Script wise wanted to show how to do this without toggling edit mode, which can mean death to an edit bmesh.
$endgroup$
– batFINGER
yesterday






$begingroup$
Yes this one is by no means better, simply more "mesh-centric". The other addon in theory will also work for other types like curve and armature too. Script wise wanted to show how to do this without toggling edit mode, which can mean death to an edit bmesh.
$endgroup$
– batFINGER
yesterday














$begingroup$
bmesh means blender mesh isnt?
$endgroup$
– Michael Ben David
yesterday




$begingroup$
bmesh means blender mesh isnt?
$endgroup$
– Michael Ben David
yesterday


















draft saved

draft discarded




















































Thanks for contributing an answer to Blender Stack Exchange!


  • Please be sure to answer the question. Provide details and share your research!

But avoid …



  • Asking for help, clarification, or responding to other answers.

  • Making statements based on opinion; back them up with references or personal experience.


Use MathJax to format equations. MathJax reference.


To learn more, see our tips on writing great answers.




draft saved


draft discarded














StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fblender.stackexchange.com%2fquestions%2f134440%2fshortcut-for-setting-origin-to-vertex%23new-answer', 'question_page');
}
);

Post as a guest















Required, but never shown





















































Required, but never shown














Required, but never shown












Required, but never shown







Required, but never shown

































Required, but never shown














Required, but never shown












Required, but never shown







Required, but never shown







-

Popular posts from this blog

Plaza Victoria

Image
Plaza Victoria Plaza Victoria en 2017 Otros nombres Plaza de La Victoria Localización El Almendral, Valparaíso, Chile Vías adyacentes Chacabuco, Molina, Plaza Victoria y Edwards Creación 1841 Metro Bellavista Ubicación 33°02′46″S 71°37′11″O  /  -33.04624167, -71.61980833 Coordenadas: 33°02′46″S 71°37′11″O  /  -33.04624167, -71.61980833 [editar datos en Wikidata] La Plaza Victoria , también llamada Plaza de la Victoria , [ 1 ] ​ es una plaza ubicada en el sector El Almendral del plan de la ciudad de Valparaíso, Chile, de importancia patrimonial, que incluye valiosas estatuas y especies vegetales. [ 2 ] ​ La plaza se creó como tal en la primera mitad del siglo XIX, tomando previamente los nombres de Plaza Nueva y Plaza de Orrego . Si bien desde sus inicios tuvo relevancia histórica, no fue sino a partir de fines de los años 1860 cuando comenzó a cobrar mayor importancia y se convirtió en uno de los principales centros sociales de l
Read more

Puebla de Zaragoza

Image
Para otros usos de este término, véase Puebla (desambiguación). Heroica Puebla de Zaragoza Localidad De arriba a abajo de izquierda a derecha: Estrella de Puebla, Volcán Popocatépetl, Catedral de Puebla, Monumento a Ignacio Zaragoza, Estadio Cuauhtémoc, Angelópolis y Vista panorámica de la ciudad. Escudo Otros nombres: El relicario de América/ La ciudad de los Ángeles/ La Angelópolis Lema: Muy noble y muy leal ciudad de Puebla de los Ángeles Heroica Puebla de Zaragoza Localización de Heroica Puebla de Zaragoza en México Heroica Puebla de Zaragoza Localización de Heroica Puebla de Zaragoza en Puebla Mapa interactivo Coordenadas 19°03′05″N 98°13′04″O  /  19.051388888889, -98.217777777778 Coordenadas: 19°03′05″N 98°13′04″O  /  19.051388888889, -98.217777777778 Idioma oficial Español Entidad Localidad  • País   México  • Estado Puebla  • Municipio Puebla Presidente municipal Claudia Rivera Vivanc
Read more

Musa

Image
Para el género de plantas, véase Musa (planta). Apolo y la Nueve Musas En la mitología griega, las musas (en griego antiguo μοῦσαι « mousai» ) son, según los escritores más antiguos, las divinidades inspiradoras de las Artes: cada una de ellas está relacionada con ramas artísticas y del conocimiento. Son hijas de Zeus y de Mnemósine, compañeras del séquito de Apolo, dios olímpico de la música y patrón de las bellas artes, quien tuvo romances con cada una de ellas, dejando descendientes. Bajaban a la tierra a susurrar ideas e inspirar a aquellos mortales que las invocaran. En la época más arcaica eran las ninfas inspiradoras de las fuentes, en las cuales eran adoradas. Finalmente, alrededor de los siglos VIII-VII a. C. [ 1 ] ​ prevaleció en todo el territorio de la Hélade la adoración de las nueve Musas, que son Calíope, Clío, Erato, Euterpe, Melpómene, Polimnia, Talía, Terpsícore y Urania. El culto a las musas era originalmente de Tracia y Beocia, y fueron de vital impo
Read more