It's just something that most of my 3D apps have. It lets you navigate your model very quickly. You just point at what you want to get closer to and zoom. It's a lot faster than trying to aim the camera first.

Just a suggestion! 

But I'd rather have it work independently of the Alt+MMB thing, as that is merely a replacement for using the mouse wheel to zoom.

Maybe something like Shift+Mousewheel / Shift+Alt+MMB. 

What exactly does it do? Does it just move the camera position or does it also point the camera to where the mouse points, effectively rotating it? 

Here's a quick video of me doing it in Modo:

https://dl.dropbox.com/u/161473/Misc/ScreenCapture_3-18-2013%207.36.49%20AM.wmv

The way it works in Modo is:

MouseWheel - Zoom along camera angle
Zoom - Zooms towards the mouse cursor 

Actually, never mind my video. This is a WAY better explanation of it, using Blender:

http://cgcookie.com/blender/2010/07/03/tip-zooming-to-the-mouse-cursor/

This is a very tablet friendly option, BTW, as there's less navigation to do. You get where you're going in one zoom as opposed to a camera turn and THEN a zoom. 

So it just moves the camera and doesn't rotate it. You're saying it's tablet friendly, so maybe it should be the default for Alt+MMB after all.

Than? 

Tablet wise, I think Modo has a well thought out navigation scheme.

Rotate - ALT+LEFT_DRAG
Pan - SHIFT+ALT+LEFT_DRAG
Zoom (to mouse) - CTRL+ALT+LEFT_DRAG

It all hinges on the ALT+LEFT_DRAG with some modifiers thrown in.

Not saying you should do this but it's more to point out how I can totally navigate with a tablet by simplying pressing and dragging the stylus. I don't have to use the pen buttons at all. 

And to be clear, I'm not too fussed about TrenchBroom being tablet friendly I was just riffing on what you had said earlier.

I'd never considered using my Cintiq to map for Quake ... hmm ... 

So I guess a preference option to toggle zoom mode would be good. 

I wanted a non-mousewheel way of zooming, since I don't use a mouse at all. I had some wrist strain a few years back and since then just switched to a tablet for almost everything. I also have a Thinkpad laptop which has the nipple pointer and no mousewheel, though I will plug in my wacom if TrenchBroom becomes a bit more stable on Linux (lots of crashing with the clipper and vertex manipulation on my lappy :( )

I'm rather used to Maya 3d navigation, which is similar to Modo I think. I think that is the 3d software standard, pretty much - it's only Blender that has a totally different navigation scheme :)

Worldcraft actually has extremely good and well thought out controls. It separates everything into modes (brush creation mode, entity mode, zoom mode, camera mode, texture application, clipper, vertex/edge edit), but has great controls for each mode and you can hold space to enable camera mode at any time (each mode also has shortcuts). I'm not suggesting you copy it though. 

has by far the worst controls IMO. The moded interface is a productivity killer, at least it was for me. My mapping got twice as fast when I switched to Radiant just because I didn't have to switch modes to do anything anymore. </rant>

But about those linux crashes - that is really odd because it shouldn't crash in vertex editing or anything. These things are exactly the same on every platform. Menu crashes I can understand, but the other stuff? Hmm. Spirit also hasn't reported any unstability with the regular editing functions.

Maybe I will have to set up a Mint Linux to try it out. 

"crash in vertex editing" in linux? Not sure if that's similar to the issue I experienced with my crappy video card, that I resolved by going into trenchbroom preferences and turning "OpenGL Instancing" to "Forced Off" fixed that crash. 

Than, did you try that? What exactly crashes the editor for you? Because I think the clip tool also uses instancing. 

XD 

is set to forced off in the menus. Without it turned off, vertex editing crashes instantly.

The console prints this info at startup:
Renderer info: Mesa DRI Intel(R) 965GM x86/MMX/SSE2 version 2.1 Mesa 9.0.2 from Intel Open Source Technology Center
Depth buffer bits: 24
Multisampling disabled
OpenGL instancing disabled

I just tried again and this time there was no crash, but after clipping I couldn't seem to creat a brush. I could go into vertex edit mode though 

*obligatory snide comment about Intel's integrated graphics* 

Yah, same here. Intel HD Graphics 3000 video card.

SleepwalkR knows they are shitty. :) 

The new ones aren't as bad though. 

It made me bring out my old tower and send it in for repairs, because that's my gaming tower. it's from August-2011, but power button suddenly stopped working aroung August-2012, and I just let the tower sit there for months.

But, I want to try trenchbroom without issues, so, TB is what pushed me to pull this tower out and send it in for repairs. It has decent gaming video card in it.

I'm on my laptop, in the meantime. Which has been fun, because I've gotten a nice feel of remote computing now, and bring my laptop to my couch, or to my stand-up desk. Nice to be able to simply move it where ever I want, including my patio outside. 

 

mfx, I don't care that you don't care. Who cares that you don't care? 

Whoever is more on topic wins. 

mfx - You misspelled "Cool story, bro". 

mfx, and Willem are on my shitlist now. grats, guys. One less person to respond/comment to anything you have to say, or any screenshots you post, or whatever. Less work for me. :)

"Who cares?"

Well, since the story was about TrenchBroom, then I think SleepwalkR would find it a nice bit to hear that his editor pushed me to fix my tower to try his editor. Maybe.

You sound like a bunch of jealous girls that have no such stories to share. Not my problem, that's your problem. Bye. :) 

You're just barely holding this new persona together dude. Best of luck.