Sandman1330

I guess the case where it would be useful would be a situation where you “lose” the TADS. You are searching the area ahead, and want to correlate the area it is looking with your view outside. Maybe you see something outside, so you set C-HMD as Acq, slave to it and get the tads into the right area, but once you unslave and start moving the tads around, you may need to fine tune where it’s looking onto the exact spot you want to investigate. Or you go too far one way and want to get back without having to change Acq back to HMD. It would be easier to walk the cross into the right area by looking outside, then transition to looking inside. I just still find it very strange that the pilot can get the cross where the tads is looking, but CPG cannot.

Perhaps I’m missing something then. In the CPG seat, when I have TADS selected as sight, I do not have the option to select TADS as acquisition source, which I need to do in order to see it in my HMD. The pilot has that option and can do this, but the TADS is not in the list for me in the CPG seat when TADS is the selected sight.

I’m no expert either, but that is what I tend to do. It also allows me to “reset” to a known point when needed. But it’s a poor workaround for not being able to see where it’s pointed in the HMD, which is strange since the pilot can.

Thanks for the prompt reply!

@NineLine I know you may not have come back to this one as it's marked missing info, but there's now a couple of tracks provided. If there's still info required, can you advise what is needed? Can we confirm if this is a bug being investigated? If it's not, clearly we're all doing something wrong that we'd like to rectify. Thanks!

He's absolutely terrible at hitting moving targets... Like others have said, very difficult to post a track as it's prevalent on multiplayer servers, but the hellfire always hits behind the target. I have seen it on single player in the CPG seat with stationary targets too, sometimes it seems as if the laser is passing through the target (not sure, maybe this is unrelated?) Here's one that should be fairly short to sit through (~10 mins probably to get to the point) https://1drv.ms/u/s!Ascm8Kmu7NR0hIA27M1bvx_bYjw43A?e=7GPPgg edit: what I’m seeing may be related to this… https://forum.dcs.world/topic/297462-george-doesnt-aim-correctly/

I’m trying to figure this myself. So, as pilot, I can set my ACQ to TADS and see where the CPG is looking with the TADS. However, in the CPG seat, I can’t have TADS set as both sight and ACQ. The reason I want to do this is so I also get the dashed cross on my HMD where the TADS is currently looking, it would help to identify visually something I’m looking at with the TADS. Am I correct reading above that the only way I could do this would be to deselect TADS as sight, so that I can select it as ACQ? I feel like there should be a more streamlined way for me to quickly look outside the cockpit and know where my TADS is looking…?

You should note that both of these techniques will result in an increased tendency to overtorque or droop the rotor. Stirring the cyclic is actually something we need to train out of many of our new pilots. Doing this causes your rotor system to “spill lift” as you are constantly tilting your lift vector away from the vertical. This will increase power requirements for your hover, so if you are heavy or hot/high, you are going to be hitting limits sooner. I’m not sure where you’re going with pumping the collective, but again at the edge of the performance envelope while heavy/hot/high, this will cause power spikes that are likely to exceed limits. It will also increase your workload, as every collective movement requires a corresponding pedal movement, and even a cyclic movement. The gold standard of helicopter flying is very minute, precise control movements only as necessary to control drift. Anything more wastes available performance. The way to achieve this is to work on your hover references and scan, learn to identify drift or deviations early, and make a small correction. Wait for that correction to take effect before making another if necessary. You should constantly be scanning, correcting, waiting, scanning and correcting again.

Another track here: server-20220331-160400.trk

Doesn't appear to be fixed in the hotfix. Still having the issue online, and no mention of it in the patch notes.

Yeah, good point. It would stall asymmetrically and at the wrong AoA, which would confuse the FLCS and make for very weird and unpredictable control response. There are so many ways this could be modelled fairly easily, while avoiding the on/off wings break at exactly xG model we currently have.

Yeah, cumulative damage could work. Over G once for a short duration, fine. Sustain an over g condition several times in a short period, start breaking things. Make the radar go inoperative, cause the gun to jam, cause stores to jam, and after enough cumulative over G, break the wings. Each spawn would start clean slate, but in the span of a dogfight, someone who blatantly disregards limits will pay for it. I wouldn’t even see this as being an option that needs to be enabled or disabled. If the existence of the paddle is realistic and should be modelled, so should the realistic consequences of doing so.

Great idea! I’m in!

+1, I don’t see it as a cheat option since the whole implementation of force trim is an unrealistic workaround for PC game controllers anyway!

Aha! I was playing online trying to figure out why I couldn't get George to coop with me, this explains it. I haven't tried single player or coop multiplayer yet, so I just thought I was doing something wrong... (Could still be the case!)

Anyone else have this freeze up on loading? I waited over a half hour for it to compile, it just never came back. Basically locked up on loading. I've never had to wait that long for compiling before... Anyone else?

https://youtu.be/sAwq0R8PLHc

