wraith444

I'm not OP, but I've experienced similar issues and can reproduce consistently. Attached miz and trk for demonstration, as well as an export of the DTC. Steps taken: 1.) Configured DTC with all auto programs set to NONE for all emitter types, set to load automatically on mission start. 2.) Spawned in, sent wingman out to spread formation. 3.) Set countermeasures mode to Semi. 4.) Sent wingman to trail formation. Once my wingman popped up on RWR while in Semi mode, I was prompted to counter (audibly, despite setting REQCTR to unchecked in the DTC options; Unrelated but thought I'd mention). I acknowledged with CMS aft at that point and it fired my Bypass program. CMS possible bug.miz possible cms bug.trk Possible CMS bug.dtc

Oh, I see now! When I checked last time I didn't even see the "File" button so when I looked at Darkman222's screenshot I thought it was from the mission editor... Thank you both for your help, that does exactly what I was hoping for!

Is there a way to import a personal DTC after connecting to a server? Like say I want to use my own custom DTC to configure my countermeasures on a public server... From what I saw when I was playing around with it yesterday, the only options in the in-game DTC interface are the cartridges made available by the mission maker.

I generally prefer to keep a handful of things (CMDS manual programs for example) pretty much the same from one mission to the next, so with that in mind it would be nice to save my personal preferences for those kinds of things to a DTC file that can be used in all missions, regardless of whether the mission maker adds it to the mission file in advance, or can be used to quickly populate partitions in the manual DTC editor that comes up when you pull up the DTC interface.

I'm not sure if this is a Combined Arms issue or a general DCS UI issue, but if you give an artillery group a fire mission and that group has an FDDM, the Aiming task timer at the bottom left of the F10 map does not count down to launch correctly. Instead of counting to zero then switching to firing like it does normally, instead it counts down from 180 and continues to count down Aiming after the vehicle starts firing. Eventually once the last round is fired the task resets from "Aiming XXX.X seconds" to Inactive. Attached is a trk file (not sure if that's helpful in this case but I felt it was better safe than sorry) and a screenshot of the F10 map showing rockets actively outbound while the timer still shows Aiming. So far I've only tested this with the M270 MLRS. System info: DCS Open Beta ver. 2.7.11.22211 OS: Win 10 Home edition version 21H2, build 19044.1645 CPU: Core i9 10900K RAM: 32 GB GPU: RTX 3090 FDDM timer.trk

I had this issue too initially, but was able to correct it. Try going to Settings > Special > F-16C, change the HMD render eye (mine was Left Only so I changed it to Right Only), load into a flight, then exit and change the render eye back to your preferred setting.

I've noticed the same thing. With a little experimentation I found that if they're light enough to do a vertical takeoff they will, but if not they'll taxi up to be right next to the superstructure (if they were a ramp start), set the wheel chocks, then sit there doing nothing. I'm not at my computer at the moment but if needed later I can see about catching a track of it happening.

Hi CaptDoctor, after doing the steps Hollywood recommended I was able to get the Easy Communications setting to detect correctly. As for the Invalid Radio option I realized I was releasing the hotkey too early; You can't treat it like a conventional PTT. Hold it down until you hear the success or failure beeps, then you can release.

I think I must've mucked up the setup... It doesn't send commands, and if I monitor the VoiceAttack window when I speak it detects my speech correctly but gives an "invalid radio" error. Also it always thinks easy communication is turned off, even when I turn it on and reload the profile (When it loads the profile it says Easy Communications is false). I tried turning on easy communications in both 1.2 and 1.5b and it still has the same message...

As far as I can tell this started with 1.2.16, but I didn't update during 1.2.15 so it may have persisted since then. I did a search under this sub-forum and didn't find any related threads, and apologize if it has been posted and I missed it. First, the fixed net sticks out of the top of the combiner glass: Also, the direction of the reticle's deflection when you bank appears reversed of what would be normal (It may be correct, I'm honestly not 100% sure but it looks wrong compared to what I remember seeing in previous versions. In both of these screenshots the gunsight is in A-G mode.

Shiny! I'm guessing map, maybe a few missions and/or campaigns? Gorgeous work on the terrain!

