Describe the bug (mandatory)
When dumping with nxdumptool's Rewrite (Specifically a build based on Rewrite commit 232fe05) and a self built copy of ns-usbloader puts a lot of empty, 0 byte, files next to the NSP.
Information about environment (mandatory):
OS: Windows 10 10.0.19042.746
Java version 1.8.0_241
Steps to reproduce
Steps to reproduce the behavior:
Build ns-usbloader, editing only what's required to enable NXDumpTool's tab
Specifically in /src/main/resources/NSLMain.fxml, all that I am changing is disable="true" to disable="false" on L74, and visible="false" to visible="true" at the end of L79
Open ns-usbloader and set dump directory output, open nsp_dumper_usb/nxdumptool-rewrite.nro on console connected to host PC via USB, and start dump
When dump is complete, check output directory on PC, and you will see a lot of extraneous, 0 byte, files in output directory.
Expected behavior
Only NSP is dumped and not extraneous files.
Screenshots and/or information from application log
Screenshot of directory after dump:
Did you see this issue in previous versions?
Yes
Additional context
Said extraneous files seem to be named the same as those that were packed into the resulting NSP.
I have talked to DarkMatterCore about this before, and if memory serves - He does not believe it to be an issue with NXDumpTool.
Describe the bug (mandatory) When dumping with nxdumptool's Rewrite (Specifically a build based on Rewrite commit
232fe05) and a self built copy of ns-usbloader puts a lot of empty, 0 byte, files next to the NSP.Information about environment (mandatory):
Steps to reproduce Steps to reproduce the behavior:
Build ns-usbloader, editing only what's required to enable NXDumpTool's tab Specifically in
/src/main/resources/NSLMain.fxml, all that I am changing isdisable="true"todisable="false"on L74, andvisible="false"tovisible="true"at the end of L79Open ns-usbloader and set dump directory output, open
nsp_dumper_usb/nxdumptool-rewrite.nroon console connected to host PC via USB, and start dumpWhen dump is complete, check output directory on PC, and you will see a lot of extraneous, 0 byte, files in output directory.
Expected behavior Only NSP is dumped and not extraneous files.
Screenshots and/or information from application log
Screenshot of directory after dump:
Did you see this issue in previous versions? Yes
Additional context Said extraneous files seem to be named the same as those that were packed into the resulting NSP. I have talked to DarkMatterCore about this before, and if memory serves - He does not believe it to be an issue with NXDumpTool.