All Activity

I assigned the mini stick on my CH Throttle to the X and Y axis for the cursor control. The X axis works in the correct directions, but the cursor moves down when I move the stick up and vice versa in the Y (vertical) axis. Selecting "Slider", "Invert", nor "User Curve" nor any of the saturation curves does anything. Any ideas on how to reverse the cursor Y axis?

Just in from support...I swear to god, this couldn't be made up. "...and we fully understand your concern about the order progress. Regarding your order, we have arranged with Amazon for expedited handling, but Amazon system currently indicates the shipment date will be delayed until August." Followed by... "Your experience is always our priority, and if you have any questions or need assistance, please feel free to let us know. We will do our best to resolve them for you." My reply, "So send it DHL ffs. Duh!" Time for the video now, the title of which will be 'Pimax Malice'. Somebody very clearly needs to have their employment terminated.

This same issue happened on the Growling Sidewinder Server. I started hot, loaded up the Litening Targeting Pod. This time the visual of the TGP camera came up on the MFD for a few seconds, and then my screen froze, and DCS crashed. Logs and Track File Attached. Server_1_Operation_Urban_Thunder_V7.7.85-20250725-232502.trk dcs.log

Now you know why A6 AI is taking so long. Just throwing the AI in the player aircraft makes many troubles. Not big troubles mostly, but troubles. Too many animation arguments for poor robotbrain.

Hi, I created a custom Laser Guided Bombing mission on the Afghanistan map that uses the older Litening TGP. I get the jet ready to rock with a hot start from the ramp, and when I go into A-G Mode, and select the TGP it shows on Standby, but when it seems like it's about to show the video my screen freezes and the game exits. I am including the recent logs (Looks like errors around MFD textures and possibly loading terrain textures). I have also attached the log and mission files. This is happening right at the beginning before I even get moving. dcs.log Afghanistan Ground Attack Practice.miz

Rob10 you were right!!! You literally saved tonights Trapz video shoot for the Stingers! And therefore ensuring I got to be in tonights recording! You are the freaking man!

Добро пожаловать в клуб...

Regarding the latest update 2.9.18.12722, I would like to confirm that the issue has been solved, as per the changelog: Fixed: CBU-99 with FMU-140 slightly short in AUTO in another pass CBU-99s are working as intended in AUTO mode. They do fall short in CCIP mode, but I understand that it was not the issue being corrected in this patch. Just for you to know. Regarding the effectiveness of the CBUs, be it Mk-20 or CBU-99...you must hit exactly over the target, almost with a Mk-82 precision. I know that in the patch is noted that ED is working on the warhead power and fragmentation effects, so I'll wait for that to be implemented. Right now, from my testing, when released at 10,000 feet, the best burst altitudes, with FMU-140, are between 2200 and 3000 feet AGL over the target. If the bombs are a bit off, they won't work. But, anyway, I can live with it, listening to pilots interviews is not always that a weapon works as intended. F-18 - CBU 99 - FMU-140 Effective.trk

So today the launcher has decided to launch with Chinese? language...What??..... Let me guess - english conflicts with ED logic? 'Deal with it' response posted and marked as 'solution' by 'someone' in 3....2...1... EDIT: Yesssss - my language is selected to English - sigh.

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.