Xemu hangs on load and crashes before menu

[Sirchacha2]

Batocera build version

39 2024/03/04 10:11

Your architecture

SER5, Ryzen 5560U

Your Graphic Processor Unit(s) (GPU)

iGPU

Issue description

When trying to load any xbox game it will get through splash screens but before hitting the main menu it will flash 2-3 times, audio cuts out and after about 5-10 seconds it bounces me back to ES.

Detailed reproduction steps

Load any Xemu .XISO in ES

Details of any attempts to fix this yourself

38 loads them fine in same machine, 39 install and 38 were both fresh, also happens when updating from 38 to 39.

Details of any modifications you have made to Batocera.

On my SER5 Pro (5800h) I have some but the test system with the Ryzen 5560U is fresh and only added bios and halo 2.

Logs and data

amd.log es_launch_stdout.log es_launch_stderr.log batocera.log

[direngrey31]

v40 builds after today will have the fix. Or you can try my test builds here...

https://drive.google.com/drive/folders/1_bqmR7CoZ78i7DolYt5b-RRqB5c-LPyN?usp=drive_link

@dmanlfc Hi , very good job 🙂. Great , AMD Radeon RX550 batocera dev40 ok 👌

[paronowitz]

@dmanlfc 5500U update works... Running a backup now but will play more to see if I encounter any other issues. Thanks! Looking forward to being able to use some of the controller refinements in the last 2 releases!

[paronowitz]

Ive tested 1 of every system I typically play.. Everything worked well. Only libretro: yabasanshiro works on Saturn with zip files. The other cores say unsupported file type. I havent investigated further but yabasanshiro seems to work well either way. Atari 5200 the games run at awkward speeds but I havent played a 5200 game in a while so it may have been that way for a bit. Tried berzerk (ran slow) and pacman (ran really fast). The only thing I havent tried yet is my sinden gun

[nhalh]

Clean installed the current dev build with Mesa 24.0.4, though I seem to be still running into the same issue with Xemu specifically. I've attempted to run different games, settings, and resolutions, to no avail. Seems to only work on v38.

Would truly appreciate any support troubleshooting this.

es_launch_stderr.log es_launch_stdout.log

[paronowitz]

Use the build posted above in the gdrive link or wait for the next publicly available butterfly release.

[eugene373]

This issue is with the mesa 24.X driver, Now I understand it's not the Batocera Dev. fault! But they do control what goes into their build's, the lack of testing before they put them into the stable build is on Batocera. I personally have reverted back to v38 until the mesa issue is resolved.

[dmanlfc]

The lack of testing?!!! FFS we had v39 go through multiple releases candidates. Did ANYONE bring this to our attention before release? NOOO! We don't have EVERY GPU. It's a FREE open source project of which we spend countless hours on for little rewards.

So if you want to have better releases, get on the Release Candidates. Otherwise keep your snide comments to yourself @eugene373

Rant over.

[eugene373]

The lack of testing?!!! FFS we had v39 go through multiple releases candidates. Did ANYONE bring this to our attention before release? NOOO! We don't have EVERY GPU. It's a FREE open source project of which we spend countless hours on for little rewards.

So if you want to have better releases, get on the Release Candidates. Otherwise keep your snide comments to yourself @eugene373

Rant over.

Not snide sir! There is a dev. branch correct? I build your stuff from source, it's not an issue for me as it is for some. Definitely wasn't trying be snide so I do apologize if it came off that way. Fact is, it's a know issue in the mesa community after they pushed it, I just viewed it as an over sight and it's a simple fix with version control.

[lbrpdx]

But they do control what goes into their build's, the lack of testing before they put them into the stable build is on Batocera. I personally have reverted back to v38 until the mesa issue is resolved.

I don't think you understand how free and open source projects work. How much did you pay to get this tested? Nothing. Have you tested it during the release cycle for v39? No. You probably saw on the comment above that is fixed on v40... but rather than testing on the current dev version and make sure it works for you, you prefer to revert to an old version (v38). This won't help to make sure it is corrected on v40, and you will complain again for the "lack of testing". 🤷‍♂️ This problem happens only on certain GPUs, we do rely on the community to help and test the dev releases.

[eugene373]

Dev. 40 is not fixed on amd 3050e / Ryzen 3 gpu.

[dmanlfc]

Actually 3050e (AYN Loki) is what I used to verify the fix for Xemu.

[eugene373]

Actually 3050e (AYN Loki) is what I used to verify the fix for Xemu.

I'll download it again, it wasn't working a day ago. Thanks for your reply and I'll test it again.

Again, I wasn't trying to be snide & understand how much time goes into testing.

I'll report back soon -sam

-Update: When downloading Dev build 40 there's a checksum error with the online updater.

-Update 1: Did manual upgrade, xemu is working now but found new issues in other emulators using the mesa 24.0.4

[cham2019]

Just wanted to add something here: When I came here to just report (no to complain) about the same issue, it was without even knowing what MESA mean. I'm new with this system (1 month ago just learned about it).
I am not a coder at all, I work in a total different area (accounting) but I also understand some IT stuff that helped me a lot with my personal requirements. I wish I could help with spare time to this project, but I will consider a donation and buying your merch.

