Blender with Better Selection and More

I’ve made a custom build of Blender for Windows, Mac, and Linux. The idea is to keep things the way they are, while giving you more options for:

Box, Circle, and Lasso Select
X-Ray
Facedots
Selection Radius
Mouse Cursor
Header Buttons
Camera Zoom
Frame Selected
Repeat Last

It’s $9.99, and will include a few addons I am working on when they are finished. Buy one package for 10 bucks, and then choose what parts of it you want to download. All Blender versions I can build for, and their sub-version updates, will be available as I finish them. Bump this thread and ask for a new or old version of Blender that I haven’t done.

Upcoming Additions

Pie Menu Addon First thing will be a pie menu addon. To see what I am planning to do, check out the customizable pie menu that I made for the drag select features of this build.



This is not just, “I made this for you to use. Therefore it is custom.” It is a pie menu that is customizable by you, the user. But not in a way where you have to do that, either.



No coding. Just pick something from a dropdown for whichever pie slices you need, and you’re done. But, if you need something more advanced, there’s also an even CUSTOM-ER pie menu that will accept any bpy code you send at it, any number of operators per slice, any name you want to give it, and any icon (including the larger toolbar ones)



Anyways, the more basic pie menu operators will be tailored to a general area of Blender or workflow style. They will have a default layout that you can just use, but they will have a lot of operators and settings available that can be assigned where you want them to be. The available options will be limited to what makes sense for the intended purpose of that pie menu operator. No need to scroll past tons of stuff that makes no sense.



Since it is assignable in the keymap, it can be as modular as you need. Make one generic version for Window, or whichever Interaction Mode makes sense, and then a more specific version for a tool that you need a different layout for.



This will be an ongoing thing that will expand with feedback and feature requests.

Selection Addon After that will be an addon version of various selection features in this custom build. The addon version of the selection features will work slower and harder, that's just the way it is. I don't think python will ever have access to `gpu_select` / `open_gl select` so it needs to reinvent the wheel into an octagon to do the same thing. Either way, an addon could be useful for people who aren't interested in a custom build, or when an update is late and you need the latest Blender version before the build is ready.
Update Old Blender Versions As I work on whatever else, I'll fill out older versions of Blender. I probably won't back-port everything in the latest version of this custom build to old Blender versions unless it is requested by somebody. Plan is to just update whatever state this custom build was in for the latest subversion of Blender that it was made for.

Feature requests are encouraged!
Donate :money_mouth_face:

PRESETS
Preferences → Luke’s Custom Build → Presets

I made some presets to give you a quick way to get everything I change about Blender back to the way it is in the official release, or to give you a starting point for an improved experience. Just choose one from the dropdown, and click the Apply button. I can make you a preset upon request. Tell me what settings you use and a name for the preset, and I’ll add it to the list.

DRAG SELECT OPTIONS
Preferences → Luke’s Custom Build → Drag Select

Box, Circle, and Lasso Select
This build gives you full control over the ways that Box, Lasso, and Circle can select Objects, Edges, and Faces. There are a lot of limitations and inconsistencies with Blender regarding this. My build fixes them in a way that works the way you want, not the other way around where you do things the way Blender wants.

What Problems Could Blender Possibly Have With Selection?

Box will select any object the selection area touches. Circle and Lasso only select objects if their origin is touched by the selection area.



Edit mode will not select through mesh. It can be very useful to select unseen verts, edges, and faces without moving your view or turning on X-Ray.



Box and Lasso select fully enclosed edges, where both verts are inside the selection area. Except when none of the edges are fully enclosed. In that case you select any edges touched by the selection area. Circle will select any edges touched by the selection area.



Box, Circle, and Lasso will select any face touched by the selection area. Except when you turn on xray. In that case you only select faces if their center is touched by the selection area.



Box, Circle, and Lasso will select stray edges and faces that you can’t see when not using xray. How bad it is will vary based on the position/rotation of the viewport, and the shape of the mesh you are working with. What matters is that it’s random and unpredictable. Subdivide the default cube a couple times so there’s more than 1 extra face to select per side, makes it a little easier to see what’s going on. Then drag over some or all of what you can see, just be sure to hit the borders of the mesh. Now spin your view around to see the extra junk you selected. Was hoping Vulkan would fix this, but it does not.

