Closed Doperr closed 5 years ago
Did you click the button with bf1 open?
Did you click the button with bf1 open?
Yes. Have tried it both (bf1 open and close)
And you get the same exact error in both cases? That log looks like you probably had it open. Do it with it closed and send me a log of it still fails.
And you get the same exact error in both cases? That log looks like you probably had it open. Do it with it closed and send me a log of it still fails.
here is the latest crash logs Open BF1 : https://pastebin.com/L64XXUZj Close BF1 : https://pastebin.com/Yj8HxPi5
Seems like I know the problem that LogitechLed.dll used by LGS. When I close LGS I can patch led sdk but keyboard no light while in BF1 so I open LGS again but also no light too. so I patch again and then it crash again. Maybe LGS cause this?
When you patch it should send lights to aurora, but it wont send them to LGS anymore. Have you restarted your system after patching?
Also, if you want lgs to get the lights again, go into C:\Program Files\Logitech Gaming Software\SDK\LED\x64
, delete LogitechLed.dll
and rename LogitechLed.dll.aurora_backup
, deleting the aurora_backup part. Repeat this for C:\Program Files\Logitech Gaming Software\SDK\LED\x86
.
Again, as the wrapper makes light go to aurora, it shouldnt be needed.
When you patch it should send lights to aurora, but it wont send them to LGS anymore. Have you restarted your system after patching?
Also, if you want lgs to get the lights again, go into
C:\Program Files\Logitech Gaming Software\SDK\LED\x64
, deleteLogitechLed.dll
and renameLogitechLed.dll.aurora_backup
, deleting the aurora_backup part. Repeat this forC:\Program Files\Logitech Gaming Software\SDK\LED\x86
.Again, as the wrapper makes light go to aurora, it shouldnt be needed.
WOW man it works. After follow your instructions it's work like charm. Thank you very much man!!
I'll close topic now
How often does this problem occur?
Always
Please describe the steps to reproduce this issue:
The issue can be reproduced by doing following steps:
What is the version of Aurora you are experiencing this issue with?
beta0.6.3
Does the previous version of Aurora have this issue?
idk
Please include any logs, screenshots, or files that are related to this issue:
Crash logs [ https://pastebin.com/kuJSQjNy ]