If this is your first visit, be sure to
check out the FAQ by clicking the
link above. You may have to register
before you can post: click the register link above to proceed. To start viewing messages,
select the forum that you want to visit from the selection below.

Bridge

Introduction
Back in Blender 2.4x when you were in edit-mode and pressed F, you got the option "Skin Faces/Edge-Loops". Recently when I was working in 2.5 I needed this functionality as well, but unfortunately it isn't available yet in 2.5. Hence I decided to write my own implementation.

It works fine for my own needs, but if I'm not certain if it is useful for other people as well. Some examples:

Download and instructions
I've implemented it as a python add-on that works with Blender 2.54.
You can download the script from my website: <bridge version 1.0.0>

If you don't know how to install and enable add-ons, you can have a look at this video at BlenderCookie (installation at 3:24).

The add-on extends the functionality of the existing Make Edge/Face function. It leaves the old functionality untouched, but if you press the F-key and the old function can't handle it, the bridge function is executed. So the simple instructions are:
- Install add-on
- Enable add-on (it's called "Mesh: Bridge")
- Make selection in editmode
- Press F-key (or another key if you manually changed the keymap)

In the tool-panel two options show up after the tool has run.
The first is "Reverse". This is an option you can enable if you get weird results.
The second is "Mode". This determines the algorithm used for bridging. Most of the time "Shortest edge" should give the best results.

Request for help
What I need feedback on is if it works as you would expect (no weird results, crashes, etc.) and if you miss anything. Especially feedback from experienced modellers is highly appreciated.
If you get any weird results I'd be very happy if you could provide a .blend-file with the mesh that gives problems, or a picture (even though an images doesn't give all information).

Thanks in advance.

Last edited by Crouch; 25-Mar-11 at 16:46.
Reason: Integration into LoopTools

I think all of the settings are saved to the default blend. so if you're loading a new one, then the settings wouldn't be applied as they are pulled out of the new blend instead of the default.

I'm guessing, this is so you can have settings particular to the project you are currently working on. ie. one project/blend has certain settings, open up a different one that needs different settings and you wont have to mess around in the settings since they come with the blend, then switch back to the first without any settings hassle either.

It's definitely different than most apps, but seems like a faster workflow. It'll just take some getting used to.

But it would be nice to have a way to apply default blend settings to the current blend. So if you open up someone else's blend who has weird preferences, you can quickly set it to whatever you're used to.

I think all of the settings are saved to the default blend. so if you're loading a new one, then the settings wouldn't be applied as they are pulled out of the new blend instead of the default.

I'm guessing, this is so you can have settings particular to the project you are currently working on. ie. one project/blend has certain settings, open up a different one that needs different settings and you wont have to mess around in the settings since they come with the blend, then switch back to the first without any settings hassle either.

It's definitely different than most apps, but seems like a faster workflow. It'll just take some getting used to.

But it would be nice to have a way to apply default blend settings to the current blend. So if you open up someone else's blend who has weird preferences, you can quickly set it to whatever you're used to.

To be clear this is what I did:

Opened a default scene. Added an add on - in this case the Space Bar menu.

Saved this as a default. When I opened up a production file, the add on was there when you click to see what is enabled and it was also enabled. However hitting space bar does not invoke the add on, rather, it gives you the search menu.

The fix was to disable and enable.

From my experience certain things you enable in the default settings remain when you open a blend file. As far as I know, it is pretty much everything except screen spaces and basically all of the other things that get saved with a file, such as grid resolution and so on.

What is confusing is saving a default set up also saves the entire file. But if you load a new file only the preferences remain.This seems to be the case also in 2.5 In particular the add ons.

However there seems to be a bug or issue or something with add - ons. That is what I was asking about. Assuming you knew. Because the way you worded it.

Does any one know?

In any case, that may also be the fix for Ninth Jake - to get back to the point.