Eugene comments

Results 125 comments of


                                            Eugene

fs_basegame behavior with mods errors with Couldn't load default.cfg

Applied in https://github.com/ec-/Quake3e/commit/93cb4701f3ca8e38849cd3fcb270be77b4aec331, please test by using `+set fs_basegame "baseq3/missionpack"`

Linux: abnormally high GPU usage on Vulkan with r_fbo 1

Try to disable `r_ext_multisample` or `r_hdr` to see what option actually causes significant performance drop

Linux: abnormally high GPU usage on Vulkan with r_fbo 1

Well, there is no platform-specific code in Vulkan/OpenGL renderers so it all depends from driver optimizations for a specific platform

Quake3e opens on the wrong screen in multi-monitor setup

try to experiment with `vid_xpos` and `vid_ypos` from command line, it might be related to problem reported in https://github.com/ec-/Quake3e/pull/210

Quake3e hangs on exit

`Com_Error( ERR_DROP, ... )` inside exception handler should close all running qvms without issues, it seems like that you already have some memory corruption at exception point

Vulkan render issue: returned VK_ERROR_DEVICE_LOST

Test with latest build

Vulkan render issue: returned VK_ERROR_DEVICE_LOST

Please tell AMD driver version you are using and hardware, at least for now, it might be useful to guide in similar cases

Dedicated server

Try `+set fs_homepath "~/.q3a"`, it is an issue with system paths, not engine

BUGFIX (minor): The body queue size is too small for more than 8 bots.

1) mod/engine can't handle big number of connected clients because it simply crashes on a massive configstring updates so in real you should use less than 32 clients, anything greater...

BUGFIX (minor): The body queue size is too small for more than 8 bots.

Possible fix - do not use dedicated body queue and allocate entities dynamically depending from current usage (like it works now for projectiles, events) I fixed 64-client usage but as...