jubuttib

I have tried this a few times on my end, and haven't really noticed a difference myself. Using the controls overlay the AP channels also appear to all be off when Petro takes the controls anyway, though I'm not sure if this is a realistic representation of what happens. The control inputs are shown, but all AP channels remain centered and static.

Thanks! Haven't been able to find it yet for whatever reason, but I shall try, try again. Still in the EU region right? Would narrow it down somewhat. EDIT: Or, well, Europe region at any rate...

Hello hello, just wanted to ask if this server is still active and using the same IP address as before (94.23.215.203:30108 was mentioned)? Ran into this via the "Virpil collective honest review" video, and the heli missions you guys have seemed really cool. I haven't been able to check havoc-company.com (which was listed on the YouTube page) nor have I been able to connect to the server today using the above IP address, so was wondering if something has changed, if it's possibly down, or I might just be barking up the wrong tree altogether.

Shame. Not that it would have been an exhilarating ride anyway.

Relates to the above point, the auto-hover will try to keep you steady even in wind, but it might run out of control authority. Trimming closer to a hover helps with this too.

Fair, it could be caused by the yaw channel, but I don't think it's supposed to, since none of the other channels seem to affect trim from what I can tell.

The problem is that the yaw autopilot channel was fighting against it (it was trying to correct to the right), and turning the yaw channel off didn't actually return it to center. So I'm thinking it's something else, or a bug in the current implementation.

To my understanding the "do this" parameters for the autopilot are set either when turning the channels on, or by using the Trimmer Button. Hold the trimmer button down, and when you let it go the heli should try to maintain whatever the flight parameters were when you let go. What about the 4-way trimmer though? Currently at least if you use it a lot, the autopilot kind of ignores it, and tries to go against it. Lets say I wanted to slow down a bit by lightly raising the nose using the trim backwards command, the autopilot will try to push forwards to counteract this. Is this as intended, and correct? I guess no-one ever claimed that the 4-way trim functionality is tied to the autopilot system in any way. Would just have been nice if I could use them co-operatively, rather than them fighting against each other.

Track file (larger than 5 MB): https://anonfiles.com/Hf3058R1u3/Hind_mystery_death_zip Just confused as to what happened here. My random damage is off and I don't think birds were in the mission (might be wrong about that one), and as far as I can tell I didn't cause damage to the heli while flying around engaging targets. At the end I was flying in a mostly straight line towards an aircraft carrier, intending to land on it, gradually using trim back and collective to slow down in a very gentle way. Suddenly my left engine catches fire out of nowhere. I start to prepare for an emergency landing, and then my right engine seems to go out as well, and shortly after my rotor blades snap, and I plummet into the sea. This was very confusing to me.