That being said, thanks eugene373 for testing and confirm about that mesa driver issue. But also, a HUGE thanks to you guys (Batocera devs) for this AMAZING project. Sometimes it is just the frustration that some users experience, and out of that we start typing something that might sound rude, but it is totally unintentional and not in a way of demanding something (Not saying that you guys have not encountered that kind of situations -I can imagine- but I hope it does not reflect what the majority of users think and feel about this project).

A final note (just to chill out with a funny fact here) every time I read the "troubleshooting" page, phrases like these ones:

• My game is black and white!
• Everything is appearing too small in the file manager!
• My TV isn't respecting that!

I can feel the message here, lol. I see the "!!!" pattern. Yes, sometimes we sound like that, lol, but at least speaking for me, I've never done that, and I will not have that intention to "demand" anything from any opensource project, but instead to report anything that could help to fix bugs or to shape the final product better.

Thanks again guys and good weekend! Cheers

[eugene373]

I'm going back & forth between v38 and Dev. Build 40. being mesa 24.0.4 has brought new bugs to games that was working fine with mesa 23.X

From it being psvita, mame, to xbox or psp. there's an issue going on or slow downs and trying to pin point the cause of things.

At first glance everything seemed to work on problematic games that was int. effected by the mesa 24.x upgrade, but now deeper in depth of games my kids play ( have over 9K games I own ) more things are broken on multi gpu's from my AMD to nVidia cards.

I'll try to do my best to make an active log, but the issue isn't with xemu and maybe create an mesa error tracking from 23.x to 24.x

-Sam

[eugene373]

But they do control what goes into their build's, the lack of testing before they put them into the stable build is on Batocera. I personally have reverted back to v38 until the mesa issue is resolved.

I don't think you understand how free and open source projects work. How much did you pay to get this tested? Nothing. Have you tested it during the release cycle for v39? No. You probably saw on the comment above that is fixed on v40... but rather than testing on the current dev version and make sure it works for you, you prefer to revert to an old version (v38). This won't help to make sure it is corrected on v40, and you will complain again for the "lack of testing". 🤷‍♂️ This problem happens only on certain GPUs, we do rely on the community to help and test the dev releases.

I missed you're reply, but google eugene373 / xda. I rooted more android phone then anyone! I do understand and again wasn't being snide but was truly trying to offer feedback that was progressive.

I DO understand, I do know how it feel's when someone post something that doesn't resonate with you. With that being said, text can be dry and lacking tone as well.

All good Sir! Keep up the great job that myself and my Family loves! -Sam

[eugene373]

The lack of testing?!!! FFS we had v39 go through multiple releases candidates. Did ANYONE bring this to our attention before release? NOOO! We don't have EVERY GPU. It's a FREE open source project of which we spend countless hours on for little rewards.

So if you want to have better releases, get on the Release Candidates. Otherwise keep your snide comments to yourself @eugene373

Rant over.

First things first, is there bug tracker on this issue already? I don't to keep posting here regarding mesa issue's if there's already a topic for it.

So I figured out most the issues by resetting to a fresh install of dev. 40. however there is an issue with psvista emulation on both accounts, meaning the latest psvista emulator and mesa have issues.

example: Mesa 24.x with v39+ vista3k = not playable on game's that played fine, texture / shader issues and lockup Mesa 24.x with vista3k from v38 = texture / shader issues on game's that played fine Mesa 23.x with v39+ vista3k = texture / shader issues on game's that played fine Mesa 23.x with vista3k from v38 = games play perfect.

i.e. conflict with both of the latest versions of vist3k & mesa 24

Vista games tested on Loki Zero: 10 second ninja ( This game is fine for the most part, with a few shader issue's ) 1001 Spikes / texture issue Farming Simulator ( This game is fine for the most part, with a few shader issue's ) Reel Fishing / Full lockup on fishing

There's also a few issues with mesa 24.x on RPCS3 but still trying to figure out what all games are effected.

Testing was done at first was unsquashing the system.sfs and rebuilding it for quick tests of vista3k, but doing that breaks wifi function and most people wouldn't resort to this anyways.

I then went back to building from source, add back the older vista3k with reverting back to the mese 23.x

Hope this help, if any, I'm sure you're aware of these issues too having a loki zero as well.

-Sam

[dmanlfc]

The lack of testing?!!! FFS we had v39 go through multiple releases candidates. Did ANYONE bring this to our attention before release? NOOO! We don't have EVERY GPU. It's a FREE open source project of which we spend countless hours on for little rewards. So if you want to have better releases, get on the Release Candidates. Otherwise keep your snide comments to yourself @eugene373 Rant over.

First things first, is there bug tracker on this issue already? I don't to keep posting here regarding mesa issue's if there's already a topic for it.

So I figured out most the issues by resetting to a fresh install of dev. 40. however there is an issue with psvista emulation on both accounts, meaning the latest psvista emulator and mesa have issues.

example: Mesa 24.x with v39+ vista3k = not playable on game's that played fine, texture / shader issues and lockup Mesa 24.x with vista3k from v38 = texture / shader issues on game's that played fine Mesa 23.x with v39+ vista3k = texture / shader issues on game's that played fine Mesa 23.x with vista3k from v38 = games play perfect.

i.e. conflict with both of the latest versions of vist3k & mesa 24

Vista games tested on Loki Zero: 10 second ninja ( This game is fine for the most part, with a few shader issue's ) 1001 Spikes / texture issue Farming Simulator ( This game is fine for the most part, with a few shader issue's ) Reel Fishing / Full lockup on fishing

There's also a few issues with mesa 24.x on RPCS3 but still trying to figure out what all games are effected.

