Upscayl 2.15.0: Folderviewer out of order

[Hikodi]

Checklist

• [X] I have tried ALL of the steps mentioned in the troubleshooting guide.
• [X] I have searched for this in the issues tab.

Describe the Bug

If all work done, Upscayl say "Open Upscayled Folder". If I do this, I see the source folder, not the target folder. And - the folder is empty, but not in real. The older version 2.11.5 worked in this area well.

The other problem: I have to say on every program-start, that I want output in JPG-Format. Upscayl 2.15.0 can ´t remember.

What can I do?

To Reproduce

Every time if I use Upscayl 2.15.0

Upscayl Version (or commit hash)

2.15.0

Platform

Windows

OS Version

Windows 11 23H2

GPU Name

GeForce GTX 1650 SUPER

Expected Behavior

No response

Screenshots

Logs

I think, it ´s not neccessary, because Upscaling without problem.

[dosubot[bot]]

Hey @Hikodi!

I'm here to help you with any bugs, questions, or contributions you have for Upscayl. Let's get to the bottom of this together!

I found a similar unsolved discussion titled Default Output Folder, which might be related to the issue you're experiencing with the folder navigation in Upscayl 2.15.0 ^[1].

Regarding the issue with the output format not being remembered, the output format preference is stored using the saveImageAsAtom, which persists the value under the key "saveImageAs". This should automatically retrieve the stored value from local storage upon program start ^[2][3]. If this is not working, it might be worth checking if there are any issues with local storage permissions or if the application is correctly saving the settings.

For the folder navigation issue, Upscayl determines the default output folder path by appending a dynamically generated folder name to the provided outputPath. The logic to open the folder is triggered in the onClose function, which sends a command to open the folder if the process completes without errors ^[4]. If the wrong folder is opening, it might be due to an error in this logic or a misconfiguration in the outputPath.

Additionally, there is error handling and logging implemented in the code that could provide insights into why the folder navigation might be malfunctioning. The code uses logging functions and error handling mechanisms to diagnose issues with folder navigation ^[5][6]. Checking these logs might help identify the problem.

To continue talking to Dosu, mention @dosu.

---

^{Help Dosu learn! Give it feedback: Great Response | Irrelevant Answer | Incorrect Sources | Too Verbose | Hallucination | Other}

[Hikodi]

Here the logfile

