All Activity

At first sight of this the pedantry made me chuckle . Being a lifelong sazzy bassa and an English pedant myself I have to point out the ‘Eagle Dynamic’s Map’ should have no apostrophe at all. Written as it is would mean ‘Eagle Dynamic is Map’ which just isn’t right .

Latest update shows rotor rpm and the skids have feedback now. Still no weapon feedback. For those curious

Why do you @ me on this issue?

I apologise if this has been answered but will Murharraq Airbase Bahrain be included in Southern Iraq map? There are some missions I would love to recreate if we ever do get a Tornado.

At the current state of the module, what we observed is not an inaccuracy related to the INS+GPS. Taking care of the standard procedures, that @BIGNEWY kindly reminded us, the drift is within the expected amounts, expecially when observing it through a Targeting pod in INS tracking mode. What we continue to find very odd is the constant misalignment of the SPI/Steerpoint symbology on the HUD, (given that what a TGP is showing in INR is the current INS solution for that coordinates+elevation). That Square, or diamond, is never aligned to the same point where TGP is pointing, there is always a difference and in some missions i've flown that discrepancy became very big (more than 200ft). I don't know how to reproduce the steps to make that misalign bigger, but it's never correct, even when just took off with a hot started jet. Seems there is always an elevation error, because the symbology seems to drift over/under the ground so it moves changing the view perspective. But, for example the calculated SPI for CCRP is never the HUD symbol (just try a good drop to see it), but the actual INS postion shown by a Targeting pod in INR, so it's the HUD to be inaccurate. This is the issue i think it's making the DTOS mode quite useless with GP ballistic bombs, if you don't have a TGP all the designations made by the HUD are wrong. Aswell, expecially in the pre-GPS-era operations, without a TGP even the INS fixes made by HUD are inaccurate.

Good talk.

Is making a DTC easier then adding additional waypoint properties? In that case, how long do we have to wait till the DTC is coming out since we don't have a roadmap that gives us an general timeline.

perhaps in video game land, in a world bound by the laws of physics mavericks very much cannot.

Ok in that case we need to do the same for aircraft on multiplayer servers. Aircraft got destroyed before you had a chance to slot in? Tough luck.

Just out of curiosity, whats the caution light panel say? I don't have 23 minutes to spend watching the track

Okay, I just replayed it and the game crashed. I didn't restart the game, so hopefully this is what you need. I should mention that I have played a couple of the other missions in this campaign through the mission editor...because I can't advance from mission 1 and I have had no problems. Also the FCR does not seem to be identifying any of the targets although the TADS shows them. Also the TADS does not seem to be looking at the targets that the CPG is targeting. Stone Sky thinks the issue is P and E cores? It just seems odd to me that I have no other issues except for mission 1 in the outpost campaign? Thoughts? dcs.log-20250904-225029.zip

Can someone help? Trying to make ground targets that will not shoot me. I have HOLD ROE = Weapons HOLD Disperse Under Fire = OFF Mi-24 Gunnery.miz

Looks outstanding. Thank you.

Try looking at an image that has a real heat signature greater than ambient. The images are essentially blobs. I believe it's being caused by too much bloom in the shader. At 5.7nm I CANNOT resolve that I'm looking at an F-16 in flight without it being at 90 deg profile image. I believe that it is less sharp an image than were used to but I also believe that the shader bloom is washing out more details than perhaps it should in DCS for a balance of realism vs playability since the MFD screens and images we're using can't display images greater than 1024 resolution as set in the settings (as I understand it, please correct me if I'm wrong)? So it may be a way to achieveing a more "realistic" effect being able to go from an unresolved blurry image to one that has good detail in XR, but because we're using lower resolution already it's hard to make that a effect compelling without making it more blurry to begin with? I could be way off base but seems like it could be part of what's happening.

Maybe i'm saying something obvious, but try to go in CNTL Menu and do the FLIR CALIBRATION. With that done i achieve almost the same quality of the Litening pod, in NON-XR flir modes, i mean.

Yup. All that should work out of the box with your TM Warthog. So the answer is yes. Yes. There is a "Reset category to defaults" option in the controller assignment dialog for each controller category. None that I am aware of. Now what's missing...? Chances are DCS fails to detect the position of your throttles when you enter a mission, and thus fails to detect when they get moved from OFF to IDLE. There's a sensible explanation for why that is, but the gist of it is, there are 2 common ways to solve the issue. After entering a mission in the A-10C or A-10C II modules, move your throttles from OFF to IDLE, then back to OFF. Now DCS will detect the next motion from OFF to IDLE. (Or, my personal SOP: Keep throttles in IDLE, then when entering a cold start A-10, move them to OFF after I've slotted into the cockpit and the mission is actively running). Set Options -> Misc. -> Synchronize Cockpit Controls with HOTAS Controls at Mission Start to Checked Does either of these solve the problem?

TGP is too shaking in multiplay and multi-crew

Just keeps getting better and better . . .

Oh yes, apologies. After a long day at the office I would have preferred to respond sooner. But I had to watch your 48 and/or 23 minute long tracks, or else all I could have responded with would have been "Hello." You omitted a few key parts in this initial description, but at least the 23 minute track does clear things up. Repairs have nothing to do with your issues. The repair works fine. I'm going to give you a hint without actually answering your question. You'll thank me later. Check. The. Caution. Light. Panel.

9/04/2025 - Updated to version 2.0 - 3 NEW cirrus cloud textures - Improved several other cirrus cloud textures - Improved cirrus cloud shadows - Various cirrus shader improvements - Increased fog visibility cap in the mission editor. - Fixed artifacts in Scattered Shower 5 cloud preset Low Resolution and legacy versions available here: https://drive.google.com/drive/folders/1jEVEdgFXQAVfvUsUMLnOiC4RaUGxEaA5?usp=sharing

Приветствую! Возник такой вот вопрос, который я уже пробовал задать в англоязычной ветке. У Сушек из ГС3 код лазера 1113. насколько помню, у старого Ка-50 тоже. Однако, для BS3 код изменился. Может ли кто-нибудь подсказать, какой у него сейчас код? А то на том же Апаче сушкам я светить могу, а вот превратить полтинник товарища в круглосуточную машинку уже, увы, нет. Был бы крайне благодарен, если бы кто подсказал

"Don't laugh, but DCS: Cessna 172 (or similar)" lol 172 in DCS. ....jokes aside. Honestly, it would be alright and same would go for civilian helis. I guess the market/user base interest dictates that? I would love for A2A to have a dab into DCS with their persistent wear system, it doesn't necessarily need to be a 172. Could be a Cessna Caravan that could sneakily get into that civilian slot by having weapons as well.

I'm asking because if I'll recognize the code for Ka-50III I'll be able to support other 50's with my Apache. Even make them day and night. Anyway, thanks for the advice. I'll try Ru sub-forum

how far from the target are they hitting?

It seems track reliability is also dependent on one's hardware (mostly peripherals). Thus, the same track can work OK for some guys and be useless for others even when recorded and played in the same DCS version.