My build has none of those problems, but it will preserve them by default so can you keep working with them if you prefer. It will not force you to select things differently just because you are using a different tool or shading mode.

How Does Luke's Custom Build Fix That? Turn on Select Through in Edit Mode, so you can select unseen mesh when you need to.



Turn on Automatic X-Ray in Object and/or Edit Mode, it will enable X-Ray while selecting and turn it off when finished.



Select any object that is touched by the selection area, fully enclosed within it, or only if the origin is inside.



Select any edge that is touched by the selection area, or fully enclosed within it.



Select any face that is touched by the selection area, fully enclosed within it, or only if the center is inside.



Facedot Priority will always select by face center if facedots are visible. Speaking of which, you can turn off facedots in xray now. You’ll find some options for how that works in the Visual section at the bottom of the Luke’s Custom Build tab.



For eliminating unwanted backfacing edges and faces, set Backface to Edge & Face Near. You can also use No Backface but that will also apply to Xray and Select Through, and you probably don’t want that. At that point you could leave Select Through on all the time, and the backface filter would essentially work like the Xray button, while allowing you to turn Xray on without changing selection at all. It would also do a little extra work to remove backfacing verts when not using Xray or Select Through. But this is wasted effort since Near Select has no issues grabbing extra verts, at least not that I have observed.

You Get To Decide How Much Control & Flexibility You Actually Need

The Default options mean, “Do what regular Blender does. It might be weird, but just leave it alone.”

Change the Mode to Easy if you want the three drag select tools to act the same. Change the Mode to Split if you want some, or all of them, to act differently from each other, or if you want to use drag direction control (left vs right, or up vs down) for Box and/or Lasso.

If you don’t need to change these selection options on the fly as you are working, you can just set things the way you want and do your thing. Set it and forget it. If you need more than that, there are many options for cycling through selection modes and toggling options as you work. No need to open userprefs once you set things up the way you like them. I made operators to control everything in a highly customizable way.

Flexible Operators

You’ll be able to customize the dynamic controls for whatever you need to change about drag select while you work. They all use the same operators whether you prefer keyboard shortcuts, interface buttons, or a pie menu.

Expand the Dynamic Controls section and start with Button Visibility. You can choose what operators you’d like to see in the Viewport Header, Toolsettings, or both. They all have icons that will change their appearance based on the modes and settings that are currently active. If you only want to use keyboard shortcuts without adding extra buttons to your interface, just show these buttons temporarily, right click them, and assign them to your keymap.

For the Object, Edge, and Face selection modes, I have an operator that will cycle through the modes. The dynamic controls for them allow you to exclude modes from the cycle. That way you don’t need to waste time clicking through modes you never want to use. For the Backface Filter and Auto X-Ray, you can choose what type of toggle the operator will perform. Backface has 2 styles, and Auto X-Ray will let you decide whether to toggle the setting in both Object and Edit, or just the Interaction Mode you are currently using.

Pie Menu

There is also a customizable pie menu for my drag select settings, and other drag select features. You can decide what parts of it go in any of the 8 pie menu slices. Add a keymap entry for pie.drag_select in the keymap. You can make this as modular as you need it. Put a main entry in Window or wherever else, and then another for a specific tool like Box Select if you want it to have a new layout for different tools or interaction modes.


Tools That Are As Unique As You Want Them To Be

If you use Split Mode controls, you can synchronize 2 of the 3 tools so they stay the same when using the operators, while the unsynchronized tool will act independently.

Directional Control

The drag directions I’ve made work like they’re supposed to, unlike the ones you’ll find in the keymap. You don’t have to live with a deadzone, or some compromised version of left and right, or up and down, that is rotated 22.5 degrees. You also don’t need to create a ton of keymap assignments per tool. You can use drag controls for everything, or opt-in to only the ones you want and use the operators for the others.

Settings That Will Persist

Your choices for the new features in my build are user preferences instead of toolsettings. They will remain the way you left them, instead of changing depending what .blend file you open like toolsettings do. This only happened because a feature request made me realize how much better it could be. Can’t say it enough times, feature requests are encouraged.

MOUSE OPTIONS
Preferences → Luke’s Custom Build → Mouse

Selection Radius

