Issues

• broken graphics on various locations

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

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

From @BenNottelling on March 21, 2017 5:18

Looking like windows 7 is the best OS for this emulator

From @furrya on March 22, 2017 0:23

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

From @furrya on March 25, 2017 1:15

With the latest commits - Win 10 x64

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

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

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

@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 : Cxbx-Reloaded/Cxbx-Reloaded@2a8cc37 )- this IS the one you're referring to, isn't it?

@furrya This flickering is also present in other software, specifically the Dashboard, JSRF and other titles - see Cxbx-Reloaded/Cxbx-Reloaded#91 (comment)

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

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.

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.

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

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

From @bhodg22 on April 18, 2017 22:53

Strange, my JSRF runs fine on that same commit

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

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

From @jarupxx on April 19, 2017 12:5

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

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.

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.

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.

• Re-test 22/04/2017: Thank you, Luke for that PR #389 (Fix HLE Cache) which included an option to clear HLE cache. That should become useful when testing various games to ensure that a previous bootup doesn't in any way affect sequential ones if one doesn't want that to happen.
  Of course, this game has returned to 'normalcy' in buggy terms.

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?

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

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.

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

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

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...

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

This should now render a lot better!

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!

KrnlDebug_(2017-04-30_Index-Buffer_Crash).txt

• Re-test: After using Luke's PR #410 (Revert of some AV query capabilities) I can now get in-game. Though the game would crash before entering the start menu a few times. So you have to clear the HLE cache before trying again, which will test your patience.
  But I now see that my character's head in the intro cutscene is corrupted again.

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).

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.

Ingame still but this new video from JGG seems to suggest that the 'white-out' problem with the in-game GFX has been stopped but that the framerate has grinded almost to a halt.

Edit: Ah ha, that's right. Luke has a new PR#956 where in one of the commits he says that this game no longer has THAT same 'white-outs' problem.

• Cxbx-Reloaded Xbox Emulator - Jet Set Radio Future Ingame! (fb5436e4) (John GodGames Emus. Published on 1 Mar 2018.)

But this video from another tester shows it to be running just fine.

