All Activity

Hi Guys - an update. But first, a big thank you for all your comments and suggestions - WE HAVE IT FIXED (hopefully) Went back and checked the 'dodgy' SSD on another USB port (original USB port was a USB 3.0 so should have been OK) - same slow rating with Crystal Mark. I also had another of the same SSDs (bought them on discount for the pair) - is being used just as additional back up drive on my wife's PC. Same slow rating on Crystal Mark. Does work fine as a back up file drive anyway - so looks like the wife gets another one. They are a Seagate 2TB SSD so you would think OK. However, maybe the discounted price was for a reason !!! For info Drive H has a USB-C connection and works great. So, copied (as suggested) DCS folder back onto the original Drive D internal SSD. Did a slow repair, edited relevant shortcuts etc ...... and it worked just GREAT. Much quicker loading, runs as smooth as silk, no stuttering or lagging in both triple screens and VR .. I am in love with DCS again. So looked like those SSDs are just not up to the demands of DCS. So have placed an order for an ADATA Elite SE880 USB-C Portable SSD 2TB Drive. Specs seem to indicate that will do it. so once that arrives will copy over to that SSD and start to reinstall all those maps and modules waiting for me. So once again, thanks

Invert does it for me. Are you confirming your choice with double OK? Sometimes people just cancel their choices without thinking about it? You can also do a repair.

Where does it say that? I'll bet you $20 the real horn comes on in the first 1/4" of the throttle's travel, not the first 1/4 of the throttles full range of motion, then someone misinterpreted it, and no one went back and checked.

This horn cannot be right at all, min rpm of 1800 lets me run a little over 33" of mercury (+3 boost) before the horn sounds, and the mosquito cruises along at about 230mph. Fine, but what if I want to loiter in a spot, say in a maximum economy mode, perhaps while attempting to communicate with the navigator, or via a radio. Why do I need to listen to this horn throughout that? Please someone show me a source that says it was really like this, otherwise common sense was not consulted on this module.

I ran VAICOM PRO with 2.7 a couple of years ago and could say 'Salute' to launch off the cat (SC). Took a break for a couple of years and coming back to it and for some reason 'Salute' won't work any more. It looks like the Pilot Salute key bind changed to LAlt + LCtrl + LShft +S, so I changed the keys in the VAICOM profile, but when I give the command, I still sit there on the cat. I'm getting the Recognized: 'salute' and it's sending (Ground Crew], [Salute] but nothing happens. If I manually press the keys, then off I go. I've tried reconfiguring the key binds in DCS and VAICOM and am at a loss. Anyone have a suggestion? Thanks!

Yes, I’ve tried that too. I’ve installed DCS on both of my solid-state drives, but it didn’t improve the issue at the time. From what I’ve found through searching, this beeping sound might occur when the system freezes due to high CPU load

Lol. Couldn't make it up? Pimax managed it. Again.

And if one side has breached said agreement, repeatedly, why would you wanto to implement it? Timelines and attention to things and details being said and done outside of the box are important here.. 6 months ago on various platforms one of the main protagonists in all of this stated that ED hadn't even been in communications and/or were not responding to communications, and shouting to all who listened that ED actually went back on a deal that had been made.. IIRC this was about a release of funds... first breach of said confidentiality clause twice in the past 4 months Ron Zambarano has gone to the court of public opinion stating more or less the same thing, and that they had exhausted all measures... more breaches of the confidentiality clause... Do you not see a pattern here? Ron and his subcontractors should have stuck to "Less said, soonest mended" If the confidentiality clause kept being broken, why would you implement whatever agreement was put in place... Ron needs to take a close look at himself and realise his ego is one of the main issues here. Notice that by all accounts, he still has accesss to ED's SDK after it removed, he's not mentioned anything recently about it having been removed again...so that's the glimmer of light in this shyshow.. Nick Grey also needs to do similar.

Happened to me three times, once on 4YA server and twice in Afganistan weapons practice instant action mission. Command George to FCR area search; select target; select George weapon missile; consent to fire...instant CTD. Track attached. Edited to add: engagement with laser HF on point target worked fine, as did the traditional PHS point search and engagements. LastMissionTrack.trk

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!