Zandronum 2.1
RE: Zandronum 2.1
Then people simply don't play and the release never happens, or takes months to happen.
While testing of course is good in helping make things more stable, we really need to stop thinking that just because a release failed, it's because of not enough testing. You can lower the probability of releases breaking but not eliminate it. 2.0 was pretty well tested yet a pretty bad crash bug waded in and one of the major codepointers (A_LookEx) broke completely.
I think we instead need better damage control mechanisms. While the discussion about auto-upgrading didn't really go anywhere because it would not cater for the 1% of users who do not use a server browser on Windows, it could probably still help things considerably. If servers upgrade to a patched binary fast enough (best-ever doesn't take long and most of the gameplay happens there) and most of the users would use a hypothetical auto-upgrade system in Doomseeker (ideally also in Doom Explorer for maximum coverage), having things break like this wouldn't be so catastrophic and we could even patch security issues without it taking 6 months.
While testing of course is good in helping make things more stable, we really need to stop thinking that just because a release failed, it's because of not enough testing. You can lower the probability of releases breaking but not eliminate it. 2.0 was pretty well tested yet a pretty bad crash bug waded in and one of the major codepointers (A_LookEx) broke completely.
I think we instead need better damage control mechanisms. While the discussion about auto-upgrading didn't really go anywhere because it would not cater for the 1% of users who do not use a server browser on Windows, it could probably still help things considerably. If servers upgrade to a patched binary fast enough (best-ever doesn't take long and most of the gameplay happens there) and most of the users would use a hypothetical auto-upgrade system in Doomseeker (ideally also in Doom Explorer for maximum coverage), having things break like this wouldn't be so catastrophic and we could even patch security issues without it taking 6 months.
RE: Zandronum 2.1
One of the things that seems to be overlooked is the fact that as Zandronum goes along the road of catching up to ZDoom, the project inherently gets larger and more complex. As a result of this growth, there are more chances for things to go wrong and they do go wrong. A release and the testing phase isn't a total failure if some bugs creep through. After all, how often do PC games need patching?
As for the testing itself, people testing things locally, in small groups or bursts isn't going to cut it anymore. As mentioned above, the best way to evolve the testing phase is to put out a beta on some of the popular server clusters and allow the players to stress test the builds. The only way this method can succeed is by coordination between the Dev team and the main server hosts of the community followed by people actually playing the builds.
As for the testing itself, people testing things locally, in small groups or bursts isn't going to cut it anymore. As mentioned above, the best way to evolve the testing phase is to put out a beta on some of the popular server clusters and allow the players to stress test the builds. The only way this method can succeed is by coordination between the Dev team and the main server hosts of the community followed by people actually playing the builds.
Last edited by Ru5tK1ng on Thu Jun 25, 2015 11:59 pm, edited 1 time in total.
Projects
EonDM - With Hatred as my sidekick.
RageCTF - Made 1 map and did much more.
DBAB LMS - Pack made for Last Man Standing.
EonWeapons - Improve vanilla weapons and add stuff for kicks.
Progressive Duel - Leaving the old behind.
IDL201X CTF - Maintaining since 2013.
Strife AA - Helped tested + 1 map
EonDM - With Hatred as my sidekick.
RageCTF - Made 1 map and did much more.
DBAB LMS - Pack made for Last Man Standing.
EonWeapons - Improve vanilla weapons and add stuff for kicks.
Progressive Duel - Leaving the old behind.
IDL201X CTF - Maintaining since 2013.
Strife AA - Helped tested + 1 map
RE: Zandronum 2.1
I am of the same mind as Rust. Broken stuff on release is never fun, but it's not that big of a deal as long as point releases can be done in a timely fashion. If there are big obvious problems with a release, or if there are big obvious problems found with a release (such as security vulnerabilities), the turnaround on new a point release should be a day or two, tops.
In the future, I will host any posted test builds on FUNCRUSHER with DUEL32 and IDL CTF, which ought to cover the competitive community's concerns.
In the future, I will host any posted test builds on FUNCRUSHER with DUEL32 and IDL CTF, which ought to cover the competitive community's concerns.
Last edited by AlexMax on Thu Jun 25, 2015 11:19 pm, edited 1 time in total.
The only limit to my freedom is the inevitable closure of the
universe, as inevitable as your own last breath. And yet,
there remains time to create, to create, and escape.
Escape will make me God.
universe, as inevitable as your own last breath. And yet,
there remains time to create, to create, and escape.
Escape will make me God.
RE: Zandronum 2.1
Doomseeker will already prompt players to install beta versions. I don't see why this can't be extended to installation of stable versions too. However, in such case, Zandronum directory structure would have to be under complete control of Doomseeker, so that Doomseeker can decide where to install game executables of given version.
We can maintain current directory structure and still provide users the option to point to the default "Zandronum.exe" but there must be a way to obtain version from this .exe. Having zandronum print its version to stdout and close itself when being run with --version argument would be sufficient. That way whenever user joins a server with mismatching "version" string he would get a prompt asking to install the new version.
Another problem is that many hosts use their own, customized builds of Zandronum where the version string can be anything and it will throw off the version checking system and screw it up, unless we want to maintain a compatibility list of which custom server accepts which official client and this is ridiculous and fucked up beyond belief...
All in all, custom server builds can even ruin the current beta build installation system that is already in place in Doomseeker. Doomseeker can still provide auto-updates for the main version but --version for zandronum.exe must work first.
We can maintain current directory structure and still provide users the option to point to the default "Zandronum.exe" but there must be a way to obtain version from this .exe. Having zandronum print its version to stdout and close itself when being run with --version argument would be sufficient. That way whenever user joins a server with mismatching "version" string he would get a prompt asking to install the new version.
Another problem is that many hosts use their own, customized builds of Zandronum where the version string can be anything and it will throw off the version checking system and screw it up, unless we want to maintain a compatibility list of which custom server accepts which official client and this is ridiculous and fucked up beyond belief...
All in all, custom server builds can even ruin the current beta build installation system that is already in place in Doomseeker. Doomseeker can still provide auto-updates for the main version but --version for zandronum.exe must work first.
Doomseeker - a real answer to cross-platform server browser.
Doomseeker dev builds - unofficial Doomseeker builds for Windows.
Gamer's Proxy - a program to emulate ping and packet losses.
Doomseeker dev builds - unofficial Doomseeker builds for Windows.
Gamer's Proxy - a program to emulate ping and packet losses.
-
- Retired Staff / Community Team Member
- Posts: 865
- Joined: Tue Jun 05, 2012 11:06 pm
RE: Zandronum 2.1
I don't think I understand the need for this time limit, considering bugs are not always so polite as to be easily identifiable and fixed, and usually rushing such fixes tends to create more problems.AlexMax wrote:the turnaround on new a point release should be a day or two, tops.
The Ranger - New class for HeXen.
ZDoom Wars - I drew some pictures.
Samsara - Some class-based mod I guess?
Metroid: Dreadnought - I am a dumb fanboy.
DemonSteele - ~come with me to anime world~
ZDoom Wars - I drew some pictures.
Samsara - Some class-based mod I guess?
Metroid: Dreadnought - I am a dumb fanboy.
DemonSteele - ~come with me to anime world~
RE: Zandronum 2.1
I like the idea. 2.0 was solid imo since I personally didn't receive any game breaking bugs. It sucks that there were so many problems with that build. I'd try out a beta. The alphas? Not so much.
-
- Retired Staff / Community Team Member
- Posts: 2559
- Joined: Sat Jun 02, 2012 2:44 am
RE: Zandronum 2.1
Maybe an auto-update feature is needed in Zandronum itself instead of server browsers. Of course something like this doesn't happen over night, but that's probably the best way to get builds out faster, and get more reliable testing done.
Last edited by Catastrophe on Fri Jun 26, 2015 1:40 am, edited 1 time in total.
RE: Zandronum 2.1
This could have the added benefit that ZCinema could also work more or less out of the box without the user having to give the exe paths or install old versions manually.Zalewa wrote: Doomseeker will already prompt players to install beta versions. I don't see why this can't be extended to installation of stable versions too. However, in such case, Zandronum directory structure would have to be under complete control of Doomseeker, so that Doomseeker can decide where to install game executables of given version.
RE: Zandronum 2.1
Make a new regular event for testing sessions like FNF or SNS. These always attract folks.
Thursday night testing?
Thursday night testing?
Code: Select all
Mode #grandvoid -o Konar6 by Frits
<Konar6> the fuck
<Konar6> who made this IRC
<Konar6> how is this possible
-
- Zandrone
- Posts: 1244
- Joined: Thu Jun 28, 2012 9:07 pm
- Location: Rwanda
RE: Zandronum 2.1
As brought up in multiple posts before this, maybe it's time for an auto-updater? I know I threw the idea around a while ago, the issue would be getting all the different browsers to stay up to date. Wouldn't be a problem with Doomseeker but I have no idea what Doom Explorer would do.
ZDaemon does it and it's nice when they break the entire game (usually theirs is much worse than stuff like this), but then have a hotfix in usually 30-60 minutes. It's not uncommon to see them roll out 3-4 hotfixes within 24 hours of a version upgrade.
ZDaemon does it and it's nice when they break the entire game (usually theirs is much worse than stuff like this), but then have a hotfix in usually 30-60 minutes. It's not uncommon to see them roll out 3-4 hotfixes within 24 hours of a version upgrade.
-
- New User
- Posts: 2
- Joined: Fri Jun 26, 2015 1:46 pm
RE: Zandronum 2.1
I don't know how bad other peoples' versions are acting, but after many install attempts the 2.1 Mac build of Zandronum won't even finish booting up under my computer with OS X 10.6.8. I've only started playing online Doom within the last 2 months and version 2.0 worked like a charm, aside from missing audio channels which wasn't a major issue. I'm basically choosing between being blocked from most servers (2.0) or a dead duck (2.1).
Zandronum didn't generate the crash report file in its directory, but if let me know if I can help with some more info. Really hope this gets fixed up!
Zandronum didn't generate the crash report file in its directory, but if let me know if I can help with some more info. Really hope this gets fixed up!
Last edited by thehighesttree on Fri Jun 26, 2015 2:40 pm, edited 1 time in total.
-
- New User
- Posts: 14
- Joined: Mon Nov 19, 2012 12:46 am
RE: Zandronum 2.1
I noticed that INBAR items, if they stack in the inventory the amount automatically drops to 1 when the map is changed. I tried using every flag to allow the items to carry over and this still happens. I have to make a strange workaround to fix it.
RE: Zandronum 2.1
AFAIK, it has always been that way.Scott_Minikhiem wrote: I noticed that INBAR items, if they stack in the inventory the amount automatically drops to 1 when the map is changed. I tried using every flag to allow the items to carry over and this still happens. I have to make a strange workaround to fix it.
"For the world is hollow, and I have touched the sky."
RE: Zandronum 2.1
There are a couple of separate problems that need to be solved here:Zalewa wrote: Version insanity
1. Forcing the client and server version to match exactly by default is, frankly, obnoxious in some cases. I tried to use edward-san's version of Zandronum, which had the desync problems fixed, and players couldn't connect to my server. I had to apply the fixes as a patch against a stock 2.1 checkout.
2. On the other hand, if there is a new version of the Zandronum client that is released, you want to have players on that new version as soon as possible. For this, having the server inform the client that they are out of date is a good thing. But do demos have to break too?
3. And on the third hand, if you're running testing sessions, sometimes you want the freedom to be able to make updates to the server without the player having to download a new client, and sometimes it's important that the client isn't using an older testing client that will exhibit bugs that have already been fixed in a newer version.
A thorny situation, which requires a thorny and nuanced approach. I've collected my suggestions in this ticket:
http://zandronum.com/tracker/view.php?id=2331
The only limit to my freedom is the inevitable closure of the
universe, as inevitable as your own last breath. And yet,
there remains time to create, to create, and escape.
Escape will make me God.
universe, as inevitable as your own last breath. And yet,
there remains time to create, to create, and escape.
Escape will make me God.
RE: Zandronum 2.1
Great update! I love what you guys come up with :)
I have 2 questions.
1. I recently heard that Zandronum 3.0 is under development already (But still in a beta) and I was crazily excited and tried to download it from the website, but it says there are no development builds. So I went to compile it and see it, but I don't which source code I should compile. I mean, the one you are currently working is for the 2.0 branch, right? Or is it for 3.0? I'm completely lost.
2. In the first post you said; "Fixed: Too high volume parameters to A_PlaySound and friends caused the volume to overflow online. [Dusk]"
But wait, you can't amplify sounds over 1.0. You can make them less loud only.
I mean, this line in the source code clearly says that. Is this just for G/ZDoom?
I have 2 questions.
1. I recently heard that Zandronum 3.0 is under development already (But still in a beta) and I was crazily excited and tried to download it from the website, but it says there are no development builds. So I went to compile it and see it, but I don't which source code I should compile. I mean, the one you are currently working is for the 2.0 branch, right? Or is it for 3.0? I'm completely lost.
2. In the first post you said; "Fixed: Too high volume parameters to A_PlaySound and friends caused the volume to overflow online. [Dusk]"
But wait, you can't amplify sounds over 1.0. You can make them less loud only.
I mean, this line in the source code clearly says that. Is this just for G/ZDoom?
[quote=The Forum Community] We all love you, Quaker540.[/quote]
RE: Zandronum 2.1
1.) The zandronum repository has the 3.0 development branch while zandronum-stable has 2.x. So if you want to build 2.x you need to clone zandronum-stable instead.
2.) If SNDINFO has used $volume to reduce the volume of the sound effect, then values greater than 1.0 amplify the sound. So such values have to be supported, though volumes greater than 2.0 still overflow so we have to draw the line there.
2.) If SNDINFO has used $volume to reduce the volume of the sound effect, then values greater than 1.0 amplify the sound. So such values have to be supported, though volumes greater than 2.0 still overflow so we have to draw the line there.
RE: Zandronum 2.1
Thank you!Dusk wrote: 1.) The zandronum repository has the 3.0 development branch while zandronum-stable has 2.x. So if you want to build 2.x you need to clone zandronum-stable instead.
Um, no. The line clearly says that sounds can't get over 1.0, you can make them less loud only.Dusk wrote:2.) If SNDINFO has used $volume to reduce the volume of the sound effect, then values greater than 1.0 amplify the sound. So such values have to be supported, though volumes greater than 2.0 still overflow so we have to draw the line there.
THIS. Since the people working on the project are working fast as fuck, and people always want to have the latest bleeding-edge features and stuff, you have my vote. Not sure how such thing could be done, though other source ports already did that and it's fantastic.Catastrophe wrote: Maybe an auto-update feature is needed in Zandronum itself instead of server browsers. Of course something like this doesn't happen over night, but that's probably the best way to get builds out faster, and get more reliable testing done.
Last edited by Quaker540 on Sat Jun 27, 2015 6:37 pm, edited 1 time in total.
[quote=The Forum Community] We all love you, Quaker540.[/quote]
-
- Posts: 82
- Joined: Mon Nov 24, 2014 8:19 am
RE: Zandronum 2.1
It's to explain that you can't actually amplify a sound using the function. You can, however, dequiet a sound you're already making quieter by other means.Quaker540 wrote: Um, no. The line clearly says that sounds can't get over 1.0, you can make them less loud only.
- ibm5155
- Addicted to Zandronum
- Posts: 1641
- Joined: Tue Jun 05, 2012 9:32 pm
- Location: Somewhere, over the rainbow
RE: Zandronum 2.1
Code: Select all
Note: You need a copy of Doom (or Heretic, Hexen, or Strife) to play Zandronum. If you don't have the game, Steam sells it for about $5 - $15. Once you install it, Zandronum will find it automatically. Zandronum requires the latest version of the supported games. If you have an older version you can patch to the latest version.
I actually use freedoom as my main iwad, and I can play everything without problem (except the vanilla servers)
Projects
Cursed Maze: DONE, V2.0
Zombie Horde - ZM09 map update: [3/15/13]
Need help with English? Then you've come to the right place!
<this post is proof of "Decline">
Cursed Maze: DONE, V2.0
Zombie Horde - ZM09 map update: [3/15/13]
Need help with English? Then you've come to the right place!
<this post is proof of "Decline">
RE: Zandronum 2.1
Strife isn't free.ibm5155 wrote:Why don't you guys offer freedoom (or even strife) since both are free now...Code: Select all
Note: You need a copy of Doom (or Heretic, Hexen, or Strife) to play Zandronum. If you don't have the game, Steam sells it for about $5 - $15. Once you install it, Zandronum will find it automatically. Zandronum requires the latest version of the supported games. If you have an older version you can patch to the latest version.
I actually use freedoom as my main iwad, and I can play everything without problem (except the vanilla servers)