Open Repl0idZer03 opened 3 years ago
This is for 1.3.1 - Can you give 3.0.3 a run? I really need to remove 1.3.1 as it has a lot of problems.
https://github.com/akai-katto/dandere2x/releases/tag/3.0.3
To download / update,
1) Download the base 3.0
2) Install 3.0.3.exe into the same directory as dandere2x.exe
This is for 1.3.1 - Can you give 3.0.3 a run? I really need to remove 1.3.1 as it has a lot of problems.
https://github.com/akai-katto/dandere2x/releases/tag/3.0.3
To download / update,
- Download the base 3.0
- Install 3.0.3.exe into the same directory as dandere2x.exe
After installing the latest version (being 3.0) and moving the 3.0.3 patch (which sometimes disappears right after downloading it) into the same directory as the dandere program (I'm not sure if it is the same as "installing" into the same directory), I ran 3.0.3 as administrator, only to receive an error message, which claims the patch has "a virus or potentially unwanted software". Not running it as an administrator makes the file disappear for some strange reason. Should I be concerned about this?
(Here is another file which showcases my new issue.)
This is something that I've recently discovered this as well - I checked the virus totals for the last 3 dandere2x releases, and apparently they're marked as false-positives. I associate this mostly with dandere2x downloading external files and using a lot of sub-processes.
If you feel comfortable with running it, marketing it as safe is the quickest solution, else, you can run dandere2x via the source code for now until I figure out how to fix the false-positive issue.
If you want to avoid running the binary for now, the google collab verison builds dandere2x from the source.
While running the software (as an admin), I have noticed a multitude of problems within the logs. First being, "dandere2x could not start... trying again. If it fails, try running as admin (which I was doing, as stated before). Then "Traceback (most recent call last)" was written twice, though I'm not completely sure whether or not this is part of the upscaling process or if this is an actual error that must be addressed. Last, which is by far the most perplexing in my view, would be "PermissionError: [WinError 32] The process cannot access the file because it is being used by another process: [the same directory that dandere2x log uses].
Below, I have attached an image of the issues in question.
I will provide further information/context regarding the files/directories should you ask for them.