ProtonDB | Game Details for The Floor is Jelly

The Floor is Jelly

Silver

Deck Verified Status

Unknown

Chromebook Ready Status

Unknown

Steam SteamDB Steamcharts Steambase PCGamingWiki Github Issue Search

Natively Supports:

Show Minimum Requirements

9 Reports

Filter:

Willex(7 reports)

Willex (7 reports)

Tinker Steps:Launcher: Lutris, Custom Proton: Lutris-GE-Proton8-2

Input:Responsiveness

Controller didn't work at first, restarting the game fixed it

Custom Proton: Lutris-GE-Proton8-2

Distro:Freedesktop.org SDK 22.08 (Flatpak runtime)

Kernel:6.4.8-arch1-1

RAM:15 GB

GPU Driver:4.6 Mesa 23.1.1 (git-fa55e3c026)

GPU:AMD Radeon (renoir, LLVM 15.0.7, DRM 3.52, 6.4.8-arch1-1)

CPU:AMD Ryzen 7 5800H with Radeon Graphics

Willex(7 reports)

Custom Proton: Lutris-GE-Proton8-2

Distro:Freedesktop.org SDK 22.08 (Flatpak runtime)

Kernel:6.4.8-arch1-1

RAM:15 GB

GPU Driver:4.6 Mesa 23.1.1 (git-fa55e3c026)

GPU:AMD Radeon (renoir, LLVM 15.0.7, DRM 3.52, 6.4.8-arch1-1)

CPU:AMD Ryzen 7 5800H with Radeon Graphics

LordAnton(4 reports)

LordAnton (4 reports)

Works perfectly well; game finished on Steam Deck without issue.

Proton 7.0-4

LordAnton(4 reports)

Proton 7.0-4

guggelfunsus(4 reports)

guggelfunsus (4 reports)

Proton 7.0-1

guggelfunsus(4 reports)

Proton 7.0-1

elronzorro(3 reports)

elronzorro (3 reports)

Played for 10 min w/ no issues. Used Proton Experimental and had gamemoderun in the launch options. Played perfectly with DS4 controller.

Proton 5.13-6

elronzorro(3 reports)

Proton 5.13-6

Unknown

Unknown

Borked

Decided I'd give this one another shot under Proton 4.11, still no dice. The game starts after installing lib32-lcms2 but still got the behaviour described by other reports. Tried with D9VK and disabling esync as well.

Distro:Unknown

Kernel:5.2.8-arch1-1-ARCH

RAM:32 GB

GPU Driver:NVIDIA 430.40

GPU:NVIDIA GeForce GTX 1060 6GB

CPU:AMD Ryzen 7 2700X Eight-Core

Unknown

Distro:Unknown

Kernel:5.2.8-arch1-1-ARCH

RAM:32 GB

GPU Driver:NVIDIA 430.40

GPU:NVIDIA GeForce GTX 1060 6GB

CPU:AMD Ryzen 7 2700X Eight-Core

high-falootin.tar.gz(174 reports)

high-falootin.tar.gz (174 reports)

Borked

"Fatal error: The application lost the device context!" displayed across the screen right away. I was still able to navigate the menu beneath, but the game itself was not playable

Distro:Ubuntu 18.10

Kernel:4.18.0-10-generic

RAM:32 GB

GPU Driver:NVIDIA 410.73

GPU:NVIDIA GeForce GTX 1080

CPU:AMD Ryzen 5 1600 Six-Core

high-falootin.tar.gz(174 reports)

Distro:Ubuntu 18.10

Kernel:4.18.0-10-generic

RAM:32 GB

GPU Driver:NVIDIA 410.73

GPU:NVIDIA GeForce GTX 1080

CPU:AMD Ryzen 5 1600 Six-Core

Unknown

Unknown

Borked

"Fatal error: the device lost the device context!"

Distro:Ubuntu 18.04.1 LTS

Kernel:4.15.0-34-generic

RAM:32 GB

GPU Driver:NVIDIA 390.87

GPU:NVIDIA GeForce GTX 1080

CPU:AMD Ryzen 5 1600 Six-Core

Unknown

Distro:Ubuntu 18.04.1 LTS

Kernel:4.15.0-34-generic

RAM:32 GB

GPU Driver:NVIDIA 390.87

GPU:NVIDIA GeForce GTX 1080

CPU:AMD Ryzen 5 1600 Six-Core

Unknown

Unknown

Borked

Unknown

Unknown

Unknown

Borked

Upon start, thows a "Fatal error: the device lost the device context!" error over the screen (along with a weird background)

Distro:Mint 18.1 Cinnamon (kernel 4.4)

GPU Driver:Intel HD graphics

Unknown

Distro:Mint 18.1 Cinnamon (kernel 4.4)

GPU Driver:Intel HD graphics

ProtonDB is a passion project from @bdefore and a dedicated community of reporters.

This site uses data from Steam as well as data provided by SteamDB via Algolia.

This site has no affiliation with Valve Software. All game images and logos are property of their respective owners.

Have some feedback? Come chat with us!

DISCORD

IRC

,