-
Notifications
You must be signed in to change notification settings - Fork 312
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Shin Megami Tensei V: Vengeance - 010069C01AB82000 #4991
Comments
Game Name Game Version Emulator Build Version OS Graphics Backend Hardware Specs Game State Runs without any issues at 30fps native resolution, didn't spotted any graphical or sound glitches either. Developers team thank you very very much. |
Game Name Game Version Emulator Build Version OS Graphics Backend Hardware Specs Game State Runs without any problems except a lot of stuttering when loading shaders. The problem i am facing its that after closing the game, and booting it up again, it starts compiling shaders again but without "too" much stuttering. |
Game Name Game Version Emulator Build Version OS Graphics Backend Hardware Specs Game State Post-update performance is so smooth that it almost seems like black magic. Using graphic upgrade mods to test this new level of performance (increased LOD, etc.) gives a very playable FPS across the board without bouts of stuttering. Already reported visual bugs, like some characters occasionally flashing during cutscenes or some surfaces flickering in the World of Shadows, are still there, but do not detract from gameplay in the slightest. |
Literally has nothing to do with the latest update of the emu. Its just shaders being made, its always gonna be like that. |
I think you're misunderstanding me because I didn't explain it with the right terminology ("first boot" is probably wrong; I meant every time the game is booted up and loads into the game proper), but to confirm my case I downgraded back to version 1.1.1336 and all described issues were back. Went back to 1.1.1337, issues gone again. Loading times were especially noticeable: from approx. a minute and a half to load my savegame, to barely eleven seconds. Since no other variables changed, I can only think of the emulator's update being the reason why. |
Game NameSHIN MEGAMI TENSEI V: Vengeance Game Update Versionv1.0.1 Emulator Build Version1.1.1337 Graphics BackendVulkan Hardware Specs
Game StateGame runs fine with some graphical issues. Note The game is using Unreal Engine 4 and has issues with flickering objects. Stuff comes in and out of existence during cutscenes and during gameplay. Video of issue: vid10.mp4ScreenshotsLog File |
Yeah its not the update, seems like W11 is doing stuff differently than W10 is. |
I upgraded and im still getting the same stutters at first boot (after loading the game) even after compiling shaders. i dont know why this is, doesnt happen with the other emu. |
Game NameSHIN MEGAMI TENSEI V: Vengeance Game Update Versionv1.0.1 Emulator Build Version1.1.1340 Graphics BackendVulkan Hardware SpecsCPU: Ryzen 5 4600G Game State:Game runs mostly stable at 30fps, only stutters when loading new textures, but that's to be expected. The only issue so far is that the game freezes, then crashes when entering Cadaver's Hollow sometimes for some reason. This only happens specifically when entering Cadaver's Hollow after playing for 30 mins to 1 hour. I also sometimes pause the emulation when I take a smoke break then un-pause when I get back, I'm not sure if that has anything to do with it but there's that. Log file: |
Game Name
Shin Megami Tensei V
Game Update Version
1.0.1
Emulator Build Version
1.1.1332
Graphics Backend
Vulkan
Hardware Specs
CPU: i7 8700
GPU: NVIDIA GTX 1070
GPU Driver version: 32.0.15.5599
RAM: 16GB
Game State
Appears playable but with flickering objects throughout. Played through the intro sequence up to when you first make it to the netherworld. The map screen flickers sometimes, and the main character flickers. This only happens with Vulkan, not OpenGL, although OpenGL is much slower.
Screenshots
Log File
Ryujinx_1.1.1333_2024-06-16_14-34-31.log
The text was updated successfully, but these errors were encountered: