Mari's Mountain Rollout [Post Jam Update]

Projects
, , , , , , ,
1

Hey everyone, I have release a new major update for my Get Large game jam submission.

It took a bit longer to get this out than I initially expected. Mainly because I didn’t want to just release a small patch to improve the controls and call it a day. I wanted to take the time to make the game something that is worth going back to for those who have already played it.

As such, I have added a good number of improvements to the game. As well as a few new features!

Here is a tldr of some of the major changes:

  • Updated models and textures for characters

    Mari_Comparison
    Mari_Comparison525×376 134 KB

  • New maximum size for Mari, and a new ending scene

  • More responsive controls that no longer feel like trying to control a fat woman rolling down a mountain

  • New main menu with an interactable Mari

    image
    image1146×645 75.5 KB

  • Intro cutscene is now fully animated, instead of being just a slideshow presentation

  • Level updated to be less empty

  • Jiggle Physics

The full patch notes can be read HERE for those who are interested.

Thanks to everyone who gave feedback on the original game,
and I hope you guys enjoy the new update!

14 Likes
2

What to do when screen looks like this?
Using the post jam version.

image
image2484×1251 208 KB

3

I have not seen this happen yet. It kind of looks like the camera is stuck in one of the trees.

A few questions

  1. When does this happen
  2. Is it just frozen on that image
  3. Are you using the Windows or Linux version
  4. What graphics card do you have
  5. Does “Turning it off and on again” do anything? (My IT background dictates that I am required to ask this question)
4

Reloading the application does not help.
AMD Radeon RX 6700 XT
Windows
It’s not a static image, and I can hear audio.
It begins as soon as you start a game, no problems are noticeable when the application first loads.

1 Like
5

Someone else had a similar problem with the old version of the game. I believe it might be an issue with AMD.

The person in this post reported that reverting to a driver before August and disabling updates fixed the issue.

Hopefully this helps

1 Like