That new NetRadiant is a pro-click btw, for anyone still stuck on the 2012 version. Fixes loads of stuff and runs a lot better! (the 2012 version hogged my cpu when flying around in the 3d view for some reason) 

Also somewhat misleading since this is actually about the recently modified "custom" version which is a fork of the original Netradiant. The later seems to have gotten at least a little attention by Ingar up to 2015.

Having said that, this new version does look nice and has the floating windows layout working/fixed - something which the other developers/maintainers seem to have been incapable of doing.

How does one bring back the classic (shift+drag type) selection box? 

Gonna give this a shot. 

Yeah really digging the new bits here and there in this version. Problem is, to find out what's new, you have to read through an eleven page thread. 

you can read the changes in changelog-custom, new mouse shortcuts are documented too. 

One thing I really like in Netradiant is the ability to just click in the 3D window and move around in the map as if in Quake using noclip. I can use the mouse and arrow keys exactly the same way as I do in game. I hope that hasn't been changed. 

you can read the changes in changelog-custom

Lol, oh right :} Chalk me up as another one of those fellas who always misses the readme file...

Rick: 3D window movements are the same as before, and for me it runs silky smooth now (before it was a bit chuggy for some reason). Only crit is that the FOV is locked to 110 (before it was 90), but I have requested the FOV to be exposed in preferences in the q3df thread (my username is SlugWobblerBumbleChops). 

have a Mac version? 

About where the custom settings are stored, because bugger me it took me a while to figure this out.

If you create a subdirectory called "settings" in your NetRadiant install, the install becomes "portable", that means it'll write its settings there. If you don't do this, it will write its settings in some bullshit random directory like C:/Users/ben/AppData/Roaming/....blah blah blah....

E.g. on my pc, my "portable" settings folder would be:
C:/NetRadiant/netradiant-custom/netradiant-custom-20160911/settings

Now I *think* the new NetRadiant comes with a portable settings folder by default. Old NetRadiants certainly did not though. Check yours to make sure! 

Anyone by chance registered at the q3df forum?

Three things about the Custom Radiant: it crashes if the mouse is locked in camera freelook mode when the camera window/Radiant is moved to the background by some other program taking priority on screen. Floating window layout, but probably occurs with the other modes, too.

There's still (or again?) that feature from 1.5 that adds numbers to the target/targetnames of copied/cloned entities. Always hated that as it does more harm than good. Used to be removed in NetRadiant. I wish it was disabled or at least had a field to customize it where you can choose whether to have it append numbers, letters, any kind of string, or leave the field empty to keep the original names.

When rotating entities with the 90� buttons, it adds 0.000003 instead of "0". 

How do i reproduce that crash exactly?
Was there 'freezepointer: can't freeze' assertion?
There is focusout handler, that disables freelook, once app is focused out and it works well in all 1.5 branch radiants.
XYwnds have that handler too, but one never worked in nonfloating layout, untill i accidentally fixed that by adding some focus-in events -) (in 9.11 release)
Texbro has no such handler atm, thus it's possible to alt+tab, while tracking (m2), and still keep tracking, once switched back; though is unlikely to get crash here, since tracking is done in widget's center

2.Need some more extended data on this, since i can get both types of behavior in all 1.5 branch radiants
What do you do, in what version used to be removed...

3.Is not real problem. Might think of adding some rounding to int later (for gloss) 

I haven't found a reliable way to reproduce the error, yet (although it did occur several times since). Radiant.log doesn't show anything, and there's no error message by Radiant, either (only the standard Windows thing "The application has stopped working").
What sometimes seemed to trigger it is switching to the MP3 player (VLC in this case) with alt+tab or win+tab while mouselook mode is active. Upon switching back, the camera window is behind the 2d and entities windows and mouselook is still active for a brief moment before the error. At other times, it works.

I'll report back here if I have more information.

Target/targetnames: afaik the name change upon copying/cloning entities were introduced in Gtkradiant 1.5 and it was removed in Netradiant (Yngar branch).
I like to keep track of the entity linking myself and adjust it accordingly. When making single player maps, often multiple entities are targeted at once, all with the same targetname; or, when scipting entities, e.g. a chain of triggers or waypoints, it's really annoying if the editor constantly screws up the numbers.


Some other things:

There's an error when using doubleclick on a texture in the texture window:
radiant/texwindow.cpp:785
assertion failure: pointer "archive" is null
Obviously standard Q1 editing, so there are directories or shader lists.

When zooming in and out repeatedly with alt+mouse2, the focal point changes. It doesn't stay at where the mouse arrow was when starting the action.

Dragging the horizontal borders in the entities window, the ones between the entity list/description/keys, is wonky. They appear to be somewhat linked and can't be moved independent of one another in order to enlarge a section without affecting the other.

File menus (open, save, ...) and preferences should be always on top until closed - currently, they can get behind the other windows.

Three ideas: when using ctrl+mouse1 clipper, it would be nice if the clipping could also be executed with mouse3. This way, one could do fast clippings without having to lift the hand off the mouse to reach the enter key.

I noticed that the outer grid coordinates in the 2D window are gone. Can't think of the correct word right now - you know, where it says 0...1024...2048... on the sides. I found them useful, especially since Q1 has restrictions when it comes to map boundaries.

Would it be possible to allow the editor to accept multiple entity types with the same classname in the def file? For example, "trigger_multiple" as both brush and point entity coexisting at the same time. In the other versions of Radiant, there could be only one; the other type would disappear from 2D/3D view.


By the way, I really appreciate your work on this. I had already given up hope of ever seeing useful development on a Radiant-type editor again. Many nice additions/changes on top of Win10 support. Good job!