MantisBT - Zandronum
View Issue Details
IDProjectCategoryView StatusDate SubmittedLast Update
0004237Zandronum[All Projects] Bugpublic2024-04-23 04:542024-07-19 20:04
ReporterMr. Satan 
Assigned To 
PrioritynormalSeveritycrashReproducibilityalways
StatusacknowledgedResolutionopen 
PlatformMicrosoftOSWindowsOS Version8.1
Product Version3.1 
Target VersionFixed in Version 
Summary0004237: Zandronum crashes when connecting a client to a server from the same PC.
DescriptionZandronum 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 ReproduceHost a server with just an IWAD and connect.
Additional InformationI tried zeroing out all the flags (DM, ZandroDM, Compatibility, etc) still happens.
TagsNo tags attached.
Relationships
Attached Fileszip ServerCrashReport.zip (18,300) 2024-04-23 04:54
/tracker/file_download.php?file_id=2971&type=bug
Issue History
Date ModifiedUsernameFieldChange
2024-04-23 04:54Mr. SatanNew Issue
2024-04-23 04:54Mr. SatanFile Added: ServerCrashReport.zip
2024-04-23 18:00Ru5tK1ngNote Added: 0023638
2024-07-19 02:09Mr. SatanNote Added: 0023802
2024-07-19 20:04KaminskyNote Added: 0023803
2024-07-19 20:04KaminskyStatusnew => acknowledged

Notes
(0023638)
Ru5tK1ng   
2024-04-23 18:00   
Crash happens in fmodex64.dll.
(0023802)
Mr. Satan   
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.
(0023803)
Kaminsky   
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.