Are you getting an error from the compiler or from the GUI frontend ? The compiler should definitely support this. 

So, I'm just saying, if you can find something that keeps things as simple and straightforward as they are now, it's win-win. But I just feel more precise movement would save me a lot of time in the end, and I'm skeptical a non-gizmo thing can do that. They've been in virtually all 3D packages for almost 2 decades now which should account for something. But at the same time I would honestly love to be proven wrong. 

I get an error from the command line when I run the compiler and the BSP fails to run. (error code 01) 

For me, the best thing about gizmos is it means you can securely move an object in any direction without having to get the camera view in a better position, and more importantly you don't have to keep holding different keys on the keyboard. 

So, I'm just saying, if you can find something that keeps things as simple and straightforward as they are now, it's win-win. But I just feel more precise movement would save me a lot of time in the end, and I'm skeptical a non-gizmo thing can do that. They've been in virtually all 3D packages for almost 2 decades now which should account for something. But at the same time I would honestly love to be proven wrong. 

 

 

You refreshed the page. Your browser sucks. 

Can mean whatever its perceived as.

The task requirement is 'tool that allows precision movement along specified axis'.

Doesn't exactly roll off the tongue though. 

 

 

Changes
- Improved Quake.fgd and Quoth2.fgd (thanks negke!).
- Improvements to clipboard pasting.
- Fixed a crash bug when loading maps with invalid brushes. 

I saw this in the notes for 1.0.3 and wanted to say that:

"Objects are no longer displaced when duplicated"

This is still offsetting duplicated things for me. Do I need to clear a config file or something? I checked the About box and it said 1.0.3 ... 

Same with 1.0.4 ... heh.

Am I interpreting that correctly as saying ctrl+d shouldn't be offsetting anymore? 

I think it *should* displace but should only displace one grid block toward you. 

Displacing sucks. :) We've talked about it already but every time it displaces my duplicate, I have to move it back into place before working with it. It's almost never what you want... 

I made an error, the displacement will be gone in 1.1. Sorry! 

Heh, no worries! Thanks... 

I just realised that CTRL+D displaces by a small amount rather than the huge amounts that Copy and Paste are doing... I've wasted so much time (also, if you're duping brushes you're moving it somewhere else, plus it's better that it displaces so that you don't accidentally dupe multiple times without noticing). 

You'd think that, logically, but my experience says otherwise. Over time it becomes far easier to dupe in place and then move it since at least one of the axis that it got bumped on is going to be wrong. 

yeah, that is my experience with it also. I almost always follow a Ctrl+D with a Up and Left to push the brush back to the original spot. 

There is something like this in Quark.
The big difference with quark vs (afaik) all other editors is that there is a tree view of the entire map where you see individual entities and brushes as nodes in the tree, grouped by brush entities or user made group folders.

entities that are defined in a certain way (for example: trigger_relay, trigger_counter) do not appear in the map at all, only in the tree view. Since quark407 was the first editor I used, I was really confused about how script entities were like when I went over to radiant.
I actually still find them very cumbersome having all these boxes floating around with lines going everywhere. They are a very poor method of doing any kind of scripting.

There is a downside though: when you load a map like this in other editors, you end up with a giant pile of overlapping script entities all at '0 0 0'. :\ 

This looks really interesting! Is there any plans to support other closely related Quake1-engine games? Specifically: Hexen 2?
I REALLY need a better editor for the levels I am making... 

Quake 2 and 3 are on my todo list. You're the second person to ask for Hexen 2 support. I have no idea what would be necessary to support that game though. But I'll look into it once I start supporting other games. 

I think all it takes to make it support a wide variety of (id-engine) games are surface/brush flags and patches (curves). Everything else is a matter of having a proper fgd. Quest 2.4, for instance, supported HL, Hexen 2, Sin, and several Q1-3 mods out of the box with this additional fuctionality.

Having some visual representation of entity linking would be nice (target#/killtarget#->targetname#) of course, it would have to be toggleable to avoid a mess. necros, I usually place script entities close to their area of action for easier accessiblity. But, yes, things like relay and counters can be at 0 0 0, or even lack an origin field altogether. However, the editor must have an entity list then (TB needs one, too, if it doesn't have it already).