Autoenlarging, I don't know. Would have to see a prototype to be sure. It sounds possible, but I can't say for sure how easily I could adapt or accept it if it's too much of a change. Certainly sounds like neat feature (if not too complicated to add) that could just become a fourth layout option while keeping the floating layout despite its gtk limitations.
I have a fairly annoying issue of my own, where the camera jolts several degrees at a time, even when I turn it slowly. For some reason, it happens only after I select an object or I create a brush.
Using Windows 10. The old March 2012 version doesn't have the problem but Ingar's most recent build (June 2015) also has this problem. Why is that so?
This could be significant, he seems to have the same problem as me but on Linux: https://gitlab.com/xonotic/netradiant/issues/100
Well, I found a band-aid to my problem. It doesn't actually resolve the problem but it makes the editor not annoying again. Leaving the DPI scaling to the application instead of the system somehow fixes the camera despite changing nothing else (my system is already at normal scaling).
I can finally get back into mapping but it still feels weird that this is happening.
Good find! Still judders now n then, but way less often.
Thanks, quite worthy note about 2012 vs 2015 builds.
Basically comment on github is right, and the difference between these two builds is exactly that fix for touchpad on linux.
I'll consider reverting that commit back, since it's producing more harm, then use (mapping via non apple touchpad is the heck anyway (imo))
Does this have a MAC build somewhere? If so a mod should add it to the main post.
It got no mac build, but build system allows to make one
Some tip on requested 'align texture with given face edge' feature here:
I'm Amazed At How Fast You Built This!
Map Text Encoding
Some quirk I (or ericw, for that matter) discovered: apparently this version of Radiant saves the .map files in UTF-8 enconding which is probably fine most of the time, but can cause issues in specific cases.
In Quake, there are some special characters used for colored text and symbols that can be used in level/player names and centerprint messages. x. The problem is that the file encoding appears to be incompatible with the compilers, so these characters get all messed up in the compiled BSP and are displayed incorrectly in game. Converting the map to some other format like ISO8859-1 or even ANSI solves the problem and subsequent editing in Custom Netradiant won't change the encoding back.
In Radiant 1.5, message fields with those special characters would be garbled and trying to edit the corresponding entities could even lead to a crash. In Netradiant, the message fields are displayed correctly - except after converting to ANSI, they show placeholder characters, which isn't a problem, in my view.
This is not a big issue, and I'm not even sure something should be done about it, especially if there's a risk something else breaks in the process. At any rate, it's a little heads-up for people to know in case they run into the same issue.
What i see, is that GtkEntry handles these chars as UTF ones, and then radiant saves them correctly (not the whole .map, but only respective string)
I think that compilers do nothing with them too, so you end up with UTF chars in your bsp (which aren't understood by engine apparently)
I barely could find an application, which was truncating such strings in wished manner (they either show UTF one, or '?' char)
Texture Alignment - Face Projection?
Is there a way to align a texture to a face instead of to the grid? I have a sloped surface 30-degrees from xy-plane, and then 45-degrees around z-axis. I cannot seem to get the texture to project to the face, only the grid, meaning I cannot really get a non-slanted texture alignment. I can post a picture if I am unclear.
Does NetRadiant support the "Valve 220" map format?
Yes, you can get it non-slanted in this particular case (i'v got it by rotating a brush with texture lock enabled), but not every time, because default q1 map format is 'axial projection', which has quite strong limitations.
There is newer format from q3: 'brush primitives', which is face projection by definition and has no limitations (you can get axial or w/e projection with it); It is enableable via q1.game and is supported by modern ericwa's compilers.
Valve 220 format is almost supported except of a few malfunctioning tools in Surface inspector;
The plan is to make these 3 formats switchable via preferences for most of games and convertible to unlimited ones.
Probably video explanation of various texture projections in mapformats could be useful?
Thanks For The Info!
Is there any way to convert quake brushes to quake3 brushes?
Outside Of Radiant..
v0.15.10 of my qbsp ( https://ericwa.github.io/tyrutils-ericw/
) has a map converter built in. you can use it from the command line like this:
qbsp -convert bp something.map
will convert to Q3 brush primitives (iirc it writes the output to a file called something-bp.map)
You guys are awesome, thanks!
Great to see this is still improving! I can smell my mapping trousers warming up...
Valve220 map format has arrived btw .)
The Link Is Dead
You read about how to setup Radiant here: quakeone forum
Is there a backup?
Also, does this work on Windows 10?
That was odd tutorial anyway (was considering classic radiants)
netradiant-custom\q1pack\q1pack.txt is enough to setup; 1st post got to be updated
Also yes, it does work on Windows 10.
Yeah, apparently all the links are dead except for the Radiant direct download.
Just wondered if it's possible to make the free rotate tool (R) use some (customizable) fixed value like Step in the surface inspector, e.g. steps of 5 or 15 degrees - as quicker way of doing 'conservative' rotations than the Arbitrary Rotation window.
you can hold shift after grabbing the rings to snap at 15 degrees