Posts: 10.556
Threads: 57
Joined: May 2017
Normally, installing dev over existing version and resaving the defaults should work fine.
(Otherwise it is listed in the changelog, or I'm not aware of a problem.)
Cu Selur
----
Dev versions are in the 'experimental'-folder of my GoogleDrive, which is linked on the download page.
Posts: 68
Threads: 11
Joined: Aug 2024
(15.09.2024, 18:00)Selur Wrote: Normally, installing dev over existing version and resaving the defaults should work fine.
(Otherwise it is listed in the changelog, or I'm not aware of a problem.)
Cu Selur
Yeah I don't think that was because of that. I just finished uninstalled and reinstalled Hybrid, but the issue remains. Everytime I close Hybrid in full screen, it starts without Windows bar.
Screen capture
Posts: 10.556
Threads: 57
Joined: May 2017
It switches to fullscreen, but switched back so normal view, I thought I had fixed that in the Hybrid_dev_2024.09.15-155137 dev.
=> can't reproduce this here, will look at it some more during the week.
(maybe a complete rebuild of Hybrid on my side will help too, strange)
Cu Selur
----
Dev versions are in the 'experimental'-folder of my GoogleDrive, which is linked on the download page.
Posts: 68
Threads: 11
Joined: Aug 2024
(15.09.2024, 18:13)Selur Wrote: It switches to fullscreen, but switched back so normal view, I thought I had fixed that in the Hybrid_dev_2024.09.15-155137 dev.
=> can't reproduce this here, will look at it some more during the week.
(maybe a complete rebuild of Hybrid on my side will help too, strange)
Cu Selur
OK, very strange indeed... If it can help, i'm running Windows 10 Pro version 22H2
Posts: 10.556
Threads: 57
Joined: May 2017
I'll try to look at it next week.
----
Dev versions are in the 'experimental'-folder of my GoogleDrive, which is linked on the download page.
Posts: 68
Threads: 11
Joined: Aug 2024
Is there a way to flush HybridDebugOutput.txt after X days ?
In only one week, the .txt file is more than 700MB (!)
Posts: 10.556
Threads: 57
Joined: May 2017
No, the debug output is not meant to be kept on all the time
----
Dev versions are in the 'experimental'-folder of my GoogleDrive, which is linked on the download page.
Posts: 68
Threads: 11
Joined: Aug 2024
(26.09.2024, 12:07)Selur Wrote: No, the debug output is not meant to be kept on all the time
Hmm, but since we don't know when a bug will occur, isn't it more logical to keep it enabled ?
Posts: 10.556
Threads: 57
Joined: May 2017
No, depending on your input 700MB debug output can come from one source.
If you have a bug, that you can't reproduce, it's a bug I can't fix.
Cu Selur
----
Dev versions are in the 'experimental'-folder of my GoogleDrive, which is linked on the download page.
Posts: 68
Threads: 11
Joined: Aug 2024
(26.09.2024, 12:13)Selur Wrote: No, depending on your input 700MB debug output can come from one source.
If you have a bug, that you can't reproduce, it's a bug I can't fix.
Cu Selur
OK.
Another thing that I noticed, is that jobs that are removed from queue are not deleted from temp folder.
Sometimes I start a job just to see the estimated bitrate and/or file size, and then remove it (and it can also concern failed jobs)
Is this something that you would change ?
![[Image: 2024-09-26-15-01-45-NVIDIA-Ge-Force-Overlay-DT.png]](https://i.ibb.co/bXqVCrb/2024-09-26-15-01-45-NVIDIA-Ge-Force-Overlay-DT.png)
