All Activity

this worked for me too however not during case 3 landings (ctd occurs)

They've yet to agree to enact the agreement. I know, it's like something out of the minds of Monty Python. It's great and all, but honestly? Some assurances in a worst case going beyond "It'll work in 2.9.x" would be REALLY appreciated. I don't think a legacy version is going to cut it in the event of 4 modules going the way of the dodo. This wasn't a small install base like the Hawk was. ED's going to have to do something very, very big for consumers in that worst case scenario. I'd be a lot more gunshy about DCS in that case. I would not be alone. That's money I can put into cycling or flying.

I think I found it! It's an alternative to SlugMouse and PointCtrl. Cheaper and easier. I bought it. Works like a regular mouse. D06 Mouse on alibaba.com

Maybe the bomblets are not having time to arm. The canister may be opening but the bomblets are not arming in time. Depending on the altitude you are releasing the bombs, they need time to open and arm the submunitions. You cannot release the bombs from a high altitude and set the burst altitude too low, otherwise you are not giving enough time for the bomblets to arm. Refer to the following thread: Also, I attached a spreadsheet showing the calculated height above ground that the bomblets will armed. Line 36 of the spreadsheet refers to your first run. You released from 19,000 feet with a VT1 of 700 feet AGL. The problem with this setting, considering a standard ARM Delay of 1.2 seconds, is that the bomb will open 33.73 seconds after release and be armed at 34.93 seconds. It gives an altitude of -625.36 feet AGL, meaning that the bomblets will hit the ground before being armed. For the other bombing runs, with the burst setting at 2,200 feet AGL, it gives the bomblets enough time to arm, being able to arm at around 1,000 feet AGL over the target (lines 33 to 35 of the spreadsheet). However, the problem I noticed is that with CBU-99 you need to be right on the money when attacking the target. As precise as you should be using Mk-82s, for example. If you hit a little bit off, the bomblets won't have much effect, or none at all. And by releasing them from altitude, the bombs miss by a little and the bomblets cannot have an impact on target. See the attached track file. I make one run from altitude with no effect, and the another at low level, with much success. From my testing, CBU-99 and Mk20 work way better at low level, from 1,000 to max 5,000 feet over the target. CBU-99 Height of Function.xlsx F-18 - CBU 99 - FMU-140 High and Low.trk

thats an odd series of beeping and it definitely sounds hardware related. Start looking for issues in your device manager, try installing it on a separate disk drive not on your windows partition, and if anything try to install it on a new hard drive separated from the other hard drives. Id just remove the others - save for the windows disk drive and just go from there.

This is what is frustrating and puzzling....if there was an agreement reached 8 or 9 months ago why is the issue not resolved? That is what agreements are supposed to do, right?

Rapier is an optically guided system that's radar simply cues an operator to a target area: "Rapier is a surface-to-air missile developed for the British Army to replace their towed Bofors 40/L70 anti-aircraft guns. The system is unusual as it uses a manual optical guidance system, sending guidance commands to the missile in flight over a radio link. This results in a high level of accuracy, therefore a large warhead is not required." The available units in DCS are the optical tracker, aquisition radar and launcher. In DCS the system is modelled as if it were a radar SAM, and will launch even if the tracker is destroyed. Modelling it as a radar system is OK, but it should stop launching if it has no available tracker. See debrief snip for timing, track attached (Sh*t flying was trying to get the Kh-25 working while discovering my control mappings were all mixed up) Guide after guidace gone 2.trk

Sorry, it should be a "dodo" sound. My description was incorrect. Anyway, as shown in the following video, once the DCS is about to freeze, it will occasionally get stuck and alarm before freezing. VID_20250724_051735(1).mp4

Yeah, when you're dealing with someone who's got an ego the size of Jupiter, things are NEVER easy.... This should've been an easy thing: "Either give us the code so we can keep this module working, or sign this new contract and get paid and we can continue selling like normal." But no... the head of RB seems to think that he can do whatever he wants... while the people who worked for him go unemployed, and the people who bought his product get stiffed with products that have an uncertain future now. Let's just hope that SOMETHING breaks, and we get to keep flying those modules. I'm holding onto them for that very hope.

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