Single-click an edge, vertex, or facedot and there’s a pretty big area you can grab it from. Faces in near select have zero radius, so you have to be right on top of them.

I made this adjustable and consistent. Change Click Select to Custom and choose a radius. Blender’s default is 75. Faces will act the same as verts and edges now. Blender gives unselected mesh a slight bias, this can be turned off by using Select Unbiased.

Mouse Cursor

I don’t like the Edit Mode crosshair, so I made a replacement. Then I decided to just make this available to most of the cursors and have a few options to choose from.

If you need to get things back to normal, just click Reset Cursors. The Paint and 2D cursors have an additional option called Blank. It’s an empty cursor that was made by an unrelated request in another thread.

You’ll need to move your cursor in and out of whatever area they’re from to see the change take effect. If you are on Mac or Linux, most of the cursor options don’t work, but System and Cross should show up correctly if you’d like them as an alternative for any cursor. I’ll expand on this feature if there’s interest.

VISUAL OPTIONS
Preferences → Luke’s Custom Build → Visual

Facedots

You can turn off X-ray facedots. They’re in the same area as before up in the viewport header, it’s just an operator now instead of a checkbox. An operator because you can choose how it works. Either toggle them in both X-Ray and non-X-Ray shading, or both. This also makes it possible to preserve Blender default behaviour without relying on default settings that won’t exist if you already have a startup file for the same Blender version as this custom build.

Shading Buttons

I don’t need buttons for X-Ray or Shading, so I thought of a few ways to combine or reduce them to save space in the Viewport header.

X-Ray will have the X-Ray button replace the Shading buttons, and it will change its icon to reflect what Shading Mode you’re in.

Cycle will shrink the Shading Buttons down to a single button. The new operator will cycle through the 4 shading modes. You can reduce the number of shading modes in the cycle. These options will show up next to the dropdown when you select the Cycle mode for Shading Buttons.

X-Ray Button

You can hide the X-Ray button from the Viewport header. If you change the Shading Buttons mode to X-Ray, this option will be disabled since it is already “hiding” it.

NEW & EXPANDED TOOLS

Camera Zoom

You can make camera move faster or slower for view3d.zoom. If you want multiple zoom mappings you need to manually set the speed for the existing zoom keymap or the speed of the new one you make will be used for both. 1.2 is the Blender default zoom speed. It slows down as you approach 1.0, and gets very fast as you go up to 10.

Frame Selected

You can set a camera offset for view3d.view_selected. Like camera zoom, if you want more than one mapping for different distances, you need to manually set the existing one or it won’t work right. Camera Offset at 0 is the Blender default, increase it to move the Viewport camera further away.

Invoke Last

A new operator called screen.invoke_last that works the same as Repeat Last, except instead of executing everything the same, it just invokes the last operation. You’ll need to add a new Keymap entry for screen.invoke_last. Undo makes it lose memory the same as Repeat Last.

Thankyou
This build is only possible because of the knowledge and experience shared by the community. I want mention some people that helped me figure things out like Christoph Lendenfeld, Chris Blackbourne, LazyDodo, Brecht, Thomas, Harley, and Campbell. Everyone on devtalk, blender artists, and in the chat, thank you.

Most of all, I want to thank kio. Select Through, Facedot visibility, and Touch select faces in X-Ray are from the work he did. In the older versions of this custom build it was basically untouched, and I learned a lot by updating it and changing how it works. There were a couple issues with it, and over time I finally understood more about how everything works. After fixing those issues, and making a few optimizations and flexibility changes, it is pretty different. The main thing that makes everything fast though, using gpu_select aka opengl_select goes all the way back to his work.

4.0 Source Code
3.6 Source Code
3.5 Source Code

old video of version 3.6

28 Likes

This thread on Blenderartists flew under my radar, I am really suprised it hasn’t gotten more responses :smiling_face_with_tear:, the build is great! And these features were very much requested for 2.8, so please folks, have a look!

1 Like

Incredible work. I’ve been searching for such a behaviour in Blender hoping it was already implemented but hidden behind the giant that the keymap system.

I am an architecture student, thus I’m usued to 2D/3D software having the “full enclosed” or “touched” behaviour implemented since it allows for a much better experience in selection. Thank you for your contribution to Blender!

1 Like

You’re welcome, glad you like it

