Super Monkey Ball Banana Splitz [PCSE00017]

[Zangetsu38]

Game summary

• Game name: Super Monkey Ball Banana Splitz
• Game serial: PCSE00017
• Game version: 1.00

Vita3K summary

• Version: v0.1
• Build number: 1076
• Commit hash: https://github.com/vita3k/vita3k/commit/bc03af6

Test environment summary

• Tested by: Zangetsu38
• OS: Windows 10
• CPU: AMD Ryzen 2700X
• GPU: NVIDIA GTX 1080 Ti
• RAM: 16 GB DDR4 3600 mhz

Issues

• stop boot with open mai module with unicorn error

  Unicorn error 0x7 at: start PC: 0x81438B81 error PC 0x81211382 LR: 0x81218E69

Log

vita3k.log

[DniweTamp]

I only have the JP version, but it goes into menus now

https://user-images.githubusercontent.com/39583006/139515038-4916d7d6-c338-48cf-8537-0ada9b3ddedd.mp4

[gymzatan]

App summary

• App name: Super Monkey Ball Banana Splitz
• App serial: PCSE00017
• App version: 1.00

Vita3K summary

• Version: v0.1.5
• Build number: 2686
• Commit hash: https://github.com/vita3k/vita3k/commit/27e0c030
• CPU backend: Dynarmic

Test environment summary

• Tested by: gymzatan
• OS: Windows 11
• CPU: AMD Ryzen 7 5800H
• GPU: AMD Radeon(TM) Graphics
• RAM: 16 GB

Issues

Black screen after selecting the game mode.

Screenshots

Log

vita3k.log

Recommended labels

• Menu

[othmanead]

Vita3K summary

• Version: v0.1.6
• Build number: 2842
• Commit hash: https://github.com/vita3k/vita3k/commit/0a6ef4d9
• CPU backend: Dynarmic

Test environment summary

• Tested by: othmanead
• OS: Windows 11
• CPU: Intel i5-10300H
• GPU: RTX 3060 mobile
• RAM: 16 GB

Issue:

Game plays with no issues

Screenshots:

Log

vita3k.log

Recommended labels

• Playable

[JessicaIn3D]

App summary

App name: Super Monkey Ball Banana Splitz
App serial: PCSE00017
App version: 1.00

Vita3K summary

Version: v0.1.6
Build number: 3004
CPU backend: Dynarmic

Test environment summary

Tested by: LukeGreatwow
OS: Windows 10
CPU: AMD Ryzen 5 5600X 6-Core
GPU: NVIDIA GeForce RTX 3080
RAM: 32 GB

Issues

Game runs fast in most areas, crashes between the first and second level PCSE00017 - [Super Monkey Ball Banana Splitz].log

[poudink]

App summary

• App name: Super Monkey Ball Banana Splitz
• App serial: PCSE00017
• App version: 1.00

Vita3K summary

• Version: v0.1.6
• Build number: 3091
• Commit hash: https://github.com/vita3k/vita3k/commit/e3956248
• CPU backend: Dynarmic
• GPU backend: OpenGL

Test environment summary

• Tested by: poudink
• OS: SteamOS 3.4.6, Kernel 5.13.0-valve36-1-neptune
• CPU: AMD Custom APU 0405
• GPU: AMD AMD Custom GPU 0405 (vangogh, LLVM 14.0.6, DRM 3.45, 5.13.0-valve36-1-neptune)
• RAM: 14.47 GB

Issues

Game is fully playable, but has several minor issues. This was tested both launching the game from the Steam Deck's gaming mode and launching the game directly from the Steam Deck's desktop mode (meaning stock KDE Plasma).

• Leaving V-Sync enabled often causes the framerate to randomly drop to 40fps. It seems to happen a bit more often in more complex stages, but it's not consistent at all. Resolution scaling doesn't seem to affect this much and sometimes just dying and respawning or pausing and unpausing will bring the framerate back to 60fps. With V-Sync disabled, the game always runs at a consistent 60fps at 2x resolution.
• Skipping the intro video while using the OpenGL backend crashes Vita3k, but only if the emulator is launched from Steam. Launching the vita3k executable directly prevents the crash from happening. Waiting for the intro video to finish prevents the crash too. Using the Vulkan backend also avoids the crash, but that just causes the game to unavoidably crash after the title screen instead, so using OpenGL is still preferable.
• Slight audio crackling.
• Using the Vulkan backend causes a crash after the title screen. In gaming mode this crash just closes Vita3k, but in desktop mode it brings the entire Plasma session down, forcing a system restart. Looking at earlier screenshots here, it seems the Vulkan backend isn't a problem for other people, which seems to indicate that Vita3k's Vulkan backend has trouble with the RADV Vulkan driver. I've encountered an identical crash with Vulkan in Persona 3: Dancing in Moonlight after the title screen, which others using the Vulkan backend also seem to have no problem with.

Recommended labels

• audio quality
• crash
• Playable
• vulkan crash

[nishinji]

@poudink can you post log?

[poudink]

sure, sorry for the lateness regular gameplay: too big for github (it's only 2mb with 7z lzma2 but github only lets you upload zip or targz and then it's 26mb) regular gameplay + vsync (cleared beginner): regameplayvsync.tar.gz opengl intro skip crash: glcrash.tar.gz vulkan crash: vulkancrash.tar.gz

[poudink]

By the way these logs are huge so I'm thinking maybe the logging settings I used were too extreme. I set Log Level to Trace and enabled Shader logging and Uniform logging. I didn't enable Import logging and Export logging, mostly because I didn't notice those options. What are the logging settings I should be using for reporting issues? I don't remember the defaults, since I usually have all logging turned off (I've had problems with logging reducing performance in some other emulators).