ACS_Dev

DxDiag.txt Can't hear others in dcs VOIP. Yes 10309 is forwarded. Yes I am in stereo, mono, auto, doesn't matter. I see green and hear beeps but no audio.

Bump, our Kord is 10 years newer than the Afghan war and thus anachronistic for the conflict and likely the module in general. Having a PKT would be a very welcome option, also in the case of the MI-8.

@randomTOTEN@Flappie@admiki I just figured this out finally, it was (surprise!) never a bug. In order to use the sight I must first press the 'request aircraft control' to cede control of the aircraft to the AI, after which I can access the sight.

@Flappie@admiki I disconnected my joystick and throttle, restarted my PC and launched the mission again. I confirmed no other controllers were present via the adjust controls menu. It still doesn't work. At this point I will reiterate for what feels like the umpteenth time that this was absolutely not a problem a couple of updates ago, it persists not only after a slow repair, a game install and a COMPLETE PC WIPE, is occurring with multiple users, happens regardless of whether I bind it to a joystick, keyboard or throttle, whether I have either of the above extra peripherals plugged in and WORKS FINE IN TRUE MULTIPLAYER. As a tech support guy myself I know how frustrating this is given that you yourselves cannot reproduce it, thanks for the effort so far.

I will do that tonight, thanks for the suggestion.

@Flappie I submitted a support ticket, no reply to it yet. I know of at least 2 people who have the same issue as me. For unrelated reasons two days ago I completely wiped my PC and set it up again from scratch (I mean re-installed windows, updated all drivers, bios, and of course redownloaded DCS entirely from scratch save for my backed up missions, my custom payloads and the Syria map and the F-16 which I had backed up on an external drive.) As such my keybinds and the MI-24 were also redownloaded from scratch. I still can't look down the sight.

Are the people reporting these issues forwarding port 10309 on the hosting machine? I know that when I was just forwarding 10308 it was completely unusable. I have yet to convince enough people to try it for a good test since then because they all think it's garbage and insist on using SRS or discord.

I just watched it. He spent most of the last half in f10 map view for me. Essentially all of it for that matter. Did you see something different? I never saw the sight.

Hi Flapplie, I am at work currently but will have an answer for you in about 5 hours.

I want to stress for the final time that it does not matter how long I wait, what I bind it to, whether I am in internal or external views, what mods I have (I don't), IT DOES NOT WORK. It works in 'true' multiplayer when someone else first occupies the helicopter and I take the co-pilot slot. Yet it doesn't work when I try it myself in singleplayer. It worked fine for the past several months prior.

As previously stated, I deleted the entire folder housing each of the MI-24's binding categories. It is currently bound to one thing, the default. Before that I tried multiple buttons from 3 different input sources; my keyboard, joystick and throttle, none of which work. The default binding still does not work.

Alright I just got the opportunity to test it in multiplayer with a friend. If someone else occupies the helicopter and I join them it works. If I just try to switch to the front seat in singleplayer or I am the original pilot it does not work.

Halfway through the track I start spamming it yes. I just pressed the button and waited 10 sec and it didn't work

I am confused; what do you mean by ghost inputs? I just manually deleted the files housing all of my MI-24 binds for every seat in my savedgames. Loaded back into the game, now with just defaults, and it still didn't work. Again all of this was working just fine before the update.

Absolutely nothing happens.

Slow repair did not fix the issue.

Hi Aeria, It is not possible for me to view the missile sight. The button press (9K113 Aiming Profile - ON/OFF) does not actually do anything anymore when pressed, meaning I cannot guide ATGMs as a copilot in the MI-24. As any MI-24 I front-seat for will be denied the ability to use ATGMs, I am effectively useless as a copilot.

I posted this in Discord last week but got no acknowledgement so I am posting it again here. At least one other person is having this issue. I tried binding the buttons on the stick the throttle and my keyboard, none worked. Even if the CPG station isn't in observ mode I should be able to at least ADS on the sight, regardless of whether or not I can see anything. This worked fine last weekend and for the past several months but now it doesn't. Attempted by myself in a client controlled aircraft with various ATGMs. Neither a game nor pc restart fixed the problem. Again I tried 3 different input methods, all 3 of which successfully interact with the chopper in other ways. Player doesn't work either, neither does different missions or making new ones. Track enclosed. I tried again after today's OB without success, both singleplayer and on 4YA servers. My build far exceeds minimum specs and passes IC. I was hoping for an update to fix this this week and was thus disappointed when it wasn't. This completely breaks the module for people like me who are primarily front seaters. HindADSAttempt.trk

So this was their 3rd chance to give us the advertised models and they still haven't delivered?

Also I don't believe any of the radar-guided systems are fully modeled (and I don't mean self-protection shutoff), guidance modes, cold-launch, stuff like that isn't a thing.