Testing was done at first was unsquashing the system.sfs and rebuilding it for quick tests of vista3k, but doing that breaks wifi function and most people wouldn't resort to this anyways.

I then went back to building from source, add back the older vista3k with reverting back to the mese 23.x

Hope this help, if any, I'm sure you're aware of these issues too having a loki zero as well.

-Sam

Post your findings here - https://gitlab.freedesktop.org/mesa/mesa/-/issues/10838 If necessary, create a separate issue for what you've found in Vita3k.

[eugene373]

Please try my build, I'll get in contact with dmanlfc on how to better version release builds if it means staying active and using my github on such a great project!

This build does not include the Fixed Vita3k! More importantly I want dmanlfc to try this! https://drive.google.com/file/d/1qj6uEIommvsqO0aiFjIWvuwlzKjNMRRA/view?usp=drive_link

All Credit goes to the MESA Team! Mame Dev's. Batocera... I take no credit, this is built from the original Dev's Code! -Sam

[paronowitz]

Please try my build, I'll get in contact with dmanlfc on how to better version release builds if it means staying active and using my github on such a great project!

This build does not include the Fixed Vita3k! More importantly I want dmanlfc to try this! https://drive.google.com/file/d/1qj6uEIommvsqO0aiFjIWvuwlzKjNMRRA/view?usp=drive_link

All Credit goes to the MESA Team! Mame Dev's. Batocera... I take no credit, this is built from the original Dev's Code! -Sam

What is in this version that is not in the repo 4/19 release? Nevermind I saw your notes in the mesa thread... You reverted to mesa 23.2.1... I wonder if Im missing something here. The last 2 v40 beta releases played everything I tested with (I dont use vita3k) XBOX, PS2, Gamecube, N64 and down all seemed to play well. My lineup of controllers worked well too.

[eugene373]

Please try my build, I'll get in contact with dmanlfc on how to better version release builds if it means staying active and using my github on such a great project! This build does not include the Fixed Vita3k! More importantly I want dmanlfc to try this! https://drive.google.com/file/d/1qj6uEIommvsqO0aiFjIWvuwlzKjNMRRA/view?usp=drive_link All Credit goes to the MESA Team! Mame Dev's. Batocera... I take no credit, this is built from the original Dev's Code! -Sam

What is in this version that is not in the repo 4/19 release? Nevermind I saw your notes in the mesa thread... You reverted to mesa 23.2.1... I wonder if Im missing something here. The last 2 v40 beta releases played everything I tested with (I dont use vita3k) XBOX, PS2, Gamecube, N64 and down all seemed to play well. My lineup of controllers worked well too.

They play but there's definitely a performance boost with opengl 3.0 enabled, but the biggest & noticeable thing is on the lower end hardware like the amd 3050 / 3020.

On the lower end of things, you wont notice any changes meaning xbox and above is what you'll notice on. I mainly do emulation on PS3 or do a lot of up-scaling on psp games & ps2. Honestly I would have never noticed the issue if it wasn't for my love of vita games and did a lot of searching on the issue. I happened to stuble across this post regarding the issue & tried the xemu emulation to find the same issues going on.

I'll have the fixed version posted later with vita3k fixed.

[paronowitz]

Please try my build, I'll get in contact with dmanlfc on how to better version release builds if it means staying active and using my github on such a great project! This build does not include the Fixed Vita3k! More importantly I want dmanlfc to try this! https://drive.google.com/file/d/1qj6uEIommvsqO0aiFjIWvuwlzKjNMRRA/view?usp=drive_link All Credit goes to the MESA Team! Mame Dev's. Batocera... I take no credit, this is built from the original Dev's Code! -Sam

What is in this version that is not in the repo 4/19 release? Nevermind I saw your notes in the mesa thread... You reverted to mesa 23.2.1... I wonder if Im missing something here. The last 2 v40 beta releases played everything I tested with (I dont use vita3k) XBOX, PS2, Gamecube, N64 and down all seemed to play well. My lineup of controllers worked well too.

They play but there's definitely a performance boost with opengl 3.0 enabled, but the biggest & noticeable thing is on the lower end hardware like the amd 3050 / 3020.

On the lower end of things, you wont notice any changes meaning xbox and above is what you'll notice on. I mainly do emulation on PS3 or do a lot of up-scaling on psp games & ps2. Honestly I would have never noticed the issue if it wasn't for my love of vita games and did a lot of searching on the issue. I happened to stuble across this post regarding the issue & tried the xemu emulation to find the same issues going on.

I'll have the fixed version posted later with vita3k fixed.

Hmm... I've been pretty much using Vulkan for most cores. I have had some random reboots but they are just that... random. (Super Mario 64 with libretro-mupen64next system rebooted while in the retroarch menu as an example) Nothing specific that seems reproducible and I haven't gathered any logs. I'll give your build with Mesa 23.x a go. I'd stay on 38, however there are some controller improvements that are pretty compelling in =>39.

[paronowitz]

Please try my build, I'll get in contact with dmanlfc on how to better version release builds if it means staying active and using my github on such a great project! This build does not include the Fixed Vita3k! More importantly I want dmanlfc to try this! https://drive.google.com/file/d/1qj6uEIommvsqO0aiFjIWvuwlzKjNMRRA/view?usp=drive_link All Credit goes to the MESA Team! Mame Dev's. Batocera... I take no credit, this is built from the original Dev's Code! -Sam

