ACS_Dev

At what PD would you say it becomes legible? Please do!

Thanks for the quick response! Did you have the quest 2 before and can you comment on the differences you experienced? Have you tried at regular 1x resolution? Is it still legible then? I have a 5600x and a 6900xt and don't want to compromise performance by super-sampling if possible.

Can anyone confirm or deny that the quest 3's resolution is sufficient to read F-16 displays without zooming in or leaning forward?

https://discord.com/channels/542985647502393346/543014378643914752/1196060649525092462 from the main ED discord, directly responding to a discussion chain on this topic. This is all very unfortunate. In addition to Georgia, ED is releasing Iraq and Afghanistan in the coming years, two hallmark maps for Mi-24 conflicts. At the same time, the Kord pushes our Hind to ~1998 if we are being generous and the gunner's EMR pattern pushes it 10 years further (also being generous) to 2008. A cursory search of pictures of the Georgian war shows few, if any instances of soldiers wearing the pattern. I am curious as to why they chose the Kord instead of working with the PKT or NSV.

Open Beta.

https://www.digitalcombatsimulator.com/en/files/3335222/ I have been developing and testing the above mission for around a month. I never experienced a front seat crash with it.

who are you replying to?

This is very nice and I haven't had any issues for a little while now. I just wish we would have been told about this, it would have helped convince my friends to give it another go and hopefully boosted adoption among the playerbase.

For what it's worth, I was experiencing crashes just like the ones described every time I re-entered an Mi-24 (specifically as CPG) on Rotorheads a month or so ago. The first time I slotted in on the server all was well but if we went down or otherwise reslotted I crashed reliably when we respawned. I forgot about it until seeing this thread because, interestingly, since then I have been playing SP and on MP missions I built with my friends and I have not experienced the crashing once. I have flown many hours and reslotted several times with no issue. Many of those times where in missions with other human-piloted Mi-24s.

Hello, With the most recent update we (the 3 of us who tested it) have been experiencing a couple of issues with the Hind. To preface, I know that I am running an up-to-date, clean build with no mods. Issue 1: When in multicrew, as soon as I or the others join a pilot's MI-24 we immediately request control of the helicopter. This occurs in both Equally Responsible and Pilot Only modes (we didn't test others). As you can imagine this can be very dangerous in air starts. I know that this occurred in two different servers every time I slotted in as the front seater. It also happened when I was the pilot and he slotted in as CPG. It happens instantly, and, at least for me, I could not cede control once I had it. He had to manually take it from me. Issue 2: When joining the front seat, either in a cold start or air start, the cargo doors appear to be open for me but not for my pilot. To fix the issue he needs to manually open and then close them. I am pretty confident that this is a new issue with the most recent update. I do not recall if this happened when the roles were reversed, just that it was 100% consistent for me. Issue 3: I can look down the sight of the ATGMs and get a tone but I can't fire them. The button to fire them does nothing. I tried both my joystick and keyboard and neither worked. I do know that 2 others were able to launch ATGMs successfully from the front seat so it might well be a me problem. I did a slow repair after the session to see if that fixed it and haven't had the chance to test since. I will need to test it further before I can claim with any confidence that it's an actual bug.

Hi BN, thanks as always for the reply. When did these changes occur? Incidentally I have been running some missions more recently without issue but since I hadn't heard anything about changes and it was with a smaller player sample I put it down to luck.

The most I have successfully tested with was 4 so far. It's too unreliable to be counted on as your only solution no matter how few or many people you are working with. I really, really want it to work but it is in the extremely frustrating area between being too buggy to even try and useful enough to attempt once a mission or so. Also, to be clear, it is happening because of ED, not (usually) you. Different users have the issues on the different days so it's not them. I have read every single bug fixing/large feedback/guide thread on this forum multiple times and nothing I have read has made VOIP work reliably. Allegedly it works for most people and ED needs more data/testing to iron out the last remaining issues. This data gathering and testing has been going on for almost 2 years now, so I don't have my hopes up.

Bump. Any update on this bug? GCI and the F10 map in general have been broken for months because of this.

