跳转到帖子

myxomytosis

Members
  • 帖子数

    10
  • 注册日期

  • 上次访问

最新回复 发布由 myxomytosis

  1. @Trini86 I tried Copying M12 to Desktop, editing in the Mission Editor, and pasting it back into the appropriate Campaign Folder. I removed the Lantirn and GBU's from Tiger flight, added one MK.84, and set the Bombing Task to "Auto". For me, that still didn't fix the no comms issue. If you could send me your fixed .miz, I'd appreciate it. 

  2. On 7/14/2022 at 12:55 PM, Trini86 said:

    I found a fix for mission 6… But it requires editing the mission  file in your .miz file…..

     

     Since having the F14 set to drop as guided breaks the comms I changed it to auto and I had to put dumb bombs on them and that seemed to fix it….. This also fixed mission 12 which has the same issue. If you want the mission file send me a message and I’ll send it to you. If your not sure about what I’m saying I’ll put instructions with it when I send it.😊

     

    Thanks for this. I'll give this a try.

  3. Today, I updated CTS to the latest version, (2.430), as well as updated DCS to v. 2.5.6.45317. Additionally, I purchased the F-16C module, after the free-trial period. Currently, when I build and run a CTS script for the F-16C, a constant "h" key input is being sent from my Warthog. I am able to open DCS by running as administrator, and this behavior temporarily stops.If I kill the TARGET app, the behavior stops. It seems that other aircraft profiles do not exhibit this behavior. I've tried restarting, and unplugging the HOTAS, but the behavior re-occurs, whenever I re-build the F-16C script and run. In light of world-events, i realize there are for more pressing matters, I just wanted to bring this to your attention. Thanks!

×
×
  • 创建新的...