search

Cxbx-Reloaded / game-compatibility

Cxbx-Reloaded game compatibilty list, using GitHub issues
GNU General Public License v2.0
115 stars 29 forks source link

Jet Set Radio Future [PAL] [IG-024] [1.01] #178

Closed PatrickvL closed 6 years ago

PatrickvL commented 7 years ago

>> See updated issue HERE <<

Issues

From @furrya on March 21, 2017 0:58

I just have launched the game on windows 7 x 64 , and I can see normal graphic on some locations , but on others it's broken screenshot_7 screenshot_9 screenshot_11

Copied from original issue: Cxbx-Reloaded/Cxbx-Reloaded#251

PatrickvL commented 7 years ago

From @BenNottelling on March 21, 2017 5:18

Looking like windows 7 is the best OS for this emulator

PatrickvL commented 7 years ago

From @furrya on March 22, 2017 0:23

With the latest commit, the graphics now is same on Windows 7 and on Windows 10 screenshot_4 screenshot_5 screenshot_7

PatrickvL commented 7 years ago

From @furrya on March 25, 2017 1:15

With the latest commits - Win 10 x64 screenshot_1

PatrickvL commented 7 years ago

From @bhodg22 on March 25, 2017 11:56

Does the rest of the level stay normal for you? I find it sometimes flickers to shades of black at times, also what GPU are you using

PatrickvL commented 7 years ago

From @furrya on March 25, 2017 12:20

@bhodg22 Same behaviour on my Palit Geforce 610, Regardless of the OS ( Win 7 x64, Win 10 x64) . Flickers appears many times on the start and ingame also

PatrickvL commented 7 years ago

From @bhodg22 on March 30, 2017 9:4

With the latest commit, I managed to get past the first cut scene and back into the garage, and the game was actually running full speed but then crashed when I tried going to the next level

PatrickvL commented 7 years ago

@bhodg22 : When reporting something like this, please mention exactly which commit you're referring to, by copy-pasting the URL for it, like this : https://github.com/Cxbx-Reloaded/Cxbx-Reloaded/commit/2a8cc3722ba1eea8fe61c035149cd923f9ffe0a0 (which GitHub renders like this : https://github.com/Cxbx-Reloaded/Cxbx-Reloaded/commit/2a8cc3722ba1eea8fe61c035149cd923f9ffe0a0 )- this IS the one you're referring to, isn't it?

PatrickvL commented 7 years ago

@furrya This flickering is also present in other software, specifically the Dashboard, JSRF and other titles - see https://github.com/Cxbx-Reloaded/Cxbx-Reloaded/issues/91#issuecomment-280917520

PatrickvL commented 7 years ago

From @bhodg22 on March 30, 2017 9:52

yeah thats the one i was referring to, I didnt bother posting any details because I tried to recreate it a second time but it didnt quite make it to the end of the cutscene, might try a third time soon

PatrickvL commented 7 years ago

From @LukeUsher on March 30, 2017 9:56

I've been able to play up to the point of the tutorial where you do the 'boost dash'. I usually get a crash at that point, but it seems to be caused by my graphics drivers.

PatrickvL commented 7 years ago

From @ObiKKa on April 18, 2017 17:43

Urgent disaster! Needs remedying! After PR #375 (Overlay conversion) & #376 (Integrated copy OOVPAs. Most likely problem.) game crashes after company intros shown.

2017-apr-19 _crash-after-intros KrnlDebug_(2017-04-19_Crash-after-intros).txt

PatrickvL commented 7 years ago

If the function locations differ, that's probably the main cause of regressing. Video issues shouldn't give such hard crashes

PatrickvL commented 7 years ago

From @bhodg22 on April 18, 2017 22:53

Strange, my JSRF runs fine on that same commit

PatrickvL commented 7 years ago

Then maybe you're running another version of the same game

PatrickvL commented 7 years ago

From @bhodg22 on April 18, 2017 23:9

Might be similar to the futurama issues, where other people can boot the PAL version as I still cannot

PatrickvL commented 7 years ago

From @jarupxx on April 19, 2017 12:5

@ObiKKa compare PR #374 log & #376, we will find the cause of the regression

PatrickvL commented 7 years ago

From @LukeUsher on April 19, 2017 12:19

JSRF also still works for me. How many times did you try? JSRF only boots successfully 8/10 times for me, the other times I get a similar error you see above.

PatrickvL commented 7 years ago

From @ObiKKa on April 19, 2017 15:46

@LukeUsher & @jarupxx, that's strange. today I restarted the merged master of PR 374 (b525828e6959bd2f57b260e784b77391cb8c3024) coz I already downloaded it before. Still worked. Then I booted up the merged master of PR 376 (77933ad8ebf261634cfc2bde978f4fb8cc14d689), the old download - could be before you made that 2nd commit after I read the page ( OOVPA integration D3D 5849 to 3925). But never mind that, in that build I ran JSRF (US region) again and it got to the menu and in-game again.

