StarLiner

Why would you destroy a bride?

Well folks, it's not the news we wanted to hear but it seems like this campaign may be lost to the sands of time.

Still working flawlessly. My purchase all those years ago still paying off today. One thing I'd love to see is, you know how when you open up the Maps tool and it shows speed, altitude, heading? Something like that, but just that, would be really nifty. Like just flight telemetry.

Is there any chance of an update to this @baltic_dragon? I know the MiG 19 campaign probably isn't a profitable thing to work on with your finite time, but it would be lovely to have a quality campaign to go with the module for how nifty the airplane is. Thank you again for your time!

Howdy! I'm at my wits end after trying to troubleshoot this for a couple hours. I was playing DCS just an hour before, then I sat down to play again and it unfortunately crashes. This is right after I hit to launch button in the launcher. I've nuked my Mods folder, run a cleanup and slow repair, but no dice. I'd love any help. And if I do end up doing a complete reinstall, will my keybinds transfer over or do I need to save those somehow? Here is my attached log file, I would greatly appreciate any help sorting this out. Thank you for any advice! dcs.20241101-050003.log

So, Baltic Dragon last said he may need to talk to Razbam, and Razbam is saying to talk to Baltic Dragon. I let Razzy know about BD's comment from last year but they didn't seem to be aware of it. Here's hoping this can be fixed soon!

Howdy! Has there been any update on this issue @baltic_dragon? Thank you again for all your work!

Unfortunately this might be out of the scope of modding, or too niche to bother with. Hopefully one day ED will #bless us.

+1, hope this gets looked at soon.

Any chance of an update to this status of this bug @BIGNEWY? It's pretty easy to tell there's an issue with the slip indicator when say, firing rockets.

The Cyrano IV IVM Radar was supposedly quite interesting. It had both A2G and A2A modes, Track while scan, and some form of look-down filter using MTI. It had three different azimuth modes, iirc a 60, 30, and 10 degree mode but I could be misremembering numbers. It also had no form of IFF interrogator outside of some specific model. It had both low and high altitude modes of operation. How much of this is modeled we don't know yet, Arges has been tight lipped about the radar. Hyped to see what kind of modeling they do.

Unfortunately, whether you assign / or Ralt + / to a Voice Attack commands, there's a 50/50 chance the command won't execute properly and the comms menu won't pop up. I understand that Vaicom is meant to serve a complete, total replacement of the comms menu, but there's just too many edge cases where that isn't practical. For example, on Enigma's Cold War, I rely on the comms menu to use the text based Overlord Bot commands. Or to load troops, or find CSAR beacons. I have voice attack commands bound to all of these, but they tend to fail due to this Vaicom bug, which seems to be reported in quite a few threads.

According to the manual, when the AWACS page on the Interactive Kneeboard fills up, new commands should overwrite the ones at the top. This doesn't appear to be happening, and the last command seems to be cutoff as well. See screenshot. Anybody else experiencing this?

Something about Vaicom seems to stop the comms menu (the one normally accessed with /) to stop reliably showing up. A few people in this thread seem to be experiencing it. This interferes with commands I have to say, load troops or check other F10 options that rely on that comms menu.

Howdy! May we have an update for this? The Mig21 still unfortunately doesn't produce a lock tone. I posted the issue on Mag3's bug tracker, and they said the issue is ED related. This is quite an annoying bug on cold war servers in that it renders one of the F5's (and soon to be the Mirage's) main sensors useless. The bug also breaks 'Jam on Lock' events in the mission editor for this aircraft. With the Mirage coming out soon, we'll finally be able to have interesting, crappy fox 1 fights. Unfortunately, the mig will still be able to stealth lock the Mirage.

Ah, so this is what has been wrecking havoc on my stock Voice Attack scripts. I'm probably going to have to just get rid of Vaicom unfortunately, it seems to be causing a few issues with normal VA operation.

In addition to the AWACS page not adding new messages once it fills up, it seems to cut the last message off. This is a picture showing wat I mean. Also note how the new message in the upper left does not appear on the page.

Has anybody run into an issue with the AWACS page not writing down new callouts when the page fills up? The manual says it should start overwriting the top, but that doesn't seem to be happening.

I've heard five different answers from five different people. Some insist it will have one, some insist it won't. So what's the skinny, will we have the ability to independently IFF or will it be Real VID Hours?

This is low hanging fruit that would really earn a lot of good will with the community. I hope ED takes a closer look at this issue.

Quick update, two months ago Mag3 posted the following on my bug report: "We know about this issue for some time now. It appears to be ED related." Unsure if that means ED is the one who has to fix this, or if they have to communicate with eachother to get it fixed. Would love a follow-up on this, as it really takes some of the fun out of cold war engagements.

I did a little more digging to see if anybody else had tried something like this, and @mcfleckran into the same issue trying to do the same thing to the hornet before it was officially added: I wonder if changing whatever they did to the Hornet to apply to other aircraft is within the scope of modding.

Bumping in hopes of getting noticed. I think changed to Jester's IFF accuracy, especially when STT'ing, is something most people would really like to see improved.

Did you know that many DCS Aircraft have a Declare command they can access through the AWACS? Well, actually it's just the Hornet, Viper, and FC3 aircraft. You lock something with your radar and AWACS will declare friendly or hostile. Very cool, but wasted on aircraft with datalink and IFF. No third party aircraft has this feature, not even the F14. So I was curious if the Declare function could be modded into to other aircraft for fun and immersion I looked through the comm lua for a few modules with the feature, and found a line that said Radar = true. For the F14 and F5 it said Radar = False. So, I changed the line to true on both planes, loaded the mission editor, and it almost worked! Declare appeared as an option within the comms menu where it hadn't before, but when you lock a plane and try to use it, no audio plays and no interaction with the AWACS occurs. Other commands like bogey dope work just fine. Any idea what's happening here? I'm guessing that fundamentally the radars on other aircraft don't work like FC3 and 18/16 radars, so they can't be made to work. But if anybody has ideas, I'd love to hear it.

Maybe whoever on the team is responsible for the F18's radar implementation can explain their viewpoint? Because this doesn't seem to jive with what other sources and experts here say.