What is in this version that is not in the repo 4/19 release? Nevermind I saw your notes in the mesa thread... You reverted to mesa 23.2.1... I wonder if Im missing something here. The last 2 v40 beta releases played everything I tested with (I dont use vita3k) XBOX, PS2, Gamecube, N64 and down all seemed to play well. My lineup of controllers worked well too.

They play but there's definitely a performance boost with opengl 3.0 enabled, but the biggest & noticeable thing is on the lower end hardware like the amd 3050 / 3020.

On the lower end of things, you wont notice any changes meaning xbox and above is what you'll notice on. I mainly do emulation on PS3 or do a lot of up-scaling on psp games & ps2. Honestly I would have never noticed the issue if it wasn't for my love of vita games and did a lot of searching on the issue. I happened to stuble across this post regarding the issue & tried the xemu emulation to find the same issues going on.

I'll have the fixed version posted later with vita3k fixed.

Ok So I got motivated. Seems stable so far with everything I tried. I havent tested it with my sinden, the mayflash bar, the usb to gamecube controller, or the n64 knockoff usb controller. Maybe tomorrow. I run on a 5500u. Im not sure I could say its any better or worse than the latest v40 butterfly build but everything works that I need to

[eugene373]

Please try my build, I'll get in contact with dmanlfc on how to better version release builds if it means staying active and using my github on such a great project! This build does not include the Fixed Vita3k! More importantly I want dmanlfc to try this! https://drive.google.com/file/d/1qj6uEIommvsqO0aiFjIWvuwlzKjNMRRA/view?usp=drive_link All Credit goes to the MESA Team! Mame Dev's. Batocera... I take no credit, this is built from the original Dev's Code! -Sam

What is in this version that is not in the repo 4/19 release? Nevermind I saw your notes in the mesa thread... You reverted to mesa 23.2.1... I wonder if Im missing something here. The last 2 v40 beta releases played everything I tested with (I dont use vita3k) XBOX, PS2, Gamecube, N64 and down all seemed to play well. My lineup of controllers worked well too.

They play but there's definitely a performance boost with opengl 3.0 enabled, but the biggest & noticeable thing is on the lower end hardware like the amd 3050 / 3020. On the lower end of things, you wont notice any changes meaning xbox and above is what you'll notice on. I mainly do emulation on PS3 or do a lot of up-scaling on psp games & ps2. Honestly I would have never noticed the issue if it wasn't for my love of vita games and did a lot of searching on the issue. I happened to stuble across this post regarding the issue & tried the xemu emulation to find the same issues going on. I'll have the fixed version posted later with vita3k fixed.

Ok So I got motivated. Seems stable so far with everything I tried. I havent tested it with my sinden, the mayflash bar, the usb to gamecube controller, or the n64 knockoff usb controller. Maybe tomorrow. I run on a 5500u. Im not sure I could say its any better or worse than the latest v40 butterfly build but everything works that I need to

I'll have to upload the mesa 23.2.1 source as it's needed 3 files fixed to compile against the latest batocera. Like I said, on the lower end of things you won't notice much if any, once you get into PS3 or up-scaling is were you'll see it. The first thing I noticed was running 50 cent blood on sand was the aiming was finally fixed, as well with better graphics i.e fire and so on. halo 2 on the xemu still had some shader issues but not as bad. Its noticeable in some game and minor in others, If you take Reel Fishing from the Vita, it's a major improvement in water and after awhile it would start having shader issues with the pole after you cast, those issue's are now gone as well.

[paronowitz]

Please try my build, I'll get in contact with dmanlfc on how to better version release builds if it means staying active and using my github on such a great project! This build does not include the Fixed Vita3k! More importantly I want dmanlfc to try this! https://drive.google.com/file/d/1qj6uEIommvsqO0aiFjIWvuwlzKjNMRRA/view?usp=drive_link All Credit goes to the MESA Team! Mame Dev's. Batocera... I take no credit, this is built from the original Dev's Code! -Sam

What is in this version that is not in the repo 4/19 release? Nevermind I saw your notes in the mesa thread... You reverted to mesa 23.2.1... I wonder if Im missing something here. The last 2 v40 beta releases played everything I tested with (I dont use vita3k) XBOX, PS2, Gamecube, N64 and down all seemed to play well. My lineup of controllers worked well too.

They play but there's definitely a performance boost with opengl 3.0 enabled, but the biggest & noticeable thing is on the lower end hardware like the amd 3050 / 3020. On the lower end of things, you wont notice any changes meaning xbox and above is what you'll notice on. I mainly do emulation on PS3 or do a lot of up-scaling on psp games & ps2. Honestly I would have never noticed the issue if it wasn't for my love of vita games and did a lot of searching on the issue. I happened to stuble across this post regarding the issue & tried the xemu emulation to find the same issues going on. I'll have the fixed version posted later with vita3k fixed.

Ok So I got motivated. Seems stable so far with everything I tried. I havent tested it with my sinden, the mayflash bar, the usb to gamecube controller, or the n64 knockoff usb controller. Maybe tomorrow. I run on a 5500u. Im not sure I could say its any better or worse than the latest v40 butterfly build but everything works that I need to

