Nooch

At the moment, you mean currently in DCS? Not right now but the F-16 and F-15E will be coming sometime in the future and those can drop it.

That's some good news indeed. Excited as well!

I'd go with Korea.

ED really need to fix that. Way too many times have we seen an update that breaks a major part of the sim. I think it's time they take that problem very seriously. Hornet updates are now released monthly to avoid problems, which is already a step in the right direction but that might not be enough. I'm not a coder but I think they might need to rethink the way they write their code.

Ok, I compiled and ran the code and it works... until I shut down my pc. The lights do not remain off after I boot back up.

Do you mean .fcf file? I haven't heard of .tmc, not sure how you would create that type of file.

It's a fantastic module and as said before, all it lacks is a Korean map to go with it.

Flying the Open Beta on a SSD with a 4670k (@4.4GHz), 16GB of RAM and GTX 1080 Ti and I'm not having any issue.

That's pretty obvious stuff. These campaigns have been designed by normal folks with fun in mind, not by real life A-10 experts or die hard realsim enthusiasts. If you are looking for something super realistic then I would encourage you to make your own campaign. I would buy it!

I don't know what I'm doing wrong but I can't have the leds turn off permanently. I simply unselect the enable led backlight option in the target gui app and it works as long as I have the pc turned on but when I reboot the leds light back up. Any idea?

Pimax seems to have a crappy customer service. I remember someone on this forum who had to send back his unit because dust made its way behind the lens and the Pimax guys straight up refused it. Maybe an isolated case maybe not.

I agree with you there and just as you have, I've heard pilots say the same. A thread was already created about it but nothing was done... I don't get it.

About 3 feet (height between the sensor and the ground) which seems perfectly correct in this case.

I think you didn't read my post properly. The issue isn't that it shows something other than 0 when it is off. That could be a normal thing, as you said. The issue is that it shows 60 feet when you are starting up on the deck. It doesn't make sense for a radar altimeter. It's like it was able to see through the carrier. Plus this happens to be inconsistent with when you turn the thing off manually, where it shows the height between the sensor and the deck (about 3 feet or so) which makes a lot more sense.

I know it's a small issue but please consider reporting it. Thanks.

I've noticed an odd behavior when using the stopwatch on the IFEI. Basically when you press the button when the timer is running, the display stops but not the timer itself. In other words when you press again, the time on the stopwatch jumps forward. Not a huge deal but might be incorrect behavior. If I recall correctly it was not doing this in the past. I've attached a track below. hornet ifei timer issue.trk

I've noticed an issue with the time displayed on the bottom of the DDIs not matching up with what's displayed on the IFEI. The four digit number on the DDIs represent minutes and seconds and they should in theory match what the IFEI displays. Track included below. hornet ddi time issue.trk

When parked on the carrier on a cold start with the radar altimeter off, it does not display zero. Not only that but it reads the aircraft height above the water, somehow sensing through the carrier deck. When switching it on, it returns to zero and correct height starts being displayed. Track included below. hornet radar altimeter issue.trk

You can already play music as much as you want, it doesn't have to be handled in-game. Sorry, I don't see the point.

Basically. ED's engine is very well optimized on the GPU side but not on the CPU side.

I would be in favor of having SLI in DCS but before this we would need to have better CPU optimization. Right now DCS basically runs on a single core and that creates a huge bottleneck for the GPU. Until we get that fixed first, adding a second card will only increase FPS by a marginal amount.

From what I've heard on Youtube the Tomcat sounds great overall but there are a few minor things that annoy me: -when pulling G's, it sounds like your old grandma's chair squeaking. I would prefer no cockpit shaking noise. -when the canopy gets shut, it sounds like your kitchen's door and not like a fighter jet canopy. -when lighting up the afterburner, you get a roar inside the cockpit (just like the Viggen by the way) and this is a sound you should be getting only when outside the airplane, not inside.

I think you are mixing up things. There are two separate versions of the sim: the "Open Beta" branch and "Release (non beta)" branch. Open Beta is used to test new stuff before they get validated and put into the Release version, usually a couple of weeks later. Now a module can be also tagged Open Beta (or Early Access, same meaning) but this is different. This means that the module is still new, being developped and not feature complete yet. So basically Open Beta can designate two different things, whether it's used for talking about the version of the sim itself or talking about a given module. As Quigon said, the A-10C has been out of beta for many years.

NineLine said nothing changed with the update and it's just correcting the version number but why is the update over 300 MB then ?