GeoS72

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

Here's a quick update: the problem appears to have resolved itself. Don't know how or why. I'd like to leave this open in case anyone else has a similar occurrence or wishes to share their experience/insight.

Quick update: I changed the name of my Saved Games\DCS folder to DCS.old. Then I ran DCS, it built a new Saved Games\DCS folder. I was able to get into the main DCS menu. Next, I exited the game. I then changed the name of this newly constructed folder to Saved Games\DCS.temp and reverted the folder Saved Games\DCS.old back to Saved Games\DCS. I then ran DCS and I was able to get back into main menu with all of my settings intact. The screenshots represent what I see when the error happens, create a new saved games folder, and then revert to the original folder. I also want to point out that I get the same result (crashing at 10%) even after a repair to DCS.