Wishlist of everything

[LDAsh72]

I would be honoured to contribute to the project financially since it's a big list, I've thought about it thoroughly.

Many of these are cosmetic but some of them are really important such as the ability to assign a material to a surface via a clipboard header - this allows for external material libraries without trying to use Radiant to view thousands of images. Another is selection by exact coordinates, for splitting maps into chunks to export separately. Tighter zoom for modern detailing, selection sets for adjustments to multitudes of elements not easy to select in the first place, independent rotations and dropping/snapping. These are vital, in my opinion.

I hope they will all be considered to make NetRadiant perfection now that DarkRadiant has most likely ceased further development, leaving only NetRadiant standing. It's very important to me that it continue development.

---

• Paste material to surface via header (clipboard)

• Select-by-coords input dialog (ala Sunplug)

• Selection sets (faces and vertices)

• Rotate objects independently toggle

• Drop-to-floor / snap-to-surface

• Tighter zoom in ortho view

• Select complete tall

• New Map toolbar button

• Rearrangeable toolbar items

• Vertically resizable toolbars

• Clear selection toolbar button

• Surface browser toolbar button

• Repeat transforms toolbar button

• Custom colour for green mapobject meshes

• Optional material header "textures" prefix

• Accept either material header / slashes

• Custom texture highlight borders and colours

• Optional horizontal scroll for texture folders

• Custom colour right-click selection box

• Custom purple text in ortho view

• Custom workzone colour

• Tooltip text to gray

.
.
.

[Garux]

Thank you for the offer, this is really appreciated. However my vision of perfection on average does not necessarily match vision in niche use cases.

• Paste material to surface via header (clipboard)
  Will input in statusbar similar to surface inspector be good enough? This would be more intuitive and also allow text copy/edit.

• Select-by-coords input dialog (ala Sunplug)
  Doesn't bounding brushes setup + select inside/touching do this? Doing via numbers input is super special case.

• Selection sets (faces and vertices)
  This is quite problematic, as these things are created on the fly. I'd start with undoable selection in this regard, same problem, but more feasible.
  Regarding selections there are layers and select textured surfaces.

• Rotate objects independently toggle
  This is interesting (technically). Tbh in doubts about real use cases, what they are?

• Drop-to-floor / snap-to-surface
  Exists, menu.help.mouse shortcuts.

• Tighter zoom in ortho view
  Seems np to make it tighter a bit, would 2x be enough?

• Select complete tall
  Exists, menu.help.mouse shortcuts.rect

• New Map toolbar button
  This is rarely used function, access via menu or keyboard is okay, no need to make toolbar intimidatingly complex.
  There is bigger feature idea, which would allow to have this, if user would like to: adding any editor command as toolbar button.

• Rearrangeable toolbar items
  I like current simple setup, which allows to hide buttons, rearranging would be extra mess.
  May be hiding all of them + adding any editor command as toolbar button would do it?

• Vertically resizable toolbars
  Unsure which kind of resizing is meant, have not seen such functionality elsewhere.
  You can customize toolbar params in .qss file. Also GUI theme with bigger buttons is planned.

• Clear selection toolbar button
  I'd say this is super niche, nobody wants to move mouse for most frequent action, which can be done by keyboard.
  adding any editor command as toolbar button would allow to add this, if wanted.

• Surface browser toolbar button
  adding any editor command as toolbar button would do this.
  This dialog has no much use with the current tooling.

• Repeat transforms toolbar button
  adding any editor command as toolbar button would do this.
  Is not the 1st aid function, finely usable via keyboard. Repeat menu may be detached to see the feedback, when many repeats gonna be done.

• Custom colour for green mapobject meshes
  This is controlled in .def/.ent/.fgd per game.

• Optional material header "textures" prefix
  Unsure what this implies exactly.

• Accept either material header / slashes
  Accept in which places exactly?

• Custom texture highlight borders and colours
  This can be added. Not that it feels worthy.

• Optional horizontal scroll for texture folders
  Dym optional horizontal scroll instead of vertical in textures view?

• Custom colour right-click selection box
  Dym rectangular selection by right mouse drag? Can be added, not that it feels worthy.

• Custom purple text in ortho view
  Dym adding user text labels?

• Custom workzone colour
  Makes sense for 2D workzone users.

• Tooltip text to gray
  Customizable in .qss. Need exact idea definition to consider it as default.

[LDAsh72]

Hey man, I've been trying to find a way to contact you privately about it. I feel bad coughing up so many demands out of nowhere while not offering anything.

The main issue is that (all) Radiants get treated as a texture browser, and while this might have been okay in the old days, now we're looking at up to 8K images and so many of them. I personally feel that the texture browser should exclusively handle only those being used by the map, not an entire project or shared between multiple projects. In our case it's approaching 10,000 entries. I use Chrome and the clipboard, this allows an external browser not even necessary on the same PC because the clipboard (material header) gets passed over the network.

There are other concerns, but if to choose the most critical I would say that's the one, as into the future it will only become a worse issue. As of now, all textures in Radiant are maximum of 2K and the engine uses (up to) 8K versions of the same graphics, but I'm unsure how authoring will be done into the future and more clarity is needed.

Sometimes people tell me simply "do not use Radiant", but I refuse to listen to fools.

[The-Gig]

The main issue is that (all) Radiants get treated as a texture browser, and while this might have been okay in the old days, now we're looking at up to 8K images and so many of them. I personally feel that the texture browser should exclusively handle only those being used by the map, not an entire project or shared between multiple projects. In our case it's approaching 10,000 entries. I use Chrome and the clipboard, this allows an external browser not even necessary on the same PC because the clipboard (material header) gets passed over the network.

I'm sorry, I lost track... Chrome as in "Google Chrome"? What's the correlation between Chrome and NetRadiant?

However, Radiant Texture Browser having a quick toggle to only show the texture/shaders you already used in that map sounds like a very useful addition to me (it's a long time I don't map... it sounds strange to me if it isn't a thing yet). Of course you would need to be able to enable/disable it easily, as everytime you will need a texuture for the first time (e.g. while starting a new map from scratch) you'll need to temporariy disable the filter. Of course the filter should not be enabled by default.

[Garux]

I've been trying to find a way to contact you privately about it

discord 246624639655215114

The main issue is that (all) Radiants get treated as a texture browser

I'd say this is serious issue, if an editor doesn't provide browsing textures to be used on geometry.

If the actual issue is vram, there are texture quality and texture compression options. Don't they help?
Or alternatively can generate downsized editorimages. D3 materials support editorimage, right?

quick toggle to only show the texture/shaders you already used in that map sounds like a very useful addition

exists

[xanhast]

quick toggle to only show the texture/shaders you already used in that map

first option on the Eye button :)

[xanhast]

In our case it's approaching 10,000 entries. I use Chrome and the clipboard, this allows an external browser not even necessary on the same PC because the clipboard (material header) gets passed over the network.

this is an interesting setup

at its core i think you're suggesting decoupling of the asset browsers and the editor due to the separation of concerns? or is this just the path that you've resorted to due to texture browser issues in radiant?