Page 1 of 1
"you can not edit controls when backup sights are deployed"
Posted: 2018-05-08 14:37
by winject
Can't change any controls in game anymore no matter if you're in the main menu or already playing, I had to run bf2 in order to change it there and then finally swap the control.con file within the pr profile folder.
Re: "you can not edit controls when backup sights are deployed"
Posted: 2018-05-08 18:10
by Mats391
Try enabling+disabling BUIS on any server and try again
Re: "you can not edit controls when backup sights are deployed"
Posted: 2018-05-08 21:07
by winject
not working unfortunately
- Windows 7 - Home Premium (x64)
- Latest .net framework
- tried both windowed and fullscreen
- tried with perf beta on/off
- admin session
I disabled all antivirus and antimalware software as well.
EDIT:
Even on local account it won't enable controls.
Re: "you can not edit controls when backup sights are deployed"
Posted: 2018-05-09 12:40
by Mats391
Can you post your Controls.con? Something in there might cause it.
Re: "you can not edit controls when backup sights are deployed"
Posted: 2018-05-19 12:02
by winject
[R-DEV]Mats391 wrote:Can you post your Controls.con? Something in there might cause it.
Controls are the default one...
Issue resolved by joining a local server hosted on another machine. For some reason I can now edit controls without any problems even online
Re: "you can not edit controls when backup sights are deployed"
Posted: 2018-05-19 17:44
by Mats391
Weird. Let me know if it happens again.
Re: "you can not edit controls when backup sights are deployed"
Posted: 2018-05-21 09:37
by winject
[R-DEV]Mats391 wrote:Weird. Let me know if it happens again.
I'm going to install Project Reality on 12 different computers in my local internet café, I'll let you know if this issue will pop up again.
Re: "you can not edit controls when backup sights are deployed"
Posted: 2018-05-23 06:57
by winject
[R-DEV]Mats391 wrote:Weird. Let me know if it happens again.
Sorry for posting twice in a row but I finally installed PR on different computers and the issue showed up again. All the computers have the same components and software so I don't know why this is happening on only 3 of them.
Reinstalling the latest .Net framework and joining a local game (with online) account resolved the "bug" again.