Jump to content

Sedlo

DLC Campaign Creators
  • Posts

    2008
  • Joined

  • Last visited

Everything posted by Sedlo

  1. I'm seeing this also with eject events, too... Something has totally screwed up.
  2. Easy Communications is not enabled in this campaign.... You'll have to use the Comm Switch-COMM1 and Comm Switch-COMM2 bindings... Right Alt + \ and Right CTRL + \ respectively.
  3. You can create a separate folder within the miz file and refer to that location that in your scripts. Allows for bulk additions of sounds, images, etc via Windows drag/drop cut/paste
  4. hey Dave! Not at my computer ATM but wait until you get pushed to Marshall. It can range from 20-45 miles out. cheers, Sedlo
  5. It’s fictional? A what if, if it were. There are Tomcats because there are no Super Hornets. There are Sparrows in the first mission because… well, because. Don’t worry, AIM-120 appears very shortly.
  6. Ah, ok... Just saw the red waypoint lines and thought that might be it... The only thing I can think of right now is that: 1. Confirm the Set Frequency for the AWACS has AM chosen as the modulation. (I've seen it get switched before for reasons I cannot understand) 2. Check to see if there is any line of sight / distance issues between the player and the transmission source.. ... Or maybe push the set frequency a second before the transmission happens?
  7. Is your Viper on the Blue coalition? For some reason, blue cannot hear red and vice versa.
  8. Hey Nikoel! Glad you're enjoying the campaign so far! OK, for mission 10... For the landings in VR, yeah, I hear you. There isn't anything I've done with mission 10 to make the carrier light up, it's just the weather conditions I guess were such that the core game put the lights on. Is there a particular mission you're having issues with? I have tested it in my Oculus 2 and haven't had that bad of a time with it, though I have had to reference the TACAN and BRC sometimes to get a good run into the initial. I can try and tweak the weather / time a bit maybe, what mission are you seeing the problem in? Noted about the loadouts, I'll have a look. In terms of mission 9.... Thank you for the feedback, I'll see what I can do. Sedlo
  9. No worries at all!
  10. Argument 285 is the cabin altitude gauge.... null
  11. You could use the standby altimeter with a cockpit argument in range trigger... It could be a little more lenient to altitude variables... Try Cockpit Argument In Range 219 and the Range like 0.690 to 0.710... That will trigger it from about 6900 ft to 7100 ft. Add argument range 220 from -1 to 0 to ensure this only fires at 7000ft and not 17,000, 27,000, etc. So yeah, two conditions Cockpit Arguement in Range 219 0.690-0.710 and Cockpit Argument in Range 220 -1 to 0
  12. 3.103 now up! Added MB-339 to player and adversary roles. Added F-15E as advesary. Fixed script error with neutral F-5E scenario. Download here: https://www.digitalcombatsimulator.com/en/files/3326657/
  13. Thank you for the kind words, @Spirale! It really means a lot to me when I hear that people have enjoyed the campaign. The next campaign will take some time to come out, but I think you will enjoy it!
  14. Today I learned of the passing of Olivier Balland, known as Olivier Gaming or HODGY... Olivier kindly recorded the lines of MAGIC for mission 12 in Bold Cheetah, and helped me a lot in Beta Testing. In the DCS community, he was a star, helping so many people with his tutorials, livestreams and 1 on 1 help. I am very sorry to hear that he is gone. He certainly won't be forgotten. Bold Cheetah is dedicated in his honour.
  15. I think it used to be called Strait of Hormuz...:-)
  16. No idea. I imagine it has to go through an external hook, similar to how SRS can read some of these parameters and indications.
  17. 3.102 now up... fixed potential error with eject script in certain situations. DOWNLOAD: https://www.digitalcombatsimulator.com/en/files/3326657/
×
×
  • Create New...