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

Feedback and bug for USB HDD installation (libusbhsfs) #7

Closed
ghost opened this issue Dec 1, 2020 · 15 comments
Closed

Feedback and bug for USB HDD installation (libusbhsfs) #7

ghost opened this issue Dec 1, 2020 · 15 comments

Comments

@ghost
Copy link

ghost commented Dec 1, 2020

Some feedback for the new USB HDD installation feature (Atmosphere 0.15.0 without fsp-usb running, Firmware 10.2.0):

  • Games install correctly but after exiting DBI you can get an error
  • After installing any game from USB HDD if you exit and open DBI again you will get a black screen and you are unable to open DBI again until you reboot the Switch
  • The installation speed seems slower, around 33% - 50% of what it was with fsp-usb (I used the same exFAT USB HDD to test)
@rashevskyv
Copy link
Owner

How do you launch DBI? Applet (albums) or title (game) mod?

@rashevskyv
Copy link
Owner

And did you tests installation with the same game to the same place?

@ghost
Copy link
Author

ghost commented Dec 1, 2020

How do you launch DBI? Applet (albums) or title (game) mod?

I tested both and it was the same for both.

And did you tests installation with the same game to the same place?

I tested two games both in AUTO mode.

@rashevskyv
Copy link
Owner

Try with latest version please. It built with newest version of libusbhsfs

@ghost
Copy link
Author

ghost commented Dec 6, 2020

Try with latest version please. It built with newest version of libusbhsfs

Tested (firmware 11.0.0 and atmosphere 0.16.0 second prerelease, DBI 201):

  • Speed is a lot faster, looks the same as fsp-usb or maybe a bit faster

  • There are still some errors after installing games from USB drive. For example this is what happened:

  1. Install game from USB0, the game installs correctly
  2. Exit DBI and receive error (Nintendo error, asking to share or do not share error report)
  3. Open DBI again, it works
  4. Install another game from USB0, the game installs correctly
  5. Exit DBI, no error
  6. Open DBI, black screen. Need to reboot to access DBI again.

@ghost
Copy link
Author

ghost commented Dec 7, 2020

DBI 202: USB drive not detected at all in DBI

@ghost
Copy link

ghost commented Dec 8, 2020

Since 202 libusbhsfs is opt-in: to use it create /switch/dbi.libusbhsfs flag file.

@ghost
Copy link

ghost commented Dec 8, 2020

Also, make sure you are using dbi in applet mode.

@ghost
Copy link
Author

ghost commented Dec 8, 2020

Since 202 libusbhsfs is opt-in: to use it create /switch/dbi.libusbhsfs flag file.

Ok thanks, is that for hiding the option while it's under development?

Anyway I just tried it and USB0 is not appearing with DBI.nro + dbi.libusbhsfs flag file in either /switch/ or /switch/DBI/ (I usually use folder)

It appears fine in 201.

@rashevskyv
Copy link
Owner

Try with new 204 version

@ghost
Copy link
Author

ghost commented Dec 8, 2020

Try with new 204 version

The flag works now. DBI has a black background in application mode now, intentional?

Atmosphere 0.16.0 prerelease 2, DBI 204, tested firmware 10.2.0 and 11.0.0, both same result:

@ghost
Copy link

ghost commented Dec 8, 2020

Did you tried the same scenario with libusbhsfs example application?

Black bg is intentional. DBI not designed to be run in application mode.

@ghost
Copy link
Author

ghost commented Dec 8, 2020

Did you tried the same scenario with libusbhsfs example application?

Black bg is intentional. DBI not designed to be run in application mode.

I checked, it seems that the example application can also trigger this bug. I'll open an issue there.

By the way I've never had an issue with DBI in application mode, unless you mean it can specifically cause issues with libusbhsfs.

@ghost
Copy link
Author

ghost commented Dec 9, 2020

@duckbill007 It was a libusbhsfs issue.

Should be fixed in: DarkMatterCore/libusbhsfs@ae8663d

@ghost ghost closed this as completed Dec 9, 2020
@ghost
Copy link
Author

ghost commented Dec 9, 2020

Confirmed fixed in DBI 206, thanks!

This issue was closed.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant