In radiant. Sometimes it can be helpful to build small sections which can be cloned and reused. I think the current answer to that is regions. It is my understanding that if one imports multiple regions each is a separate fully copied group of brushes. Regardless of the benefits, the implication is that if there if a flaw is discovered in the region (later on), one must destroy each copy and reload the region at each instance.

It would be nice if each instance of a region behaved like a symbolic link, where a change to the original regions would propagate our to the copies.

Maybe this is already possible, if so, I've not figured it how to do it. Anyone know?

Nice idea.

Yes, this is very common in audio/midi editors like cubase or cakewalk. Actually interesting coincidence. I was just thinking about how i miss this feature in NetRadiant a few days ago..

lda17h wrote:Yes, this is very common in audio/midi editors like cubase or cakewalk. Actually interesting coincidence. I was just thinking about how i miss this feature in NetRadiant a few days ago..

Its common in most major graphics applications too. And it would be a lifesaver in terms of work needed to rework a map. But it would break probably break comp ability with other editors.

tZork wrote:

lda17h wrote:Yes, this is very common in audio/midi editors like cubase or cakewalk. Actually interesting coincidence. I was just thinking about how i miss this feature in NetRadiant a few days ago..

Its common in most major graphics applications too. And it would be a lifesaver in terms of work needed to rework a map. But it would break probably break comp ability with other editors.

Well, it breaks compatibility in a good way So that should be not a reason against it. I guess also that there's always a pretty straightforward way to convert this .map format into the older one by just replacing all "links" by their template..

Well incomparability in the map format it would be a bitch for ppl like me who don't want to use NetRadiant (or rather more like to use another editor). That said, there are proly ways to make it work w/o compat breakage. but it would be messy.. as in assigning a entity key, lets say "groupid" with a uid shared by all "instances" and updating each instance after edit. You'd have to keep track of rotations and such done after cloning too tough..

q3map2 has a facility for this, using keys "_clonename" and "_clone". However, Radiant at the moment cannot render clones in the editor.

Can anyone find out whether this q3map2 feature actually works, and if it does, what are its limitations (it probably is brush only, but what else)? If it works out well in q3map2, I may try adding display for it to Radiant.