I don't know, but I remember some people having this issue before in this forum. So if you use the search function you probably find some good informations about it.

Same loop error here

The solution is to unable freesync

same problem here.

And how do you do this? Where?

Originally posted by exejuarez2012:

The solution is to unable freesync

to have freesync enabled at all- must have an AMD video card, a monitor that supports it, and a connection that supports it. if you have one but not the others- this isn't the problem.
easiest way to disable freesync is use the Radeon software in your system tray or search for it in the start menu (its part of the standard driver install package.) if you have a multi monitor system you only have to disable the monitor gris is running on. it should be listed as an option. turn it off, the monitor(s) may blink when this is done. start gris and it should work. if that does not help or you can't find the option in the driver, it may be an option in the monitors own menus (see monitor documentation for details) note that only the monitor that is running gris needs to be changed.
i have no idea what happens in an eyefinity installation but i doubt Gris even supports eyefinity.
Is there someone out there that has had to do this seen the screen tearing that Freesync is supposed to stop in gris?

This just happened to me on a GTX 1060. The solution was to quit, continue, then go up the other side of the temple leading up to the birds.

I had been going left and getting stuck at the edge. First time I went right, the mechanics worked.

Can confirm, going on the right side worked

For me, I had to put my monitor on 60hz

Huh. Is it really using frame counts as trigger delays? After every major area transition, the game sits around after the transition for over a minute, floating in the air stuck. The first time it happened I thought the game had softlocked, but it eventually woke back up. I'm playing on a 240Hz monitor. This game looks really well-made and I can't imagine that it's really doing something that silly, but it seems like a lot of people are having problems like this.

Originally posted by ank:

For me, I had to put my monitor on 60hz

This is the way

The 60hz trick worked for me since I was on 165! Thanks

the usual thing that gets this to work is to disable fullscreen, and limit FPS to 60

(there's a lot of threads on this from earlier when the game was new, if you do a search here in Discussions)