vectorsatyr / legacy-sonic-for-gms-1 Goto Github PK

When selecting the delete option, press the left button quickly until you reach slot 1 (but without the animation has yet reached), and then when you press start and left, this happens.

roll_slope_friction_up = 0.071825;

In the Sonic Retro Physics guide, they have a constant called slprollup set to 0.078125
http://info.sonicretro.org/SPG:Solid_Tiles

Did you mean to use their value?

When the ring counter reaches maximum, if you collect more rings, the ring collecting sound will not play.

1. Is it possible to have multiple shaders being used at the same time? If not, not a big deal.
2. Does the shader engine only support four colors? I did this,
   normal_color = array_create(5);
first_array = array_create(5);
second_array = array_create(5);
third_array = array_create(5);
fourth_array = array_create(5);
   Using array_create(5); instead of array_create(4);
   And set up the fifth color the same way I did the others, yet still only the first four colors animate.
3. Is there a way to disable shaders for specific parts? Like the HUD.

When using a Quarter Pipe Mask lower to 96x96, collisions don't work properly.

https://cdn.discordapp.com/attachments/702170883116105748/712780315378057276/Honeycam_2020-05-20_18-31-43.gif
https://cdn.discordapp.com/attachments/702170883116105748/712785114752483469/Honeycam_2020-05-20_18-51-31.gif

If you are in file deletion mode, select any file, and by directly pressing the start button, you will see the Eggman sprite slowly descend pixel by pixel.

This occurs when Eggman's sprite returns to the original position.

A new update to GMS2 finally fixed the 1.4 importer, and now the Sonic For GMS engine runs well using it. The only issue is object FileSelectMenu uses a temporary variable called layer, which is now the name of a built-in variable. Changing this name allows the game to run fine on both VM and YYC mode.

If you think it might be worthwhile to support GMS2 as well, I could send you a key to the software if you don't already own it.
(Also I apologize, issues isn't the right place for this)

I found this bug when testing out different terrain layouts. Basically, you either get stuck in a single place building up speed until you jump, or you snap to the terrain below. I uploaded a video to YouTube showing the bug in action: https://www.youtube.com/watch?v=_YQiwt1-3FE

I am not sure if this is intentional, or if it can be fixed normally. It only seems to happen when curve terrain is next to normal terrain. I am not sure if this happens if curve terrain is next to slopes, but I will test that out if needed.

I see there is LayerFlip object, but if the player jumps over the loop, they won't be able to go through the loop backwards. Is there a way to force the entrance and exits layers of loops?

Hello, i'd like to point out that if sonic get's crushed/fall into a pit/etc. the lives count won't drain by 1 and the timer will freeze at 0:00

game_audio_fmod_add_sound(path + "Studiopolis1Music.ogg", 4663458);

Looking through the .ogg file, I have no idea where that numbers comes from.

Trying to add zoom tubes in the form of pathing. Just want the player to follow a path, and then resume normal routines after the path is done.

Device: Windows PC
Environment: Windows 10 Home
Severity: Major
Frequency: Always (10/10)

Steps to reproduce:

1. Launch the Sonic for GMS executable.
2. Progress to Demonstration Zone 1.
3. Wait for the timer to expire.

Expected result:
The player character is defeated; "Time Over" appears on the screen, unless the player's last life was lost, in which case "Game Over" appears.

Actual result:
Nothing noticeably different happens.

Sorry if I'm not allowed to ask this here. I wasn't sure where I could ask questions on how to fix something.

I'm attempting to implement the classic debug mode from S3K into the engine (I prefer it over the current one, which is kind of limited). I've run into an issue though while implementing it: the player character does not seem to be jumping to the debug object's coordinates properly.

I'm putting the player into the already provided debug state (which I removed the movement code from) with this code:
if (game_player_find(0) != noone) { with (game_player_find(0)) { if instance_exists(character) { with (character) { game_pc_perform(self, player_is_debug); } } } debug_active = 1; }

and attempting to make the player jump to the debug object with this code:
with (game_player_find(0)) { if instance_exists(character) { character.x = other.x; character.y = other.y; } }

Sorry that it looks sloppy. I'm not sure how to keep the formatting and line breaks. Also I uploaded a video of what happens in-game: https://youtu.be/G-hyQKXOW6w

Am I doing something wrong? Or am I suppose to be controlling the coordinates in another way?

Not sure if this is because of how the spike is set up, but when the player spindashes into a spike underwater, they are put into the death state for about a frame before being placed back on the ground and are able to do normal actions until the room resets.

Video of the bug in action: https://www.youtube.com/watch?v=GOzaN1x_ItU

Not sure why this is happening. Any suggestions? This also happens when doing just normal vertical movement.

Just discovered this when implementing some of the recent bug fixes into my own build of the engine. Basically, when you create a new WorldRing object in the stage, get it attracted to you, go into the player_is_debug state, and exit the player_is_debug state while the newly attracted WorldRing and an enemy is colliding with you, the game instantly crashes with an error message.

I was able to replicate this in both my own build and the latest GitHub version of the engine.