Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Ludo crashes when trying to scan GB/GBC/GBA ROMs folder #463

Open
LOuroboros opened this issue Aug 24, 2021 · 13 comments
Open

Ludo crashes when trying to scan GB/GBC/GBA ROMs folder #463

LOuroboros opened this issue Aug 24, 2021 · 13 comments
Labels
bug Something isn't working

Comments

@LOuroboros
Copy link

Basically what I say in the title.
I have my collection of GBA ROMs located in "E:\Lunos\Emulation\ROMs\GB, GBC and GBA", and when I go there by navigating through folders, Ludo closes right away.

pn_511.mp4
@LOuroboros LOuroboros changed the title Ludo crashes when trying to scan GBA ROMs folder Ludo crashes when trying to scan GB/GBC/GBA ROMs folder Aug 24, 2021
@kivutar
Copy link
Member

kivutar commented Sep 2, 2021

OK thanks for the bug report.

Can I get a list of the content of this folder?

Do you know how to launch Ludo from the command line to get a log or a stack trace?

@kivutar kivutar added the bug Something isn't working label Sep 2, 2021
@LOuroboros
Copy link
Author

Can I get a list of the content of this folder?

The folder contains multiple folders. In each folder there's a ROM, and in some cases there's a couple of extra files. Documentation, savefile or savestate files generated by either VBA or mGBA and such.

Do you know how to launch Ludo from the command line to get a log or a stack trace?

Well, "opening from the command line" sounds as easy as opening Ludo.exe in the Windows Command Prompt, no?

But I've no idea about how to generate a log or a stack trace 👀

@kivutar
Copy link
Member

kivutar commented Sep 9, 2021

Yes opening ludo.exe from the command prompt should be enough, and you can pass a flag like -v to get more logs.

@LOuroboros
Copy link
Author

Yes opening ludo.exe from the command prompt should be enough, and you can pass a flag like -v to get more logs.

I don't think it's working?

Booting up Ludo by using ludo.exe -v doesn't seem to record anything on the terminal, and if I hit "Scan this directory" the program closes just like it happened a few weeks back when I opened this issue post :/ ...

Untitled

@kivutar
Copy link
Member

kivutar commented Sep 9, 2021

Maybe on Windows passing a flag would be done with another syntax. Try ludo.exe /v maybe?

@LOuroboros
Copy link
Author

Maybe on Windows passing a flag would be done with another syntax. Try ludo.exe /v maybe?

Still nothing :/

explorer_894

@kivutar
Copy link
Member

kivutar commented Sep 22, 2021

Ah sorry for that... I don't know how to get enough information to fix this.

Maybe you can try creating a new folder where you would transfer the GB roms one by one to see if there is one in particular that causes the crash?

@LOuroboros
Copy link
Author

LOuroboros commented Sep 22, 2021

Ah sorry for that... I don't know how to get enough information to fix this.

Maybe you can try creating a new folder where you would transfer the GB roms one by one to see if there is one in particular that causes the crash?

Something tells me the crash is being caused by the fact that I'm trying to make Ludo read a folder with ROMs allocated in an external hard drive (E:) and the program just doesn't like that, but I'll try to move the folder to my desktop and scan it from there anyway. Will edit in a moment.

EDIT: Yep, it works normally if I scan the folder while in the Desktop.
Untitled

EDIT2: I celebrated victory too soon. I just realized that it scanned 6 games, which means it's skipping a bunch of other games, mostly ROM Hacks.

@kivutar
Copy link
Member

kivutar commented Sep 30, 2021

ROM hacks not being scanned is a separate issue, due to the scanner being checksum based.

What filesystem was this E drive?

@LOuroboros
Copy link
Author

ROM hacks not being scanned is a separate issue, due to the scanner being checksum based.

What filesystem was this E drive?

It's NTFS.

@tompruitt
Copy link

@LOuroboros can you still reproduce it?

@LOuroboros
Copy link
Author

@LOuroboros can you still reproduce it?

Yup. Ludo v0.17.2 crashes the moment I hit the X button to scan my D:\Lunos\Emulation\ROMs\GB, GBC and GBA directory, @tompruitt.

I have the external HDD where I keep my ROMs and emulators on D: now. Windows things. I formatted my PC about 2 times during the past 3 years and during my last formatting Windows just decided to host it on D: instead of E:.

@LOuroboros
Copy link
Author

LOuroboros commented Mar 30, 2024

For whatever it's worth, I checked something at random which was to rename my "GB, GBC and GBA" folder to "GBGBCGBA", but Ludo still crashed regardless.

I reverted the folder name change, then copy-pasted the folder in my Windows desktop (C:\Users\Lunos\Desktop) and that did work just fine.

%pn_20240330_132401153

%pn_20240330_132717578

It's a shame that Ludo still can't recognize ROM Hacks despite being completely valid and functional GBA ROM files though.

Also, ignore the black bars on the sides in the pictures above. I had to use an external application called Magpie in order to set Ludo to Borderless Fullscreen because the program doesn't seem to offer an option for that in its settings 😅 ...

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

3 participants