GeoS72

FWIW, there is no difference when using the rudder AND wheel brake at the same time. An adjustment to the wheel brake/tail wheel caster effect is requested.

It would be very helpful to add text to the Controls Indicator overlay to differentiate between Propeller, Throttle, Blower (Super Charger), and Mixture axes. I added text using GIMP; the text may be oversized but it could be resized accordingly. I wanted to have the vertically oriented text be superimposed on the respective axis with it outlined & filled. But GIMP was not cooperating with me. As an alternative, adding P (Propeller), T (Throttle), B (Blower/Super Charger), and M (Mixture) at the bottom of the axes would also be informative without being intrusive. Could this be added to the module?

When you takeoff, skid off the runway then land on your nose...and not die. It looks like the spinning prop acted like a gyroscope and kept the aircraft wobbling like this. You could even raise the gear, fire guns and rockets with no detriment to the pilot or plane!

UncleStains, I already have a bug report for that keybind issue.

Case in point: After cold starting the Corsair, I pulled forward and began to turn left on the taxiway. I couldn't make a sharp enough turn despite the tail wheel being unlocked (by default) and fully pressing on the left brake pedal. It barely turned left. This should be addressed because it makes turning on deck (carrier) or on land a bear to accomplish. Warbird Practice_005-20250620-142341.trk

Cheese, Thanks for commenting. However, the axes are properly bound. When I step on the left brake, the aircraft will first turn to the left. After releasing the brake, it will then swing right. And vise versa. It's like there is a phantom applying brakes. It is also very difficult to "spin in place" when applying brake to one side; it is the opposite effect when you jump into the P-47 or P-51. You can spin around to your heart's content in a P-47 or P-51.

A keybind for charging the guns would be awesome!

I'm not sure if this is a bug or not: Differential braking is challenging in the Corsair. It will suddenly turn right after applying left brake and turn left when applying right brake after it makes the turn in the proper direction. Additionally, when attempting to take off from ground, the brakes feel like they are engaging. All keybinds are properly set. I do find it odd there is no brake axis visually represented in the ControlsIndicator overlay.

The keybinds for turning the gunsight light switch on/off and gunsight light intensity +/- do not work.

I was certainly confused, especially when the narrator says, "the red button on your stick"! Thank you for the attention to detail! For some reason, any preset loadout with the Tiny Tim rockets will not load. You can manually add them, but the Tiny Tims will not load from a dynamic spawn or automatically load in the tutorial.

Thanks for the tip! Not sure why a separate rocket release button needs to be mapped.

After following the tutorial twice, the HVAR rockets & Tiny Tim rockets will not fire.

Bumping thread for visibility & awareness. The TEDAC is still being actively blanked for the Pilot and covers up the Autopilot Controls Indicator overlay.

Looking to garner some attention by ED regarding this month old thread.

I month old post. Bump again to address IC failure with ControlsIndicator file.

@BIGNEWY, Thank you for re-examining the Hornet Pilot survival rate with the rest of the ED team!

@BIGNEWY, thank you and the ED team for quickly fixing the detailed score bug in the 30 May hotfix.

@Orko & @CaptJackG, What did you use to replace your springs? After some shipping issues with WinWing, I finally installed my replacement springs. TBH, I went back to the weaker replacement springs that I purchased through McMaster-Carr. The weaker spring rate is perfect for flying helicopters, especially when I choose not to use force trim. Yes, I'm aware how strange that appears (a topic for another time). Has anyone used the 1NAV4 spring from Grainger that @Orko recommended? I suspect it would exhibit similar spring rates with the McMaster-Carr version because they feature similar specs. My concerns with the Grainger-sourced spring are: 1. Eyelets are turned 90 degrees from each other (should be aligned). 2. Total length: 1 inch 3. Wire Diameter: 0.045 inch 4. Outer Diameter: 0.36 inch 5. Active coils: 8.65 The WinWing spring dimensions are as follows with metric (inch) values: 1. Total length: 22.2mm (0.87 in, close to 7/8") 2. Wire Diameter: 1.4mm (0.055 in) 3. Outer Diameter: 9.4mm (0.37 in, close to 3/8") 4. Active coils: 8 to ~8.4

@MadKreator, et al: The squeaky wheel gets the grease. When more people complain about an issue then the higher priority it becomes. One of my arguments to enable users the ability to modify the overlay location: the ControlsIndicator overlay for FC 2024 aircraft has a file that can be edited. While many of us share your sentiment regarding ED's priority for improvements, the more users get involved would help resolve these long (or very long) standing issues. Feel free to share this thread with other multi-monitor users flying FC3 aircraft. For the forum moderators: I provided at least 2 options to potentially solve this problem. @Eagle Dynamics, shall we talk about this topic some more?

Can this topic be revived or investigated further? It's been on the back burner for quite some time.

Bumping the thread for increased visibility. I'd like to explore the potential to reposition the ControlsIndicator overlay for FC3 aircraft AND not break integrity check. This will help many of us with multi-monitor displays.

Bumping the thread for added visibility. ControlsIndicator file causes IC to fail. Can this issue be addressed, please?

Affirmative, Detailed scoreboard is broken. Overall points are good.

Rob, Thanks for the recommendation. Removed the B-2 mod and still had the same issue. I had to create a new DCS Saved Games profile, start DCS, then exit DCS, change the new DCS Save Games folder and finally restore my original DCS Save Games folder. Then I was able to get past the 10% choke point.

This god-damned game frustrates me to no end! I just want it to work consistently! The dreaded crash at 10% loading screen came back after updating to the current version of DCS. I had my VPN enabled previously and I was able to log in to DCS. When I attempted to join a multiplayer game, it loaded but then booted me after 30 seconds. That's a separate issue with NordVPN. Please check my NordVPN thread about that boon-doggle. After disabling NordVPN, I restarted DCS. Aaaaaand it's gone! DCS crashes! I ran the DCS log analyzer and this is what it said in the errors section: Attempt to index local 'b' (a nil value) on Line 77 in ./Scripts/image_search_path.lua So why is this happening? dcs.log