Captain Orso

He looks to me like someone who hasn't practiced touch-n-go's enough. When the main wheels touch the ground you have to push the stick forward just a touch, otherwise the inertia of the COG behind the main wheel forces the tail down and the nose upward, which is exactly what you see happening here. When that happens you are supposed to go around, even if it's embarrassing to bounce and have to go around. It's not as embarrassing as trying to force the landing and wiping out your million dollar warbird. This is also why every warbird manual tells you to do a three-point landing, even if it's not as cool.

There were a number of issues, the uneven stall was just one of them. That got fixed by adding a block to the leading edge of the left wing to change the stall speed on the that wing. Another issue was the undercarriage bounce - it was very extreme for an aircraft that, because of the fairly high landing speed, hit the deck fairly hard, and then because of the shock absorbers not working enough, caused the airframe to bounce back into the air. The Brits complained about this and IIRC modified the shock absorbers themselves to reduce bunce. Grumman later replace the shock absorbers with better working ones. Another major issue in carrier landings was that the Navy trained their pilots to make a long, straight approach, more or less the same as Army pilots landing at an airfield. But the Corsairs extremely long nose blocked the view of the carrier on a long, straight approach. With all three of these issues unsolved the Navy gave a no-go to carrier operations and kicked the Corsair to the Marines, who couldn't figure out why the Navy had given them such an excellent airplane.

Yes, we can all see that this was a joke: Even in the P-51 they were instructed to not slam the throttle, even though the affect was not a pronounced, the yaw and role tendency is still extreme and dangerous. IIRC there were a few deadly accidents in P-51s caused by slamming the throttle on an aborted go-around. Panic is the last thing you need in the cockpit. Yes, that slamming the Corsair's throttle would lead to a deadly roll is known. IDK why you are repeating it yet again. What does the fact that Corsairs were also land based have to do with anything? Wildcats and Hellcats were also used land based. So?

Strawman argument. The pilot doesn't wave himself off. The landing officer does, and he's not going to wait until there is only 0.8 seconds before impact. He can see with enough time for the pilot to go around. Nobody said anything about 3 seconds to throttle up; another thing you made up. There is a wide range between slamming the throttle forward in 0.5 seconds and going from 30% to 100% throttle in 2 seconds. Also, just because you are not immediately at 100% does not mean that there is no affect. With every inch of throttle movement, thrust is increasing. Slower motion than "slamming" means that torque is spread over the same period of time of the 30% -> 100% throttle motion. On the one side you argue that the power of the engine is so immense that you need 3 seconds to go to 100% throttle, but on the other hand you act like going to 60% in 1 second means nothing. Also, I'm sure Corsair pilots trained to see what happens when you slam the throttle forward while flying at 8000 feet with plenty of time and altitude to recover from flipping the airframe over through sudden torque overload, the same as they trained stalls and spin recovery.

Many thanks for the answer. It's pretty much what I expected, but I had to ask anyway, just to be sure. I guess I'll have to do everything manually *sigh*

This is the situation. There is a file inside 'c:\Program Files\Eagle Dynamics\DCS World OpenBeta\CoreMods\aircraft\FA-18C\Textures\FA-18C.zip' I want to mod. I want to automate this process as much as possible with OMM. I could simply copy the original 'FA-18C.zip' to somewhere safe, open the archive and replace the file I want replaced and repack the archive, and then add this newly archived 'FA-18C.zip' as a mod to OMM. That would work. I've already made it work. But 'FA-18C.zip' is 163MB and the file inside the archive is only 1.4MB in size--shooting cannons at sparrows. Is there a away to mode a single file inside an archive, without replacing the the entire archive? -- If option 1 isn't possible, I understand I could simply unpack the archive in place and then remove the archive. This is option 2. I could then use OMM to replace the single file I want to mod. Is there a way to create a mod which will replace the archive with it's contents, thus making the entire process automated, per 2 mouse clicks in OMM, before any updates and again two clicks after updates?

That's the problem... or is it. After hearing for years how long it is taking to complete the P-47, because they didn't have the documentation, and now they are saying, for the F-35 they don't need documentation, for an AC that is far more complex and difficult to model, now I realize--at least from the stand-point of today--if ED wants to do something, they will. No excuses accepted. BoB loses all appeal to me, if it's not era-conform. The appeal is in flying the same way then did back then, because that was all that their aircraft could give them - also in encountering all those clunky airplanes they thought were good enough at the time and finding that they weren't. Oh, man. To be a fly on the wall... My father was in the Marines--crew chief for Corsairs, at first. After all his training he was put on Peleliu after they took the airfield, while they were still fighting in the mountains. About the biggest danger he was exposed to was that every day some big, fat artillery piece, in some cave, up the mountain, would pop out long enough to fire off a few rounds and then duck back into the depths of the cave. That was it, excitement over, and he never said anything about the rounds dropping anywhere near to where he was. After that he was on the Philippines for a while, but the way he talked about it, it may have been long after all the fighting. He was also moved from being the crew chief for corsairs to C-46s--same double-wasp engines--but he never said why. Thinking about it today, I kind of think he got himself into some kind of trouble, and got pulled back to the backwaters of the war, to where he wouldn't be a problem. He had real issues with his temper, but I never thought much about it back when I was a kid, and later didn't think about asking him about it. Now it's too late.