• Cxbx Reloaded Mar 1 2018 - Jet Set Radio Future 60FPS (bhodg22. Published on 1 Mar 2018. Doesn't mention the build used.)

EDIT (04/03/2018): See this game in glorious ultra-widescreen format courtesy of Esppiral V!

• Jet Set Radio Future CXBX -R 21:9 (Esppiral V. Published on Mar 1, 2018.)

In this new video from Literalmente, see the garbage splash visuals popping up on-screen at a couple moments (i.e. when the skater reaches some of the round-shaped marks) in the tutorial stage after 3:58 and 4:46 (While just simply running). There are some missing graphics on a couple key characters & background props in a music room in the intro cutscene after the tutorial level. Otherwise, it almost all looks fine.

• Emulação - Jet Set Radio Future in-game no CxBx-Reloaded (emulador de XBox) (Literalmente{Game}. Published on Mar 3, 2018. Build used: fb5436e; PR#957.)

A nother crash found it. I can´t bypass this.
The older versions before 1 March was working good.
Thank you all!

When does the crash occur exactly?

@CakeLancelot After we defeat Hayashi the in the stadium.
When he speaks 'What was i'm thinking...?' the error appears.
https://www.youtube.com/watch?v=udBHidVrDSw
Go to 3:25.
And i can´t finish this level.

Can you please zip and upload your savedata so we can easily reproduce & investigate:

Go to %AppData%/Cxbx-Reloaded/Partition1/UDATA/<TITLE_ID>

Where Title ID is the title Id for your version of JSRF, you can find it in the Xbe dump.

After trying to play, All I can say is that it is currently in a playable state.. Other games as well are getting into the stages of playable this year, And It amazed me enough to try CXBX after my attempts on doing that a couple months ago when It wasn't stable enough to run on my computer.

y'know? 120 FPS feels like 60. But unfortunately, on my side. most of the ground textures are not working, But the game is still very playable. Unlike the original hardware or 360.

But mind you, Theres a few sounds that are not working, like voicelines, Spray Sounds. ETC. And i Recommend you turn your sound off for times like that. Once that is fixed, Ill be one happy person over here.

And from what the user Hyper Scorpio has said, The game stops after we beat hayashi again. And I hope this is fixed in the next update. That along with the SFX errors, Or pops.

Tested again and still crashes, i got something before i defeat Hayashi. DJ Professor K when he speaks the last ballon message just changed to french language. I will send 2 saves. The first one is all levels untill there with all Graffiti Souls completed and collected. The 2nd save is before i fight against Hayashi.
Please if you guys can fix it to able to continue to play.
Thank you all!

Update: Even after cleaning All CXBX Data it doesn´t work, but before was working.

I just forget to post the french bug letters.

Hi here, it's great to see the work accomplished ! Now my game runs perfectly fine talking to FPS...
The last bug I've seen comes when I paint graffitis... They don't appear:
Tried almost everything.

My specs:
Intel i5-7300HQ @2.5-3.5GHz
NVidia GTX 1050 @4GB GDDR5
8GB DDR4-2400 RAM
Jet Set Radio Future PAL
Cxbx-Reloaded build b8c5808a

@HauruI they removed for a reason, need to be fixed.

JSRF PAL used to be able to go ingame for me, but it regressed to instantly crashing a couple of months ago. I still keep the build from Nov 27, 2017 around because it's able to start both JSRF and Panzer Dragoon Orta.

I'm running an I7, GTX 1080 and Win10 64 bit

Here are the log dumps:

@SputnikKaputtnik no difference anymore to the older version.

@HyperScorpio What do you mean no difference? I ran both versions today. The older one will start the game, the new one will crash instantly.

@SputnikKaputtnik Strange. i always remove the %AppData% CXBX Reloaded and the Folder on the regedit.

@HyperScorpio Deleting the roaming/appdata/cxbx folder did the trick. Thank you for pushing me in the right direction!

I Tested the game again, i clean all files including the configuration, i just start and play and i got the crash again. Total 2h10 min. We can use 2 free tools, one is Registry Scanner to delete all files belongs as CXBX and File Searchy to remove all the CXBX Database. It seems is not problem from the save game after all.
Waiting for next month. Bye.

Regarding the Hayashi bug, the first bad commit appears to be 179c158. As the commit was mainly pertaining to HLEDB_V2, I've uploaded two HLEcaches in a zip file. BAD is the one generated by build 179c158 and doesn't work, while GOOD is the build right before it (e252cdf) that does work.

By tweaking my HLEcache ini file on the latest build I've confirmed that this is related to it, but I haven't found out which specific function yet.
(Noise Tanks after beating Hayashi boss battle)

Summarizing the differences between the BAD (Cxbx-Reloaded/Cxbx-Reloaded@179c158) and GOOD (Cxbx-Reloaded/Cxbx-Reloaded@e252cdf) HLECache files attached above by @CakeLancelot :

D3DCubeTexture_LockRect isn't patched, so it's address equaling Lock2DSurface causes no problems.
Same for D3DVolumeTexture_LockBox and Lock3DSurface.
D3DDevice_CreateImageSurface and D3D_CreateStandAloneSurface both aren't patched, so it's also unlikely that these cause trouble.
So, it might have something to do with D3DDevice_GetTexture2 not being found anymore, because that one is patched...

For reference, @CakeLancelot generated Jet_Set_Radio_Future-8f0bb158.zip an unmodified HLEcache from the latest build (Cxbx-Reloaded/Cxbx-Reloaded@61fc3c5)
In it, D3DDevice_CreateImageSurface is restored to 18d710 and D3DVolumeTexture_LockBox to 18f120 (all other differences between GOOD and this are sound-related).

The hard crash after Hayashi has been solved as of this PR Cxbx-Reloaded/Cxbx-Reloaded#1000

Turns out that the cause was simply a patch that we neglected to remove after fixing D3DDevice_SetTexture to correctly update the internal state.

To further what @ObiKKa was mentioned earlier, I was able to get 60FPS easily from build in early March however after some recent commits, the game basically chuggs down to a 1-5 fps. When the game is not in focus the FPS returns to normal, but no sound plays.

I have uploaded another video which demonstrates this (For some reason audio still does not record). https://youtu.be/093Lyz8kRFc
I can grab logs if required

Edit: CPU is also pretty much pinned on all 4 cores, AND the same slowdown/speedup is also happening in Crash tWoC when loading in to main menu

Thank you guys! Tired of Guinea Pigs. Soon or later will be forced to use the latest DX because happens the same to demul, it have DX11 because of the bugs and crashes. I know is not the same thing soon you will understand it why.

The only problem I have is the sounds having that loud pop every time. Like selecting something, grabbing a graffiti soul. And spraying paint. I still don’t know if you could fix that.

Another problem is frame dipping on the intro, Missing textures on my side.

This issue got out of hand (more than 100 comments!) so I've created a more up to date issue here. Please only post issues about the game there with detailed explanations. All other discussion can be in the Discord or Gitter channel. Thank you.