Spread the word to all your fellow students, I’m sure they’ll like it too. :wink:

1 Like

Ooh, how did I miss this. This is fantastic.

1 Like

Will update to 4.0 soon, just announcing an announcement.

Website doesn’t want to rebase, just sits there and stays on 3.6 after telling it to change to 4.0. Updating in this way is a lot more work because you have to manually remove incompatibilities (a lot of it is just C to C++ missing files) before manually fixing them. At least that’s the only way I know how to do it.

So I’m just going to do it the easy way that I had in the past: checkout 4.0.x tag version, apply diff, manually fix conflicts, done. I might make a new branch on the website and ask for a build. Worth the attempt so it’s a more official looking download. If I can’t get a buildbot request granted I’ll just do like before and make a Windows build with link to the source / diff. Going to be a few weeks probably because it’s that time of year and I haven’t looked at the C to C++ conflicts yet. Usually not a big deal, but I haven’t looked at Blender source in a few months either.

1 Like

Is there any chance when you finalize V4.0X that you put a link that is more obvious. Have been unable to find the V3.6 ???
Cheers & Happy Holidays
MR HOLLYWOOD

Thanks for the heads up, didn’t know that my patch build isn’t there anymore. I guess those are a temporary thing when they make a build for you, so I won’t bother asking for a buildbot going forward. The only OS I can’t do myself is Intel Mac, and it looks like AMD finally has a Windows sdk so that should work for HIP. There will be a dropbox link for Windows and Apple Silicon in a few days hopefully.

If I don’t get any help from chat by tomorrow I will temporarily leave out the new icons for select through and auto-xray. Getting an error when I do a ‘make icons’. I also see that the links in the description of my youtube video are clipped off now, meaning they are unclickable, what a joke.

Lcas … thanks so much for your reply … What a bummer you having these problems. Your build sounded very interesting. All the best and happy holiday. Hope you can work things out.
Cheers
MR HOLLYWOOD

1 Like

If possible, please try to continue this, me and my friends shall contribute but we lack exp!

1 Like

Here’s a link for 4.0.2 (free / name a price on gumroad)
Luke’s Blender Build for Windows (gumroad.com)

I’ll put the source up on the website soon, and then add a build for Apple Silicon. I won’t bother with linux because most people using it would probably just compile it themselves. Top post link updated, will add new screens where necessary later. Everything is the same as 3.6 but some of the youtube video and 3.6 screenshots aren’t quite right with the changes to Blender’s 4.0 header etc.

I had 3.5 on gumroad, then a buildbot for 3.6, now gumroad again going forward with dropbox as necessary. When I did 3.5, it didn’t let me upload because free gumroad stuff had a filesize limit that was something like 200-250MB which is right at the edge of this build. With max compression it was able to fit the linux build back then, and for now at least the Windows build is small enough. That’s why each OS has a different page. If anybody needs Intel Mac or Linux let me know and I’ll ask for a buildbot, but from what happened to the 3.6 buildbot links, I’m guessing they are temporary.

I tested a lite build to make sure the features were there, and the release build for cycles with Cuda, Optix, and non-RT HIP. No intel or AMD gpu to test, but they should be there. IGP on 7900 CPU can at least see the render using cycles, but no RT stuff to test, and barbershop was saying a 2 hour render estimate. Let me know if cycles is working if you have intel or amd gpu.

@Ujumaki_Naruto
Sounds great, let me know if you need something. My exp isn’t much but it get’s the job done with help from chat and forums.

Some general help:
https://wiki.blender.org/wiki/Building_Blender

https://wiki.blender.org/wiki/Tools/Pull_Requests

https://wiki.blender.org/wiki/Communication/Contact/Chat

https://docs.blender.org/api/current/info_overview.html

Best thing for me figuring things out myself is using grep tools. On Windows I use dnGrep. Basically, once you have an idea where/what you want to change, you can track it down with this. Much preferred to guessing and scrolling, and scrolling, and scrolling like I did a few years ago when I got started :wink:

4 Likes

Lcas … WOW is your middle name :zap: FLASH :zap:. That was supper quick. :bangbang:
Cheers
:canada:
MR H

1 Like

You may want to rename your project- while you can legally sell/distribute Blender source code under the GPL license, you cannot do so using the name Blender, as that is a trademark of the Blender Foundation and they’re legally obligated to defend it

