The workflow for just mapping and making textures isn't bad but as already discussed above the toolset for modeling is far worse and if you want to do stuff like edit the conchars file you have to pray to your deity of choice that you remember to export and import in the right order in the right programs (including goddamn AdQuedit which is apparently the only editor to properly handle it as the specific console characters file instead of just a .spr). 

Hmm… Creating whole new tools for simple stuff like conchars editing doesn't sound like the best approach for me.

A GIMP plugin for loading and saving LMP images could be enough. 

GIMP is awkward and unproductive.

Takes 5, 10 or 20 clicks to do what many other alternatives can do in 1 or 2.

It also takes things easy to do in most other editors and finds a way to make them needlessly difficult. 

Redfield, you can have a dozen different colored apples. MDL supports multiple skins. Just create additional skins for your model in QME with 1 click. Then recolor your skin with your favorit editor and add it into your mdl file. Yes, adding skin textures is also done with QME with another click.

You may speak bad about QME, but it can do unique things to your mdl file that not many other tools can do. It has its strenght and its weakness. Just like all other tools out there.

If you do not want to use it for modeling thats fine. But do not underestimate all the other things it can do. Yes, also setting (trail) flags to models and so many other stuff. 

re: QuArK. I use it to take a look at models and wads. Wally is really buggy on my machine and the white background makes it difficult to see the textures. QuArk uses a black background and show animations for buttons etc. I've never used the level editor but for other things QuArK is pretty handy. The UI is terrible. 

I would like to revise my answer to:

A single map by me that I actually like which isn't part of any sort of jam or speed scenario.

I'll be happy with that. 

Quark,what good is that for anymore?

I use Quark4.07 for lots of model additions, may be old but gold for me. 

QuArK duplicates all vertices belonging to both front-faced and back-faced triangles. 

Good for view, not for saving

I miss QuakeWebTools. The dragndrop rocked and worked for viewing sprites and models and exporting skins. What happened to that? 

Quake Web Tools
You should be able to run it by yourself. 

Another remarkable fact, although nowadays not so important, is that models loaded in quark and saved again tend to incline a lot of size.

What I'm trying to say is, when a model has a size by example 800kb one upload to Quark and saving it again reduces it to 200kb, without noticing changes.

I have no idea why this is so, but it saves some space, especialy with large models. 

Models saved in qME 3.0 contains additional higher-accuracy vertex coordinates (which are ignored by the engine, but are useful when modifying the same model again). Re-saving them in another editor will delete that data.

qME 3.1 changed that behavior, storing the higher-res vertex coordinates in its MDO format only.

There may also be other kinds of extra metadata stored in MDL files. 

That explains a lot. Never paid attention to it.
I can't see no difference between both. The grid is rather rough I thought, 512x512. 

Quake 2 Stuff, mainly now that we will have the tools and ports to it.

A Tenbebrae Reborn with Quakespasm and vkQuake stuff, or vice versa with vkQ. 

All I really want is to get an engine like quakespasm to have the ability to use a frame rate higher than 72 without the physics messing up 

Use QuakeSpasm-Spiked then. 

Type host_maxfps 0 in Quakespasm-Spiked console to decouple the framerate. More info at 3.1 here 

Off hand, that is probably is a bad idea.

You'll get a lot of frame rate variation.

And if you get really high fps, you might overheat your graphics card.

Quakespasm, Quakespasm Spiked and FTE love to overheat with no map running ... (not that DarkPlaces doesn't love this also).

Kicking out tons of frames per second rendering the console over and over again.

Also the above engines if I recall, love to kick out 700 frames per second when the application is hidden or in the background.

In contrast, Mark V throttles down when no map is running or not the active application. No point in rendering an idle console 700 times per second or rendering hundreds of frames per second when the app isn't even active.

/My thoughts 

Also the above engines if I recall, love to kick out 700 frames per second when the application is hidden or in the background.

Interesting, that reminds me of when i got my latest computer and began to install old games (from around 1990) and the computer began to overheat, as it happened with several others. Curiously it didn´t happen when they weren´t on fulscreen. 

I set mine to 144 to match my monitor. 

@A_COCONUT
If you really want to let it rip, set sys_throttle 0 too, otherwise it'll still idle a little (and thus struggle to go above 800fps iirc).

@Baker
cl_idlefps defaults to 30 in FTE - the equivalent of your selling point for your own engine. if you cleared that cvar then you're getting exactly what you asked for.
DP has cl_maxidlefps. Same behaviour. 

Spike, I looked at the code it looks like your intentions are right.

That being said, when FTE is not active app for me, it uses 50% cpu. This laptop is dual-core that is that is the most it could use (100% of one core).

Here is FTE in idle (50% cpu): screenshot

Here is Mark V in idle (9% cpu): screenshot

And right now, my video fan is finally spinning down some after FTE had it screaming.

FTE going idle causes my video fan to go crazy.

FTE operates fine when it is the active application. 

Windows 9x interface will always be the best.

I'm particularly fond of the Windows Me interface, too bad the underlying OS was crippled. 

Also the above engines if I recall, love to kick out 700 frames per second when the application is hidden or in the background.

In contrast, Mark V throttles down when no map is running or not the active application. No point in rendering an idle console 700 times per second or rendering hundreds of frames per second when the app isn't even active.

Oh shit, so that's what that is.

A fix for QS/QSS would be great. I have a laptop, and it will cook itself if I'm not really careful.