News | Forum | People | FAQ | Links | Search | Register | Log in
The NetRadiant Level Editor
NetRadiant-custom is continuation of NetRadiant, based on GTKRadiant, which supports numerous games, with some emphasis on Quake.

win32 build
win64 build

Simple install instructions are included in q1pack\q1pack.txt
First | Previous | Next | Last
Thats No Good Lol 
This is so-called 'stupid quake bug'
Orienting model is much simpler via rotation manipulator
ad_quake misc_model definition: angles: "pitch roll yaw"; actually is pitch yaw roll :) 
A very small/minor feature request. The pointfile that Q1 compilers generate uses the extension .pts instead of .lin, so it would be nice if the Pointfile function in the editor searched for a .pts file as well if it can't find one with .lin. 
True. Does .pts uses same format, as .lin? 
Yes, when renaming the file it displays fine in Radiant. 
This is so-called 'stupid quake bug'

I think its more just a difference in how Quake 1 interprets angles_x versus radiant. I'm not saying radiant's wrong - I assume its treatment of angles conforms to how Quake 3 does it.

Orienting model is much simpler via rotation manipulator

Yep, that's what I am using.

ad_quake misc_model definition: angles: "pitch roll yaw"; actually is pitch yaw roll :)

Yes, although that's an unrelated issue I think.

I'll just check with the coders to see what Quake 1 is doing with angles vs Quake 3... 
It's not question of interpretation, but well-known pain-in-the-ass bug, making even more problems, than necessity to inverting pitch everywhere in engine.
Problem src is mathematical mistake in VecToAngles function;
Bug is present in q1, hl, q2 and possibly in q3 in some masked form, since function is still wrong there.
Need to sorta support that behavior in editor, it seems.
I'll look, if this is possible.
Is it problem only with misc_models, or some more entities use angles key? 
Yeah Sorry My Mistake 
I guess it is a bug with quake, not a "feature", heh.

Well, existing workaround is easy now that I know what's going on. However, it could make sense to support it in the editor, for future users who are not aware of the bug or don't want to mod it out in the quakeC.

I am not aware of any other entities it affects - I think misc_model is the only thing where you want to mess with angles_x and also see the model in the editor. 
Flipping And Grid Offset 
Hi, I've noticed a change in behaviour with the flip operation, from previous versions, that for me is undesirable.

In older versions of NetRadiant, when you flipped an object, it sort of mirrored it along a grid line, so the components still had the same grid relationship when flipped. I find that 90% of the time this is what I want.

Now, it makes it so the flipped object sits in the same space as the original, but typically this will just mean all the components of the flipped object are now sitting on the wrong grid, and it takes longer to re-position it.

See image here:

This is not a problem for simple objects, but with large complex structures, I find I have to spend more time shuffling it into the desired position.

Could I request either adopting the old behaviour again, or adding an option? 
Ok, i'll try to add snapping of transform origin specially for flip commands.
Atm there are two options to get old result, but behaving like that by default is likely to be better. 
Great, thanks for this :) 
Entity Def 
I noticed the Q1 entity definitions file contains some errors. The box size of the powerups is wrong, posing the risk of them falling out of the level. There also were some non-existing entities and missing spawnflags here and there. Apart from that, I was almost inclined to rewrite the entity descriptions, because the writing is inconsistent and in some places misleading, to say the least. Maybe I'll do it at some point.

If anyone is interested in a slightly updated version, you can grab it here
Nice one, numerous worthy commits there.
I do grab it for sure :) 
Found Another Error In The Def 
The spawnflag to have a light start switched off is 1, therefore the correct line in the definition must be:
<flag key="START_OFF" name="Start off" bit="0"/>

Btw, this thread should probably be renamed to "The Custom NetRadiant editor" since it's really only about this new version. 
Which Ironically Was Introduced By Myself 
Don't Look At Me 
I took my cues from you all in the General Abuse thread before compiling this into one list. Ironically, I still have never even used any Radiant. 
the default for all spawnflags should be zero. 
Qmaster: I meant the error was introduced by me, because the whole start_off part is missing in the def file that comes with the editor and I added it in the first place.

metl: It is. Just the way the def file works: bit=0 makes it spawnflags 1; bit=1 is spawnflags 2; bit=2 is spawnflags 4 and so on. 
Ah Ah 
i see. 