Alright I’ll ask about that in chat, thanks. I don’t know at what point I’d be allowed to mention “Blender 3D” in the description of it.

Well.. in fact is called “Luke’s Custom Build for Windows” ??

..too bad.. so only for W..

But also BforArtists.com uses..

The Power Of Blender Energized By Artists

Bforartists is a fork of the popular open source 3D software Blender.

Reimagined by 3D enthusiasts to make Blender intutaive and more productive

Bforartists is fully compatible with Blender files and addons.

Even if the offical site clearly says:

Blender is a registered trademark (®) of the Blender Foundation in EU and USA. The Blender logo itself is property of the Blender Foundation. The logo and the brand name “Blender” are not part of the GNU GPL , and can only be used commercially by the Blender Foundation on products, websites, and publications.

..so it’s somekind of minefield.. better ask for permission for referencing the project but use a distinct different name..

because: you collect money → commercial usage of registed TM !!!

1 Like

Don’t worry, not windows only. It’s just the main platform I use and the one I develop on. Will try to send up the source today and maybe the Apple Silicon build. If you use Linux and don’t want to compile, or you are on Intel Mac, I’ll ask for a buildbot once the source is up. Been busy with holiday’s type of stuff like playing Yahtzee and Monopoly.

The usage of “Blender” in the title of my stuff wasn’t an issue from what I was told in chat. It’s pretty clear that I’ve never tried to confuse anybody about what I’m doing. I wouldn’t worry too much about the name “Blender” in the title of what other people are doing, not in a legal sense. When a mod comes in here and uses words like, “Legally obligated to defend it” it gives off a different vibe than what I’ve experienced while working on this. But still those are some powerful, if not goofy as hell considering the context, words. So I had to go ask to be sure I wasn’t transported into the Twilight Zone™ (I have no affiliation with the Twilight Zone™, it’s publishers, creators, broadcasters, or advetisers :stuck_out_tongue_closed_eyes:)

If a mod is warning me about it here, then basically anybody could start getting a little confused, I guess? The only thing I can think of is that it could lead to a situation where somebody who actually is being shady would start saying things like “Hey, ‘Luke’s Blender Build’ gets a pass to use the name, why not my stuff?”

But I think if that were to ever happen, the issue would be the shady business, not using Blender’s name. Either way, I don’t care. Having “Blender” in the title was mostly a means of describing what my build is it is to anybody who didn’t know, and somehow stumbled upon my gumroad page. Come to think of it, I wouldn’t want anybody to think I’m some sort of food processor technician, now would I? I wouldn’t want to receive any ill-gotten money by stealing donations that were intended for a freelance kitchen appliance repairman :grin:

So I changed the name on my paypal button and the gumroad from “Luke’s Blender Build” to “Luke’s Custom Build”. Subtext of the paypal currently reads “Creation & compilation of custom builds for that app you like. Not endorsed by or affiliated with anybody. Just doing my part.” and the subtext of my gumroad is “A custom build of Blender3D for Windows with many features related to selection and the viewport camera. Consider any price above $0 as a donation to me, a person who is not endorsed by or affiliated with anyone.”

I’ll update my Mac and Linux gumroad pages to reflect the same once I have a build for them. Probably won’t be updating the Linux build from 3.5, but I’ll try to remember to at least change some of the text.

Seems to be a “wise step” .. :wink:

There was this example where someone made an LoD-fan roman.. but.. he sold it… → commercial basis → copyright infringement .. :person_shrugging: ..( https://entertainment.slashdot.org/story/23/12/21/2342211/tolkien-estate-wins-court-order-to-destroy-fans-lord-of-the-rings-sequel )

That’s pretty hilarious. Some guy writes a fanfic, then sues Amazon for making that LOTR tv show. Not just frivolous, but fraudulent. So he get’s countersued by Tolkien Estate for being such a cool guy. That’s what I got from skimming that thread anyway, seems about right.

A actually didn’t read the NYtimes article :sweat_smile: (and also i can’t without registering…)

…so in general he tried to sell “his” book… so now he even can;t give it for free (as the usual fan -fictions do and so do to infringe any copyright )…

…but you are smarter :stuck_out_tongue_winking_eye: