nickos86

That's great news! Thanks! Seriously, I understand from the long time it took to create those flares that it far beyond changing a constant in the code. If possible - it would be great to learn about the challenges/ research/changes required even for a 'small' item such as a flare. This 'peeks behind the curtain' are very interesting and shade some light about the challenges of sim development.

Hi ED, seems like you really put an effort to academically research the HARM flight profiles! Good job! That would be awesome if you could share more info in this regard. P.S The increased number of flares seem to be a community request for around two years now Hope we'll see the same academic approach and research update prior to release. Seem to be a hard and demanding task... Keep the good job!

I honestly don't understand how the current mechanic of the AUTO/PTRK of the ATFLIR/LIGHTNING can be some thing that the pilots can work with... It's makes it incredibly hard and not intuitive to lock a moving target...

Hi Ugra, any chance you can comment on this? Thanks!

Yep. Flew to waypoint per the speed the HSI gave me. At waypoint 1 pressed the WPDSG and it brought the required GS in the HSI way below the desired speed I've entered (520). I guess that the WPDSG calculated the correct speed required to be on target on time. Without the WPDSG - the speed stays 520 const.

0-1-2. the TOT was for waypoint 2. BTW, I've kept the speed until waypoint 1 as instructed by the HSI. Then switched to waypoint 2 and accelerated per the desired speed. Because it was the leg of the bomb run, I pressed 'WPDSG' and it completely changed the speed. Seems like at the waypoint before the TGT you need to press WPDSG in order to get 'live' GS requirement. In WAYPOINT - it stay constant on the HSI

I've entered the TOT and GSPD for a target waypoint (selected it as TGT - it had a white square around it). It wrote a constant GS on the HSI instead of giving me the required GS I need to keep in order to be on time at the waypoint. Does the GSPD works? Is there a know bug? Should I do something differently? Thanks.

Issue was already brought up in the past. Personally I think the perspective right now ain't good. You can't see the RWR as you've said and you barely can read the MFDs without zooming in. From talking to multiple F-16 pilots - it's not an issue IRL - You easily see the whole RWR and the MFDs are super readable. I don't believe we'll get an ED response here. Maybe just a [Correct as is]

After using SEA and AGM-84E - game crash at exit dcs.log-20210204-190920.zip AGM84D_training.miz

Same here. It's a horrible bug lasting for ages now. No matter how many time I do the process above - it returns. Every time you go for a SP/MP sortie - it's a Russian roulette in regard of whether your FLIR will work or not... ED, can you explain what is the reason for this bug? Plans to fix it soon? Thanks.

Hi, Seems like it not implemented at the moment. ED, any plans to make it work? Thanks.

Superb! Thanks for the info! One last question - Is there a 'forced' allocation for 'other' contacts? In case inside the chosen distance there are 10 'friendlies' and 5 'others' - will it show 4 friendlies and 3 others or all the 7 slots will belong to friendlies? Thanks for your time and knowledge!

So, you would prefer to keep the HMD distance small as possible? If you put a 100 NM distance - the HMD will most likely show you only friendlies. You would prefer to keep it around 20-40 NM tops to increase the chance for the 3 spots allocated not necessarily for friendlies to actually show 'others'? Moreover, If I've got you correctly - in case there are no friendlies - it should show only 3 'others' or in this case it will allocate them the whole 7 symbols? Thanks.

Good job ED! Thank you!

It mean that when you turn on the battery you immediately get all the power load from the pumps. It could damage the electrical system, no? I would be better to add this systems one-by-one, no?

Awesome! Thanks!

Bumping. Dear Nineline/WAGS/BIGNEWY - could you please provide a mini update regarding the Hornet? Almost a month since last update and we craving for some info and perhaps some eye-candy. Thanks in advance!

why not doing a D like model so that the plane could carry 4 missiles?

+1 The cockpit is very dark again. Internal light barely change anything.

Hey Maple Flag - any chance to convert the campaigns to the new A10C II?

For the 'swap' function - it might be useful in real life because it might be better to remove the hand from the throttle to touch an MFCD instead of removing the hand from the stick. As a simmer - i guess it's impossible to 'imagine the scenario' and the benefit it might bring. It would be superb if a real pilot/SME could give his two cents in this regard. regarding the the Ad 2- I agree with your theory. Overall It make sense. In the F-16 you switch SOI by pressing DMS down (could have been collie switch down for the A10), changing the pages on the MFD with DMS right short for the right MFD (it will move one page at a time) and DMS left short for the left MFD (again, it will move one page at a time). Those could be collie right/left short. DMS up puts the HUD as SOI. Overall - much better in my opinion. The collie down long bringing the DSMS is really a nice touch. I use it to verify what ordinance i still got left on the plane without going out from the TAD screen. I guess that after a while when HOTAAS become muscle memory it becomes pity to change the HOTAS config... Although if it was done as in the F-16 - it would be better in my opinion

Hi, Snoopy/experts - can you explain the SOI changing logic using the coolie switch? In the F-16 switching the SOI (or the 'active performed MFD') is faster and easier - pressing short DMS down. In the A10 its a long press to the side while the short DMS down swaps the screens. 1. Is the 'swap' function is really that useful in real life? 2. What's the logic of a LONG press to the side instead of a short press down? It's interesting to know if it's simply an historical decision or there is a real benefit to that in term of 'flow'? Thanks.

Radio volume, tacan, etc.

attached a few tracks attached a few tracks For GBU38 - seems like the range in the HUD is wrong - too long. Need to lunch much closer to the target + it less accurate than before in. For GBU54- In case you've lased the target and stopped - it behave like a GBU12 - continue it's ballistic drop instead of aiming to the last point of the laser. So, incase you've started lasing - you have to continue until it hits the target. Else - it will miss. In certain lunch profiles - if you lased and stopped - it will lose track of the laser and continue flying forward instead towards the target. GBU38_miss1.trk GBU54_miss1.trk GBU54_miss3.trk

+1 There is some kind of a problem with the GBU38/54 now. I experience the same problems as mentioned above.