Of all 3 of these videos, that's the only part I still share with people on the Discord server. Glad it helped you.

Not that I know of, no. Many, many, many games (even games not made in GM) do this.

@@PixelatedPope I assume that was not noticeable since all games start with a loading screen. Thank you

Yeah. Had my noise gate set too high, unfortunately. Something to fix for next time.

@@PixelatedPope Great content all round though in general <3

Rip

Watch again and follow along carefully. I promise it works

@@PixelatedPope triple checked it all and even redid my whole code and it still doesn't work, here's my code, is thar anything wrong? //create view_width = 1280/6 view_height = 720/6 view_scale = 3 window_set_size(view_width*view_scale,view_height*view_scale ) alarm[0] = 1 surface_resize(application_surface,view_width*view_scale,view_height*view_scale ) //end step #macro view view_camera[0] camera_set_view_size(view, view_width,view_height) if (instance_exists(Obj_pcat)) { var _x = Obj_pcat.x - view_width/2 var _y = Obj_pcat.y - view_height/2 camera_set_view_pos (view, _x, _y) } // Alarm 0 window_center(); // Room Start view_enabled = true; view_visible[0] = true;

@@imnotme2681 have you placed an instance of this camera object in the room?

So when you divide 1920x1080 by a whole number, the higher that number, the more zoomed in you are going to be. The problem comes from when you want something between like 3 and 4. 4 is too zoomed in, 3 is too zoomed out. You could try like 3.5 or something, but this could introduce distortions. There are work arounds for that, but it gets complicated.

@@PixelatedPope It actually worked out incredibly well, I got exactly what I wanted with virtually no issues. Thank you for the help, have a good one.