Hi All, I am in need of tacview files from Enigma's Cold War server recorded prior to Object Export being disabled. I am asking here because it is no longer possible to source new ones and, at least for me, replays of the server crash during load. I am building a database of engagements from the server in order to analyze, both to identify trends and interesting facts but also to develop insights and best practices that can help people be more lethal on the server. With data I can do things like find the average combat altitude of each aircraft, the hit rates for various missiles in different scenarios, average dogfight duration and so much more. There are many possibilities but I need Tacviews to get data from. I am specifically in need of tacviews set to record the most data possible (which is the default option), recorded on the syria version of the server, longer than 30 minutes and recorded prior to the settings change. I know that it is possible for tacviews meeting these criteria to have been recorded to prior to march of 2023, anything afterwards is uncertain. If you have tacview they will be in your documents/tacview folder and can be sorted by date. It does not matter at all what you were doing during the tacviews so long as the above criteria are met. I don't see a privacy concern with this as the most identifying thing I will have from you is your callsign at the time of recording. Again it is no longer possible to record new ones so the files left on your computers are the only traces remaining. The number of remaining ones will only shrink with time as people re-image or upgrade from their computers. I have already asked on other platforms pertaining to the server and this game as a whole but have not had any success. I am running out of options. Please look in your files and comment/DM if you find some. I would be very grateful. I will take all I can get. Thanks for reading, happy holidays.

I tested this with a friend as well. The tricky thing is that it worked fine when I was CPGing solo but didn't work in multiplayer. In order to test this I placed 4 Mi-24 slots, each with 8 AT-6 and 2 rocket pods. Each slot had a different control priority. We only tried "equally responsible" and "pilot only". I could view and manipulate the sight and systems. Everything worked except the ATGMs themselves. My ATGM fire button is located on my joystick. I know the joystick worked because I was (unknowingly) flying the helicopter during the first flight and I also use it to control the sight's axis in subsequent attempts. Just to be sure, I bound it to my keyboard as well with no result. When I got tone and held fire nothing happened or the tone stopped working. This is especially abnormal because prior to the update I could fire even outside of tone in many cases. In the track file I am the CPG and we (my pilot and I) attempt to use the ATGMs, first in an Equally Responsible helo and then in a Pilot one. We first targeted the fuel tankers and then a treeline. No missiles were launched in either case. The other armaments (gun, rockets) worked. I have spent a good bit of time in the CPG seat so, for what it's worth, I am confident that this is a bug. server-20231225-084842.trk

What would be gained from having the MI-24V? The gun jumps out to me as the main feature but its reputation seems to have been lacking in practice; Source: "Mil Mi-24 Hind Attack Helicopter" by Yefim Gordon, Dmitriy Komissarov, page 58. My opinion is that they should stick with the MI-24P and give us the bomb racks, PKT and S-5 variants as part of the core helicopter. The PKT is the most important feature to me besides the single-mounted ATGM option. Regarding paid upgrades the MI-8 is the way to go. It badly needs it. Unfortunately there are few things they could give us on the MI-8 that would justify a paid upgrade other than fuel tanks, a new model, or features that make it anachronistic for Afghanistan so I don't see them putting in the effort, especially with how low its relative market share surely is.

F-10 map is still broken on servers like ECW.

I have seen some complaints about the possibility of them also doing Iraq. As long as they do 80s Iraq and not 2020 Iraq it actually does make a splendid map for realistic combat for the Iran Iraq war. F-1, F-4, F-5, F-14, MiG-21, 23, 29, Su-17, 25, Mi-24, AH-1, CH-47, S-342 all have a place on that map at the same time. Again that's only the case if they do the 80's version...lately it's been much, much more boring.

What is spans overflow?

