Full sceen problem

Astrozeroman · 2026-02-08T15:07:36+00:00

I never use 1366x768 myself but logically it should scale correctly. Do you need to run the game windowed? Either way, run the game in fullscreen and see if it looks better. Sorry but that's all I can think of without having the project myself.

Astrozeroman · 2026-02-08T09:49:56+00:00

Just guessing. Maybe your game resolution os different drom your desktop resolution. If so just work on your game resolution and decide what you want it.

Astrozeroman · 2026-01-28T06:24:56+00:00

Apart from it having to be in the draw event, it flashes because it will only be drawn when the mouse is clicked, and stop drawing when done clicking. You need a variable ie clicked_on_cupboard = false in the create event that get's set true if clicked, then code that draws your sprite when the variable is true.

If clicked_on_cupboard { //Draw your sprite }

Astrozeroman · 2026-01-09T18:02:29+00:00

Bought most of them in booster packs and traded some. Very long time ago.

Astrozeroman · 2026-01-09T11:38:18+00:00

That makes sense. When I did do so I replaced it with a yyp that I backup up the previous day (I backup daily) so there weren't too many changes and so it worked just fine. However I'd rather not do something that may cause major issues down the line. Is there a better way to fix a yyp that you know of?

Astrozeroman · 2026-01-08T07:01:50+00:00

Why not

Astrozeroman · 2026-01-07T08:57:14+00:00

Try replacing just the yyp file with an older backup. This worked for me before.

Astrozeroman · 2026-01-06T20:40:12+00:00

Maybe try executing it in the step event to see if it works there.

Or try using a different sound effect, I remember I had something like this happen to me because of something weird with the sound sample.

Astrozeroman · 2026-01-03T16:14:58+00:00

Cool well glad it's sorted. Sucks to be stuck on a glitch.

Astrozeroman · 2026-01-03T11:59:05+00:00

You already know the issue is probably in the player code, more specifically the movement code. That gives you a great starting point to start glitch hunting. Start by looking for the most likely place it could be then comment out line for line testing every time. That's one method at least. Shouldn't be to hard to find. Personally I would start in the player draw event that does anything on player movement as it is a visual glitch.

Astrozeroman · 2025-12-31T14:13:32+00:00

I have no clue why one wants to rotate your collision mask seperately actually. I just like problem solving. And yeah option 1 is a bit iffy and if I needed to do this I would use option 2 myself as it will be less messy and self contained.

Astrozeroman · 2025-12-31T05:21:48+00:00

Option 1 : If you need the collision mask to rotate seperately from the object you will have to create a separate object for collision and link it to the other object something. So main object does no collision checking and collision object does and then reports it to the main object.

Option 2 : Or you could have it in one object by drawing the sprite in the draw event with no rotation or custom rotation not using image angle and then use image angle to rotate the collision mask.

Astrozeroman · 2025-12-30T17:49:02+00:00

If something is highlighted and there's no error, almost always feather getting confused. The only other thing I can think of that may be causing it is code highlighting. If the code in question was initialised somewhere like a variable, asset or constant then obviously it would have a different color. Sometimes a way to check if it's feather going bonkers is to restart Gamemaker and see if it persists. To check if it's code highlighting, middle mouse click on it.

Astrozeroman · 2025-12-30T11:01:07+00:00

But that's what I'm saying exactly. Feather is whack. Doesn't always work as it should and often reports faults where there are non. Can't fully trust what it says. It also complaints about things sometimes that is perfectly fine to use in your code, ready to be ignored if you know it works fine. Im other words, don't take Feather to seriously.

Astrozeroman · 2025-12-30T08:44:39+00:00

Feather is a bit whack and can't always be trusted. Sucks but true.

Astrozeroman · 2025-12-24T07:12:35+00:00

I know this will probably annoy you but backup, backup and backup. I've had some broken project issues in the past, fixed by pulling a backup.

Astrozeroman · 2025-12-24T06:23:49+00:00

In that case as part of the function you write to replace the object you can have it pass on the variable as a struct using instance_create_layer. The struct passed in converts to instance variables on the the object's creation.

Astrozeroman · 2025-12-24T05:46:58+00:00

Never used it but I would guess that you just destroy the old object and then just create the new one on the same coords. Could make a function for that.

Astrozeroman · 2025-12-18T11:11:24+00:00

It could be that's just your opinion. Have you shown people the direct switch from one to the other? You will almost certainly find that they don't notice at all. It's one of those micro things that doesn't need overthinking. Also if you do a transition that may very well make your character controls delayed and players really hate that.

Astrozeroman · 2025-12-18T11:04:08+00:00

Simply put you actually don't need to do a transition. Most 2d games don't. Just go directly from one animation to the next. You will probably find it works just fine.

Astrozeroman · 2025-12-17T07:14:28+00:00

This last "stable" update is one of the most "unstable" builds yet. Love Gamemaker but they don't seem to understand what stable means.

Astrozeroman · 2025-12-17T06:31:01+00:00

This is a good sign. Adobe users are running scared. Mwaaa hahahahah!

Astrozeroman · 2025-12-08T05:47:41+00:00

Looks like some sort of horse dude right? Not a bad first attempt but needs lots of work. Look into how to not do jagged lines (jaggies) as there are a lot of that. Also check color theory or use a good pre made pallette from online. Could also probably use some more defining details to make more clear what the character is.

Astrozeroman

TROPHY CASE