I'll have to upload the mesa 23.2.1 source as it's needed 3 files fixed to compile against the latest batocera. Like I said, on the lower end of things you won't notice much if any, once you get into PS3 or up-scaling is were you'll see it. The first thing I noticed was running 50 cent blood on sand was the aiming was finally fixed, as well with better graphics i.e fire and so on. halo 2 on the xemu still had some shader issues but not as bad. Its noticeable in some game and minor in others, If you take Reel Fishing from the Vita, it's a major improvement in water and after awhile it would start having shader issues with the pole after you cast, those issue's are now gone as well.

Scraper is broken...only arcadedb is listed

[eugene373]

Please try my build, I'll get in contact with dmanlfc on how to better version release builds if it means staying active and using my github on such a great project! This build does not include the Fixed Vita3k! More importantly I want dmanlfc to try this! https://drive.google.com/file/d/1qj6uEIommvsqO0aiFjIWvuwlzKjNMRRA/view?usp=drive_link All Credit goes to the MESA Team! Mame Dev's. Batocera... I take no credit, this is built from the original Dev's Code! -Sam

What is in this version that is not in the repo 4/19 release? Nevermind I saw your notes in the mesa thread... You reverted to mesa 23.2.1... I wonder if Im missing something here. The last 2 v40 beta releases played everything I tested with (I dont use vita3k) XBOX, PS2, Gamecube, N64 and down all seemed to play well. My lineup of controllers worked well too.

They play but there's definitely a performance boost with opengl 3.0 enabled, but the biggest & noticeable thing is on the lower end hardware like the amd 3050 / 3020. On the lower end of things, you wont notice any changes meaning xbox and above is what you'll notice on. I mainly do emulation on PS3 or do a lot of up-scaling on psp games & ps2. Honestly I would have never noticed the issue if it wasn't for my love of vita games and did a lot of searching on the issue. I happened to stuble across this post regarding the issue & tried the xemu emulation to find the same issues going on. I'll have the fixed version posted later with vita3k fixed.

Ok So I got motivated. Seems stable so far with everything I tried. I havent tested it with my sinden, the mayflash bar, the usb to gamecube controller, or the n64 knockoff usb controller. Maybe tomorrow. I run on a 5500u. Im not sure I could say its any better or worse than the latest v40 butterfly build but everything works that I need to

I'll have to upload the mesa 23.2.1 source as it's needed 3 files fixed to compile against the latest batocera. Like I said, on the lower end of things you won't notice much if any, once you get into PS3 or up-scaling is were you'll see it. The first thing I noticed was running 50 cent blood on sand was the aiming was finally fixed, as well with better graphics i.e fire and so on. halo 2 on the xemu still had some shader issues but not as bad. Its noticeable in some game and minor in others, If you take Reel Fishing from the Vita, it's a major improvement in water and after awhile it would start having shader issues with the pole after you cast, those issue's are now gone as well.

Scraper is broken...only arcadedb is listed

Okay this doesn't have anything do with me. So i.e. if you do a fresh pull. You can't compile Batocera. Period! Mesa3d 23.x nor 24.x doesn't compile nor does mame / xa, patches fail source ( on both mesa and mame, xa fails due to the wrong link) and not user friendly you have to know source and Patches. I'm again not trying to be snide but if you does a fresh pull you can't compile, meaning there is issues with mesa / mame / xa compiler. What it tells me is the dev's don't do a fresh build everytime I'm old school, don't put you name unless it compiles, now I did this on purposes to stay complainant back in the day. Only thing I touch in the batocera source is fixing mesa, mame (mama?) and xa cross compiler. nothing else! I'll fix what I can because I do a fresh build everytime and this is my complaint with batocera Dev's. I'm happy to upload the correct things to make batocera compile but if you try to build this, nope, figure it out. I'm okay with that though!

Update: Just tested it on all me device, It's working here! so maybe the scapper was down? But I stand behind my word, I just pulled a fresh build and it fails so that tell me the dev's are not doing a fresh build, a fresh pull. so this is null post https://wiki.batocera.org/compile_batocera.linux

[paronowitz]

Please try my build, I'll get in contact with dmanlfc on how to better version release builds if it means staying active and using my github on such a great project! This build does not include the Fixed Vita3k! More importantly I want dmanlfc to try this! https://drive.google.com/file/d/1qj6uEIommvsqO0aiFjIWvuwlzKjNMRRA/view?usp=drive_link All Credit goes to the MESA Team! Mame Dev's. Batocera... I take no credit, this is built from the original Dev's Code! -Sam

What is in this version that is not in the repo 4/19 release? Nevermind I saw your notes in the mesa thread... You reverted to mesa 23.2.1... I wonder if Im missing something here. The last 2 v40 beta releases played everything I tested with (I dont use vita3k) XBOX, PS2, Gamecube, N64 and down all seemed to play well. My lineup of controllers worked well too.

They play but there's definitely a performance boost with opengl 3.0 enabled, but the biggest & noticeable thing is on the lower end hardware like the amd 3050 / 3020. On the lower end of things, you wont notice any changes meaning xbox and above is what you'll notice on. I mainly do emulation on PS3 or do a lot of up-scaling on psp games & ps2. Honestly I would have never noticed the issue if it wasn't for my love of vita games and did a lot of searching on the issue. I happened to stuble across this post regarding the issue & tried the xemu emulation to find the same issues going on. I'll have the fixed version posted later with vita3k fixed.

Ok So I got motivated. Seems stable so far with everything I tried. I havent tested it with my sinden, the mayflash bar, the usb to gamecube controller, or the n64 knockoff usb controller. Maybe tomorrow. I run on a 5500u. Im not sure I could say its any better or worse than the latest v40 butterfly build but everything works that I need to