🎯 GET_MODELS_LIST:  F:\Upscayl\models
🎯 GET_MODELS_LIST:  F:\Upscayl\models
🎒 BACKEND REPORTED:  📁 Updating Custom Models Folder Path:  F:\Upscayl\models
🎒 BACKEND REPORTED:  📁 Updating Custom Models Folder Path:  F:\Upscayl\models
🎒 BACKEND REPORTED:  📁 Custom Models Folder Path:  F:\Upscayl\models
🎒 BACKEND REPORTED:  📁 Custom Models Folder Path:  F:\Upscayl\models
🎒 BACKEND REPORTED:  🔎 Detected Custom Models:  4xHFA2k,4xLSDIR,4xLSDIRCompactC3,4xLSDIRplusC,4xNomos8kSC,4x_NMKD-Siax_200k,4x_NMKD-Superscale-SP_178000_G,realesr-animevideov3-x2,realesr-animevideov3-x3,realesr-animevideov3-x4,RealESRGAN_General_WDN_x4_v3,RealESRGAN_General_x4_v3,uniscale_restore,unknown-2.0.1
🎒 BACKEND REPORTED:  🔎 Detected Custom Models:  4xHFA2k,4xLSDIR,4xLSDIRCompactC3,4xLSDIRplusC,4xNomos8kSC,4x_NMKD-Siax_200k,4x_NMKD-Superscale-SP_178000_G,realesr-animevideov3-x2,realesr-animevideov3-x3,realesr-animevideov3-x4,RealESRGAN_General_WDN_x4_v3,RealESRGAN_General_x4_v3,uniscale_restore,unknown-2.0.1
📜 CUSTOM_MODEL_FILES_LIST:  4xHFA2k,4xLSDIR,4xLSDIRCompactC3,4xLSDIRplusC,4xNomos8kSC,4x_NMKD-Siax_200k,4x_NMKD-Superscale-SP_178000_G,realesr-animevideov3-x2,realesr-animevideov3-x3,realesr-animevideov3-x4,RealESRGAN_General_WDN_x4_v3,RealESRGAN_General_x4_v3,uniscale_restore,unknown-2.0.1
📜 CUSTOM_MODEL_FILES_LIST:  4xHFA2k,4xLSDIR,4xLSDIRCompactC3,4xLSDIRplusC,4xNomos8kSC,4x_NMKD-Siax_200k,4x_NMKD-Superscale-SP_178000_G,realesr-animevideov3-x2,realesr-animevideov3-x3,realesr-animevideov3-x4,RealESRGAN_General_WDN_x4_v3,RealESRGAN_General_x4_v3,uniscale_restore,unknown-2.0.1
🎒 BACKEND REPORTED:  📁 Updating Custom Models Folder Path:  F:\Upscayl\models
🎒 BACKEND REPORTED:  📁 Updating Custom Models Folder Path:  F:\Upscayl\models
🎒 BACKEND REPORTED:  📁 Custom Models Folder Path:  F:\Upscayl\models
🎒 BACKEND REPORTED:  📁 Custom Models Folder Path:  F:\Upscayl\models
🎒 BACKEND REPORTED:  🔎 Detected Custom Models:  4xHFA2k,4xLSDIR,4xLSDIRCompactC3,4xLSDIRplusC,4xNomos8kSC,4x_NMKD-Siax_200k,4x_NMKD-Superscale-SP_178000_G,realesr-animevideov3-x2,realesr-animevideov3-x3,realesr-animevideov3-x4,RealESRGAN_General_WDN_x4_v3,RealESRGAN_General_x4_v3,uniscale_restore,unknown-2.0.1
🎒 BACKEND REPORTED:  🔎 Detected Custom Models:  4xHFA2k,4xLSDIR,4xLSDIRCompactC3,4xLSDIRplusC,4xNomos8kSC,4x_NMKD-Siax_200k,4x_NMKD-Superscale-SP_178000_G,realesr-animevideov3-x2,realesr-animevideov3-x3,realesr-animevideov3-x4,RealESRGAN_General_WDN_x4_v3,RealESRGAN_General_x4_v3,uniscale_restore,unknown-2.0.1
📜 CUSTOM_MODEL_FILES_LIST:  4xHFA2k,4xLSDIR,4xLSDIRCompactC3,4xLSDIRplusC,4xNomos8kSC,4x_NMKD-Siax_200k,4x_NMKD-Superscale-SP_178000_G,realesr-animevideov3-x2,realesr-animevideov3-x3,realesr-animevideov3-x4,RealESRGAN_General_WDN_x4_v3,RealESRGAN_General_x4_v3,uniscale_restore,unknown-2.0.1
📜 CUSTOM_MODEL_FILES_LIST:  4xHFA2k,4xLSDIR,4xLSDIRCompactC3,4xLSDIRplusC,4xNomos8kSC,4x_NMKD-Siax_200k,4x_NMKD-Superscale-SP_178000_G,realesr-animevideov3-x2,realesr-animevideov3-x3,realesr-animevideov3-x4,RealESRGAN_General_WDN_x4_v3,RealESRGAN_General_x4_v3,uniscale_restore,unknown-2.0.1
💻 System Info: {"platform":"win","release":"10.0.22631","arch":"x64","model":"11th Gen Intel(R) Core(TM) i7-11700K @ 3.60GHz","cpuCount":16,"gpu":{"active":true,"cudaComputeCapabilityMajor":0,"deviceId":8583,"driverVendor":"NVIDIA","driverVersion":"32.0.15.6603","gpuPreference":0,"revision":161,"subSysId":944772194,"vendorId":4318}}

[aaronliu0130]

I think we need the logs for when you upscayl something.

[Hikodi]

Next problem:

Ad first I installed 2.11.5 and made a update to 2.15.0. It works with some problems like this in this thread.

Now I deinstalled all and would make a installation of a pure 2.15.0.

This is impossible, because MS Defender find a Trojan Horse Trojan:Script/Phonzy.A!ml in file: C:\Users\User\AppData\Local\Temp\nstF33C.tmp\app-64.7z and block installation.

The old version 2.11.5 I can install without Defender-warning.

[NayamAmarshe]

Next problem:

Ad first I installed 2.11.5 and made a update to 2.15.0. It works with some problems like this in this thread.

Now I deinstalled all and would make a installation of a pure 2.15.0.

This is impossible, because MS Defender find a Trojan Horse Trojan:Script/Phonzy.A!ml in file: C:\Users\User\AppData\Local\Temp\nstF33C.tmp\app-64.7z and block installation.

The old version 2.11.5 I can install without Defender-warning.

Try downloading the exe again. It should work.

[aaronliu0130]

Let's track the latter part in #1104 and the output folder thing in this issue

[Hikodi]

@aaronliu0130 You had not to change the title.

I ´ve yesterday downloaded new 2.15.0, deinstalled today 2.11.5 an made a new installation of 2.15.0. Now MS Defender make no trouble, but the result is the same:

• I can´t see any picture in the output-folder. 2.15.0 says, the folder is empty, but other folder-manager show me the files
• After closing and restart 2.15.0 the output format is again png, not how I wish and vote jpg.

Both problems are not in 2.11.5. That ´s why I got back to 2.11.5.

Please give me a sign, if you publish 2.16 or higher without the problems from 2.15.0

[aaronliu0130]

@Hikodi Please file a new issue for the first point and watch #1104 for the second point. And we would appreciate it if you would send the Upscayling logs for this issue.

[github-actions[bot]]

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. If this is still happening, please reply to indicate so.