Jump to content

funkyfranky

ED Closed Beta Testers Team
  • Posts

    2523
  • Joined

  • Last visited

  • Days Won

    4

Everything posted by funkyfranky

  1. I am hoping for a good "controller infrastructure" for sim pit builders and simple button boxes, i.e. having axis for lights etc, CW/CCW options for rotaries, up/down for multiposition switches, ... :) This would greatly enhance the fun for people who don't like clicking with the mouse in the cockpit. For example, Belsimtek did a beautiful job in the F-5E here but some other modules do not shine so much in this department. It does not necessarily have to be already present in the CONTROLLER GUI but would be nice to have at least in the clickabledata.lua. If possible, any word from devs and/or testers in how far this will be available at early access already would also be highly appreciated :thumbup:
  2. Brilliant :thumbup: Great new feature I always wanted to have. Mach loop here we go :)
  3. Hollywood, here is the script I talks about. Thanks a lot for you help :thumbup:
  4. Tja, das ist zur zeit ein bisschen so wie mit Schrödingers Katze :D Sobald Du nachguckst :spam_laser: (oder auch nicht).
  5. Im Moment sind OB und Release identisch. Da macht das Kommando bei dem updater wahrscheinlich nix ;)
  6. You can always check the current versions here http://updates.digitalcombatsimulator.com/ As BN said, there is stuff coming "very soon". So we'll see :)
  7. Point is, there was no patch. Right now, the stable identical with what we had as openbeta for the past two weeks.
  8. Hi Hollywood, first thanks for this great software :thumbup: I love the fact that it doesn't use the menus and the documentation is also very well written. I have a small problem though. It seems VAICOM does not detect my correct DCS folder. So when I start DCS the current module is not recognized, easy comms is assumed to be on even though it is not etc. Refreshing the settings on the PTT tab does not work and instead shows the DCS radio menu. So here is the output of the log: VAICOM PRO logfile DCS World version 2.5 not found. DCS World installation found: version 2.5 OpenBeta Using Registry entry for 2.5 OpenBeta [color="Lime"]DCS World installation path = E:\Games\DCS World OpenBeta[/color] Saved Games folder = D:\Users\frank\Saved Games\DCS.openbeta Installation OK: Export.lua contains up-to-date file identifier. Installation OK: VAICOMPRO.export.lua contains up-to-date file identifier. Installation OK: RadioCommandDialogsPanel.lua contains up-to-date file identifier. Installation OK: speech.lua contains up-to-date file identifier. DCS World version 2.2 OpenAlpha not found. DCS World installation found: version x.x Steam install found for x.x [color="Red"]DCS World installation path = C:\Program Files (x86)\Steam\steamapps\common\[/color] Saved Games folder = D:\Users\frank\Saved Games\ Installation OK: Export.lua contains up-to-date file identifier. Installation OK: VAICOMPRO.export.lua contains up-to-date file identifier. Installation OK: RadioCommandDialogsPanel.lua contains up-to-date file identifier. Installation OK: speech.lua contains up-to-date file identifier. Checking VA profile. Updating keywords database... Success. Loading keywords database... Success. Loading F10 menu items... Imported menu items Adding 0 imported ATCs. Adding 0 imported menu commands. Building master keywords table... Success. Building master labels table... Success. No new DCS modules to import. Ready for commands. PTT: Client sent update request PTT: Client sent update request PTT: Client sent update request PTT: Client sent update request Updating config file. Updating config file. The green path shows the DCS version I'm running. However, VAICOM also detects a steam version of DCS (red). It's strange because I never had a steam version of DCS installed. Can I somehow remove that wrong DCS version? Or what would you say is the reason why VAICOM does not detect the used module? Edit: Okay, seems to work with the "include custom folders" option :)
  9. https://forums.eagle.ru/showpost.php?p=3413307&postcount=8
  10. Grodlund, sometimes it is just a small thing. Send me the mission which does not work and I'll have a look.
  11. Not yet. It's basically finished. I just need to polishing and test a few things before the "official" release :) Yeah, CAM is stunning! And RAT and CAM mix really well :D
  12. Good question. You don't have to delete and remake the whole trigger. But you need to open and reload the script file (right hand side). And then save the mission again(!) each time you make changes to your mission script file.
  13. Hi Snacko and thanks :) Your code looks absolutely fine. And if you get one group working, you've already mastered the most difficult part :thumbup: Please attach the mission (and if possible DCS log) file(s) you're using. Then I can figure out where things go wrong. (Having multiple groups should be no problem per se. I do this all the time.)
  14. Now that you mention it ;) Not solved (that's on ED) but circumvented I'd say. We are working on the next stable MOOSE version that will contain RAT 2.2 :)
  15. Silvern, the code looks fine. Could you provide the mission file please? Also, do you use a RAT version which already has this feature? This would be the one included here https://forums.eagle.ru/showpost.php?p=3393258&postcount=121
  16. Ach ja, und ich gehe davon aus, dass Du das gemacht hast? Siehe troubleshooting Liste https://forums.eagle.ru/showthread.php?t=172160
  17. Passiert das nur bei DCS oder auch bei anderen Spielen? Und in DCS bei jeder Mission oder nur manchmal? In der Logdatei ist kurz vor dem Absturz ein Eintrag 2018-03-23 22:38:04.525 ERROR Trigger: can't execute trigger, err:"[string "?"]:1: bad argument #1 to 'loadstring' (string expected, got function)" Irgendwelche Scripte/Mods geladen?
×
×
  • Create New...