If you drink enough, anything will give you Kopfschmerzen; I know, I've tried them all. If you have really bad luck, the Barbara who you brought back from the Weinstuble, will also give you Kopfschmerzen, not just on the next day, but for weeks, and months, and years, afterward... *sigh* tried that too. I wish ED had picked an era and theater, and just filled it. I'd not have suggested 1940 Battle of Britain, because that has already been do zu Vergasung. But Solomons 1942 would have been monumental. Zero vs Wildcat, Zero vs Corsair, Zero vs P-38, Vals, Kates, Bettys, Devastators, Avengers, Dauntless, Beaufighters, B-17Es, B-25s, A-20s, PBYs carriers, battleships, cruisers, destroyers, submarines, PT-boats, Japanese armed barges. Fighting at its grittiest, and when a one-sided conflict was still years away. Maybe I'll go play that new sim covering just exactly this era and theater, but whos-name-shall-not-be-mentioned... I use the unit list; filter down and select individuals. What I miss, is being able to have a flight (four AC) break it into two elements, each having it's own task. Currently only over two different units. I'd also like to be able to change targets, or have primary and secondary. So if I'm attacking an airfield Flak is the first target, but after Flak is dead, ground units, like aircraft (high priority), other vehicles (next priority). Currently attacking Flak is a ground attack mission, while attacking vehicles on the ground is a different kind (I don't recall which), and you cannot change them during the mission.

Schrödinger said, it isn't that we don't know whether Frankfurt is there or not, but that it is there and not at the same time, and becomes determinative only when tested. So I suggest NOT looking out the airplane window until after you are sitting comfortably in a Weinstüble, with a Bämbl. I can't suggest the Handkäse mit Musik, because to me that stuff is just nasty. You probably will not get your fill of Würschtsalat though - Prost! I would love to see a WW2 version of the Germany map, but judging from the Marianas map, it will take about another 10 years to get that.. oh, and we still need to have the entire upper Rhein valley to cover Market-Garden, Battle of the Bulge, Hürtgenwald, Aachen, Cologne, the Rhur, and of course a major part of the Rhine River. I'll probably be dead before all that comes to light.

Schrödinger was German, just so you know

Only within Tacview for watching it again inside Tacview. Absolutely nothing can allow you to start a mission from a fixed point-in-time. What you could do--but which might go spectacularly wrong--is load a DCS Track file and replay it up to the point-in-time when you want to take control again. When at the point when you want to take over, press <Esc> and in the menu, click on [Take Control]. This will put you into the cockpit and give you control over your aircraft. Only works with SP missions. You can only run that last mission you started, unless you save it manually at the end of the mission, or before you start a new SP mission, rename the 'LastMissionTrack.trk' file in 'c:\Users\username\Saved Games\DCS.openbeta\Tracks\' to some other useful name, otherwise it will be overwritten. In the main menu, select Replay and then select this file to replay. The problem is in what track files actually record. They record every control input you make from start to end, and everything the AI did with AI units. The problem is that the calculations are so complex when flying or when running the replay, that over time it is almost certain that some minor variations slip into the way your aircraft actually reacts to inputs, and minor variations build over time into huge major variations (butterfly-affect), like instead of you pulling up in time on a bombing run, your replay aircraft instead noses straight into the ground. Been-there-done-that. You can try it, but I make no guarantees of success. PS When you take over, be sure to set all your controller lever and switch settings to exactly they way they were at the point-in-time when you take over, otherwise you may immediately experience catastrophic... experiences, like when at mach 1.15 your landing gear suddenly drops. Good luck

Hi Alain! I'm not sure what you mean. It's difficult to talk about this subject, because there is no normal terminology. I call all the lines you find under 'Options / Controls / Aircraft name and seat position' the 'bind sockets'. You bind your HW buttons, switches, etc (that is to say, the labels DirectX gives to them) into these sockets. The controller names are in the columns. In the AH-64D CP/G for example, all the KU (Keyboard Unit) sockets suddenly all had the red exclamation marks, with no tool-tip telling you what the issue was, which it should do, and does when you actually double-bind the same controller button to one of the universal pages (pages that are always active, regardless of which aircraft you are flying; EG UI Layer, Airdrome Free Camera, Command Menu, or General) to another universal page or an aircraft/seat page. But this was not the case. The AH-64D CP/G page, category KU has under the keyboard column just the alphabet keys, a few of the special keys like ` , . - and the NUM-PAD keys, and none of theses are used per default in any of the universal pages without default modifiers like LAlt. I did have nearly all of them assigned in AH-64D Pilot page using the Modifier-Switches(momentary) set to TM Warthog Throttle JOY_BTN24 which I named KU_Switch. As soon as I added TM Warthog Throttle JOY_BTN24 KU_Switch to 'c:\Users\me\Saved Games\DCS.openbeta\Config\Input\AH-64D_BLK_II_AI_Menu\modifiers.lua' and restarted DCS, ALL the red exclamation marks in the AH-64D Pilot page KU category were gone. None of the sockets on the AH-64D George AI Helper page have corresponding sockets on the AH-64D CP/G page, nor visa-versa. The issue is, if you have 'Modifier-Switches(momentary)' defined, that DCS at times somehow muddles these up internally as if you had binded the same controller button in a universal page and an aircraft page, so that DCS doesn't know which socket it should asserted when the button is pressed. But this is in error, because there is no such actual case in the files. The solution is, harmonize the 'Modifier-Switches(momentary)' definitions in the Modifiers of the complaining page and then the complaints stop.

Not sure if this thread's issue is the same issue that I had, but here is my experience. I installed a new controller; a TEDAC for the Apache. There are two buttons on the grips which the real AH-64D doesn't use, but the controller has them wired up, so they are free for anything I want, so I assigned them as Modifier-Switches(momentary). So I'm setting up the AH-64D CP/G binds and I noticed a whole slew of the red exclamation marks on binds I had done nothing with. Long story short, for the AH-64D Pilot binds I had a number of Modifier-Switches(momentary) for joystick and throttle which were not in the TEDAC controller. I also and the new Modifier-Switches(momentary) in the TEDAC controller which were ofc not in the AH-64D Pilot binds, and I noted that those bind slots in the AH-64D Pilot binds using Modifier-Switches(momentary) which were not configured for the AH-64D CP/G were the ones marked with the red exclamation marks. So I harmonized 'c:\Users\me\Saved Games\DCS.openbeta\Config\Input\AH-64D_BLK_II_CPG\modifiers.lua' with 'c:\Users\me\Saved Games\DCS.openbeta\Config\Input\AH-64D_BLK_II_PLT\modifiers.lua' so that all Modifier-Switches(momentary) binds were in both files, started DCS and low-and-behold ALL the red exclamation marks were gone! Further Tip, I used WinMerge to harmonize the two lua files. This utility has been a god-send in usefulness over the years. I can heartily recommend it, especially if you edit files--like DCS lua binds--regularly.

It's already so close, I can smell the cannabis smoke wafting over from Bahnhof Zoo

The Beyond 2025 video showed it... Wags, in his Q&A admitted to it... When is the German Cold War map going to get a sub-forum under DCS: Tech & Terrain?

In the '02-QWERTY_KB and Load Coordinates.lua' file, find the line with the 'local TICKS' variable right at the top of the file. Change the setting to '2' (without single-quotes) and try it. If it's still too fast, try '3'. I've never had to use anything higher than '2'.

Did you have any luck with my tips?

What was wrong was fixed in a update of Meta Quest software. Beyond that, if it ever happens again, restart the headset and then your PC Go into Meta Quest Settings Beta Click on the Restart Meta Quest Link text and the the blue button with Restart Meta Quest Link Quit Meta Quest Restart PC Try again. Also insure that any outstanding SW and Firmware updates are completed. That's it. I haven't had an issue in months. Good luck to you.

Thanks for having a look at this. Yes, it should be FWD and AFT, the same as it is referenced in military manuals. The dangers of living a Germany, where FWD is Vor, because that's what it's for. I got a copy of TM 1-1520-238-10 TECHNICAL MANUAL, OPERATOR’s MANUAL, FOR HELICOPTER, ATTACK, AH-64A APACHE. It only uses FWD and AFT. On a side note, the AV-8B-NA NATOPS manuals also only ever talk about FWD and AFT.

In many of the controller settings, such as Sight Select Switch, ANTI COLL Switch, Weapons Action Switch, and Symbology Select Switch, they are listed as "Up" and "Down", when 1) even in your own documentation they are listed as Vor and Aft, and in many cases, such as the ANTI COLL Switch there is no Up or Down, only Vor and Aft motion possible. It is minor, but it is irritating and sloppy. Please replace all the Ups and Downs with Vors and Afts as they ought to be.

I think now that "6" is supposed to be the ramp gunner position. From it you can basically do nothing at the moment, because there is no ramp gun. "3" is the FE (Flight Engineer) position, and RCtlr-[ or ] cycles through the three different work positions (cockpit, wench, and ramp). At the ramp position, some switches and dials work, but the ramp controls do not. You can use key and controller binds to operate everything, if configured, but then again, you can operate them from anywhere, if you are occupying the FE slot. Everything still very WIP.

When I move to the Nr. 6 position, moving the mouse now controls view and there is no way to operate anything on the Maintenance Panel. What do I have to do to access the Maintenance Panel? EDIT: Also, when at 6, the default keypress configured by DCS--LShift 'G', LShuift-LAlt 'G', LCtrl 'G', and LShift-LCtrl 'G'--do nothing. If I move to the Nr. 3 position, they work.

Ignore the one on the page you open. Download the Guide behind the "Download PDF" link. That one is updated.

Yup, didn't realize that at first

Just a heads-up. The F-5E Tiger II Guide has not been updated, or at least the front page date has not. Edit: When I open your link and then https://chucksguides.com/aircraft/dcs/f-5e3/ the page open has the 06/01/2023 version opened in it, but the "Download PDF" link points to the 14/08/2024 version for downloading.