I've tagged the 2.3.5 release on gitlab. You can find the sources and pre-built binaries on the release page. No major changes, just a few bug fixes. New feature development continues in the main branch. Here are a list of changes since 2.3.4:
d66f1655 Fix bug in Europe EL cup definitions
0034767a live_game: Fix bug while selecting injured player
3363a7f7 Fix fixture scheduling bug
b01defd7 ci: Give generic RPM and Deb builds their own OS_NAME
783a73f9 ci: Make sure mingw builds are added to the package registry
03d2f593 ci: Add mingw builds
860a7d7a ci: Make jobs interruptible to save CI minutes
fde5ab82 cmake: Make it possible to override JSON-C_LIBRARIES
c64f43e6 Bump version to 2.3.5
afbbc4bb Fix incompatible-pointer-types warning
10fc8a42 fix: restore glib conditional to fix builds
716c7b70 fix: segfault on Windows after selecting new game
c7d93269 ci: Drop unsupported OSes and add newer releases
Bygfoot 2.3.5 is released
Moderator: idcarlos
-
will_the_canuck
- Posts: 145
- Joined: Tue Jan 16, 2018 5:54 am
- Location: Canada
Re: Bygfoot 2.3.5 is released
tstellar wrote:
> I've tagged the 2.3.5 release on gitlab. You can find the sources and pre-built binaries on the [url=https://gitlab.com/bygfoot/bygfoot/-/releases/2.3.5]release page[/url]. No major changes, just a few bug fixes.
Hello tstellar.
I do have an honest question about updating/upgrading from a lower version to a latest version, like version 2.3.5 which you mention here. As I have used the Ubuntu Software Repository to install bygfoot version 2.3.2, what will happen or what takes place when installing a version that you are creating? As we know, bygfoot is installed in two different areas: (1) the directory of /usr/share/games which the program and definitions / images / etc. are installed; and (2) the user's home directory with a dot directory filename, like .bygfoot-2.3.2, which contains a copy of the definitions that can be used to play with. As the program is installed in the /usr/share/games/ directory, that is basically the permanent copy of the program, definitions, and images, as well as anything else used for the game. The directory in the user's home directory is in some ways, temporary.
So with that said, I'd assume that installing a version of bygfoot that you created will overwrite what is in the /usr/share/games directory and then create a new directory in the user's home directory, likely bygfoot-2.3.5. Is that correct? Or likely delete the contents of /usr/share/games/bygfoot and then install the newer version. Would that be accurate? If the installation file does not touch the user's directory of .bygfoot-2.3.2, that would be good to know as sometimes some users may have different definitions in their directories that aren't part of the original installation, and they may only have the one copy. Or might there be a better way to install your version? Maybe uninstall the old version first and then install the new version? Just asking.
Other than that, I'm just curious what will happen. With the speed improvements you mention, I'd be curious to see how it plays and anything that can speed up playing a very large definition will definitely be an improvement. Also, I'd be curious to see what corner kicks look like in the game as they were supposedly implemented in version 2.3.3 by the original programmers before it was left unfinished.
Will aka will_the_canuck
> I've tagged the 2.3.5 release on gitlab. You can find the sources and pre-built binaries on the [url=https://gitlab.com/bygfoot/bygfoot/-/releases/2.3.5]release page[/url]. No major changes, just a few bug fixes.
Hello tstellar.
I do have an honest question about updating/upgrading from a lower version to a latest version, like version 2.3.5 which you mention here. As I have used the Ubuntu Software Repository to install bygfoot version 2.3.2, what will happen or what takes place when installing a version that you are creating? As we know, bygfoot is installed in two different areas: (1) the directory of /usr/share/games which the program and definitions / images / etc. are installed; and (2) the user's home directory with a dot directory filename, like .bygfoot-2.3.2, which contains a copy of the definitions that can be used to play with. As the program is installed in the /usr/share/games/ directory, that is basically the permanent copy of the program, definitions, and images, as well as anything else used for the game. The directory in the user's home directory is in some ways, temporary.
So with that said, I'd assume that installing a version of bygfoot that you created will overwrite what is in the /usr/share/games directory and then create a new directory in the user's home directory, likely bygfoot-2.3.5. Is that correct? Or likely delete the contents of /usr/share/games/bygfoot and then install the newer version. Would that be accurate? If the installation file does not touch the user's directory of .bygfoot-2.3.2, that would be good to know as sometimes some users may have different definitions in their directories that aren't part of the original installation, and they may only have the one copy. Or might there be a better way to install your version? Maybe uninstall the old version first and then install the new version? Just asking.
Other than that, I'm just curious what will happen. With the speed improvements you mention, I'd be curious to see how it plays and anything that can speed up playing a very large definition will definitely be an improvement. Also, I'd be curious to see what corner kicks look like in the game as they were supposedly implemented in version 2.3.3 by the original programmers before it was left unfinished.
Will aka will_the_canuck
Re: Bygfoot 2.3.5 is released
You can use the two versions at the same time completely without worrying.The old version has a catalog /home/user/.bygfoot-2.3.2, and the new /home/user/.bygfoot without version number.
-
will_the_canuck
- Posts: 145
- Joined: Tue Jan 16, 2018 5:54 am
- Location: Canada
Re: Bygfoot 2.3.5 is released
David wrote:
> You can use the two versions at the same time completely without
> worrying.The old version has a catalog /home/user/.bygfoot-2.3.2, and the
> new /home/user/.bygfoot without version number.
The way you wrote this David, I'm wondering if you're referring to the definitions only or the program and definitions? I might assume the definitions only though. Either way, I think the best way to judge the update is for me to delete or remove version 2.3.2 and then install version 2.3.5 or a newer version.
As for @tstellar, as a .deb file is available at the link you provided, for version 2.3.5, as it was posted over a year ago, would you recommend we use that version or an updated version, which would be available through the package registry, which is showing version 2.4.0, but a dev number which is currently at 97?
On a side note, I'll likely be testing it out first to see how the program has been improved since version 2.3.2, although for some things like the Russian flag, I see that it still needs to be updated as the current flag that is showing for Russia is the same as the flag of Serbia. I'm noticing this by looking at the files on your site, tstellar. It was since version 2.2.1 I believe that that was the last time the Russian flag was actually correct. After that, for some reason, it was copied incorrectly and never changed back. Anyways, let me know which version would be best to download to use.
Will aka will_the_canuck
> You can use the two versions at the same time completely without
> worrying.The old version has a catalog /home/user/.bygfoot-2.3.2, and the
> new /home/user/.bygfoot without version number.
The way you wrote this David, I'm wondering if you're referring to the definitions only or the program and definitions? I might assume the definitions only though. Either way, I think the best way to judge the update is for me to delete or remove version 2.3.2 and then install version 2.3.5 or a newer version.
As for @tstellar, as a .deb file is available at the link you provided, for version 2.3.5, as it was posted over a year ago, would you recommend we use that version or an updated version, which would be available through the package registry, which is showing version 2.4.0, but a dev number which is currently at 97?
On a side note, I'll likely be testing it out first to see how the program has been improved since version 2.3.2, although for some things like the Russian flag, I see that it still needs to be updated as the current flag that is showing for Russia is the same as the flag of Serbia. I'm noticing this by looking at the files on your site, tstellar. It was since version 2.2.1 I believe that that was the last time the Russian flag was actually correct. After that, for some reason, it was copied incorrectly and never changed back. Anyways, let me know which version would be best to download to use.
Will aka will_the_canuck
- Attachments
-
- flag_russia.png.zip
- it is a 21x13 pixel .png file in a zip file
- (291 Bytes) Downloaded 33 times
-
will_the_canuck
- Posts: 145
- Joined: Tue Jan 16, 2018 5:54 am
- Location: Canada
[Edited: 13-aug-2024] Testing the new builds...
Hello tstellar.
Well, I took the plunge and decided to test out your updates to bygfoot, both version 2.3.5 and version 2.4.0-dev-97. With version 2.3.5, I played 1 season as a team in the England definition that was in tier 10. I believe I stopped after one season because of the attendance bug, that you worked on and that was working better in version 2.4.0-dev-97. I say "worked on" and "working better" instead of "fixed" because I feel that when compared to version 2.3.2, it is still giving a greater attendance value than what would appear in version 2.3.2. At least this is my opinion with the limited testing that I did when using version 2.4.0-dev-97.
As for version 2.4.0-dev-97, I tested it by playing two separate games: a three season game as a team in the England definitions that was in tier 10, just like I did with version 2.3.5; and a six season game as a team in the England definitions that I created (a 9 tier definition), starting in tier 9. So basically I played a game with a definition that came with bygfoot that you did and then I played a second game with a definition that I created for bygfoot.
My testing parameters were that as I started off with version 2.3.2 installed that I did install through the Ubuntu Software Repository, I used that to then completely remove the game. From there, I then installed version 2.3.5 from the .deb file that related to ubuntu version 20.04 I believe it was, as I am running Linux Mint 20.3 with Xfce. Linux Mint 20.x, as you would know, works off of Ubuntu version 20.04 LTS. After I finished testing version 2.3.5, I completely removed it from the system, using the command of "sudo apt autoremove --purge bygfoot", I believe it was. I did this to give your update(s) a fair review and to allow them to stand on their own. After removing version 2.3.5, I downloaded and installed version 2.4.0-dev-97.
The most noticeable thing about the newer versions was the speed at which it processed all the other games that the user doesn't play, which is nice and helps to speed up the time between matches. So that is a positive. Although when I really look at the game and its behaviour and some of its outcomes, I do see things that need improving. I'll mention that for the games that I played, none were live games and all games played to test these newer versions were ones that the computer played for me. That could be a big thing. I just happened to check on some of the results of the games and also see some of the matches through using the "Show last match" option. I'll say that when I did check on the matches that way, I did come across a few issues too.
So now after going through all of this, I do have a few bugs/issues to report that I will report under the "Bug reports" section as well as some ideas or requests that I'll post under the "Discussions" section. I am also experiencing an issue currently where if I were to start a new game and play a league match, I instantly get a core dump and an error message saying it is a "Floating point exception". This is truly annoying, although I can safely play any saved game from before this error began surfacing. I do want to continue testing the one saved game a little more to see how far it can go, so I'll be using it for that, but at least after that is done, I'll be removing this version and likely installing version 2.3.2 if I can, until some of the bugs are worked out. Though it will take some time to post, hopefully I can finish all of the posts within a reasonable amount of time.
Will aka will_the_canuck
Well, I took the plunge and decided to test out your updates to bygfoot, both version 2.3.5 and version 2.4.0-dev-97. With version 2.3.5, I played 1 season as a team in the England definition that was in tier 10. I believe I stopped after one season because of the attendance bug, that you worked on and that was working better in version 2.4.0-dev-97. I say "worked on" and "working better" instead of "fixed" because I feel that when compared to version 2.3.2, it is still giving a greater attendance value than what would appear in version 2.3.2. At least this is my opinion with the limited testing that I did when using version 2.4.0-dev-97.
As for version 2.4.0-dev-97, I tested it by playing two separate games: a three season game as a team in the England definitions that was in tier 10, just like I did with version 2.3.5; and a six season game as a team in the England definitions that I created (a 9 tier definition), starting in tier 9. So basically I played a game with a definition that came with bygfoot that you did and then I played a second game with a definition that I created for bygfoot.
My testing parameters were that as I started off with version 2.3.2 installed that I did install through the Ubuntu Software Repository, I used that to then completely remove the game. From there, I then installed version 2.3.5 from the .deb file that related to ubuntu version 20.04 I believe it was, as I am running Linux Mint 20.3 with Xfce. Linux Mint 20.x, as you would know, works off of Ubuntu version 20.04 LTS. After I finished testing version 2.3.5, I completely removed it from the system, using the command of "sudo apt autoremove --purge bygfoot", I believe it was. I did this to give your update(s) a fair review and to allow them to stand on their own. After removing version 2.3.5, I downloaded and installed version 2.4.0-dev-97.
The most noticeable thing about the newer versions was the speed at which it processed all the other games that the user doesn't play, which is nice and helps to speed up the time between matches. So that is a positive. Although when I really look at the game and its behaviour and some of its outcomes, I do see things that need improving. I'll mention that for the games that I played, none were live games and all games played to test these newer versions were ones that the computer played for me. That could be a big thing. I just happened to check on some of the results of the games and also see some of the matches through using the "Show last match" option. I'll say that when I did check on the matches that way, I did come across a few issues too.
So now after going through all of this, I do have a few bugs/issues to report that I will report under the "Bug reports" section as well as some ideas or requests that I'll post under the "Discussions" section. I am also experiencing an issue currently where if I were to start a new game and play a league match, I instantly get a core dump and an error message saying it is a "Floating point exception". This is truly annoying, although I can safely play any saved game from before this error began surfacing. I do want to continue testing the one saved game a little more to see how far it can go, so I'll be using it for that, but at least after that is done, I'll be removing this version and likely installing version 2.3.2 if I can, until some of the bugs are worked out. Though it will take some time to post, hopefully I can finish all of the posts within a reasonable amount of time.
Will aka will_the_canuck