Or would it be easier to set all of that in a controls script with all the image sprites set to each direction, call that script in the create and step event of the player, but use it as a reference for what to replace/add for (!right_key.. etc ?

I wouldn't recommend using this movement code for top down. You should check out my top down movement and collision system on Itch. It's free and it works similar to this (whole number only coordinates) and it works great with TrueState.

@@PixelatedPope thank you!

To be perfectly honest: the REAL message is don't worry about it. It's not worth the effort. Just let there be black bars in your 2D pixel art game. Just let there be a bit of distortion if it doesn't scale perfectly. Worst case scenario, you apply a bi-linear filter (games like Sonic Mania do this). ESPECIALLY if you are new to Gamemaker, it just. Isn't. Worth it.

You should join the Gamemaker discord server. I'm often available there and can help you troubleshoot it live. discord.com/invite/gamemaker

I've got a much better keyboard/mouse wrist rest / pad thing now. But those gloves were a quick solution

@@PixelatedPope haha they looked crazy - thx for the vids, been sifting for the good stuff

Itch appears to be down at the moment. Try again in a bit

Just noticed that 🤦 went through troubleshooting my laptop resetting dns ect 😂 ​@@PixelatedPope

K

@@PixelatedPope thanks for the insightful response man 🤞🥶

@@americantoastman7296 Look, what is "simple" for some people is "complex" for others. I've been helping people with Gamemaker for a really long time, and for most people, explaining literally every single line is just too overwhelming. They want to know what they need to do to get the results they want. If they can follow along and it seems to work? Awesome. That's what they want. That's what "simple" means to them. It rarely involves them understanding what literally each line of code is doing. They can understand the technicalities later... for now, they just want something that works so they can move on and make their game. Is this video perfect? No, of course not. But you aren't going to be able to convince me that it would be "more simple as possible" if it was 3 times as long and broke down every single line of code in excruciating detail. There is a place for that video, absolutely, but that wasn't the intention here.

@@PixelatedPope hey thanks for the response, appreciate it. I might give this a rewatch some time in the future. It seems to help people and that's great. I just wanted to voice my personal frustrations as I was looking for a simple explanation of views, cams etc and this (for me) just wasn't it. Again, it felt like it assumed a lot of knowledge from the start that I was hoping to learn about in this video instead of being confronted with it outright. But hey, maybe that's a me thing. It seems to be helping out a lot of other people, so good work!

@@americantoastman7296 Certainly! And you can always join the GM Discord Server and get way too much detail on any topic you are interested in any time. I'm there most weekdays while I'm working helping people and answering questions: discord.gg/gamemaker

You can grab it from Itch pixelatedpope.itch.io/retro-palette-swapper

The basic concept is still pretty much the same, but we don't use Data Structures anymore. Everything is arrays and structs and JSON for saving and loading.

My dude. This video is almost a decade old. You should be using the latest version of Game Maker (which is free) and follow a more recent tutorial. All this info is super out dated

Yup, that's a great starting resolution. There are almost always going to be displays where it won't scale perfectly, but once you are scaling over 3x, you can apply a bi-linear shader to it and it will look awesome (Sonic Mania does this on the Switch)

im mostly concerned with making a game to play on my steamdeck, and i figure i may as well also try to make it look good for switch too @@PixelatedPope

would you please do a follow up to this video that also goes over having a rotating camera like final fantasy tactics's battles?@@PixelatedPope

@@lloyd011721FFTactics is 3D. If you wanna learn how to do 3D in GameMaker, DragoniteSpam has like 70 videos on the topic.

alright thanks @@PixelatedPope

Nope, you are absolutely correct. Getting something truly "fail safe" is prohibitively difficult. I'm in the writing stages of a new tutorial that will cover exactly this. I had similar problems on my Surface Book (3000 x 2000 display)

@@PixelatedPope 10-4 ty, just was confirming. It is an excellent tutorial as usual though and a great primer. Looking forward to seeing the next vid. Also, I just believe the issue in my use case is that it's an aspect ratio mismatch. NES resolution 4:3 and Quad HD 16:9. So the solution would be to just use a 16:9 ratio similar in size to the nes. Correct me if I'm wrong though

View Port is a combination of your app surface size and your window size. Don't change any settings in the room editor. Make sure they are all DEFAULT

@@PixelatedPope User Thank you for your quick response! If I keep the default values there, then I have a black screen. I have no idea what it could be. But I definitely want to use your camera system. especially with regard to sub-pixel movement, which you mentioned in the forum, which works perfectly. I hope I can find the problem. edit: The camera properties from the editor overwrite the values that I set with camera_set_view_size in the end step menu. Viewports are disabled and not visible in the editor and it doesn't matter which viewport I choose. no idea what it is. if I use camera_create_view in the create event of the camera object, then it works. no idea why it is like that. anyway, thanks for your good work

512x448 is the resolution of some of the original Super Nintendo games (like Secret of Mana and Final Fantasy 6). But, I do just what you suggest in my Cameras as Simple as Possible video.

All right, basic setup seems to work, camera follows at the center of my player, all fine, except the sprite of the player moves in totally different speed, not staying in the position of the player. What's up with that? Actually sprite is already drawn in a different location when I start the game, weird. Position should be absolute I think, why is it offset by that much? If I take out the camera code everything works as it should, something makes my sprite drawn in wrong place. EDIT: I found it, I had draw_self() function at draw GUI... which apparently is wrong choice. :D

Maybe? I don't use sequences for their intended purpose, but they do work as an interesting visual editor. And working with GUI elements in sequences is reportedly a bit of a pain

Ohh i see. Yesterday i tryed to set my gui at 3840x2160, i'm using 2 monitors, one Full HD and the other in 4K, how can you explain that if i run the game in the Full HD using that proportion of my gui works still great? The gui will scale lower resolution and will stretch bigger resolution for fit correctly everytime? Thank you for your answer i really appreciate that.@@PixelatedPope

Last time I checked, yes

Natively? No. But you could probably add this yourself. If you look at line 84 of scr_retro_pal_swapper you'll see that I get the texture and UV info and hard code image_index 0. You could make that an argument on the pal swap set function and you'd be good to go

@@PixelatedPope cool! Thanks for that, worked great.