We also had a lot of issues when I was trying to run on a single port. I had briefly posted a lengthy rant on this before I found the post about 10309. My friends are reluctant to try it again but 2 of us tried it since with no apparent issues. I have hope that porting 10309 solves the problem but even if it does, I feel that it should have been made more visible with the rollout of 2.9. They had one shot to really make an impression with the userbase and distinguish themselves from SRS, and at least for us that impression was thoroughly negative because of my not knowing about 10309.

A cursory glance at TRADOC discusses radar modes (specifically the PI and HOJ modes) that are different and more complex than anything I have yet seen from ED. Their SAM radar model is extremely simplistic and from what I have seen is only capable of modeling systems in which the tracking radar continuously illuminates the target and guides the missiles. While the system's radio command model does fit into this category its additional modes (which are very important for an accurate simulation) probably aren't possible with current DCS. Hopefully they are working to add more guidance schemes to their modeling portfolio and will then release this system at its full capability.

This new spotting system, at least for VR users (Quest 2, 1.0 resolution, MSAA 4X, no DLSS/FSR) is extremely overdone and downright comical in some situations. To preface, I have had the privilege of countless opportunities to observe the F-1, 5 (T-38), 15, 16, 18, 22, 35, A-10, UH-60, CH-47, AH-64, KC-135, C-130, C-17, C-5 etc. etc. both in daytime and (attempts) at night in overcast, clear or foggy weather from all ranges, both with my (admittedly imperfect) eyes, with corrective lenses and through 8x binoculars. If you want to get an idea of the realism of spotting distances at different ranges and you live in a 1st world country you can use ADSB exchange (free flight tracking website) in concert with Google Earth (also free) to identify ranges at which you spot approaching civilian airliners. For best results, focus on aircraft close in size to the KC-135 or E-3, then compare those results to what you get in game at the same range. If you want to make it easier on yourself and you live near an active airport you can go to it and see how far away you 'tally' landing aircraft or conversely how long you can maintain 'tally' on departing ones. You can also try this with static landmarks such as water towers, cell towers or tall buildings visible from your home, again using google maps/earth to find out how far away they are. It is likely that everyone reading this has the resources to test out for themselves how far they would be able to see at least tanker-sized aircraft in real life as opposed to VR. For me, at least for fighters like 35 and 16, short of the rare reflections on a sunny day it is basically impossible to see them beyond 15 miles at the furthest, even with 8x binoculars. I have tried to follow them from the end of their runway into the sky and I inevitably lose them far closer than they would be lost in DCS. In VR I can see targets much further away, with larger aircraft being easily seen 20-30 miles out, even at night. Ground targets are similar, if not worse as about 10-15 miles out they bloom to massive white dots. The dots themselves aren't consistent either, popping in and out. Essentially I'd like to see at least an option to force this system off in missions, if not a drastic reduction in effective spotting range.

Hello, Currently in DCS the MI-24 door gunner does not have ICS transmit . As a result we have to use external platforms if we want to talk to him from the front of the chopper. He also doesn't have night vision, greatly reducing his effectiveness at night. The VOIP system is wonderful and I'd love to use it more but when we use a gunner we have to use discord because he can't talk to us without it. Any chance we could get these added in, maybe as mission options? Finally, if you gave the gunner/3rd seater the ability to lase things like in combined arms it would open up a whole new frontier of joint operations. It is less of a concern but still something I'd love to see. Any chance we can get these things added? EDIT: The lack of the gunner's ability to transmit on VOIP may be a consequence of ED's VOIP system being extremely buggy. In testing in the past couple of days I have been unable to get even 3 people consistently in the same chat room and fully operational with VOIP. Being channeled into separate servers, inability to hear each other, inability to actually send audio are constant issues. The specific issue and persons affected vary randomly with mission/game restart, telling me it's not our problem.

They changed the format, I have seen it said because people were stealing their models. This is understandable. They have advertised these 3D models for a very long time, all the time obviously better then the ones they deliver. Very nice, last part less so, still explainable. They gave us the wrong versions of all 3 of the highlighted upgrades, delivering worse versions and somehow did not catch this despite testing the update for weeks. This is a bit suspicious. Nineline and everyone else in the channel refuse to simply say 'it's a bug'. Instead insist that there is more information coming later. Are they not at liberty to say if things are a bug? It is not in the Known issues list: Despite being reported no less than 4 times in the object bugs section alone, 5 times if you count this post, At least 2 of which times where reported back to ED, roughly a full day prior to the known issues list being published. Finally, there is only one livery available and every texture within it is prefixed with 'low'. I wish I could be as casually dismissive as you are and I would be glad to be proven an idiot in this case. I don't like to speculate about ED and I don't like to hate on them either. I have more reason than most to hope for the best from ED as well as their continued success. At the same time this is hard to be dismissive about. They have quietly delivered models noticeably worse than what they have been advertising since at least the beginning of this year, models that are below the standards of what they were putting out at least 2 years ago. We know that the models aren't the same, and now I have shown you all of this. Take it as you will.