All Activity

这么好的东西怎么没人说呢

Thank you for all your feedback, it is very much appreciated and I am thrilled you have all enjoyed the campaign. I don't find myself in my own campaign section of the forums often and that is largely due to the fantastic testing team I have in place, which means there are very few bugs to deal with. Also the ones that did creep in on release, were fixed immediately. Many thanks.

Пожалуйста.

When that happens always double check the radio frequencies. This mission is a years old now, and things might have changed in DCS this past year you've been gone. Cheers!

My thoughts exactly! [emoji1] [emoji1303] Sent from my SM-A536B using Tapatalk

indeed. So that's why you don't implement it (joke).

seems like sometimes MSAA doesnt work on AMD systems. So reverting the AMD driver can solve it but how and to what driver version? I have to test, but it looks like its not that bad on my side: 6700xt (latest amd driver)

And scored 50 there... Tacview-20250820-101017-DCS.zip.acmi

The work on the DTC aims for realism, its something that has been ask for by many for a long time. I'm sorry its not what you want but that is how it is. thank you

Yeah, that one! Thanks! I really need to get some mission editing skills. [emoji4] Sent from my SM-A536B using Tapatalk

+1 Damage model needs some serious love.

Можно обложку книги?

· Mission 2 both variants: Improved landing trigger.

· Mission 9: New radio conflicts at start fixed, AI adjusted. · Mission 11: Additional AI safety trigger added

Sorry SOLD.....Apologies for not removing the Ad

can you imaging the bug reports we would get

Link 16, helmet and aim-9x were not a thing before XXIc, GPS in aircrafts? certainly not 1991, during Desert Storm ground GPS tools were common, but ALL planes used during confict based on INS, drifting like hell, and pilots often turned back to radio navigation. Fun fact, that even things like NVG during 90's was not a std on F-15's. Our Hornet C lot 20 have upgraded engines and radar over 80's predecessor, it's still relatively close to CW one, if we remove DL, helmet and modern weapons,maybe for those reasons ED added Welleye II that was retired shortly after ODS, so there was practically no chance that lot 20 could even use it... Same can be said about DCS Viper. If you had to use early 80's Viper it would be a culture shock, especially old pulse doppler radar with range comperable to Fulcrum and similarly prone to notching and jamming. A Vipers were not HARM capable either, but older Vipers C were rather comperable to one we have in a2g, just diffrent weapon options with various foreign customers.

Yee, but not like the ones OP proposed Aside weapons random failure (released missiles/rockets not firing, bombs not expolding), would be also good to have radom failures on aircrafts them selfs. There in a feature in the optinos to turn on/off radom failures, but in reality I didn't encounter any so far on any of it.

I think it's a good idea to have it as an optional feature. But correctly determining the likely failure rate of each weapon is difficult.

Seems to be fixed with the latest update.

После нескольких попыток подключения.

While I appreciate that the Corsair did not have an autopilot, please leave it in as it gives me the opportunity to drink a coffee when on a long flight.

If my memory serves me then that is fine, circular error probable (CEP) of 5 meters or less when GPS is available is expected

Did this item sell on Ebay?

Yeah, so the first one is definitely him still being in FOCUS mode. I suppose he did not understand that this particular bandit died. The "bandit is down" callout isnt coming from his radar code but is a visual observation. So his radar logic likely thought that the bandit could still be there, keeping it focused to get it back on screen. You can just get him back to standard scan by using the context actions - autofocus only happens on targets actually on the screen, so he will not focus thin air. The second one, not sure whats going on there specifically. Possibly he did not understand that you left CAGE mode yourself instead of using the context actions. You can enable the Jester Console (RCTRL+L) to get some insights into what he is doing. I would also suggest to hit context action to get him back to standard scan. Note that you can have Jester leave CAGE mode for you by using the Context Action as well - no need to rotate that knob yourself (potentially losing the target visually doing that). If you can reproduce this a track would be great, then we can have a deeper look. Cheers