[Maxscript] FB quickLoopRing and UVconversion
polycounter lvl 17
Heyo all,
I've recently upgraded from max 2009 after sticking with it for a long time and one of the things that became annoying to me during brawl was the lack of a Shift+click edgeloop function for the Unwrap_UVW modifier and Skin modifiers. So I've hacked together something like that, so figured I'd share
FB_quickLoopRing.ms is a startup script that runs whenever you hold shift and select an adjacent subobject to your previous selection. It works on faces, verts, and edges. If you're using max 2010+ it'll do a UV-centric loop if you're selecting from the UV editor or a Geom-centric loop if you're using the viewport selection.
It's made for max 2010+ but it works okay on max 2009
Also, since I'm talking about UVs already I also made another quick script for converting UV selections with CTRL.
FB_UVconversion.ms - basically when you switch subobject modes it checks to see if youre on a uv modifier and if you hit ctrl, and if so it'll convert it.
Unlikely, but I don't know what scripts you're using so it's entirely possible it could fight with something you're already running.
let me know if you have any issues
============
Installation:
============
For both of these, just drop them into ...Program Files/Autodesk/3dsMaxXXXX/Scripts/Startup/ and restart max and it'll be enabled. If you want to disable it, just delete it from that folder and restart max.
I've recently upgraded from max 2009 after sticking with it for a long time and one of the things that became annoying to me during brawl was the lack of a Shift+click edgeloop function for the Unwrap_UVW modifier and Skin modifiers. So I've hacked together something like that, so figured I'd share
FB_quickLoopRing.ms is a startup script that runs whenever you hold shift and select an adjacent subobject to your previous selection. It works on faces, verts, and edges. If you're using max 2010+ it'll do a UV-centric loop if you're selecting from the UV editor or a Geom-centric loop if you're using the viewport selection.
It's made for max 2010+ but it works okay on max 2009
Also, since I'm talking about UVs already I also made another quick script for converting UV selections with CTRL.
FB_UVconversion.ms - basically when you switch subobject modes it checks to see if youre on a uv modifier and if you hit ctrl, and if so it'll convert it.
Unlikely, but I don't know what scripts you're using so it's entirely possible it could fight with something you're already running.
let me know if you have any issues
============
Installation:
============
For both of these, just drop them into ...Program Files/Autodesk/3dsMaxXXXX/Scripts/Startup/ and restart max and it'll be enabled. If you want to disable it, just delete it from that folder and restart max.
Replies
Its such an Obvious thing, You have to wonder why AD dont generalise selection methods across the whole app. XBR perhaps....(not holding breath)
If you upgraded from 2009 to something later you ought to poke around the graphite modeling tools, they have a ton of useful shit that 2009 and lower didn't have without polyboost.
and thanks ghostscape, you're right I might be missing something
but I moved from 2009 to 2012 and I can't seem to get the behavior you're talking about within UnwrapUVW and the Skin modifiers. The idea was just to try and emulate the behavior graphite adds to the Editable Poly tools.
Does it work for you? maybe I'm doing something wrong :X
After installing i've found that holding shift to constrain movement in the uv editor no longer works...hold shift and move verts to contrain along one axis, as soon as releasing it snaps back to the original position. I've had to do a work around and hold shift, then hold ctrl, release and it will work.
Anyone else had this issue after installing the scripts?
airbrush: can you open FB_quickLoopRing.ms and see if it's version 1.1 or 1.0?
I noticed this problem and it shoould have been fixed with 1.1. If so, you should be able to simply overwrite it with version 1.1
if not lemme know what version of max are you using? and I'll see if I can fix it