I'll have to upload the mesa 23.2.1 source as it's needed 3 files fixed to compile against the latest batocera. Like I said, on the lower end of things you won't notice much if any, once you get into PS3 or up-scaling is were you'll see it. The first thing I noticed was running 50 cent blood on sand was the aiming was finally fixed, as well with better graphics i.e fire and so on. halo 2 on the xemu still had some shader issues but not as bad. Its noticeable in some game and minor in others, If you take Reel Fishing from the Vita, it's a major improvement in water and after awhile it would start having shader issues with the pole after you cast, those issue's are now gone as well.

Scraper is broken...only arcadedb is listed

Okay this doesn't have anything do with me. So i.e. if you do a fresh pull. You can't compile Batocera. Period! Mesa3d 23.x nor 24.x doesn't compile nor does mame / xa, patches fail source ( on both mesa and mame, xa fails due to the wrong link) and not user friendly you have to know source and Patches. I'm again not trying to be snide but if you does a fresh pull you can't compile, meaning there is issues with mesa / mame / xa compiler. What it tells me is the dev's don't do a fresh build everytime I'm old school, don't put you name unless it compiles, now I did this on purposes to stay complainant back in the day. Only thing I touch in the batocera source is fixing mesa, mame (mama?) and xa cross compiler. nothing else! I'll fix what I can because I do a fresh build everytime and this is my complaint with batocera Dev's. I'm happy to upload the correct things to make batocera compile but if you try to build this, nope, figure it out. I'm okay with that though!

Update: Just tested it on all me device, It's working here! so maybe the scapper was down? But I stand behind my word, I just pulled a fresh build and it fails so that tell me the dev's are not doing a fresh build, a fresh pull. so this is null post https://wiki.batocera.org/compile_batocera.linux

Maybe I had used your latest build then copied my /share directory contents... oddly only arcadedb was listed... I can try reimaging my drive with your img again and look at the scraper config before copying my stuff back.

[eugene373]

Please try my build, I'll get in contact with dmanlfc on how to better version release builds if it means staying active and using my github on such a great project! This build does not include the Fixed Vita3k! More importantly I want dmanlfc to try this! https://drive.google.com/file/d/1qj6uEIommvsqO0aiFjIWvuwlzKjNMRRA/view?usp=drive_link All Credit goes to the MESA Team! Mame Dev's. Batocera... I take no credit, this is built from the original Dev's Code! -Sam

What is in this version that is not in the repo 4/19 release? Nevermind I saw your notes in the mesa thread... You reverted to mesa 23.2.1... I wonder if Im missing something here. The last 2 v40 beta releases played everything I tested with (I dont use vita3k) XBOX, PS2, Gamecube, N64 and down all seemed to play well. My lineup of controllers worked well too.

They play but there's definitely a performance boost with opengl 3.0 enabled, but the biggest & noticeable thing is on the lower end hardware like the amd 3050 / 3020. On the lower end of things, you wont notice any changes meaning xbox and above is what you'll notice on. I mainly do emulation on PS3 or do a lot of up-scaling on psp games & ps2. Honestly I would have never noticed the issue if it wasn't for my love of vita games and did a lot of searching on the issue. I happened to stuble across this post regarding the issue & tried the xemu emulation to find the same issues going on. I'll have the fixed version posted later with vita3k fixed.

Ok So I got motivated. Seems stable so far with everything I tried. I havent tested it with my sinden, the mayflash bar, the usb to gamecube controller, or the n64 knockoff usb controller. Maybe tomorrow. I run on a 5500u. Im not sure I could say its any better or worse than the latest v40 butterfly build but everything works that I need to

I'll have to upload the mesa 23.2.1 source as it's needed 3 files fixed to compile against the latest batocera. Like I said, on the lower end of things you won't notice much if any, once you get into PS3 or up-scaling is were you'll see it. The first thing I noticed was running 50 cent blood on sand was the aiming was finally fixed, as well with better graphics i.e fire and so on. halo 2 on the xemu still had some shader issues but not as bad. Its noticeable in some game and minor in others, If you take Reel Fishing from the Vita, it's a major improvement in water and after awhile it would start having shader issues with the pole after you cast, those issue's are now gone as well.

Scraper is broken...only arcadedb is listed

Okay this doesn't have anything do with me. So i.e. if you do a fresh pull. You can't compile Batocera. Period! Mesa3d 23.x nor 24.x doesn't compile nor does mame / xa, patches fail source ( on both mesa and mame, xa fails due to the wrong link) and not user friendly you have to know source and Patches. I'm again not trying to be snide but if you does a fresh pull you can't compile, meaning there is issues with mesa / mame / xa compiler. What it tells me is the dev's don't do a fresh build everytime I'm old school, don't put you name unless it compiles, now I did this on purposes to stay complainant back in the day. Only thing I touch in the batocera source is fixing mesa, mame (mama?) and xa cross compiler. nothing else! I'll fix what I can because I do a fresh build everytime and this is my complaint with batocera Dev's. I'm happy to upload the correct things to make batocera compile but if you try to build this, nope, figure it out. I'm okay with that though! Update: Just tested it on all me device, It's working here! so maybe the scapper was down? But I stand behind my word, I just pulled a fresh build and it fails so that tell me the dev's are not doing a fresh build, a fresh pull. so this is null post https://wiki.batocera.org/compile_batocera.linux

