All Activity

That's also what I saw in the track. The right engine never finished the startup, and when you taxi on the thrust of the left engine alone, the thrust asymmetry causes a severe yaw to the right. It also means the jet barely gets airborne on the takeoff roll, where the yaw instability should be the least of your worries. I'd recommend to make sure all caution lights are off prior to takeoff and give your engine instruments a good look-over to check they're all in the green. That is correct, but doesn't mean the autostart sequence is going to work 100% of the time. Anyway, in this particular case it looks like a know issue where the engines don't start up correctly when the outside air temperature is around or below freezing. So the repair didn't cause the issue. The requirement of shutting down the engines for the repair and the consecutive attempt to start them up again caused it to surface, and it wasn't evident before in what I assume was a hot spawn. The fact that the autostart sequence doesn't detect or report errors plays a role as well, compounded by the pilot's failure to monitor the aircraft systems after the automatic startup sequence.

I agree. But the the company who build the motion chair is going to bankrupt... they won't do anything. I agree. But the company who build the motion chair is going to bankrupt, they don't answer anyone. And the company who develop SRS said ED is the one who can solve this by adding a simple basic "destroyed" event to the event list.

@Massun92 will a stop animation be modeled in a future release? It would be nice to have the ability to set up ground crew who form an X with their arms when you hit a trigger zone. Or better yet, if they could direct you left and right and tell you to stop based on triggers.

OMG! Are you serious?! Vakarian?

Oh my bad. It would be Eagle Dynamics’ map since Dynamics is plural. Corrected to Wag’s map.

It's great that you are reporting the bug, and even better that you added a track. However, a track using mods will be useless to the devs as they won't have mods installed and therefore won't be able to play it.

Ein herzliches Willkommen auch von mir. Ich hatte meinen Einstieg ca. 1987 als 9 Jähriger am Atari ST mit dem Flightsimulator in schwarzweiß und war angefixt von den Instrumenten. Danach kamen auf Amiga F-29 und die üblichen Verdächtigen von Microprose wie F-19, F-117, F-15 StrikeEagle... viele andere coole Sachen wie Wings, Wings Of Fury... und zum Schluss raus Gunship 2000 am CD32. Bei meinem Freund am PC kann ich mich noch an EF 2000 erinnern aber dann war ca. 15 Jahre Schluss, bis ich mir selbst um 2008 rum meinen ersten PC gebaut habe. In der PC-Games Zeitschrift war LockOn - Modern Air Combat als Vollversion dabei und ich war begeistert! Es folgte sogleich Flaming Cliffs 2 und Ende 2010 wurde es dann so richtig "professionell" mit dem Release der A-10C und dem dazugehörigen TM Warthog Stick&Throttle. Ab da an war ich viele glückliche Jahre zusammen mit einem Warzenschwein Danach kam vieles... Bleibenden Eindruck hinterliesen die Huey, Mig-15, die F-14 und einige Warbirds, vor allem die Bf-109 und aktuell grad die P-47. Der absolute Gamecanger war im Dez. 2020 als ich auf VR umstieg. Ab da an saß ich zum ersten mal "wirklich" (also meinem Hirn wurde es zumindestens so vorgegauckelt;) im Cockpit und ich war überglücklich, bis heute... wo ich auf ein Upgrade meiner G2 warte... Entweder ne Beyond2 oder ne CrystalSuper, je nachdem was eher kommt und überzeugt. Dir wünsche ich viel Spaß hier im Forum und in den Lüften von DCS

Nice and thanks

I noticed that. To me that just means that the ground crew didn't finish fixing the aircraft; if it was actually fixed correctly there shouldn't be any caution lights after the startup sequence is finished. Instead it's showing that they left the right engine and hydraulics borked.... which is interesting becasue I didn't break any of those, just the landing gear. Do I just need to push the caution lights to fix it?

Hello, could one of the Winwing MFD displays be programmed to place the HUD view ? Hola, se podria programar una de las pantallas MFD de Winwing para colocar la vista del HUD ?

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.