To Luke, I only ran JSRF twice on that last build (PR 376) a day before as I was testing other games. Seems strange that some games do fail to run forward to the same progress line for inexplicable reasons sometimes. But, yeah, all seems to be fine. I'll test the newest build again, although that's unlikely to change my experience in Innocent Tears, etc.

PatrickvL commented 7 years ago

From @ObiKKa on April 20, 2017 23:2

Oh, after about 4 crashes (That's a lot. Luke says his own test crashes on avg 2x every 10 tries.) I was able to see the main menu screen. But lots of blackness in the background and occasionally switching to yellow/white visuals. Then in-game, first cutscene looks similar like before. But in-game was horrible. It appears that PR #384 (Implement HLE cache) may have mucked up the visuals for me. I think it may remember the first or so crash and then made the visuals worse on later boots. It's been much black over everything in the world for half of the viewing angles. Also when it's finally back to yellow and white polygons (corrupt vertex shaders ATM) I saw one gray shader on a platform was flickering.

collage-2017-04-21

But after that PR #390 (DXBX improvements, etc?) the character model hasn't changed at all. Also none of us the testers are the wiser as to why this game slows down after starting to get into the game. Is it the memory leaks?

PatrickvL commented 7 years ago

I suspect the graphics are damaged because the HLE cache might be skipping the detection of render state and texture state addresses

PatrickvL commented 7 years ago

From @LukeUsher on April 21, 2017 4:42

Sorry about that, i overlooked that part of HLE patching. Should be an easy fix, I'll hopefully get that done before Monday.

PatrickvL commented 7 years ago

From @furrya on April 22, 2017 2:39

For me the state of the emulation gets better than in previous builds The game looks better , it's looks like c1e4d973 now

screenshot_1 screenshot_2 1 st screen 18 Apr Build and second Cxbx-Reloaded Version 1a9b20ad (Apr 21 2017)

PatrickvL commented 7 years ago

From @ObiKKa on April 23, 2017 23:1

The main character model in the intro game cutscene seems to be fully rendered a bit better after PR #392 (Removed CreatePalette) and #393 (Temporarily disabled vertex buffer cache). And I could see some vehicles in the background in the main menu. But yeah loading the game takes a way long time and game runs slower as a result. This game is easier said than done to fix up...

collage-2017-04-24

PatrickvL commented 7 years ago

From @bhodg22 on April 24, 2017 0:36

I also have the very slow loading and also the main menu is very slow, graphics on characters has improved alot and ingame is a bit slower, however my speedup trick still works to get the game running fullspeed

PatrickvL commented 7 years ago

This should now render a lot better!

PatrickvL commented 7 years ago

From @ObiKKa on April 29, 2017 22:9

No. After PR #406, it has crashed many times for me. I also re-cleared the HLE cache a few times later on as well. Now the emulation seems to be so accurate that anything a game requires is missing then it becomes so brutal to said emulation!

2017-apr-30 _index-buffer_crash_01 KrnlDebug_(2017-04-30_Index-Buffer_Crash).txt

PatrickvL commented 7 years ago

You're getting the same results as me, while Luke is getting increasingly better results. I suspect it's related to the version we're running (NTSC/PAL , older/newer builds of the game, or whatever).

PatrickvL commented 7 years ago

From @blueshogun96 on April 29, 2017 22:21

This is the exact same crash that I would get with the old Cxbx. Something has definitely regressed. It's the same with both PAL and NTSC, so it's not just him.

Several other titles (most notably SEGA titles) are regressing right now, and I'll make a note of each one.

Shogun.

PatrickvL commented 7 years ago

From @LukeUsher on April 29, 2017 22:23

Interestingly JSRF still works on my machine, in fact it's what I perform most of my testing with: I know how prone to regressions it is. Perhaps there's something different between my master and this one.

PatrickvL commented 7 years ago

From @blueshogun96 on April 29, 2017 22:25

Sadly, I'd have to assume that also. It also reminds me of how Outrun2 appears to work for everyone else... except me! I'll be sure to keep you updated.

Shogun.

PatrickvL commented 7 years ago

From @LukeUsher on April 29, 2017 22:36

Should be fixed now, my new implementation of AvQueryAvCapabilities was the problem.

PatrickvL commented 7 years ago

That was quick Luke - thanks!

PatrickvL commented 7 years ago

@blueshogun96 Have you considered submitting pull requests? Bug reports are nice and all, but better code, yeah, shiver me timbers, that's what we really want! ;)

PatrickvL commented 7 years ago

From @blueshogun96 on April 29, 2017 22:47

@PatrickvL I have, but unfortunately I haven't had my own fix for such things. Some of these errors are beyond me, especially for me being out of the loop so long. :(

Shogun.

PatrickvL commented 7 years ago

From @CakeLancelot on April 30, 2017 7:26

In build 394aee6b the game is much more stable and I'm able to make it through the first cutscene, though the graphics are about the same compared to the last few builds. Seems a bit faster too but that may just be me. Excellent progress guys! cxbx_2017-04-30_02-20-22 cxbx_2017-04-30_02-23-05

PatrickvL commented 7 years ago

From @LukeUsher on April 30, 2017 7:46

In my recent testing, I managed to get past the cutscene and into gameplay properly, I played up until meeting Beat. One thing that was a little strange: after the intro finished, the music and sound became perfect.

PatrickvL commented 7 years ago

From @CakeLancelot on April 30, 2017 8:38

In my recent testing, I managed to get past the cutscene and into gameplay properly, I played up until meeting Beat. One thing that was a little strange: after the intro finished, the music and sound became perfect.

I haven't played past dogenzaka hill, but during the time on that level the audio was still broken for me.

On top of that as mentioned before that some of the particles and effects start working after using graffiti however this will revert when you enter the next 'scene' (includes the jumpcuts in cutscenes while loading in assets or whatever it's doing).

Also encountered this weirdness when spraypainting a wall: cxbx_2017-04-30_02-37-32 Then again as #271 shows there are differences in accuracy depending on graphics hardware, perhaps drivers even.

Let me know if you need any other info, my specifications are listed in #271.

PatrickvL commented 7 years ago

From @ObiKKa on May 2, 2017 16:40

Unfortunately I'm not able to continue in the Start menu for a while after all these little and big PRs. One same error message shows up before loading those intro splash screens (Press Ignore to resume) and repeatedly after a brief period of time in the Start menu (I cannot see the menu buttons at this time). I think it might be worth it to tackle that 'XInputPoll' problem.

Also congratulations to @blueshogun96 for his work on getting those Panzer Dragoon game(s) up and running! :) Hopefully a fourth regular programmer on this team? Dream on!

2017-may-03 _error-box_01

Now, to the other two games - Namco Museum and Battlestar Galactica: No, those new error messages still pop up at the same time so they are not solved yet.

Created with photocollage.com: collage-2017-05-03

PatrickvL commented 7 years ago

I've seen almost the same error for a while, until I fixed a bug in D3DSurface_LockRect; it didn't account for textures, instead of surfaces being passed in

PatrickvL commented 7 years ago

Regarding the glitches linking some elements together: this might be caused by the same issue that seems to have broken Turok (right after starting a game), probably an index buffer change. @LukeUsher Could it be that our index buffers are not correctly aligned?

PatrickvL commented 7 years ago

From @bhodg22 on May 13, 2017 3:4

Was meant to post this earlier, I managed to get to the beat mission in a build from about 2 months ago and the sound was also became perfect back then as well. As for one of the latest builds (Maybe from about 10 days ago?) Alot of the ingame elements have become invisible for me (buildings, the ground, rails, etc) making it impossible for me to progress further in the games as i cant see the levels!

PatrickvL commented 7 years ago

From @CakeLancelot on May 13, 2017 7:3

As of 2d720a1 the shading on the characters has improved, though many previous graphical issues are still present. cxbx_2017-05-13_01-59-10 vs 394aee6 cxbx_2017-04-30_02-20-22

PatrickvL commented 7 years ago

Which one is the better one? Do you have some reference material perhaps?

austinhanna commented 7 years ago
chrome_2017-08-23_02-02-40

Not the exact scene but the first one seems the most similar.

Logitech-byte commented 7 years ago

I can confirm a nother crash everytime we enter a new map location or visit the garage for 8 times. The loading stops and appears black screen with the error message to press ok or debug. The reason i'm saving the game many times to bypass the story. All that it counts in to the missions scene's we watch.

austinhanna commented 7 years ago

https://www.youtube.com/watch?v=6K3ECkhgO64 Take a look at this! Very interesting indeed,

Logitech-byte commented 7 years ago

@AustinHnn That thing happens to me as well. And the funny thing you have a Ryzen CPU and appears Black in the map, and i have a Intel CPU and all appears white. 😆 And that part when the graphics are fixed i can see the map perfectly, when you go back it shows white. 😆 Is the only part of the code is fixed?

CakeLancelot commented 7 years ago

@HyperScorpio @AustinHnn Please try to keep conversation to the gitter.im channel or the discord server, these issues have more or less already been reported. I will create a new issue to centralize everything related to JSRF soon, just need to make comparison images/videos.

Logitech-byte commented 7 years ago

@CakeLancelot Send us the links please. 👍

PatrickvL commented 7 years ago

@HyperScorpio Read the readme. It exists exactly for these type of questions.