A script to place cursor on objects' surface (and some other functionality)

[dairin0d]

animani, what does the error say?

[animani]

RuntimeError: class WM_OT_enhanced_3d_cursor_registration, function modal: incompatible return value , str(, Function.result expected a set, not a NoneType)

The funny thing is I lose the current setting for my 3D cursor shortcuts and when I try to activate it by checking the item box it reverts back to uncheck. I mean I can see it unchecking. Is this something that should be happening?

[dairin0d]

animani, you have a very old version of the addon. Install the latest one.
Deactivation of the default cursor shortcut is indeed the intended behavior (since the addon is supposed to "override" the default operator).

[animani]

Do I have an old version? I got it from here:

https://svn.blender.org/svnroot/bf-e...d_3d_cursor.py

Is that the latest? I copied that link from your first post where it says its the latest.

[dairin0d]

Ah, thanks for pointing that out! Blender at some point has switched to a different repository, and I changed the link in the wiki, but completely forgot about the first post here. Sorry
I edited the first post, it now points to my repository at github.

[animani]

Ah yeah that happens sometimes I thought that would be the case. Thanks!

[Darcvizer]

Hellow. I get script error http://take.ms/2obwF

[dairin0d]

Darcvizer, does the error appear every time you try to move the cursor, or only when certain objects are present in the scene?
Can you share the file you were working with?

[Darcvizer]

It was the only time.
The error was only on the object from the whole scene and I deleted it from it.
I can send the file but there's already no this error.

[dairin0d]

I see. If the error appears again (and is reproducible), feel free to send me the corresponding file :-)

[fiendish55]

I see. If the error appears again (and is reproducible), feel free to send me the corresponding file :-)

This is absolutely brilliant I want this in blender trunk xD

There is a problem with addon when you restart blender its not working even if its enabled. Only way to make it work again is disable and enable addon again which is pain to do everytime you restart.

[Edtion]

I thought it was already. I don't remember downloading it but I do remember it being in my /program files/blender/ directory.
I'm using version 2.79 now and it was missing, so I figure it's either currently going to be removed (like several other addons), or it's supposed to be re-added later




Anyway, I was thinking that I'd probably want to use this addon again but after testing it a bit, I found out that it doesn't work with empties/proxies. The regular cursor detects them but this doesn't see them as meshes or whatever, so I can't use it.

[Edtion]

I just found out that Ctrl+Shift+A [Make Duplicates Real] can be used to make real proxy-copies and it creates meshes that work with this.

Additionally, with proxies you can only use the character/rig once, and all copies will copy the same animation/pose, whereas with Real ones they can be individual models, and all the other proxy things still work, like refreshing mesh/rigs.

[Hammers]

Not sure if this has come up, but I've had issues for ages with Blender's autosave feature. Today I found this reddit post that suggested this addon may cause issues with autosave.

I had the addon installed but not enabled (in 2.79), but deleted it anyway, and Lo! autosave works again! I think it was v2.9.8 that I had installed. May want to check into this behaviour as it's a bit of a nasty side-effect.

[Edtion]

I'm not saying it "doesn't" interfere with saves but I "do" have auto saves.

Sometimes my files aren't auto saving but AFAIK it's always because I opened them using the Asset Management Addon. I can't say that every time it's happened was because of that, but every time I crashed and went looking for the trusty save, only to find it didn't save, I also happened to remember that I opened something from the AM addon ¯\_(ツ)_/¯

[dairin0d]

Hammers, do you mean "auto save every N minutes", "make a copy of previously-saved file when manually saving", or something else? For me, the first variant doesn't seem to work at all (even if I use a vanilla Blender without extra addons), and the second variant works even with my addons enabled.
Either way, for an addon to affect things just by being installed (and not even enabled) is very weird. Thanks for letting me know, but I'm afraid I have no idea where the problem may be.

[Hammers]

Thanks for the replies. Further tests have now shown that autosave (i.e. autosave every n minutes in system prefs) is again not working. It did work for a session after uninstalling the addon, but now not working again. I do have Asset Management, but don't think I've seen a link with sessions where I've used it. Hmmm. It's a feature that I love having, when I need it. But sadly it is very unreliable. Ah well, sorry for probably pointing the finger unnecessarily.

[dairin0d]

Huh, it seems someone has figured out the cause of the problem with auto-saves a couple of moths ago, and somehow I completely failed to notice it until now Sorry!
It seems to be related to the Cursor Monitor (which the addon uses to record cursor history). Since it's an operator that constantly runs in background, auto-save is skipped. You can disable the Cursor Monitor in addon's preferences. I added a warning about this issue to the wiki too.

[isaaccslam]

The addon is extremely useful, but i just found out that the cursor cannot correctly detect which vertex to snap in the user orthographic mode ( but it function correctly in the user persp mode).

[dairin0d]

_{isaaccslam, from what I can tell this is caused by a bug in Blender's raycast (though when I test it independently, perspective gives wrong results too. weird). The bug seems to have appeared in Blender 2.77 (in Blender 2.76, snapping in orthographic mode works fine).
Not sure if this problem is even possible to circumvent, but for now I reported the bug.}

Oops! Please disregard that; it turned out not to be a Blender's bug. There were two changes in ray_cast() semantics in Blender 2.77, but I didn't notice the more subtle one. Thanks to Campbell Barton for pointing it out!