next »

[Zack Bell]

Another Game Maker question...

Have a tough time getting my room transitions to appear like the original NES LoZ game.

Meaning exit one room via the south east corner, then enter the adjacent room from the south west corner.

Best way to handle multiple exits in rooms and appearing in the right places in the adjacent rooms?

Help is appreciated

EDIT: I believe that my player object needs to be persistent. Then I either adjust the x if I'm exiting left or right  or the y if I'm exiting up or down.
Something along those lines...

[Zack Bell]

I fixed it guys, no worries

But if anyone knows how to make the screen scroll in from the direction you're headed, let me know! (Again, look at LoZ if you don't know what I mean, conceptually)

[Geeze]

I fixed it guys, no worries

But if anyone knows how to make the screen scroll in from the direction you're headed, let me know! (Again, look at LoZ if you don't know what I mean, conceptually)

I'm not sure if there is a room transitions extension for GM(99% Sure that there is)
But that desired effect can also be achieved with surfaces. I wont go to any details as Im busy right now, and if you wanna figure it out by yourself

[ஒழுக்கின்மை (Paul Eres)]

I fixed it guys, no worries

But if anyone knows how to make the screen scroll in from the direction you're headed, let me know! (Again, look at LoZ if you don't know what I mean, conceptually)

you probably wouldn't want to do that unless everything lines up exactly right at the borders between the two rooms, otherwise it'd look weird to have mismatched tiles and stuff

[Zack Bell]

Thanks guys, I was actually looking into the Grandma Engine. Just for prototyping and for learning's sake.
I'd prefer not to use it for the final version of my game. The code in the engine is very neat though, I like it.

I fixed it guys, no worries

But if anyone knows how to make the screen scroll in from the direction you're headed, let me know! (Again, look at LoZ if you don't know what I mean, conceptually)

you probably wouldn't want to do that unless everything lines up exactly right at the borders between the two rooms, otherwise it'd look weird to have mismatched tiles and stuff

And yeah, I thought about this. Unless I cut all the rooms down to the same size (like LoZ), it doesn't look great.

[s0]

I've had that type of movement between rooms in my (now cancelled) game 444. The scrolling effect is actually one of GM's built-in room transitions IIRC.

[Zack Bell]

I've had that type of movement between rooms in my (now cancelled) game 444. The scrolling effect is actually one of GM's built-in room transitions IIRC.

Haha yeah, I totally figured that out this morning. Embarrassing much 

[sergiocornaga]

Matt Thorson has a system like this in the Grandma Engine (free) which I am using for my game "The Archer." Here is the code, which I've slightly modified.

I was going to use a system like this for a game I'm making, but the need for execute_string made me decide against it. But my only experience with execute_string has been reading people complaining about it and why never to use it... think I should just go with it anyway?

[ஒழுக்கின்மை (Paul Eres)]

you don't actually need it, you can do that without it. i've a similar system in SD and i don't use execute string

also, execute string isn't a problem if you don't run it every step, it's only a problem to use it when the game is playing, not when loading between rooms. there's no reason to avoid it if it's used only once every few minutes

[eiyukabe]

I've had that type of movement between rooms in my (now cancelled) game 444. The scrolling effect is actually one of GM's built-in room transitions IIRC.

Haha yeah, I totally figured that out this morning. Embarrassing much 

The GM built in room transitions are just full screen slides, which will move everything you're drawing (such as HUD elements and the PC). This may be fine for you, but if you want to have things (like HUD elements and the PC) stay in place on the screen while the environment moves behind them, this can be done with custom transitions and manual surface manipulation (as Geeze mentioned). I've implemented this for a similar setup before, let me know if you want more details and I'll dig it up.

[Zack Bell]

I've had that type of movement between rooms in my (now cancelled) game 444. The scrolling effect is actually one of GM's built-in room transitions IIRC.

Haha yeah, I totally figured that out this morning. Embarrassing much 

The GM built in room transitions are just full screen slides, which will move everything you're drawing (such as HUD elements and the PC). This may be fine for you, but if you want to have things (like HUD elements and the PC) stay in place on the screen while the environment moves behind them, this can be done with custom transitions and manual surface manipulation (as Geeze mentioned). I've implemented this for a similar setup before, let me know if you want more details and I'll dig it up.

For now (prototyping), GM's built in crap will be fine haha. But yeah, I'd love to hear more about how you did it just in case I take this project further in the furture! Thanks a lot!

[eiyukabe]

For now (prototyping), GM's built in crap will be fine haha. But yeah, I'd love to hear more about how you did it just in case I take this project further in the furture! Thanks a lot!

Alright it's a little more complicated than I remembered so I'll try to simplify.

First, we used a persistent player character. Each room had a start that she would be spawned at if she didn't already exist so we could test a later room without having to play from the start.

When she collides with our exit objects, we set some global transition variables that let us do custom transitions (transition_steps and transition_kind) before calling room_goto(). Example: transition_kind = global.transitionDown;

global.transitionDown is a globally defined transition ID we set up during game initialization, starting at 22 because, I believe, the numbers before that are reserved for built in transitions.
 Example:
global.transitionDown = 25;
transition_define(global.transitionDown, "scr_transitionDown");

"scr_transitionDown" is a script that gets called every frame during a transition. We used it to draw the two rooms (the one you're leaving and the one you're going to) scrolling while moving our player character in slight parallax to the scrollrate of the rooms and keeping our HUD static. It was pretty basic, like this:

Code:

var previousRoomImage, nextRoomImage, width, height, transitionFraction;
previousRoomImage = argument0;
nextRoomImage = argument1;
width = argument2;
height = argument3;
transitionFraction = argument4;

draw_surface_part(previousRoomImage, 0, 0, 640, 600, 0, -600 * transitionFraction);
draw_surface_part(nextRoomImage, 0, 0, 640, 600, 0, 600 - 600 * transitionFraction);
  
draw_sprite(spr_princess, 1, global.preTransitionX + (global.transitionX - global.preTransitionX) * transitionFraction - global.leftBorder,
    global.preTransitionY + (global.transitionY - global.preTransitionY) * transitionFraction - global.topBorder);

scr_drawSidebar(640, 0, true, true);

In hindsight, the literal screen sizes were probably bad . Oh well.

And of course we had four transitions depending on the direction you left the screen. Hope this helps.

[Zack Bell]

Thanks a lot! Great explanation and very helpful code! You don't mind if I implement it sometime?

[eiyukabe]

I don't mind, I believe code should be free to share (well, as long as it's not the whole game ). This is so small you don't even have to mention me or anything. Hope it works for you!

[Zack Bell]

Thank you!