This is the second time this month this has happened to me. This is a very big mission so I am wondering if I am hitting some sort of size limit but wanted to confirm. I am building a big sandbox mission set in 'Afghan' (Syria) in 1986. By big I mean that I have more than a thousand units, most of which are late activation so I don't have to worry about performance. (having flown it with friends it does run pretty good). This is the second version of the mission as I corrupted the first version in an identical manner to this one and had to start almost from scratch. This doesn't seem to allow folder uploads so I uploaded the contents of the folder in which the mission was housed. To see the mission in an (ideally) non-broken state, download and open SovietAfghan_1986_SandboxBackup.miz. To see the error attempt to open the non-backup version and it will (at least for me) throw a constant table overflow and go to a blank mission instead. The only difference between these two missions is that I took the group named WG01T20, put it on a road and gave it some waypoints going around the sector. At the last waypoint, like most of the other mobile vehicle groups, I gave it a go-to-waypoint 0 task so it would continue to circle. I saved and it threw the error, rendering the mission broken. I read that this was possibly the result of duplicate names so I took a backup, deleted all of the units in the sector (their names started with WG01), placed and named a new set under a different name and tried to set them up. It all worked fine until I started giving the new set of vehicles waypoints. (I tried without and it saved). The first group was fine but the second group, WG01T20, broke the mission. This leads me to believe that the issue is not duplicate names but instead an extreme number of waypoints. Is there a limit to the maximum number and distance of waypoints or is it something else? AdanaWav.wav O910Wav.wav O926Wav.wav O979Wav.wav SovietHeloSandboxScripts.lua SovietAfghan_1986_Sandbox.miz SovietAfghan_1986_SandboxBackup.miz

I cannot hear anyone who transmits in VOIP and sometimes they also don't show up in the helicopter (MI-24) room with me. Tonight they were in general and coalition but not in my helicopter and I could not hear them or anyone else transmitting despite seeing the transmit button go red and having the intercom switch on. Others could hear us both and saw him in all 3 rooms. MissionLog.old

Hi Nineline, Thanks for replying. My intent with my post was to vent frustration about my struggle to use an ED product. It was not necessarily intended as direct problem-solving feedback. When I test VOIP what happens is different people at random are either not present in the room, unable to successfully transmit or unable to hear each other. The people impacted were not consistent across server resets or game restarts, each of which where done several times in the ~2 hour time window in which we were originally intending to fly. This indicated to me that it was not so much their problem but instead a systematic issue. There are ample examples of this occurring with others. I initially thought that the issue was with 10309 not being forwarded. I was unable to test again because nobody within that group of people wants to bother with VOIP anymore and refuse to use it. I later on read that DCS by this time allegedly was just using 10308 instead so that wasn't the cause. I tested it again this last weekend with 10309 forwarded and a different group of people and was unable to hear anyone else, despite seeing the transmission indicators and hearing clicks. Again, this is something others are also reporting. I only server-cycled once this time to avoid wasting our time and the issue persisted.

I have no logs for the most recent session. I will generate some tomorrow most likely.

Did it work for your testers? I have tried it with at least half a dozen people not including myself on multiple servers including my own and I couldn't get it to work consistently for any of them. Also it has been well over a year since people started reporting these problems as evidenced by previous posts on this forum, yet today the same issues remain. What data are you looking for and when do you estimate you will have enough?

I have posted and then deleted multiple rants in this thread as I have gone through the process of trying to get VOIP to work with various people. I will try to keep this concise. I assumed ED's VOIP worked on a basic level because Wags made a video on new features coming to it in 2.9. I was eager to try it, and being a server host/mission creator, I was willing to go through the steps to host. In the video Wags said he had no friends but had he managed to muster even a couple of ED's alleged 180+ employees to actually test the software I am confident he would have run into the same problems as everyone else in this thread has. Of course I actually tested it and found over the course of many, many wasted hours (and many more wasted hours by the people who trusted my belief that ED's VOIP functioned at the most basic level) that the ED's VOIP is just broken and useless. Now they are rightfully fed up with it and don't want to touch it again. I initially thought it was on my end but over the course of those wasted hours and looking in these threads I learned the truth about it and ED's product. The fact that Wags made and posted a video showcasing new VOIP features and thus encouraging thousands of people to try it while failing to mention, let alone address the fact that 85% of polled users can't make the underlining product work and that it is and always has been too unreliable to use in any capacity is extremely aggravating to me and the people I worked with. I can only imagine how many other people have wasted time trying to fix problems that they initially thought were on their end. Furthermore, the fact that it has always been like this is pathetic. We are (very unhappily) resigned once again to using SRS, a software that, despite being made by a small or solo unpaid team completely unaffiliated with ED, put's ED's VOIP completely to shame just on the basis of being functional alone. If at some point ED fixes this 'product' we might be bothered to try it again, but given that it has been like this for well over a year, we aren't holding our breaths.