Bayonetta [NPEB01134]

Did you test with current / Zangetsu's build? Zangetsu's may be for naruto but it should fix other games too idk

Zangetsu's builds are full of horrible hacks.
Look at it like this:
You have a man with only one leg. He can't run properly.
Now you cut off his second leg and over time his hands get strong enough to move quicker than with that one leg. Except he's bleeding a lot by using that method.

It doesn't "fix" anything, but it's rather like this:
Game: "Holy fuck, some thing went to absolute shit! Jump the fucking ship, we're going to crash!"
Emulator: "Okey dokey, as you wish."
Emulator with hacks: "Ahhh, let me give you some morphine, you'll be fine."

It also has been clarified in recent guideline update, that progress on such builds should not be posted as "status updates" or changes for the game status on the forums. Only very minor hacks are now allowed.

Please only use official builds such as Bigpet's builds (we currently accidentally broke them, but should get fixed soon) or the ones from AppVeyor artifacts.

Did you test with current / Zangetsu's build? Zangetsu's may be for naruto but it should fix other games too idk

Zangetsu's builds are full of horrible hacks.
Look at it like this:
You have a man with only one leg. He can't run properly.
Now you cut off his second leg and over time his hands get strong enough to move quicker than with that one leg. Except he's bleeding a lot by using that method.

It doesn't "fix" anything, but it's rather like this:
Game: "Holy fuck, some thing went to absolute shit! Jump the fucking ship, we're going to crash!"
Emulator: "Okey dokey, as you wish."
Emulator with hacks: "Ahhh, let me give you some morphine, you'll be fine."

It also has been clarified in recent guideline update, that progress on such builds should not be posted as "status updates" or changes for the game status on the forums. Only very minor hacks are now allowed.

Please only use official builds such as Bigpet's builds (we currently accidentally broke them, but should get fixed soon) or the ones from AppVeyor artifacts.

But then the man gets robotic legs and can run again ( if you know what i mean)
Well atleast with his hacks and vij's fixes naruto runs almost perfectly, Soul Calibur 4 too, god of war hd collection should too with it, but the fps is horrible, well what do you expect :/ maybe once vulkan comes out it will increase like 5-10 fps

Did you test with current / Zangetsu's build? Zangetsu's may be for naruto but it should fix other games too idk

Zangetsu's builds are full of horrible hacks.
Look at it like this:
You have a man with only one leg. He can't run properly.
Now you cut off his second leg and over time his hands get strong enough to move quicker than with that one leg. Except he's bleeding a lot by using that method.

It doesn't "fix" anything, but it's rather like this:
Game: "Holy fuck, some thing went to absolute shit! Jump the fucking ship, we're going to crash!"
Emulator: "Okey dokey, as you wish."
Emulator with hacks: "Ahhh, let me give you some morphine, you'll be fine."

It also has been clarified in recent guideline update, that progress on such builds should not be posted as "status updates" or changes for the game status on the forums. Only very minor hacks are now allowed.

Please only use official builds such as Bigpet's builds (we currently accidentally broke them, but should get fixed soon) or the ones from AppVeyor artifacts.

But then the man gets robotic legs and can run again ( if you know what i mean)
Well atleast with his hacks and vij's fixes naruto runs almost perfectly, Soul Calibur 4 too, god of war hd collection should too with it, but the fps is horrible, well what do you expect :/ maybe once vulkan comes out it will increase like 5-10 fps

But the thing is, you shouldn't be cutting the other leg, and then developing robotic legs for both legs, but instead you should develop a robotic leg for the leg that's missing in the first place.

Just the basic gist of my argument is: we don't want to become PCSX2 of PS3 emulation.

Some strange hacks may make a game or two run but it will make many other fail in very unexpected ways, which is hard to debug. For instance instead of crashing when a game uses some unimplemented method you could just return some hard coded (incorrect) data which may work for some games but it is now completely impossible to fix any other issues because everything is running in an undefined state. In short, it's a mess.

Please not that hacks may decrease performance in some case. They're hack, ie they make games working without explanation and in some case they can make a thread spin instead of being properly disposed.
Plus some hacks are very aggressive, in Naruto it disables trap instructions. A trap instruction should never be executed in the first place so there is something wrong happening at startup.

Just tested bayonetta on Zangetsu38's latest build, game works fine until the "press start" screen, it freezes and the fps too and the log keeps spamming:
" [PPU Thread(0x8b] (CriSr_ProcessServer)[0x01025b1c]} cellSync: cellSyncMutexTryLock() ->CELL_SYNC_ERROR_BUSY (0x8041010a) "
edit: after stopping the emulation it shows up
"(rsx:thread} Exception: Working buffer not big enough
(in file g:\git\rpcs3 d3d12\rpcs3\emu\rsx\d3d12\D3D12MemoryHelpers.h:73, in function data_heap::alloc} "

Just tested bayonetta on Zangetsu38's latest build, game works fine until the "press start" screen, it freezes and the fps too and the log keeps spamming:
" [PPU Thread(0x8b] (CriSr_ProcessServer)[0x01025b1c]} cellSync: cellSyncMutexTryLock() ->CELL_SYNC_ERROR_BUSY (0x8041010a) "
edit: after stopping the emulation it shows up
"(rsx:thread} Exception: Working buffer not big enough
(in file g:\git\rpcs3 d3d12\rpcs3\emu\rsx\d3d12\D3D12MemoryHelpers.h:73, in function data_heap::alloc} "

Please see guidelines and only post updates with the master branch.

Just tested bayonetta on Zangetsu38's latest build, game works fine until the "press start" screen, it freezes and the fps too and the log keeps spamming:
" [PPU Thread(0x8b] (CriSr_ProcessServer)[0x01025b1c]} cellSync: cellSyncMutexTryLock() ->CELL_SYNC_ERROR_BUSY (0x8041010a) "
edit: after stopping the emulation it shows up
"(rsx:thread} Exception: Working buffer not big enough
(in file g:\git\rpcs3 d3d12\rpcs3\emu\rsx\d3d12\D3D12MemoryHelpers.h:73, in function data_heap::alloc} "

Please see guidelines and only post updates with the master branch.

same stuff happening with latest master branch, game freezes upon going into the press start screen

how do you know which lle module you should use ?

how do you know which lle module you should use ?

You look at what modules the game uses from the log, that or trial and error. Also not all modules can be LLE'd.