Maybe I had used your latest build then copied my /share directory contents... oddly only arcadedb was listed... I can try reimaging my drive with your img again and look at the scraper config before copying my stuff back.

Don't that !!!!! Mount the image and copy! Use something like Ubuntu live and copy everything into the boot! in other words don't touch you game partition just copy everything in the first partition!!! contact me on / @ mculover81 @ G Mail

[NYXZGames]

Can confirm my situation is resolved on the Ser5 Mini PC (5560u) model with the latest v40 Butterfly update. Everything is working flawlessly on the Xbox side, and whatever updates have happened to Dolphin, I'm getting significant gains in FPS on that too for Gamecube.

Just want to say thank you to the devs hard work in fixing this, and I'm extremely happy to be able to continue my playthrough of Halo 2.

[paronowitz]

Please try my build, I'll get in contact with dmanlfc on how to better version release builds if it means staying active and using my github on such a great project! This build does not include the Fixed Vita3k! More importantly I want dmanlfc to try this! https://drive.google.com/file/d/1qj6uEIommvsqO0aiFjIWvuwlzKjNMRRA/view?usp=drive_link All Credit goes to the MESA Team! Mame Dev's. Batocera... I take no credit, this is built from the original Dev's Code! -Sam

What is in this version that is not in the repo 4/19 release? Nevermind I saw your notes in the mesa thread... You reverted to mesa 23.2.1... I wonder if Im missing something here. The last 2 v40 beta releases played everything I tested with (I dont use vita3k) XBOX, PS2, Gamecube, N64 and down all seemed to play well. My lineup of controllers worked well too.

They play but there's definitely a performance boost with opengl 3.0 enabled, but the biggest & noticeable thing is on the lower end hardware like the amd 3050 / 3020. On the lower end of things, you wont notice any changes meaning xbox and above is what you'll notice on. I mainly do emulation on PS3 or do a lot of up-scaling on psp games & ps2. Honestly I would have never noticed the issue if it wasn't for my love of vita games and did a lot of searching on the issue. I happened to stuble across this post regarding the issue & tried the xemu emulation to find the same issues going on. I'll have the fixed version posted later with vita3k fixed.

Ok So I got motivated. Seems stable so far with everything I tried. I havent tested it with my sinden, the mayflash bar, the usb to gamecube controller, or the n64 knockoff usb controller. Maybe tomorrow. I run on a 5500u. Im not sure I could say its any better or worse than the latest v40 butterfly build but everything works that I need to

I'll have to upload the mesa 23.2.1 source as it's needed 3 files fixed to compile against the latest batocera. Like I said, on the lower end of things you won't notice much if any, once you get into PS3 or up-scaling is were you'll see it. The first thing I noticed was running 50 cent blood on sand was the aiming was finally fixed, as well with better graphics i.e fire and so on. halo 2 on the xemu still had some shader issues but not as bad. Its noticeable in some game and minor in others, If you take Reel Fishing from the Vita, it's a major improvement in water and after awhile it would start having shader issues with the pole after you cast, those issue's are now gone as well.

Scraper is broken...only arcadedb is listed

Okay this doesn't have anything do with me. So i.e. if you do a fresh pull. You can't compile Batocera. Period! Mesa3d 23.x nor 24.x doesn't compile nor does mame / xa, patches fail source ( on both mesa and mame, xa fails due to the wrong link) and not user friendly you have to know source and Patches. I'm again not trying to be snide but if you does a fresh pull you can't compile, meaning there is issues with mesa / mame / xa compiler. What it tells me is the dev's don't do a fresh build everytime I'm old school, don't put you name unless it compiles, now I did this on purposes to stay complainant back in the day. Only thing I touch in the batocera source is fixing mesa, mame (mama?) and xa cross compiler. nothing else! I'll fix what I can because I do a fresh build everytime and this is my complaint with batocera Dev's. I'm happy to upload the correct things to make batocera compile but if you try to build this, nope, figure it out. I'm okay with that though! Update: Just tested it on all me device, It's working here! so maybe the scapper was down? But I stand behind my word, I just pulled a fresh build and it fails so that tell me the dev's are not doing a fresh build, a fresh pull. so this is null post https://wiki.batocera.org/compile_batocera.linux

Maybe I had used your latest build then copied my /share directory contents... oddly only arcadedb was listed... I can try reimaging my drive with your img again and look at the scraper config before copying my stuff back.

Don't that !!!!! Mount the image and copy! Use something like Ubuntu live and copy everything into the boot! in other words don't touch you game partition just copy everything in the first partition!!! contact me on / @ mculover81 @ G Mail

Hey I did send you a couple emails. Id love to collaborate on your build. The latest butterfly releases for me have been really unstable with n64... Random reboots in mario kart 64 and mario tennis and sometime even just navigating the ES frontend

[eugene373]

Please try my build, I'll get in contact with dmanlfc on how to better version release builds if it means staying active and using my github on such a great project! This build does not include the Fixed Vita3k! More importantly I want dmanlfc to try this! https://drive.google.com/file/d/1qj6uEIommvsqO0aiFjIWvuwlzKjNMRRA/view?usp=drive_link All Credit goes to the MESA Team! Mame Dev's. Batocera... I take no credit, this is built from the original Dev's Code! -Sam

