Skip to content
Extraits de code Groupes Projets
Valider 010a467f rédigé par LouriNoel's avatar LouriNoel
Parcourir les fichiers

Update Report-Louri-Noel-26202100.md 

ready for december's presentation
parent 71d3a535
Aucune branche associée trouvée
Aucune étiquette associée trouvée
Aucune requête de fusion associée trouvée
Masquer les modifications d'espaces
En ligne Côte à côte
projects/projects_2021_22/Report-Louri-Noel-26202100.md
+ 130
− 41
Voir le fichier @ 010a467f
......@@ -12,104 +12,193 @@
## The Project
**Supertux** is a platformer game which draws its inspiration from the Mario games.
It features Tux (the mascot of Linux) instead of the red mustachioed, going through icy lands to save his girlfriend Penny from the claws of Nolok.
**Supertux** is a platformer game which draws its inspiration from the Mario
games. It features Tux (the mascot of Linux) instead of the red mustachioed,
going through icy lands to save his girlfriend Penny from the claws of Nolok.
## Motivations
I played SuperTux when I was little, and I have waited for an update since then.
I have missed the 0.6.2 version which was released in May 2020 and there is apparently a lot more to come, so I think choosing this project could be a good idea for a starting point.
I played SuperTux when I was little, and I have waited for an update since
then. I have missed the 0.6.2 version which was released in May 2020
and there is apparently a lot more to come, so I think choosing this project
could be a good idea for a starting point.
## Learning about the community
*16/09/2021 - 26/09/2021*
I thought at first the community was almost dead, because of the low number of commits these past months, the low activity on the forum, and the few recent issues and pull requests. So I decided to observe during a week to see if I could really choose this project.
The [twitter account](https://twitter.com/supertux_team?lang=fr) only retweet fanarts of the game (2 times this summer).
The active part of the [forum](https://forum.freegamedev.net/viewforum.php?f=66) is mostly about creating maps, nothing related to development.
The community is also on LiberaChat and Discord, but I don't dare to go on those for the time being.
I thought at first the community was almost dead, because of the low number
of commits these past months, the low activity on the forum, and the few
recent issues and pull requests. So I decided to observe during a week
to see if I could really choose this project.
The [twitter account](https://twitter.com/supertux_team?lang=fr)
only retweets fanarts of the game (2 times this summer).
The active part of the
[forum](https://forum.freegamedev.net/viewforum.php?f=66)
is mostly about creating maps, nothing related to development.
The community is also on LiberaChat and Discord, but I don't dare
to go on those for the time being.
## Building the project
*22/09/2021*
I tried building the project on Windows at first, but I must link the dependencies manually with my current environnement, and there are many of them.
I did not manage to build it, so instead I tried building it on a Ubuntu virtual machine, and it worked well!
But the game was lagging, so I built it again in my dual-boot Ubuntu instead.
I tried building the project on Windows at first, but I must link
the dependencies manually with my current environnement,
and there are many of them.
I did not manage to build it, so instead I tried building it on
a Ubuntu virtual machine, and it worked well! But the game was lagging,
so I built it again in my dual-boot Ubuntu instead.
## Looking for something to do
*27/09/2021 - 01/10/2021*
I didn't find any appealing Issue which would seem simple enough to start, so I played through the game looking for bugs.
I have found some, and one of them was promising (ie. I could take it on with little effort).
I didn't find any appealing Issue which would seem simple enough to start,
so I played through the game looking for bugs.
I have found some, and one of them was promising (ie. I could take it on
with little effort).
When Tux dies, the level's music fades out. Then Tux reappears at the beginning of the level or at a checkpoint, and the music fades in from where it stopped.
But sometimes (seemingly randomly), the music does not play after reappearing: the other sounds are still there, but there is no music. The music starts again when resuming the game from the pause menu, or when changing its volume in the options.
When Tux dies, the level's music fades out. Then Tux reappears at the
beginning of the level or at a checkpoint, and the music fades in
from where it stopped. But sometimes (seemingly randomly), the music
does not play after reappearing: the other sounds are still there,
but there is no music. The music starts again when resuming the game
from the pause menu, or when changing its volume in the options.
## Investigating the bug
*02/10/2021 - 03/10/2021*
I have noticed that the bug happens more frequently on the virtual machine than on the dual-boot Ubuntu. In fact, I have built the project on my dual-boot because the game was lagging too much in the virtual machine. This made me suspect a race condition issue.
I first looked into the src/audio folder, where the bug likely was. I spent a few hours adding log messages to understand the flow of the program, and I finally found the issue.
When Tux dies, the Player class [calls](# "src/object/player.cpp (line 1949)") SoundManager::[pause_music](# "src/audio/sound_manager.cpp (line 343)") with the argument *fadetime=3.0* . This then [calls](# "src/audio/sound_manager.cpp (line 351)") StreamSoundSource::[set_fading](# "src/audio/stream_sound_source.cpp (line 127)") with the same argument, which changes its state to *FadingPause*.
Then in StreamSoundSource::[update](# "src/audio/stream_sound_source.cpp (line 75)"), because the state is now *FadingPause*, it decreases the gain of the music by [calling](# "src/audio/stream_sound_source.cpp (line 121)") StreamSoundSource::set_gain while the time counter does not reach the fade time.
In most cases, Tux reappears soon enough and GameSession [calls](# "src/supertux/game_session.cpp (line 158)") MusicObject::resume_music, which [calls](# "src/object/music_object.cpp (line 77)") SoundManager::[resume_music](# "src/audio/sound_manager.cpp (line 395)") with the argument *fadetime=3.2*.
It then [calls](# "src/audio/sound_manager.cpp (line 403)") StreamSoundSource::[set_fading](# "src/audio/stream_sound_source.cpp (line 127)") with the same argument, which changes its state to *FadingResume*. Then in StreamSoundSource::update the gain increases and the music plays.
But in some cases (**that is the bug**), Tux reappears after the fade-out effect has completed, and the music is [paused](# "src/audio/stream_sound_source.cpp (line 118)") instead of decreasing its gain. When Tux reappears, the gain is increased but we cannot hear the music because *it is not playing*: it is still paused.
I have noticed that the bug happens more frequently on the virtual machine
than on the dual-boot Ubuntu. In fact, I have built the project
on my dual-boot because the game was lagging too much in the virtual machine.
This made me suspect a race condition issue.
I first looked into the src/audio folder, where the bug likely was.
I spent a few hours adding log messages to understand the flow
of the program, and I finally found the issue.
When Tux dies, the Player class calls (1) SoundManager::pause_music (2)
with the argument *fadetime=3.0* .
This then calls (3) StreamSoundSource::set_fading (4) with the same argument
which changes its state to *FadingPause*.
Then in StreamSoundSource::update (5), because the state is now *FadingPause*,
it decreases the gain of the music by calling (6) StreamSoundSource::set_gain
while the time counter does not reach the fade time.
In most cases, Tux reappears soon enough and GameSession calls (7)
MusicObject::resume_music, which calls (8) SoundManager::resume_music (9)
with the argument *fadetime=3.2* .
It then calls (10) StreamSoundSource::set_fading (11) with the same argument,
which changes its state to *FadingResume*. Then in StreamSoundSource::update
the gain increases and the music plays.
But in some cases (**that is the bug**),
Tux reappears after the fade-out effect has completed, and the music is
paused (12) after decreasing its gain to 0. When Tux reappears,
the gain is increased but we cannot hear the music because
*it is not playing*: it is still paused.
## Fixing the bug
*04/10/2021*
To fix the bug, when the music must fade in, I call StreamSoundSource::[resume](# "src/audio/openal_sound_source.cpp (line 104)") on top of calling StreamSoundSource::set_fading in SoundManager::resume_music (which is called by GameSession).
To fix the bug, when the music must fade in, I call
StreamSoundSource::resume (13) on top of calling
StreamSoundSource::set_fading in SoundManager::resume_music (which is
called by GameSession).
This additional call will play the music if it is paused, and otherwise do nothing (ie. return immediately if the music is not paused).
... I just added one line.
### References: (before my commit, these might have changed since)
| n° | file | line |
|:--:|:----------------------------------|:----:|
| 1 | src/object/player.cpp | 1949 |
| 2 | src/audio/sound_manager.cpp | 343 |
| 3 | src/audio/sound_manager.cpp | 351 |
| 4 | src/audio/stream_sound_source.cpp | 127 |
| 5 | src/audio/stream_sound_source.cpp | 75 |
| 6 | src/audio/stream_sound_source.cpp | 121 |
| 7 | src/supertux/game_session.cpp | 158 |
| 8 | src/object/music_object.cpp | 77 |
| 9 | src/audio/sound_manager.cpp | 395 |
| 10 | src/audio/sound_manager.cpp | 403 |
| 11 | src/audio/stream_sound_source.cpp | 127 |
| 12 | src/audio/stream_sound_source.cpp | 118 |
| 13 | src/audio/openal_sound_source.cpp | 104 |
## Interacting with the community
*05/10/2021 late at night*
Before doing a Pull Request, I wondered if I should do an Issue describing the bug. I decided to ask the community about it, as it will give me the occasion to interact with others.
Before doing a Pull Request, I wondered if I should do an Issue
describing the bug. I decided to ask the community about it,
as it will give me the occasion to interact with others.
I went to the community's LiberaChat using KiwiIRC IRC Client, there is about 10 people connected. I asked:
> *(21h45)* Hello, I'm new here! I have found a minor bug and I would like to do a pull request to fix it. Should I do an Issue first to explain the bug, or can I just explain it briefly in the PR?
I went to the community's LiberaChat using KiwiIRC IRC Client,
there is about 10 people connected. I asked:
> *(21h45)* Hello, I'm new here! I have found a minor bug and I would like
to do a pull request to fix it. Should I do an Issue first to explain
the bug, or can I just explain it briefly in the PR?
To which Semphris replied: (he is one of the four members of the official SuperTux Team)
To which Semphris replied: (he is one of the official SuperTux Team members)
> *(21h46)* Normally I'd be among those who promote doing an issue first
> But honestly, the management is all over the place
> so if you don't want to bother opening an issue, it's fine
> As long as you explain what the issue is/was in the PR description, enough so that we can notice it, and discuss the upsides/downsides of many remedies
> As long as you explain what the issue is/was in the PR description,
enough so that we can notice it, and discuss the upsides/downsides
of many remedies
(He was the only one to say anything, even unrelated, in the following 2 hours)
(He was the only one to say anything, even unrelated,
in the following 2 hours)
Thinking about the objective of this course, I opted to also do an Issue, in order to have more interactions with the community. So I replied:
Thinking about the objective of this course, I opted to also do an Issue,
in order to have more interactions with the community.
So I replied:
> *(21h49)* Ok thanks, I think I will do the Issue first.
And so, I made an [Issue (#1833)](https://github.com/SuperTux/supertux/issues/1833) following the guidelines of the *CONTRIBUTING.md* file. I then commited to my fork (by again following the guidelines) and did a [Pull Request (#1834)](https://github.com/SuperTux/supertux/pull/1834)
And so, I made an [Issue (#1833)]
(https://github.com/SuperTux/supertux/issues/1833) following the guidelines
of the *CONTRIBUTING.md* file. I then commited to my fork
(by again following the guidelines) and did a [Pull Request (#1834)]
(https://github.com/SuperTux/supertux/pull/1834)
Later that night, at 23h38, Semphriss approved my PR, commenting:
> I remember running across that bug a few times. Props for finding how to fix it, and big thanks for the PR!
> I remember running across that bug a few times.
Props for finding how to fix it, and big thanks for the PR!
At 00h18, Tobbi said on LiberaChat: (he also is one of the four members of the SuperTux Team)
At 00h18, Tobbi said on LiberaChat: (he also is a member of the SuperTux Team)
> Interesting. I thought the issue has long been fixed
To which I replied:
> *(00h58)* Well, I only noticed it because it happened most of the time on my virtual machine:
> *(00h58)* Well, I only noticed it because it happened most of the time
on my virtual machine:
> The game was lagging so much that Tux took way longer than 3 seconds to die. The music had all the time to be paused (see the Issue for details)
> The game was lagging so much that Tux took way longer than 3 seconds
to die. The music had all the time to be paused (see the Issue for details)
(1h23) I decided to go to the community's Discord server. **What a surprise!** The Discord server is lively! I should have joined sooner, that's where everybody is hiding!
(1h23) I decided to go to the community's Discord server.
**What a surprise!** The Discord server is lively!
I should have joined sooner, that's where everybody is hiding!
## Update: two months later
I stayed on the discord server, which is indeed pretty active.
All the important decisions are discussed and made there.
It is also funny, for example with its joke rules
("banning" people for posting oranges in the wrong channel)
Unfortunately, I didn't have time to do more, but I hope to be able to in the
near future.
## Actual status
Waiting from others' approval, and hopefully a merge soon.
Commit merged into master on 11 October.
Issue closed on 13 October.
0% ou .
You are about to add 0 people to the discussion. Proceed with caution.
Terminez d'abord l'édition de ce message.
Veuillez vous inscrire ou vous pour commenter