I've encountered a bug with incorrect spawning monsters in my old map and the newer one, which is not released yet. I've tried two different revisions of qss and in them monsters spawn differently. Anyway the both revisions have that problem (2021-03-06 and 2021-09-13). I can fix it by moving monsters above the ground or in a diffrent place in trenchbroom, but it still annoying. The maps work flawlessly in Quakespasm and DarkPlaces. 

The map that doesn't work correctly with QSS if you want to check it:
https://www.quaddicted.com/filebase/pillars.zip

The main problem with some monsters in the teleporter closets. 

Also, my newer map works fine in the old revision of QSS but it's messy in the latest one. 

Have you checked out the latest version with your maps. I thought this might have been fixed but i have no idea. QSS releases can be confusing as you can read above.

No matter what these issues have affected other maps as well. 

If there was a changelog on the QSS website. I assume most of the updates these days are for Quake Enhanced, but not sure. 

I've tried the latest one i think, form QSS website. 

*from the QSS website 

Did you already tried to change the console command:
sv_gameplayfix_setmodelrealbox ?

QSS has it turned on (1) by default, so the engine takes the real size of the enemy model instead of the size registered inside the QCs files.

I noticed that turning it off (0) can solve a lot of problems like enemies stuck in floors or walls. 

This problem happens because Quake has two different bounding boxes for it's MDLs. The physics box for clipping, and the geometry box for frustum culling. The physics box size needs to be what it is because of the BSP hulls.

The problem occurs when well-meaning engine coders intend to calculate an accurate culling box (which GLQuake gets wrong) but end up changing the physics box too.

The MDL format actually includes per-frame culling boxes so these don't need to be recalculated at all, they just need to be loaded and used properly. 

Setting an undocumented cvar shouldn't be required to play a map.

How does one know about a cvar if there's no changelog and no documentation? 

Tried and it didn't help. 

There have been a few updates to QSS. Maybe it got fixed? 

> MD3 model support, basic IQM support.

What does "basic IQM" mean? 

Short for "Inter-Quake Model". It is (or was?) intended as a replacement for MD5 and SMD skeletal animation formats. It was used in Cube 2: Sauerbraten.

If you want to read a bit more about it:
http://sauerbraten.org/iqm/

Anyway, I don't think it's a relevant feature for the average Quake player, rather a feature to cover all bases. 

Starting from version 0.94.1 and higher the QSS engine constantly crashes when switching between replacing models with MD5 from Quake Release and standard MDL models of Quake ID1 and then loading another map or restarting. Moreover it was tested with upgraded folders (particles/progs/textures, etc.) and with a standard ID1 folder and without MD5 models. All the same, versions 0.94.1-0.94.2 100% crashes when switching and loading another map or restart. On QSS version 0.94.0, everything works fine. Who solved this problem and how? 

QS already fixed:

Changes in 0.94.3
Allow loading textures not aligned to 16 pixels and warn about them.

QSS 14.10.21:
https://quaketastic.com/files/screen_shots/qss_error.jpg 

Which mod is this with? 

Texture 64x8 pix. 

I scanned ad-1.8p1, found nothing named 'litebary'. Which map is this?

BTW, the fix in qs-0.94.3 is _not_ meant as a free passport to used non-16-aligned textures: it is an open warning so the modded should fix his thing for compatibility with every other engine. 

That seems more like a bug in AD, since that is not a valid size for a texture in vanilla quake (therefore most engines) 

Just to be clear - the 16-alignment requirement only applies to BSP textures, and the reason for it is for storing all 4 miplevels for use by the software renderer; so: 16, 8, 4, 1 are the minimum allowed dimensions for each miplevel.

The requirement doesn't apply to other texture types. 

That seems more like a bug in AD, since that is not a valid size for a texture in vanilla quake (therefore most engines)

Indeed it is a bug (just like the bad sky textures sizes in ad_tears), but, as I said, what I can't find is the specific texture mentioned in #292 in ad1.8, i.e. this particular issue doesn't actually seem to be in pristine ad1.8 release. 

 

for my wip map. Of course I have already changed the texture size to 64x16 and error gone. But there is few custom wads with such "nonstandard" textures and now in Quake enhanced too. Ericw tools compiled map with this texture as usual. 

while trying to run horde2 map from 2-nd updated mg1 episode.