* doubleClick/Enter in Entity inspector Class list = convert entities
* ctrl during creating brush = cube brush
* m3: apply texture name and alignment to selected primitives
* ctrl + shift + m3/drag: project tex from face in tex clipboard to brushes(BP format) and curves[/list]

* on worldspawn entity create/convert to one do most expected move-selected-primitives-to-worldspawn
* convert point entity to group one = placeholder brush at origin + remove origin key
* convert group entity to point one: set origin key to contained primitives center
* fix uniform rotation operations for eclassmodel, miscmodel entities
* scale miscmodel entities uniformly
* added func_detail to world and detail filters
* region->set_xy: using active projection, not just xy one; is subtractive (no region off before applying)
* new brush prefab: icosahedron
* refactored CSGTool, improved Hollow::diagonal algorithm stability
* fix scaling for doom3 brush format
* Pointfile function: try to also load .pts leak line file (q1), if .lin isn't found
* snap transform origin for flip commands
* change light intensity save format from %f to %g to prevent .99999 on transforms
* support 'stupid quake bug' (invert pitch in angles)(generic and miscmodel ents)(cfg: entities="quake" in .game)
* clipper: place 1st and 2nd points far, 3rd near to ease 3 points clipping
* fixed q1 entity definitions (negke)
* changed surface inspector behavior from 'set whole texture projection' to 'set modified value' (makes sense for multiple surfaces selected)
* BP: surface inspector and Tex* binds scale texture by its axes, not world axes
* BP: fix rotation of tex projection with scale S != scale T
* BP: fix ruining nonregular tex projections by surface inspector (for example after fit/seamless/arbitrary projection)
* jump over tex projection scale = 0 case, while modifying one (AP and BP)
* fixed and improved normal finding in patch texture autocap algorithm
* removed axis cycling in patch cap texture; using autocap
* patch cap texture: project, using brush texture projection math of current mapformat to make it seamless with brushes by default
* Surface inspector->Project functions work for curves (in AP map format too)
* place created simple patch mesh not in middle of bbox, but on edge to make result more usable
* prefs-interface-layout-single scrollable toolbar
* tweaked Human Radaint GTK theme: toolbar pixmap separators, more compact toolbar
* Human Radiant Dark GTK theme
* new texture lock algorithm for BP map format, supporting any affine transformations
* more robust texture lock algorithm for AP map format, locking what is possible to; also improves seamless face2face tex paste function
* experimental fix of rendering scene and evaluating brush/patch representation TWICE on every transform (literally after every mouse move fraction) 
That's A Great Update! 
Thanks For The Update 
very happy to see lots of little fixes for things that bugged me in the past!

For me, the holy grail would still be a "one-click" method for rotating a texture to align with a given face edge, but it's still great to see the various little texturing improvements in this update. 
* doubleClick/Enter in Entity inspector Class list = convert entities
Hm, I always used that to turn world brushes into the specific group entity. Seemed more intuitive than the m2 menu for some reason.
While allowing group<->point conversion is neat in theory, for my purposes anyway, it's really a non-standard edge case thing that I'm not sure needed dedicated editor support. By "dedicated" I mean a way to actively do it, rather than simply accepting manually converted entities.

Not sure if this is actually the case, but earlier on it seemed like an increased UNDO queue size does not affect redo in the same way?!

I only just noticed the color/theme settings. Good stuff.

Minor feature idea: There's that option to make the clipper use caulk. Since in Q1 there is no "caulk" texture, there could be an extra checkbox to make the clipper use "skip" instead. Or maybe even one with a field where you can enter the name of any texture to be used when clipping. 
Or maybe even one with a field where you can enter the name of any texture to be used when clipping. 
"one-click" method for rotating a texture to align with a given face edge

Interface could be something like: select face, then (whilst holding a key combination) just click on/near one of the face edges, and it rotates the texture to line up with the edge. 
...maybe 4 different key combos to specify which side of the texture (top/bottom/left/right) butts up against the face edge. 
First | Previous | Next | Last
You must be logged in to post in this thread.
Website copyright © 2002-2022 John Fitzgibbons. All posts are copyright their respective authors.