Posté le 24/11/2019 17:47
!
Ici j'ai ajouté le fond des niveaux, la texture de la roche, et la possibilité de mettre en pause le jeu (mais ça vous ne le voyez pas 
)
Ajout des compteurs(pièces, score, vies, temps) fonctionnels.
Ajout des goombas, cadeaux et des briques fonctionnelles.
Image du 15/02/2020 (J'utilise l'émulateur, c'est plus propre maintenant non ? )
scrolling de la caméra plus fluide, ajout des plateformes a mouvement horizontal correction du bug du "wall jump" découvert par Kikoodx (le grand mario pouvait grimper les murs) Voici les différentes versions disponibles versions fixées (la dernière de préférence) version temps réel (repo git), mais cette version peut être instable
Planète Casio v4.3 © créé par Neuronix et Muelsaco 2004 - 2024 | Il y a 261 connectés | Nous contacter | Qui sommes-nous ? | Licences et remerciements
Planète Casio est un site communautaire non affilié à Casio. Toute reproduction de Planète Casio, même partielle, est interdite.
Les programmes et autres publications présentes sur Planète Casio restent la propriété de leurs auteurs et peuvent être soumis à des licences ou copyrights.
CASIO est une marque déposée par CASIO Computer Co., Ltd
Citer : Posté le 15/02/2020 17:00 | #
Pour l'instant les niveaux font 13 ou 14 tiles de haut, soit au maximum 112 pixels de haut. Mais j'envisage de (pourquoi pas après tout) tester des niveaux en forme de tour, donc qui seraient beaucoup plus verticaux
Si j'ai le temps ce soir, je fais un article pour la rdp de demain
Invité
Citer : Posté le 17/02/2020 21:03 | #
Bonjour, j'ai essayer le jeu mais impossible d'arriver au niveau 4. Le niveau 3 est comme impossible. Une explication ?
Merci d'avance
Citer : Posté le 17/02/2020 21:31 | #
En fait, le jeu est encore en développement, et donc seuls les deux premiers niveaux sont complets. Le troisième est une ébauche, et les autres n'ont pas encore été faits
Merci beaucoup d'avoir testé en tout cas, et n'hésite surtout pas à poster un retour ou proposer des améliorations
Citer : Posté le 18/02/2020 09:18 | #
Salut, j'ai testé la nouvelle version c'est beaucoup plus fluide !
La rémanence est beaucoup moins "lourde" qu'avant, sûrement grâce à la caméra et l'interface moins présente.
Comme l'a noté Lephé' on se retrouve de temps en temps dans des situations où le sol est hors vision (niveau 2), une des solutions au problème serait de déplacer la caméra en maintenant haut ou bas (temporairement).
Citer : Posté le 18/02/2020 09:25 | #
Merci pour ton test
Maintenant que j'ai complètement désactivé les touches haut et bas, je vais peut être les assigner, peut-être avec un raccourci particulier, à la caméra
Je ne sais pas encore trop exactement comment le présenter au joueur, mais c'est dans les cartons
Dans l'idée, la pression seule de la touche haut pourrait faire monter la caméra, de même avec bas. Comme ça ce serait un peu comme Gravity Duck dans l'idée
Citer : Posté le 18/02/2020 09:45 | #
Ça me paraît pas mal, surtout qu'on avance souvent à droite et taper Droite+Haut ou Droite+Bas est faisable sans s'arrêter de bouger.
Invité
Citer : Posté le 18/02/2020 10:09 | #
En fait, le jeu est encore en développement, et donc seuls les deux premiers niveaux sont complets. Le troisième est une ébauche, et les autres n'ont pas encore été faits
Merci beaucoup d'avoir testé en tout cas, et n'hésite surtout pas à poster un retour ou proposer des améliorations
Merci,
Bon développement
Citer : Posté le 18/02/2020 11:08 | #
Hello! Thank you for developing this cool add-in game. This is almost stable IMO.
In fx-9860GII emulator, its speed is fair. But in Graph 35+EII emulator, it runs just like the real game! Almost three times faster than fx-9860GII one! (And so the timer is also 3 times faster) But the startup screen and level screen skips immediately (like 0.1 sec) in fx-9860GII one unlike Graph 35+EII.
Also I found a bug that you cannot re-enter the game once you quit by pressing [MENU], [EXIT], or even in-game exit button. You have to load any element other than itself in Main Menu to solve this bug.
Citer : Posté le 18/02/2020 11:19 | #
Once you leave an add-in that terminated its main() function, you can normally not reenter, whatever the add-in.
Usually you use GetKey(), which allows you to press MENU and go back to the menu in a non-terminating way (so you can come back). This is a missing feature in gint's getkey() function, but we already know how to do this (it's a matter of time).
Citer : Posté le 18/02/2020 11:28 | #
In fx-9860GII emulator, its speed is fair. But in Graph 35+EII emulator, it runs just like the real game! Almost three times faster than fx-9860GII one! (And so the timer is also 3 times faster) But the startup screen and level screen skips immediately (like 0.1 sec) in fx-9860GII one unlike Graph 35+EII.
I guess that when you talk about the fx-9860GII emulator, you talk about the ont which is included in the SDK. Unfortunately, the bugs presents in the SDK, especially about speed, are (i think) due to a special behavior of the emulator which is not supported by gint, so I can't fix them
But if you did test it on the Graph 35+EII emulator, which is a true copy of the current model, you could test in real conditions this game
Also I found a bug that you cannot re-enter the game once you quit by pressing [MENU], [EXIT], or even in-game exit button. You have to load any element other than itself in Main Menu to solve this bug.
This is a standard addin behavior, when you exit it, you cannot relaunch it immediately again, you have to run another app before.
However, Lephenixnoir is making in gint an enhanced getkey function, designed to pause the addin when [MENU] is pressed (like in other addins like C.BASIC). When it will be developed I will use it
Thank you very much for testing, and also thanks to Lephe, for all the work about gint, which is very efficient and stable.
Citer : Posté le 18/02/2020 11:30 | #
I should mention that gint's timers are set according to the actual clock frequency so they should really be the same time on all platforms. Do you know more about that emulator special behavior Milang ?
Citer : Posté le 18/02/2020 11:39 | #
In fx-9860GII emulator, its speed is fair. But in Graph 35+EII emulator, it runs just like the real game! Almost three times faster than fx-9860GII one! (And so the timer is also 3 times faster) But the startup screen and level screen skips immediately (like 0.1 sec) in fx-9860GII one unlike Graph 35+EII.
I guess that when you talk about the fx-9860GII emulator, you talk about the ont which is included in the SDK. Unfortunately, the bugs presents in the SDK, especially about speed, are (i think) due to a special behavior of the emulator which is not supported by gint, so I can't fix them
But if you did test it on the Graph 35+EII emulator, which is a true copy of the current model, you could test in real conditions this game
Citer : Posté le 18/02/2020 11:43 | #
First, I noticed that sleep_ms and even sleep functions does not work :
The splash screen, level screens etc are displayed, but without any pause.
Because of that, when I run the game on the SDK, even if the timer speed is fine, the (virtual) cpu never pauses, and this leads to a quite high (real) cpu consumption for this kind of emulator. (This is subjective, but I think its quite heavy to use 50-80% of a single core at 2.8GHz, even in wine)
There is a second specific behavior, but I don't think that we can change anything about it:
There is no gint_panic function called when an exception occurs: The sdk comes first and shutdowns the emulator, and displays a message like this An exception occurred ! Illegal read access at 0xFFFFFFFF for example. This slows down debug, so, ironically, when I have to find the cause of a crash, I have to try it on the calculator
Citer : Posté le 18/02/2020 11:43 | #
Wait, why did I get this picture in fx-9860GII emulator (this time in actual machine), saying "RAM full"?
Did you design it, Milang?
And I can't even press any key there.
Citer : Posté le 18/02/2020 11:46 | #
Oh, maybe you found a memory leak
Can you press the L key and send a screenshot of a few log lines ?
(The key with an arrow, you don't need alpha)
Yes, I designed it, It's a custom error msg
Citer : Posté le 18/02/2020 11:49 | #
This is the latest log.
Citer : Posté le 18/02/2020 11:50 | #
Oo
This is not expected at all
Ajouté le 18/02/2020 à 11:52 :
There is a log hidden in the addin, based on liblog
At any time you can open it by pressing the [→] key, and also in the configuration menu
you should have seen something like
[std] free called
[std] number of zones
1
[std] malloc 280 OK
[std] number of zones 2
Ajouté le 18/02/2020 à 11:55 :
Ouch...
I confirm that this is a memory leak.
It seems that it allocated twice a level without freeing the previous
I will try to reproduce it and fix it
Citer : Posté le 18/02/2020 11:55 | #
Oo
This is not expected at all
Ajouté le 18/02/2020 à 11:52 :
There is a log hidden in the addin, based on liblog
At any time you can open it by pressing the [→] key, and also in the configuration menu
you should have seen something like
[std] free called
[std] number of zones
1
[std] malloc 280 OK
[std] number of zones 2
Yes, I've found out, but what "malloc 12080 FAILED" means?
Citer : Posté le 18/02/2020 11:57 | #
malloc 12080 FAILED means that when the program tried to allocate 12K of RAM, it did not work because there wasn't enough space available, so it logged that the malloc failed and then it stopped
Citer : Posté le 18/02/2020 12:08 | #
malloc 12080 FAILED means that when the program tried to allocate 12K of RAM, it did not work because there wasn't enough space available, so it logged that the malloc failed and then it stopped
Well, I think I can reproduce the memory leak now. Just load the level 1, don't press any key and wait until this error pops out.
Citer : Posté le 18/02/2020 12:10 | #
Waait, this is not a memory leak
There is always a state when a copy is done and this time, it did not work because the second allocation was impossible. However, this is the first time it happens, and it will remain very rare.
If I'm right, the sh3 have less ram than the sh4 ones. Then this bug is only for sh3 models, which are very short in terms of ram margin.