Jump to content


  • Content Count

  • Joined

  • Last visited

  • Medals

Community Reputation

1 Neutral

About Barthanol

  • Rank
  1. No I haven't tried the dev. branch myself. I figure it may cause version compatibility issues with joining servers which are not running it however I do not know if that is a fact, let me know if that is the case. I was able to fix my problem as described above so I didn't need to delve into that solution but I am happy to hear that Bohemia knew of the issue & addressed it. Kind of wish they chose a hotfix option to push that fix through though as most people rarely browse the forums for solutions & aren't even aware of the dev. branch option as a fix for certain issues. Not sure why my fix didn't work for you, you clearly have an understanding of what I was doing in my fix. One thing I could attribute this to is perhaps your changes were not saved. Did you open up the file again after your edit & see if the changes remained in effect? Did you make sure the Arma launcher wasn't opened when you made your edit? I doubt it was a read only issue because you wouldn't have been able to save your changes in the first place. Another possible fix is to change the edit from disabled to enabled instead of custom & or simply remove that controller section completely & let Arma rebuild it & detect your device on it's next startup. However I guess these further alternative fixes are kind of moot since the dev. branch fixed your issues anyhow. Glad you you got it working though & perhaps we'll enjoy some gaming in Arma in the future some time. Best wishes!
  2. No need to be sorry, You probably didn't do my fix properly or you have an unrelated problem. Seeing how you did not post in this thread until now & describe your specific problem, I am unable to help you any further. However the guy who posted after you reveals that the new dev. branch patch does fix the ability to enable & disable joystick/controller problems. So try that or elaborate on your specific problem & if it's similar you can send me your profile file & i'll try and fix it for you. Good luck!
  3. I fixed the problem by editing my username.Arma3Profile file (username is your username)within the Arma 3 folder in my Documents Folder. I simply searched for my joystick which is a Thrustmaster Cougar & edited the mode field from disabled to custom. Hope this helps others out, waiting for help from Bohemia is like waiting for the next coming. }; class Joystick3 { guid="80B12F80-3247-11E4-8001-444553540000"; name="hotas cougar joystick"; offset=768; isXInput=0; sensitivity[]={0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0}; deadZone[]={0.07,0.07,0,0.07,0.07,0.07,0,0}; steepness[]={1,1,1,1,1,1,1,1}; mode="Custom"; analogClickHigh=0.40000001; analogClickLow=0.2;
  4. Apparently enable & disable features for joysticks & pedals & controllers no longer works since last patch. Making new profiles, deleting docs folder & even clean install's will not fix it. The questions is when will Bohemia realize this & more importantly, fix it???
  5. Folders will always remain Read-only, so no need to remain bewildered as to why it always goes back to being re-checked Read-only. This is why it says right next to the Read-only checkbox, (Only applies to files in folder). What matters is that when you do uncheck read only, that the files within the folder are no longer marked Read-only. That being said... the suggested Bohemia fix above is wrong. It is not a problem due to a read only file.