What is in this version that is not in the repo 4/19 release? Nevermind I saw your notes in the mesa thread... You reverted to mesa 23.2.1... I wonder if Im missing something here. The last 2 v40 beta releases played everything I tested with (I dont use vita3k) XBOX, PS2, Gamecube, N64 and down all seemed to play well. My lineup of controllers worked well too.

They play but there's definitely a performance boost with opengl 3.0 enabled, but the biggest & noticeable thing is on the lower end hardware like the amd 3050 / 3020. On the lower end of things, you wont notice any changes meaning xbox and above is what you'll notice on. I mainly do emulation on PS3 or do a lot of up-scaling on psp games & ps2. Honestly I would have never noticed the issue if it wasn't for my love of vita games and did a lot of searching on the issue. I happened to stuble across this post regarding the issue & tried the xemu emulation to find the same issues going on. I'll have the fixed version posted later with vita3k fixed.

Ok So I got motivated. Seems stable so far with everything I tried. I havent tested it with my sinden, the mayflash bar, the usb to gamecube controller, or the n64 knockoff usb controller. Maybe tomorrow. I run on a 5500u. Im not sure I could say its any better or worse than the latest v40 butterfly build but everything works that I need to

I'll have to upload the mesa 23.2.1 source as it's needed 3 files fixed to compile against the latest batocera. Like I said, on the lower end of things you won't notice much if any, once you get into PS3 or up-scaling is were you'll see it. The first thing I noticed was running 50 cent blood on sand was the aiming was finally fixed, as well with better graphics i.e fire and so on. halo 2 on the xemu still had some shader issues but not as bad. Its noticeable in some game and minor in others, If you take Reel Fishing from the Vita, it's a major improvement in water and after awhile it would start having shader issues with the pole after you cast, those issue's are now gone as well.

Scraper is broken...only arcadedb is listed

Okay this doesn't have anything do with me. So i.e. if you do a fresh pull. You can't compile Batocera. Period! Mesa3d 23.x nor 24.x doesn't compile nor does mame / xa, patches fail source ( on both mesa and mame, xa fails due to the wrong link) and not user friendly you have to know source and Patches. I'm again not trying to be snide but if you does a fresh pull you can't compile, meaning there is issues with mesa / mame / xa compiler. What it tells me is the dev's don't do a fresh build everytime I'm old school, don't put you name unless it compiles, now I did this on purposes to stay complainant back in the day. Only thing I touch in the batocera source is fixing mesa, mame (mama?) and xa cross compiler. nothing else! I'll fix what I can because I do a fresh build everytime and this is my complaint with batocera Dev's. I'm happy to upload the correct things to make batocera compile but if you try to build this, nope, figure it out. I'm okay with that though! Update: Just tested it on all me device, It's working here! so maybe the scapper was down? But I stand behind my word, I just pulled a fresh build and it fails so that tell me the dev's are not doing a fresh build, a fresh pull. so this is null post https://wiki.batocera.org/compile_batocera.linux

Maybe I had used your latest build then copied my /share directory contents... oddly only arcadedb was listed... I can try reimaging my drive with your img again and look at the scraper config before copying my stuff back.

Don't that !!!!! Mount the image and copy! Use something like Ubuntu live and copy everything into the boot! in other words don't touch you game partition just copy everything in the first partition!!! contact me on / @ mculover81 @ G Mail

Hey I did send you a couple emails. Id love to collaborate on your build. The latest butterfly releases for me have been really unstable with n64... Random reboots in mario kart 64 and mario tennis and sometime even just navigating the ES frontend

It's 1pm now, I'll have another test build up and working. no later than 3pm. I did figure out the scraper issue btw, OPENGL will say 2.0 but built against opengl 3.0. I had to build my build with the dev's emulationstation binary due to API key and what not. I plan on updating my github this weekend or next week with compiling issue's taken care of. After digging deeper into the Dev's code I realized after the fact this isn't an issue with batocera source but at the rate things change, as I had issue with redream this week.

[cannondale0815]

Hello -- the GDrive link isn't working anymore -- @eugene373 may I trouble you for a new link so I can try this out on my Lenovo ThinkCentre M75q-1 that is experiencing the same issue that is described in this long thread? Thank you!

[bct]

I think you may not need the Google Drive build any more, the Butterfly beta release fixed this on my machine (a Ryzen 2200G).

[cannondale0815]

I think you may not need the Google Drive build any more, the Butterfly beta release fixed this on my machine (a Ryzen 2200G).

Can confirm myself now that the latest v40 beta/butterfly solved this issue. Was a piece of work to install it, as upgrades aren't possible and only a fresh install is possible. For anyone wondering where to get the latest v40 from, download it from here.

[paronowitz]

I was able to downgrade from the forked release to v38 (batocera-upgrade pointing to the v38 release) then use the standard upgrade to the latest v40 4/28 release. Going from the forked release straight to v40 via the standard ui method gave me an error.

[FetusSandwich]

What was the actual merge that fixed this issue? I'd like to see the diff.

[paronowitz]

The latest release broke xbox gameplay again x86_64 - 40-dev-9a61198db7 2024/05/27 01:56... I assume the merge has been inadvertantly reverted

[DonutBling]

Is there a particular recent release i can use for a fresh image where xbox360 still functions?

[paronowitz]

Is there a particular recent release i can use for a fresh image where xbox360 still functions?

XEMU is for xbox not xbox360... Thats xenia