All Activity

AI Aircraft won't fly a proper overhead break. They fly a goofy pattern, don't maintain assigned speed, and don't get configured properly. Tracks and Tacview attached. Su-25 AI Overhead Break Fail.trk F-4E AI Overhead Break Fail.trk Tacview F-4E Overhead Break.zip.acmi Tacview Su-25 Overhead Break.zip.acmi

I think its fair to assume the F16CM and F/A18 L2 pods are based on litening 2 AT ( or at least the l2 ER. The L2 AT based on public sources is basically just an ER with improved datalinking functions) even if its not explicitly stated in the manual. just becuase functionality wise they all have 2 levels of FOV and 9 levels of digital zoom. Razbams av8b Litening2 pod isnt called the Litening 2 G4 but we can deduce its that particular model from the additional features it has compared to the old litening 2 pod which had the same limitations as L2 pod all those other modules.

Is the return value working? I made a simple script to test, but the return value doesn't work. hookServer.onPlayerTrySendChat = function(playerId, message, all) if string.find(message , [[\test]]) ~= nil then local a,b,c = net.dostring_in('mission', 'return 1,2,3') net.send_chat("a = " .. type(a) , true) net.send_chat("b = " .. type(b) , true) net.send_chat("c = " .. type(c) , true) end end

Ok, I think I can attribute this CTD to not using comms to contact the CV inbound. I just tested the Dogfight Instant Action in Marianas WW2 map. I did a no-comms arrival with immediate CTD on the trap. Previously, I had flown this mission several times, and was able to trap ok when using the usual check-in procedure on comms. Harsh sin-bin for not using comms [emoji1787]. Cheers! Sent from my SM-G998B using Tapatalk

The VFA-41 Black Aces are now fully committed to action in support of NATO initiatives to thwart Red Russian aggression in the Kola Peninsula. (This is a re-work of the campaign from Jane's F/A-18 Super Hornet!) You can follow (and possibly join) the action here: VFA-41 Black Aces

The VFA-41 Black Aces are now fully committed to action in support of NATO initiatives to thwart Red Russian aggression in the Kola Peninsula. (This is a re-work of the campaign from Jane's F/A-18 Super Hornet!) You can follow (and possibly join) the action here: VFA-41 Black Aces

What works for me is as soon as the engine catches, move the mixture to auto-lean and disengage the starter. (I.e. don't hold the starter after the engine has caught)

post your rig specs Pappy.

What are these? Why are these? And how can we make them go away forever? They have only ever happened in multiplayer for me. It was very spotty in the past, but this last update made the game unplayable in multiplayer. I join a server, startup up, take off, wheels up, then the game crashes. Of the 9-10 servers I've flown tonight, 100% of them have crashed and all with the same error and it makes the game unplayable. Edit: I would attach the track files, but for some reason I can only add 1.8MB and every file is larger than that... Thank you for your time and consideration in advance.

Before the update, it worked smoothly. Starter engaged, stabilizing at 700 rpm, moving mixture to auto lean, waiting a little bit, moving to auto rich, disengage the starter and it runs perfectly. Now it stops working after a few seconds at 700 rpm, at mixture cut-off, auto lean or auto rich, starter still engaged or disengaged after some seconds. Nothing works. I tried everything. All controls move into the right direction visually.

This may sound stupid, but... did you by any chance forget to retract the gear? With the gear down, weapon's can't be fired (unless you set the ground safety override switch on the rear left console to override - but it's generally advised to retract the gear instead). IIRC Mavericks won't come off the rails with the flaps in the MVR or DOWN position, but that should put a big FLAPS indication or similar on your MFCDs. Also, flaps auto-retract at around 190 knots to protect themselves from overspeeding, so unless your were fairly slow (even for an A-10, that is ), that probably wasn't the issue. Otherwise, might have been a one-off DCS glitch with an incomplete repair, though I'm not actually aware of any problems with the repair option. If you can recreate the issue, ideally in a short mission, a track would be very helpful to figure it out.

So far, the fix is NOT working. Current script where Growler1 is an EA-18G Growler: EW script EA18Gv2.lua No jamming on the SA-11s, they just go right for the Growlers. Every. Single. Time. I've added a few TACVIEW tapes if that helps. Tacview-20250725-180657-DCS.zip.acmi Tacview-20250725-174258-DCS.zip.acmi Tacview-20250725-161316-DCS.zip.acmi

Blame us, blame RB, blame both of us, but be nice to each other even if your opinion differs from someone else. I can't speak for RB (but I hope they feel the same) but we just want to see this resolved and if it were easy it would have been by now.

Exactly why I suggested it. We would have a clear distinction and it would use a real term to do it.

I'm gonna hold on to my opinion until Iraq and Afghanistan are done. I will say Urgra sets the bar though. They do a really good job at making their maps not only look good, but also populating them with a lot of detailed POI's.

Hi Whisky.actual, Does the Rb-15 and/or KEPD 350 long range cruise missile work in your mod? The RB-15 rarely is able to find targets. KEPD does not seem to work at all. Thanks for this great mod in any case. Markus

Cool cool, I’ll sit back and watch silently

I am pretty sure the thread has been on repeat for well over a year, but that's what it's for, venting, and I do share feedback with management all the time.

Make sure to take pictures and posted them here. Seeing the actual product(s) should speed up the process.

That would be nice as a killbox is a thing

No matter what I do, and I hadn't any problems to get the engine running before the update. Anything new in the procedure I have overseen?

It would be great if VR could have a universal driver-level frame generation feature like Smooth Motion...

Flying with the Moza AB9, using direct input (not telemetry input) and the stick shakes with gentle pulls in gentle turns, nowhere close to stall or typical buffet. Needs a little tuning in the future when you see fit. Thanks!

It’s not the hard landing. There is chatter in the forums for all the carrier aircraft causing a CTD when catching a wire with the hook on the various carriers. I’m hearing reports that calling in your inbound with ATC commands is a fix for now, but I haven’t tested it yet.