I wonder if some of the issue here is the radar performance of AI aircraft. Since both the hornet and viper have had their radars recently rationalized to be more realistic, the AI with their simplified systems now seem to grossly overperform our jets. I find going against a MIG29S in the Viper to be very challenging now. The AI has always had perfect situational awareness, but now combined with better radar performance, it does make one feel at a disadvantage in the full fidelity modules. So if you’re playing primarily single player, maybe it’s the AI that needs fixing?

I had the same problem - Nevada, Marianas and Normandy wouldn't authorize. I think it's because I reinstalled DCS onto a new (much larger) drive, and those 3 terrains used to be symlinked over to a different drive. With the new drive, I have room to have them all on the main drive, so I removed the symlinks and moved them over. Using the trick above worked - but one note for any "lurkers" who may try the same thing. Don't just drop the terrain folders into _downloads, you need them to be in the correct folder structure (mods/terrains/nevada) etc. This fixed it for me.

Frederic is correct. The way around it, if you want ECM only, is to use TMS aft before you are locked up. This gives the ECM consent to transmit in advance, so when you are locked up it will automatically transmit without need for TMS aft. Then you just TMS aft when you want the chaff.

And I have 20 years in the military, 10 (and counting) as a pilot. I can tell you we will exceed limits in a life or death situation. We will never plan to go out and do it repeatedly just to gain a tactical advantage. There’s also the aspect of training. I’m not doing something for the first time in combat that I’ve never trained for in real life. They (I don’t fly Hornets but have many friends who do) don’t know how the jet will react so they aren’t just going to do it willy nilly for the first time in a life or death situation, unless completely desperate. And when it’s on the line, they may not even think to do it. That’s why we train, to create muscle memory. If the muscle memory to pull it isn’t there, they’re unlikely to even think of doing it when they’re amped up and running on pure adrenalin. But we aren’t arguing whether people should over g, we are arguing what are the consequences. And you agree that repeated use of it would damage the airframe. The way many DCS players use it would definitely constitute repeated use. One or two? Let them get away with it. 4,5,6,10 times in the span of one fight? Something breaks. Because that’s realistic. And not all over G are the same. Your inspections you’ve done are probably lower numbers for very short durations. If a pilot exceeds a limit, depending on the limit and how long and by how much, the trip may be over. He flies home to be inspected. An intentional over G is likely going to be a much higher G value, for a much longer duration. Some DCS hornets pull 10-11G for several seconds when the paddle is pulled. Tell me you wouldn’t find significant damage with an exceedence over 40% of the limit for several seconds? Sorry for all the edits - every time I hit submit, I had another thought. The digital equivalent of storming back into the room over and over saying “And another thing!!”

I never said you wouldn't pull it in a "pull the paddle or die" situation. I said you won't go into a fight planning to pull it, and hold it down for the entirety of the fight. People in DCS literally hold it down and use it on every turn in a dogfight. Do it once to save your ass, well the jet's down for inspection for awhile but will probably be fine. Hold it down an entire dogfight, you're damaging something. It's there for a reason, sure - emergency use only. Pull it once to save your life. Don't fight with it held down, it's not a 9G airplane despite what everyone wants to believe. Ask any real Hornet driver. Anyway, it's there and people will use it, so whatever. That they will do it is not realistic. Breaking the wings off isn't realistic either. But SOMETHING will break with repeated use - avionics, flight control surfaces, the gun. Things should start breaking if you abuse it, because they would in real life. The Tomcat has hit this balance very nicely - you over G or overspeed the flaps, things will break that will make your life more difficult, but your wings won't rip off unless you REALLY pull on it.

Thanks for the replies guys. I'm tempted to say the GUI ports are a red herring - I'm running my first instance on 8088, and my second instance on 8089, so there should not be a conflict here. I've posted the autoexec file from my second instance. Interestingly, my first instance doesn't have an autoexec file - presumably it's going with the default of 8088. I'll try creating one and forcing 8088 to be sure, but I've never had a problem with the Web UI connecting to instance 1 on 8088 and instance 2 on 8089, they've always connected correctly. autoexec.cfg I think the issue is with the second line, with the inability to open the mission file from the temp folder. I'll dig around in the antivirus, but if it was excluded from the AV, it would have this error every time, no? The server starts fine the first time, it only seems to error when it's already running and I try to switch the mission or restart the running mission. Strange... Edit: So I just examined the log for a successful startup of the server, and the mention of the GUI ports is still there. What is not there is the error regarding finding the specified path, so I do believe it's related to this.

Luckily it was extremely short duration…

It is a great video! Over my Xmas break I spent a lot of time on the dogfight servers. We cancelled all our holiday travel plans last minute so I had nothing else to do lol. I’ve noticed fewer folks using the paddle than I think there used to be. I’d say most do use it only occasionally, and the odd one flies around with it held the entire time. I don’t pull it either, and know a few guys who don’t. They’re out there