I noticed this today while practicing a bit with the Hind, for some reason the rudder trim on the Hind has a tendency to drift to the left over time, or during some maneuvers (can't identify which ones though). Over the mission I noticed that the rudder didn't always come back to center when I let go of my rudder pedals, and I had to reset trim to get everything lined up again. I must have done this at least 3 times during the mission, but it kept happening. NOTE: Rudder trim is OFF in my special settings. This also happened to my friend yesterday when we tested the Hind in the same mission, but in multiplayer. When he came back for a landing, he found that he couldn't get the rudder all the way to the right, and had trouble keeping the Hind from spinning on the way down. He also has rudder trim turned off. Checking in Windows, the actual functioning of our rudder pedals seems to be fine, they centered the same as ever, and reach both 0 and 100% inputs, so no issues there. The Hind is the only aircraft in DCS that has given us issues like this so far, across FC3, A-10C II, Ka-50, UH-1H, Gazelle, F-16C, JF-17 and M-2000C. Track file (too big to fit as an attachment): https://anonfiles.com/Hf3058R1u3/Hind_mystery_death_zip Named as "mystery death", because I saved the track file for what happened at the end, where suddenly my engines caught fire and my rotor blade broke minutes before reaching the aircraft carrier I was intending to land on, without any real cause that I could see.

I can see it now: Missions to take down enemy electrical infrastructure, but all weapons are disabled in the heli...

On the hover situation: This can easily happen if you engage auto-hover while not already trimmed for a decent hover. The auto-hover functionality uses the normal autopilot systems, and as such is limited to IIRC around 15-20% control authority, i.e. it can only use about 20% of the range of the cyclic etc. that you can. Sometimes this means that if you're not already near a hover trim, the AP system can't move the controls enough to maintain a steady hover. If this happens, push in the trim button, try to get as close to a stable hover as you can, then let go of the trim button. If you're already near a stable hover, the AP doesn't have to work as hard to maintain it.

Based on the specs I've seen (which includes some variance) the muzzle velocity for the GAU-8 using the PGU-14/B API rounds (the ones with the depleted uranium core) is about 1 010 m/s, while the muzzle velocity of the Russian 3UBR6 round is around 970 m/s and the 3UBR8 round is around 1 120 m/s. Projectile weights have been quoted as 395 grams for the PGU-14/B, 400 grams for the 3UBR6 round and 304 grams for the 3UBR8 round. So in pure terms of muzzle energy the PGU-14/B is the highest, with the 3UBR6 getting to 93% and 3UBR8 APDS getting to 95% of it. So in terms of pure ballistics at the muzzle they're all very close, with the 30x173mm being the most powerful. Of course bullet design has a huge effect on ballistics at range (drag mostly), and the design has a massive effect on the armor penetration performance, with the density of the depleted uranium penetrator being a huge boon, as well as its incendiary and self-sharpening nature. The tungsten alloy penetrator on the 3UBR8 has neither of these properties. EDIT: On the variance, I've seen the quoted weight for the PGU-14/B vary between 395 grams and 425 grams depending on the manufacturer and time period of the study, so apparently not all of them are quite equal, similarly the muzzle velocity has been quoted between 980 m/s up to 1 020 m/s... So these are all ballpark numbers anyway. PGU-14/B is the most powerful cartridge, but they're very close ballistically, and the penetration performance of the PGU-14/B is way better than on the two Russian rounds I have seen data for.

Big thanks for taking a look Ian! Good to know about the Ka-50, I'll need to test that again with my friend to see if we can get it working. Unfortunately it's the Jeff and F-16C that are the more important ones. I did try changing some of the planes first to nothing and then to CAS, but I think that was a red herring. I loaded up the original version of the mission and it would appear that the AWACS plane does indeed show up in that as well, so it had nothing to do with me changing its task, I just thought it did. I think the datalink itself on the F-16/Jeff end is probably working, since the AWACS pops up in it, but for some reason none of the planes the AWACS sees are getting transmitted. I did check out the F-16 datalink issue thread while trying to sort this out, I couldn't see it making a difference unfortunately, tried various TACAN channels. Well, thankfully it seems limited to just this training mission, so anything that really matters does still work, but it would still be great to know what's causing this. The mission does use a fair bit of scripting, so it might be that getting in the way too, but I have no way to check if that's the issue.

Welp, I guess I'm stuck with this. Thanks to anyone who had a look anyway!

Big shame, I was rooting for Jake...

Some people like operating the systems (like the ATGM sight), as well as just directing what happens, more than actually flying. I happen to enjoy both, but for example I'm much more interested in being in the backseat in an F-14, and will definitely do that once the F-15E comes in a couple of decades too. Though I'll probably end up piloting the Apache for the most part, my regular co-pilot isn't very proficient with helicopters...

VERY interesting, I'll need to try that!

Hello, complete ME noob/idiot here, trying to make some sense of things. I've been using a modified version of this mission to practice weapon employment and systems management in the modules I've bought: https://www.digitalcombatsimulator.com/en/files/3301568/ I've modified it by adding and removing some stuff, making almost all planes on the ground start cold, allowed labels, etc. The current version of the modified mission is included as an attachment, with a track file that also showcases the issue I'm having. And that issue is that I'm not getting the datalink to work at all with either the JF-17 or F-16C when in SP or MP, and when trying in MP even Ka-50 datalink wasn't working properly. When I play missions generated by Liberation I get datalink working just fine, and to my memory datalink HAS worked in the recent past (meaning not that many months ago) even in this practice mission. I have no idea where to get started solving this, and would appreciate some help. Even just a confirmation whether or not the datalink works for anyone else when running the mission could be useful. One thing that I did try, but isn't included in this version, was to assign the AWACS plane in the mission to do the task Nothing, then back to AWACS. That at least made the AWACS plane itself pop up in the datalink though none of the targets it sees are in there. And it does actually work and sees targets, because if I tune to the AWACS radio channel it gives me non-stop information about enemy units. So this would somewhat hint that something in the mission has gotten bugged at some point, and things aren't initializing in a proper way for them to be showing up in datalink? Perhaps because it's an older mission (2.5 period), and ME does some things differently now? Thanks in advance to anyone who even looks at this mess... JF-17 and F-16C datalink testing 2.zip

While you certainly can't edit the red side flight packages in the Liberation GUI, it does of course generate a bunch of flights for the red side too. So as a stop gap solution what you could do is generate the mission via Liberation, open it up in Mission Editor, then change some of the red side planes to have Client slots. It's certainly not perfect, but it'd be something, for now. *shrug* EDIT: There might be some slight jiggery pokery required with the timings, but I don't see a reason why it wouldn't work overall.

To improve performance in some cases you can also load up the mission on a dedicated server instance running on your computer, and join that via multiplayer menu. What this effectively is trying to accomplish is put some of the computation into the dedicated server thread instead of having everything happen in DCS, which as we know doesn't really do multithreading...

I have to admit that I've used Petrovich very little as a pilot, because unfortunately in my experience he has... Let's call it a tendency to hit the bottle, or something. He can fly around a bit, if you're careful with your instructions, but he also has a propensity to go a bit nuts, and quite often enters into VRS and drops the heli out of the sky if you're not careful with what you request.

There's a saying in my country: "A pessimist is never disappointed."

Thanks, though I should have specified I meant more from a mission setup perspective. I know I need to have an AWACS plane in the air, but beyond that I'm clueless. I have however tracked the issue down to the mission itself. I was mistaken before when I said that the datalink was working fine on the Jeff, there were certainly issues, there was just a coincidence with the spawn location of the plane that made it appear as if the datalink was working. I tested a Liberation generated mission now and the datalink worked just fine on the F-16C. Now I'm really annoyed though because the practice mission included in the archive I attached is really dang useful for practicing the planes on my own, as well as teaching my friend how to use various systems on the modules. I'm pretty certain that the datalink HAS worked in it, and probably could be made to work again, but I just have absolutely no clue how one would go about achieving that... The most progress I made was taking the AWACS plane in the mission and assigning it to Nothing, then back to AWACS task, and at least IT showed up as a friendly on the datalink after that for the JF-17. But nothing else did (the AWACS is doing its job, if I tune my radio to it it's giving me notifications of enemies in the area, they're just not in the datalink), and the F-16C still doesn't show even the AWACS on datalink...