For $260? Yeah, it BETTER be built like a tank. 

More like $70 for the Lite 2. Still quite a bit for a keyboard, then again, I've been using it non-stop for 15 years. The other computer in the house generally needs a keyboard replacement every year or two, so it probably all evens out in the end. 

I just buy a clean refurbished one every year at a thrift store for a buck or 2. Most haven't ever been been out of their wrapping.

And I swear, somehow cheap keyboards type better. 

�ber offtopic 

ontopic 

Looks very familiar!

http://www.polygon.com/2014/1/12/5299450/everquest-next-landmark-dev-diary-details-advanced-building 

It's basically selection brushes, but it's rendered differently and it seems a bit more useful like this. 

I can't seem to make them work for moving around in the 3D view. I found where to change this in the preferences but it just doesn't seem to take. It shows up, down, left and right as the keys but they do nothing.

I don't like the defaults at all, even at maximum speed cranking the scroll wheel is tedious and my finger starts to hurt after a while. For some reason I find the middle mouse button awkward to use. 

Also, what are you trying to do with the Arrow keys? What OS are you on? Which version of TB? 

Windows 7
Mouse is a plain old Logitech M100, $10 at Walmart.

I just downloaded TrenchBroom today (and the VC runtime). It says it's version 1.1.1 Build 368. I had tried it last year on a different computer but it wouldn't work with the video card in that computer. This one is a GeForce 210 and display seems fine.

I just want to drive around in the 3D view the same way as in Worldcraft and Netradiant, arrows move forward and back and strafe right/left. Aim with mouse. Just like Quake :)

I was also having problems such as clicking on parts of the interface didn't do anything and the arrow keys wanted to act like the Tab key.

I maybe messed something up so I deleted the TrenchBroom registry key and I'll start all over. 

Please try if the WASD keys work after you deleted the registry key. Also make sure that the 3D view has focus when you try to move around. Finally, TB doesn't have a property flythrough mode, i.e., you cannot use the mouse to aim while moving around with WASD, but you can right drag to emulate that. 

is working now, but I never did like using them as controls. 

I tried changing the wasd keys to the arrow keys, but couldn't get them to work correctly. What's weird is that they would work if the menu was popped up, otherwise nothing.

Also, why is it that none of the other actions that used the arrow keys were conflicting until I set the arrow keys as movement keys. That was kind of strange. 

 

uses Voxelfarm
http://voxelfarm.com

Author seems to be playing with editing methods from time to time. 

I removed all the conflicts and had the arrow keys used only for camera movement and it wouldn't work.

So it can't actually be done even though it looks like it's set up correctly in Preferences? 

if it doesn't it's a bug. You can file a bug report on github, and if it's a quick fix I'll release an update. 

Sleep, how do I make these usable?

I remember you said the texture name can be forced by enclosing it in "" qoutes - did you mean doing this using a find and replace in Notepad++?

Will Trenchbroom respect the change?

Will it revert it to none-quoted texture names if reopened?

Will I need to redo the find and replace if duplicating brushes with their textures named in such a fashion?

All stuff I can find out by experimenting, just haven't got around to it yet and a bit of extra info would help.

Cheers 

If it's really important, I'll try to hack it into the map parser, which is the source of the problem. And no, if you save it the map, it will discard all the double quotes. 

So I can do one changeover as a test and then only worry about it for proper testing builds.

I think I can live with that for now, it's pretty easy to run a find and replace from a text editor. 

I'll make sure that TB2 doesn't choke on those. 

and should really be changed to _alpha or something else etc. 

Whoever came up with that has clearly never opened a .map file in their life. 

 

but sadly, this doesn't matter - I'll have to fix the parser for it anyway.