cFosSpeed Logitech display detection improvement request
2 posters
Page 1 of 1
Re: cFosSpeed Logitech display detection improvement request
I'm glad to hear the problem is gone now.
Nevertheless, I'll forward your request/suggestion regarding performing some retries before giving up on a possible Logitech device.
Nevertheless, I'll forward your request/suggestion regarding performing some retries before giving up on a possible Logitech device.
Quiss- cFos Admin
- Anzahl der Beiträge : 3
Anmeldedatum : 2017-06-21
Re: cFosSpeed Logitech display detection improvement request
Thanks for your answer!
Well, pretty sure it was being delayed.
Sometimes did work, others not.
Right now the issue is gone...
My Win10 install got corrupted and I just had to reinstall everything from scratch
But indeed would be better to have at least a couple of retries.
I always had success by forcing it manually on the Logitech display.
Well, pretty sure it was being delayed.
Sometimes did work, others not.
Right now the issue is gone...
My Win10 install got corrupted and I just had to reinstall everything from scratch
But indeed would be better to have at least a couple of retries.
I always had success by forcing it manually on the Logitech display.
ManniX- Newbies
- Anzahl der Beiträge : 10
Anmeldedatum : 2018-03-16
Re: cFosSpeed Logitech display detection improvement request
Hello,
I am a bit late (found your post while searching for something related), but maybe I can still help.
I'm running a Logitech G13 here and it works fine with "startup_delay=25".
Are you sure the delay is actually executed? You then should find lines in trace.txt (C:\ProgramData\cFos\cFosSpeed\trace.txt) similar to these:
181302'732 ------ cFosSpeed (x64) daemon v10.26.2312 starting ------
181302'732 OS: Windows 10 Pro Multiprocessor Free (x64) (4 procs) v10.00.17134, LangId 0407
...
181303'075 startup delayed by 25 secs
I am a bit late (found your post while searching for something related), but maybe I can still help.
I'm running a Logitech G13 here and it works fine with "startup_delay=25".
Are you sure the delay is actually executed? You then should find lines in trace.txt (C:\ProgramData\cFos\cFosSpeed\trace.txt) similar to these:
181302'732 ------ cFosSpeed (x64) daemon v10.26.2312 starting ------
181302'732 OS: Windows 10 Pro Multiprocessor Free (x64) (4 procs) v10.00.17134, LangId 0407
...
181303'075 startup delayed by 25 secs
Quiss- cFos Admin
- Anzahl der Beiträge : 3
Anmeldedatum : 2017-06-21
ManniX- Newbies
- Anzahl der Beiträge : 10
Anmeldedatum : 2018-03-16
cFosSpeed Logitech display detection improvement request
I'd like to ask an improvement on the Logitech display detection.
The parameter startup_delay=x never really worked for me.
Most of the times the detection fails.
I have to manually trigger the detection, it's very annoying.
Especially cause I have a G15 keyboard and the skin is unusable on the monitor.
Would be possible to have it not delay by x seconds but retry every x seconds until it's successful?
Thanks
The parameter startup_delay=x never really worked for me.
Most of the times the detection fails.
I have to manually trigger the detection, it's very annoying.
Especially cause I have a G15 keyboard and the skin is unusable on the monitor.
Would be possible to have it not delay by x seconds but retry every x seconds until it's successful?
Thanks
ManniX- Newbies
- Anzahl der Beiträge : 10
Anmeldedatum : 2018-03-16
Similar topics
» Dashboard request
» Feature Request
» Program Priority List improvement - Anybody knows what the application ficus-ui.exeis?
» [feature suggestion] Addition of new display light APIs
» Mal ne Frage... der windows service spd frisst immer cpu cycles auch bei deaktiviertem shaping
» Feature Request
» Program Priority List improvement - Anybody knows what the application ficus-ui.exeis?
» [feature suggestion] Addition of new display light APIs
» Mal ne Frage... der windows service spd frisst immer cpu cycles auch bei deaktiviertem shaping
Page 1 of 1
Permissions in this forum:
You can reply to topics in this forum
|
|