Anonymous | Login | Signup for a new account | 2025-07-26 18:11 UTC | ![]() |
My View | View Issues | Change Log | Roadmap | Zandronum Issue Support Ranking | Rules | My Account |
View Issue Details [ Jump to Notes ] | [ Issue History ] [ Print ] | ||||||||||||
ID | Project | Category | View Status | Date Submitted | Last Update | ||||||||
0004237 | Zandronum | [All Projects] Bug | public | 2024-04-23 04:54 | 2024-07-19 20:04 | ||||||||
Reporter | Mr. Satan | ||||||||||||
Assigned To | |||||||||||||
Priority | normal | Severity | crash | Reproducibility | always | ||||||||
Status | acknowledged | Resolution | open | ||||||||||
Platform | Microsoft | OS | Windows | OS Version | 8.1 | ||||||||
Product Version | 3.1 | ||||||||||||
Target Version | Fixed in Version | ||||||||||||
Summary | 0004237: Zandronum crashes when connecting a client to a server from the same PC. | ||||||||||||
Description | Zandronum 3.2 client crashes when it tries to connect to a server hosted on the same PC. Happens in builds ending in 1910 and 2229, but not in build 1914. I connected to the server through LAN and through the external IP it happens with both. Does not happen if you try to connect a client using the wrong version of Zandro. (server 1910, client 2229) Can't choose 3.2 as a Product Version because it is not an option. | ||||||||||||
Steps To Reproduce | Host a server with just an IWAD and connect. | ||||||||||||
Additional Information | I tried zeroing out all the flags (DM, ZandroDM, Compatibility, etc) still happens. | ||||||||||||
Attached Files | ![]() | ||||||||||||
![]() |
|
Ru5tK1ng (updater) 2024-04-23 18:00 |
Crash happens in fmodex64.dll. |
Mr. Satan (reporter) 2024-07-19 02:09 |
Changing Output System from Default to DirectSound in Sound Options fixed it. This doesn't happen on my laptop. Default output device is a TV connected via HDMI. Changing that setting also fixes'https://zandronum.com/tracker/view.php?id=4217. [^]' Plugged the laptop into the TV and no problem. Turning off Voice Chat in Voice Chat Options && || disabling that device in Windows also fixes the problem even with Output System set to Default. I think this is some how linked to the above tracker. |
Kaminsky (developer) 2024-07-19 20:04 |
It seems that there's something wrong with how FMOD handles your device in WASAPI (in Windows Vista or later, FMOD chooses it when the output system is set to default). Unfortunately, since FMOD is closed source, we don't have any way of debugging or fixing this ourselves. It's good to hear that DirectSound fixes the crash for you, at least. On a side note, I'm curious to see if rewriting the voice chat system to use OpenAL instead of FMOD (if or when we get it someday) will fix the few edge cases that some people are having. |
Only registered users can voice their support. Click here to register, or here to log in. | |
Supporters: | No one explicitly supports this issue yet. |
Opponents: | No one explicitly opposes this issue yet. |
![]() |
|||
Date Modified | Username | Field | Change |
2024-04-23 04:54 | Mr. Satan | New Issue | |
2024-04-23 04:54 | Mr. Satan | File Added: ServerCrashReport.zip | |
2024-04-23 18:00 | Ru5tK1ng | Note Added: 0023638 | |
2024-07-19 02:09 | Mr. Satan | Note Added: 0023802 | |
2024-07-19 20:04 | Kaminsky | Note Added: 0023803 | |
2024-07-19 20:04 | Kaminsky | Status | new => acknowledged |
Copyright © 2000 - 2025 MantisBT Team |