After beating Shub game won't return to start map, player is locked in camera looking on ranger and game doesn't allow to do anything, basically game-breaking glitch. This was on standard quakespasm. 

I think that's how it was in original game. It's the very final end of the game, so there was no point of making player go back to start.

Another issue I reproduced twice is that if you teleport at the wrong time when the spiked sphere is not going through Shub, it (sphere) will stop right before Shub and just hang there rotating in place, preventing from successully telefragging it even if you do get out of lava and try again. 

https://www.twitch.tv/videos/773110951

or youtube

https://www.youtube.com/watch?v=6GfW8rLL2G0 

@Bal, thanks, I'll edit it in quake.rc!

Regarding the sound issues, I've recorded two short clips to show the difference. This is with QSS, but it's the same with QS and vKQuake.

First, how it sounds with AD 1.8:

https://youtu.be/S1lAZd5_HEU

Second, the same with AD 1.7:

https://youtu.be/PQpqlr7oQcI

The settings for sound seem to be the same in both cases. Weird. 

Slightly longer clip with the sound issues:

https://youtu.be/gJJdooHRmCw 

It's hard to compare those 2 vids, cause the 1.8 metmon has an extra ambient sound at the start (that pulsing sound, which is indeed clipping in your vid).
That sounds does clip quite a bit when I put the volume too high, what is your volume at? 

any idea where I can find the swamp key in ad_akalakha?
6/10 secrets atm. 

I have the sound at max and music at a third, but it doesn't help to lower the sound either in Quake or Windows (or both).

I have the same issue in the final arena of ad_tears, which also have some kind of pulsating sound IIRC. It's as if that sound overwhelms everything, making all sounds distorted. 

Guess clipping is a more correct term. 

I want another kind of jump boots or smth, which makes you dash forward. Kinda like in Doom Eternal (Bloodshot did some similar feature in Slayer's Testaments Quake Mod), so you could gain some instant forward momentum, basically jump module from Half-Life, simplyfiyng bunnyhopping start and allowing to GO FAST, and NOT slowing down to base speed after landing/dash stop. This was actual feature in SlayerTest, they scrapped it, but imo you could make whole maps built around this long speedy jumps(inb4 Tribes/defrag/xonotic). 

It's seen right from your spawning position in the beginning, if you know exactly where to look. 

I seen that in test map with grappling hook, when you use jump boots with hook they propel you forward instead of upward, I want that effect in regular jump boots, probably on different key. 

Check out the test_artifact_jboots map, they have a few options, including forward momentum on second jump.
There's always been a strong stance to not add any obligatory new keys, that's really awkward cause people will usually unbind it / ignore it / not understand how it works. 

thanks, looking for it I found all the other secrets, 10/10 now :) 

Yeah, thats it. Thank you! 

Please check the outside areas of your map again. In some places outside the framerate goes down by a huge amount (down to ~ 50 fps). Would be cool if you could see if there's a way to tweak these areas to avoid such a massive fps loss. 

Probably it is because the engine isn't suited well to render huge open areas, and more about corridors and rooms, and mappers create such huge maps only because of modern hardware computational power. 

Sorry, unfortunately there's not much I can do without completely reworking the layout, or closing off whole segments of the map to the outside.
I optimized the stuff I could but since it was running ok (=almost never under 60)on my ~8 year old pc, I decided to stick to my initial layout. 

Someone tell that big open maps run better in vkQuake on Vulkan-compatible rigs.

About ad_akalakha: Most compare it to ad_sepulcher, but for me it resembles Shadow and Flame (xmasjam2018_ionous), remade with boggy assets instead of obsidian and lava. Not only because of spiral staircase structure, again these tight player pathways, traps in both brushwork and monster spawns, these ruthless secrets... Pulsar basically imitates Ionous' approach to level design(and that's not a poor imitation in any ways)! This is not a complaint, rather not exactly mine taste, and not what I am launching quake for. 

Yes the framerate in vkQuake is better than in QSS (at least on my end) but unfortunately the current version 1.04.1 of vkQuake has some issues with AD 1.8.

For example when you die vkQuake will crash with a "Could not allocate memory for texture" error message.

The custom huds are also not working at the moment.

Maybe one day a new version will fix the problems or the AD team ads vkQuake to the list of officially supported source ports so the current version can run it without any issues but right now QSS seems to be the only stable way to play AD 1.8. 

Akalakha was originally an entry to Xmas Jam 2017. 

@Berzerk
Unfortunately, that's probably a problem with your machine. I've been using vkQuake exclusively for a long time, and have been playing AD 1.8 nonstop since release, and have experienced zero crashes.

Also, where does one report bugs where the team will see them? 

The vkquake crash is definitely reproducable with the latest release, but apparently it's fixed on the most recent codebase. Would be great if a new executable was put up for all of us scrubs that don't go around compiling stuff. :)

For bug reporting, you mean for AD? Here is fine, or you can contract Sock from his site, or me (my mail is in my profile). 

I also have issues with vKQuake, namely that it crashes (or rather freezes) when trying to load a save within the game. Can load saves fine when restarting, but not while playing. Agree that it would be nice to have it work as it's faster.

Replaying ad_tears, it's not a pulsating sound in the final arena, but rather a humming one, same as in The Source. I have the same sound issues with that sound as with the pulsating one. 

it seems to be map dependent now and AD 1.8 engine ignores r_wateralpha config variables. How specifies my own value?