Jump to content

mrmat01

Members
  • Posts

    228
  • Joined

  • Last visited

Everything posted by mrmat01

  1. MATY #1 F-16 SIM AB Is the .diff before the update It can be found here Post #3 https://forums.eagle.ru/showthread.php?t=281897
  2. Requested files MATY #1.1 F-16 SIM AB This is the .diff I had to bind today after the update. MATY #1.1 F-16 SIM AB.diff.lua dcs.log
  3. Please use picture as a reference. After opening the options menu & selecting the controls tab. Step 1. Highlight something in the column. Step 2. Click on Load Profile. Step 3. Check to make sure it is loading the profile from the correct location. Step 4. Select the profile you want to load. Step 5. Click ok. I hope this is helpful.
  4. No worries I will load it up with a step by step later this evening as I'm out of the house at the moment. To be honest I just load them up like everyone else. Open adjust controls highlight a control binding & click on load controls. Pick the file & ok. nothing abusive about it. I'm not the only one that has this issue. I'm just the only one that says something. Jabbers has even mentioned it in his video's.
  5. This is what I get after I load my controls .diff
  6. The whole control debacle needs an over hall. None of my saved .diff files are combatable with the latest update. eg: will not load as they would before the update.
  7. This happens every time there is an update. :mad: :censored: :furious: I just jumped into my F-16 in OB. Went to take off no thrusts no aileron none of the buttons are bound. So I thought ok Ill try & load from my controller profile (.diff ) & what do you know that doesn't work either. In fact it makes it worse. I know it worked before the update because I tried it. Now all I'm getting is axis bound to the wrong axis & the usual duplicate controls. So in short I have to spend the next hour going through my controls & rebinding them. When is ED going to fix this PLEASE.
  8. :wallbash::wallbash::wallbash::wallbash:
  9. I have already mentioned everything is up to date. I'm sorry but his sentence wasn't helpful. I did not understand what he was asking/saying. I am describing my issue as best as I can with as much information as I can. Yes you did give me a suggestion on how to fix it temporarily by renaming a core file. The next time there is an update I have to do it again. :wallbash:
  10. Gday Digga If ya need an Aussie voice be happy to help. I have a pretty ocker accent.
  11. No that’s not what I want. I want the .diff files to be compatible between stable and OB. If I have spent 30min-1 hour setting up & bindings my control I would like to just copy it over or load it from either the saved games stable or OB folder.
  12. Being patronizing kind of annoying.:noexpression:
  13. ?? I'm sorry but that statement doesn't make much sense. Its pretty obvious that you are not interested in acknowledging the issue. I'm just reporting a issue I am having & it just seems that it is being completely dismissed.
  14. I think what I'm trying to say maybe getting lost in translation.:( Thank you for you help. :thumbup: They are not compatible for me. It would be a lot simpler not so time consuming if you didn't have to bind your controls twice & be able to copy your .diff files from your saved games dcs to your saved games openbeta & it just worked.
  15. Ok I'm sorry but it still isn't compatible. Different windows version ?? Impossible my stable & OB are on the same PC Different drives & everything is up to date. I wish I could afford two PC's that would run DCS. Not wrong file name same file (MATY #1 F-16 SIM AB.diff) tested multiple times. Please see attached images of example as to what is happening. The 1st pic is of .diff file loaded from F:\Mat Saved Games\DCS.openbeta\MY CONTROL SETS The 2nd is loaded from F:\Mat Saved Games\DCS\MY CONTROL SETS Notice in the 2nd pic the duplicate & missing control bindings. Tested while running in OB & then stable. got the same result just visa versa. This is a simple .diff file (control bindings) there should not the compatibility issues that I'm experiencing even when stable & OB are different versions. MATY #1 F-16 SIM AB.diff.lua
  16. Ummm the control bindings .diff files aren’t part of what gets tested in OB they are just control bindings. They should be compatible between stable & OB just for simplicity reasons. :noexpression:
  17. The .diff files are not combatable between OB & stable I copy my .diff file from my stable saved games to my OB saved & OB just doesn't recognize them.
  18. Thanks for Your help but its the .diff files I'm having the issue with (control files) They are not compatible between stable & OB. & I can not understand for the life of me as to why. I should not be having to rename the input folder. It should be a simple case of having one set of .diff files for OB & Stable.
  19. I feel your pain mate. Yes we are paying customers. Since the last update thing have been much better for me. So I thank ED for their hard work & getting some of the issues fixed. But I had a month of unplayable OB DCS & that meant No P-47.
  20. Take it easy mate. It is fixed with out running the repair. By removing the mod that was stuffing it up. It was actually a mod I forgot I had installed. Like I said in my 2nd post. The very few mods I do run are very well tested & are updated by the creator. As for the repair tool. I have used it in the past & for me it creates the very tedious task of having to go through all of my control settings & deleting all of the duplicate controls & settings my curves again. So that post on hoggit regarding the repair tool potentially wiping the hard drive was just a load of crap then? Well I’m not willing to take that risk.
  21. Hi guys Im not sure if it has been reported but the 540 mod kills the encyclopedia in the mission editor. It just crashes too a black screen if you have the mod installed. You have to shut down DCS via the task manager.
  22. Thank you. I do have the EDGE 340. It just seems to be the generic answer from ED remove mods & run a repair. I don't like running the repair as it can create more issues than you had before you did it.
  23. Thanks works fine in OB :confused: Worked fine last time I flew the F16 in stable a couple of months back.
  24. I just tested in OB & all works fine.
×
×
  • Create New...