Quake3World

Reading this thread I thought a little poll might be in order.

Still using 1.2.13, I'm particularly curious what the benefits are of using 1.4


EDIT: Maybe I missed a version. Please mention this as well, so I can add a poll entry.

Netradiant - I win the game.

Oops... I added NetRadiant to the list and the poll was reset.

I've been using 1.5 as my stable everyday editor and I've been testing the development build of 1.6. I can't imagine anyone using anything older than 1.4.

Hmmm, shitty but understandable code for poll to reset after adding entry.

Stubborn fucker that I am, I again vote 1.2.13, and again hope for some explanation about how using anything newer is superior...

What no wordpad option?

PlanB, I used to be with you in the 1.2.13 camp but after migrating to Windows7 I had to make the swap over to 1.5. It was initially painful, but some of the features such as model rotation etc. make it a little smoother than 1.2.13. I wouldn't bother unless you're forced. :P

Windows 7, forced to 1.5... Any other version wont save the map files. They just make 0kb empty files.

Bacon wrote:Windows 7, forced to 1.5... Any other version wont save the map files. They just make 0kb empty files.

1.4 works fine under windows 7 for me, although I must say I've ran into the same problem you mentioned with new map files under Windows Vista some times as well.

I use 1.4 under Windows 7 as well.

I'm using 1.5. I wonder why you use older versions? Do they have any features I don't know about? 1.4 for example has the thicken command for patches for example, and selecting faces works different (better in 1.4 than in 1.5 imo). But in 1.4 selecting brushes by dragging a frame isn't possible, and that's mainly why I dislike 1.4.

Couldn't get the texture window to work properly in 1.5 (didn't display any textures) so I went back to 1.4.
Never tried 1.6 to be honest.

1.4 hands down. learned radiant in 1.4 and by the time i found out about 1.5 i couldnt get used to the switch.

and to get saving to work in 1.4 with win7, either use autosave function, or install radiant onto a external drive or something.

1.5's bleeding edge (I track the Subversion repo). Been meaning to check out ZeroRadiant but it failed to build on linux for the longest time.

Some ppl still use Q3Radiant .
One thing I remember to be very useful from Q3Radiant was to display the players "air-travel" of jumppads.

Such a plugin would be great aswell for gtk .15 ...

neoplan wrote:Some ppl still use Q3Radiant .
One thing I remember to be very useful from Q3Radiant was to display the players "air-travel" of jumppads.

Such a plugin would be great aswell for gtk .15 ...

Q3Radiant user here.

http://sst13.net/pics/jump-path-patch.png (red thing is a simple patch mesh in side view)

And what about some plugin for real-time lighting preview?

I guess that won't work. The lightmaps have to be baked into the bsp, and that can't be done in real time.

I think the real time lighting preview is for the newer games(doom 3,q4,prey) so see how it might look.

Noruen wrote:And what about some plugin for real-time lighting preview?

For testing local lights/mapparts, just make a fast test compile by clipping off the rest of the map with large caulk brushes. In this case, the light stage runs very fast.

How is that supposed to work if there are already entities outside the caulkbox?

The caulkbox must include the entire rest of the map: http://sst13.net/pics/caulk-cull-compile.png

Simply amazing! I didn't know this trick. Could really become useful some time.

Didn't regions at some point in the past do this (or maybe I'm thinking of a different engine that I worked on in the past). It might be something worth adding to Radiant/Q3Map2.

They have a function like this in VHE. Very useful.

obsidian wrote:Didn't regions at some point in the past do this (or maybe I'm thinking of a different engine that I worked on in the past). It might be something worth adding to Radiant/Q3Map2.

You are right obsidian, regions do the same, but I believe it only pulls that portion and leaves the rest, more or less like clipping a pic.