RPCS3 Forums - Super Street Fighter 2 Turbo HD [NPUB30034]

Pages: 1 2 3 4 5

If playing with a keyboard, you can only go to the "press start" screen

It doesn't work anymore with latest official master builds from https://rpcs3.net/download

The problem:

after booting to the game, if a key in keyboard (for example, "W") is pressed at any moment, the game freezes.
If music is playing, it continues, but there's no sign of the game responding to the inputs.

It seems like it freezes the framebuffer (don't know if it's the right term), as doing alt + ENTER to go fullscreen will show a duplicated image of the game. See below:

[Image: attachment.php?aid=11015]

Build tested: rpcs3-v0.0.5-7486-90f81659_win64 (the same problem happened to a build from yesterday, and also from the day before yesterday)

Latest build (I've tested) where the game works: rpcs3-v0.0.5-7189-6c62f42d_win64

RPCS3 Settings: (don't know if it's needed, as it might be in the log file)
-Renderer: OpenGL and Vulkan (DX12 isn't recommended (it crashes, anyway));
-Default Resolution: 1280x720, 100% scale;
-Loaded liblv2.sprx only;
-Framelimit: 60
-PPU Decoder: LLVM
-SPU Decoder: ASMJIT

Whenever I copy the files from rpcs3-v0.0.5-7189-6c62f42d_win64 to RPCS3 folder, the game works.
Whenever I copy the files from rpcs3-v0.0.5-7486-90f81659_win64 to RPCS3 folder, the problem happens.

(11-07-2018, 11:40 PM)alb3530 Wrote: [ -> ]If playing with a keyboard, you can only go to the "press start" screen

It doesn't work anymore with latest official master builds from https://rpcs3.net/download

I have the same problem.
Just tested rpcs3-v0.0.5-7503-65ca9344_win64, but the same symptom is happening.

After testing several builds, I realized this problem began in rpcs3-v0.0.5-7337-ed7012c9_win64 onwards.

Commit ed7012c9dbefd6b700f72b5b17d5e178ce8bf243 description is:

cellKb/Qt: Improve basic keyboard

(https://github.com/RPCS3/rpcs3/commit/ed...78ce8bf243)

I believe it's something related to Keyboard support in games...

Video showing the issue: (NUMPAD / is pressed between 0:22 and 0:23, triggering the freeze)

Is the game now unplayable can anyone confirm?

(11-07-2018, 11:40 PM)alb3530 Wrote: [ -> ]If playing with a keyboard, you can only go to the "press start" screen

It doesn't work anymore with latest official master builds from https://rpcs3.net/download

The problem:

after booting to the game, if a key in keyboard (for example, "W") is pressed at any moment, the game freezes.
If music is playing, it continues, but there's no sign of the game responding to the inputs.

It seems like it freezes the framebuffer (don't know if it's the right term), as doing alt + ENTER to go fullscreen will show a duplicated image of the game. See below:

Build tested: rpcs3-v0.0.5-7486-90f81659_win64 (the same problem happened to a build from yesterday, and also from the day before yesterday)

Latest build (I've tested) where the game works: rpcs3-v0.0.5-7189-6c62f42d_win64

RPCS3 Settings: (don't know if it's needed, as it might be in the log file)
-Renderer: OpenGL and Vulkan (DX12 isn't recommended (it crashes, anyway));
-Default Resolution: 1280x720, 100% scale;
-Loaded liblv2.sprx only;
-Framelimit: 60
-PPU Decoder: LLVM
-SPU Decoder: ASMJIT

Whenever I copy the files from rpcs3-v0.0.5-7189-6c62f42d_win64 to RPCS3 folder, the game works.
Whenever I copy the files from rpcs3-v0.0.5-7486-90f81659_win64 to RPCS3 folder, the problem happens.

Hold on in your log it says you put mouse handler basic and keyboard handler basic. Set them to null and try again.

(11-26-2018, 11:13 AM)digitaldude Wrote: [ -> ]Is the game now unplayable can anyone confirm?
...

...
Hold on in your log it says you put mouse handler basic and keyboard handler basic. Set them to null and try again.

The game is playable with a joystick (tested with XBOX360 controller, xinput), but not with a keyboard.

Note:

I've tested another game (After Burner Climax), and keyboard doesn't freeze that game.

Regarding your suggestion, I had already tried setting keyboard to null, and pad type to keyboard but by doing so, pressing keyboard keys do nothing: it doesn't freeze the game, but keyboard inputs aren't recognized either.

(11-26-2018, 05:53 PM)alb3530 Wrote: [ -> ]
(11-26-2018, 11:13 AM)digitaldude Wrote: [ -> ]Is the game now unplayable can anyone confirm?
...

...
Hold on in your log it says you put mouse handler basic and keyboard handler basic. Set them to null and try again.

The game is playable with a joystick (tested with XBOX360 controller, xinput), but not with a keyboard.

Note:

I've tested another game (After Burner Climax), and keyboard doesn't freeze that game.

Regarding your suggestion, I had already tried setting keyboard to null, and pad type to keyboard but by doing so, pressing keyboard keys do nothing: it doesn't freeze the game, but keyboard inputs aren't recognized either.

Look at my screenshot im playing the game with keyboard...you did something wrong with settings copy the settings in the log.

(11-26-2018, 07:37 PM)digitaldude Wrote: [ -> ]Look at my screenshot im playing the game with keyboard...you did something wrong with settings copy the settings in the log.

You are right: the problem happened because when I set Keyboard handler to null, I had inadvertedly changed Gamepads Settings back to default map.

As I normally map Start to NUMPAD /, I was pressing that key to test (which was doing nothing).

Now everything is fine.

For anyone having problems, this is what need to be set in order to avoid freezing when playing the game with a keyboard from rpcs3-v0.0.5-7337-ed7012c9_win64 onwards:

[Image: 96ez6b.jpg]

Looking at your screenshot, may I ask you why are you using OpenGL instead of Vulkan?

I was testing games in opengl and didnt change settings thats all. I usually use vulkan.

Hi guys I am totally new to emoulation stuff
I just noticed that I got artifacts (vertical tearing lines) on charachter portraits during charachter select screen.
I have looked in youtube videos and none of other users have experienced this problem
What might be the cause of this?
maybe I have got some other problems that I am not aware of. Because my log lines in the emulator fills with red lines (errors I think)[attachment=14274]

rpcs 0.0.6 - 8091 Alpha

Core:
PPU: LLVM (fastest)
SPU: Recompiler (ASMJIT)

Graphics:
Render: Vulkan
Resolution: 1920x1080
Frame Limit: Auto
VSync enabled

Audio:
XAudio2

(05-12-2019, 12:31 PM)taucommander27 Wrote: [ -> ]Hi guys I am totally new to emoulation stuff
I just noticed that I got artifacts (vertical tearing lines) on charachter portraits during charachter select screen.
I have looked in youtube videos and none of other users have experienced this problem
What might be the cause of this?
maybe I have got some other problems that I am not aware of. Because my log lines in the emulator fills with red lines (errors I think)

rpcs 0.0.6 - 8091 Alpha

Core:
PPU: LLVM (fastest)
SPU: Recompiler (ASMJIT)

Graphics:
Render: Vulkan
Resolution: 1920x1080
Frame Limit: Auto
VSync enabled

Audio:
XAudio2

You can try updating your NVIDIA drivers....

I get SEGMENTATION FAULT here in every game ONLY with Vulkan renderer on both this and rpcs3-v0.0.6-8105-3753d27a_win64 builds.
UPDATE: It was caused by "vulkan_1.dll" that was in the same folder as RPCS3 (It was either from an older RPCS3 build, or copied manually by me). After removing every dll and exe and copying RPCS3 contents back to the folder, Vulkan worked here.

But I'm not on Windows 8.1 like you. I'm on Windows 10 1903 18362.86.

rpcs 0.0.6 - 8000 works, though there's frameskipping here with both GSYNC on or off (likely Vulkan-related, as OpenGL didn't present this problem).
UPDATE: Fixed. Details in this topic

In OpenGL, rpcs 0.0.6 - 8000 and rpcs3-v0.0.6-8105-3753d27a_win64 builds freeze at character selection screen: no sound, only a black screen with a 15 (character selection countdown) .

Code:
·F 0:00:41.072523 {RSX [0x02dd90c]} RSX: struct gsl::fail_fast thrown: GSL: Precondition failure at c:\projects\rpcs3\3rdparty\gsl\include\gsl\span: 621

·W 0:00:41.074386 {cellAudio Thread} cellAudio: Audio backend stopped unexpectedly, likely due to a buffer underrun

·! 0:00:41.114419 {rsx::thread} Thread time: 20.343750s (72.482122Gc); Faults: 209 [rsx:209, spu:0];

·! 0:00:41.127779 {RSX Decompiler Thread} Thread time: 0.031250s (0.994616Gc); Faults: 0 [rsx:0, spu:0];

·! 0:00:41.129891 {VBlank Thread} Thread time: 0.000000s (0.161100Gc); Faults: 0 [rsx:0, spu:0];

·! 0:00:44.784952 Stopping emulator...

I'm not even concerned about OpenGL, as there were a problem where its performance got degradated over time (FPS became slower until it reaches sub 60 FPS), so I'm trying to find what happens here that I'm getting constant frameskipping with Vulkan renderer on capable hardware.

I don't have the problem you're describing.
I have vsync off here though.

Pages: 1 2 3 4 5