One potential solution if you would be willing to do a pit that uses other systems together with DCS-BIOS is using a Teensy as a USB joystick. Here's a pretty good video going through the process of setting that up:

Just read through the F-20 Tigershark's wikipedia page... Man this makes me angry! Here we have a fighter that meets or exceeds pretty much every spec of its contemporaries except range and payload, and it just languishes for 6 years and is cancelled with no buyers over a bunch of political nonsense... http://en.wikipedia.org/wiki/Northrop_F-20_Tigershark

This makes me wish for a Borderlands-esque visual effects mod... Cel-shaded DCS?

I've only had two major mishaps myself. One was a takeoff gone wrong (throttled up to around 80%, you can imagine how that went for me), had a pretty typical bounce-bounce-bounce-BOOM reaction you might expect from any other module running off the end of the runway at 300 km/h and slamming into a fence. The other was a low stall recovery followed by a pancake, and that one gave the insta-boom you might expect from slamming into the ground at high speed. The only damage issue I've observed was a while before the module released but after they added the MiG-21 as an AI unit. It took a pretty impressive number of hits from the F-15's cannon before I got a pilot kill and watched him go in. No flames, no leakage, no smoke, no missing bits (although he still exploded on impact with the ground). Had I not hit the pilot I suspect he would've gone on to fight for quite a while. No idea if this is even remotely relevant to the topic at hand, though.

I also encountered this problem, during the ARC training mission. It tracked fine on sector 2/1 beacon 3, but once I overflew the beacon and switched to beacon 5 it pointed directly forward and stayed there even as I turned. Toggling to a different beacon and back a couple times fixed it, but it took me a bit to realize there was a problem at first. :S

Hi Nuts, I did get your message. I just replied back before coming here. Sorry, I haven't had time to come on here before now today. As an aside to anyone interested, I tried another volley against some targets on the /r/hoggit Tuesday night noob server last night and got 4 out of 4 hits. My engagement method was pretty much the same, although the targets were spaced out a bit more so that slowed me down a touch. Also the angle between me and them was a fair bit steeper, so I suspect that's part of it also.

True enough, but a 50% failure rate seems a bit high for IR mavericks at midday in otherwise clear conditions.

I'm honestly not sure if I'm force correlating. I'll have to review the track when I get home tonight and read up a bit on force correlation.

Yep, that's what I did. It closed from a normal-ish gap about the size of the target to a nearly-not-there small one around the center of the target. The missiles then tracked on the locked targets, passing just a few feet above them.

Yep, they go down to just a teeny little gap around the center of the target. In the test cases I've done I generally use the AGM-65D. My targets are a mass gaggle of 20-25 APCs (BMP-1, if memory serves). I set up a single one then just copy-paste it into a cluster, so each is in its own group and stationary. Ultimately during these tests the targets are all holding still for me unless I get a near miss, then the one that took splash damage will mill around a bit.

I've been practicing in the A-10C recently and will set myself up with targets in a clearing near Poti to shoot at. Whenever I do Mavericks I typically get a 50% hit rate, and I can't figure out why. I'll find the first target with the TGP and slave the first Maverick to it, then as soon as I'm within the Maverick's lock range I'll start locking and firing like mad. They track on the targets, but about half of them tend to sail a few feet right over them. I asked the same on reddit.com/r/hoggit, and they recommended I try asking here. Here's a track file of it happening: https://drive.google.com/file/d/0B5steFmPM-eyMkZLMGhvQVpIQ1E/edit?usp=sharing Here's an .acmi file for Tacview of a different flight, with the same problem: https://drive.google.com/file/d/0B5steFmPM-eyejM5d29XRkM3bG8/edit?usp=sharing

Yep. There's a Hellcat on the home page, though.

I'm not completely sure I understand how this works... Do you have to first export the gauges/info needed to a second monitor, then Gremlin's program exports certain coordinates from that to the Saitek panels? Or can you export the info directly to the panels? In short, do I need to have a second monitor in addition to the Saitek instrument panels?

Awesome, thanks a ton!!!! Flying in DCS is about to become so much more immersive now!!!:joystick: EDIT: Wait... April 1st... That's not an April Fools joke, is it? Sorry, I get so suspicious of everything on April Fool's...