All Activity

Any change to this? I keep having the same problem.

I got the bug to happen again and the track works this time. I replayed it myself to double check. .LTD/R was in the forward position so it definitely wasn't that. .I was holding down the trigger button good too so I don't think it was that either. Bombed missed anyways. Never tracked the target. This only happens when I find targets with a waypoint at first instead of with the HMD. It's the 2nd GBU-10 I dropped on the 2nd sortie. Russian Bottleneck on Bridge (2025) - BUG happened - GBU-10 didnt track on 2nd sortie.zip

Thanks Patgun for the great explanation ! I had no clue it could sense flaps, gears, afterburners etc. Very very cool stuff for sure do you have a link to the product? I might be quite interetsted to buy it in the future!

Just need to assemble it. Thanks for the instructions and code man.

Can AI use this? Like Maatdors?

This is the best its ever run with the super. so far, its exceeding expectations and seems stable. this maybe dialed in now from a "this is a solid starting point" Ill let you know if it stays fixed. Thanks

Be Carefull! Test on an old laptop or something. Not your new rig! There is also a version that has 4 buttons on it. Look for it at the end. Flight sim throttle: https://www.thingiverse.com/thing:5440863 D/L from the links he provides, and read the page. He shows you what to do. DO NOT SKIP! https://github.com/JammyJ1mJ1m/FlightSimThrottle Here is a link to help be a bit more quiet https://www.thingiverse.com/thing:4599583 Arduino Joystick Library https://github.com/MHeironimus/ArduinoJoystickLibrary Easy Switch: https://github.com/JammyJ1mJ1m/easySwitch 4 Button Throttle https://www.thingiverse.com/thing:4572199 Circuit board design https://mega.nz/file/5hYEnaKT#Do_0LLvn8MpcwfsK564IMBSMZMiB1nlqBuKjJ7Wu6z0 Throttle code: I found a comment from the maker: This is the code you have to upload with the Arduino IDE on your Arduino Pro Micro 32U4. https://pastebin.com/sA26rfCC Hope this helps someone and that it all works in your game. Here is bom for ShoYun's throttle https://3dmdb.com/en/3d-model/flight-simulator-throttle-quadrant-by-shoyun/8195713/ All thanks to JammyJimJim and ShoYun

Ok, I found the issue. I was reducing saturation of the elevation axis to make the radar tilt more controllable (fine). If I reduce the saturation to 5 then the zoom doesn't work. If I set it at 10, the zoom works.

Working great so far!

FUSE SELECTION DOES NOT WORK.trkSee Attached Track. In this situation the bombs are equiped with 11 second delay tail fuses and instantaneous nose fuses. With Tail fusing selected, the nose fuse should not function, resulting in 11 second delay. With Nose/Tail selected, both fuses should function, resulting in instantaneous explosion. As you will se in the track, with tail fusing selected, the bombs explode immediately on contact with the ground. The nose fuse should not function in this situation (except in cases of weapon malfunction which is not modeled in DCS and in any case the results are consistent in all of my tests).

Видео из таквью синхронизированных лучших результатов

Interesting I thought I unparked the cores. Ill look into all this. Thanks!

Is it possible to have your F10 preferences saved some time in the future? It saves for the time of the session but would be really cool if it always saved based on the options you have and don't have selected, View, map/alt/sat, weapon names etc

The magic comes not from any technical wizardry but from how our brains perceive latency. When repeatedly exposed to latency of up to around 150msec our brain adapts and we perceive events such as our motor input on the controls and the visual feedback in the headset as being simultaneous. That however does not make the events simultaneous in reality and means that for things where a delay could be significant (like say oblique gunnery in BFM) the effect is still there even though we don’t perceive it. So when someone says they can’t feel any latency with a standalone headset they are entirely correct, they can’t feel it. That doesn’t mean however it isn’t there.

Hey, no worries — I was totally lost at the start too If you give me your email address, I can send you my files. You’ll need to do quite a bit of tweaking to add your own lights, but at least you’ll have a working base to start from. Upload the files to ChatGPT and it will reply and even modify for you. if ChatGPT wants some more Lamp ID's, upload "\DCS World\Mods\aircraft\FA-18C\Cockpit\Scripts\lamps.lua". file to GPT, it can find everything. Also there is more lua files like clickabledata.lua e.t.c. DCS can send cockpit value out through Export.lua. i had already have a export.lua because of a mod or something. So i add a simple code inside. a Node.js bridge just reads those values and pushes over a Websocket. Runs via powershell but you can build an exe file after you feel satisfied. Then a custom SignlRGB HTML effect listens to and lights the RGB lights. If you're not familiar with SignalRGB, basically, effects are simple canvas. You place your RGB lights on that canvas, and each lights shows the color of the spot it's positioned on. So first things first, your device needs to be recognized by SignalRGB. (almost all my RGB lights, my keyboard and mouse, philipsh hue, case lights, logitech hotas e.t.c positioned on the canvas) Great cockpit btw, have fun.

It does not need to be on that level but SNP2 launch probably should not result in i stant RWR warning.

Here's another recent crash. dcs.log-20250901-234714.zip

I was about to write about this on the previous post but my knowledge about the issue is limited. I saw it on JayzTwoCents report on a yt video but that was it. If I recall correctly, my motherboard wouldn't induce the issue as it is a basic motherboard for personal reasons AFAIK. Of course I would read a lot more nearer the upgrade. Thank you for the writing. It is something to consider too, although I'm leaning more towards the intel upgrade, depending on the 14th gen condition at the time. Thanks!

Heyo, please download the attached .miz file with the fix You used the "condition" field witch is a LUA statement and the number "30" is not valid LUA lol nothing todo with the previously attached "GPS_GNSS.lua" enjoy Syria Operation Lizard Phase #1 .miz

Nice job almost destroying that server. Will you be on alert 5 on Monday at 7 AM just to be on the safe side if the phone rings? The timing with this thread is impeccable. Got a story to share as well. So I run a few Linux servers, and I have a hand written script that anonymizes IP addresses from their log files so I don't get in trouble with the GDPR. It's hooked into the logrotate daemon as a prerotate script. Super simple thing. I'd noticed a while ago that one of the servers takes unusually long to process the log files and is under heavy load every night. Well, the websites shouldn't have that much more traffic than those on other servers, but it's probably some AI scraper crap that's filling them up again and again day by day, forcing the server to go through countless lines of logs to scan for IPv4 addresses and replace the last 2 octets with zeros before the backup runs. Not ideal, maybe I should optimize the script. Maybe tomorrow. You know, the "that was 6 months ago" kind of tomorrow. Last week I found a smart article about optimizing backups and creating transparent snapshots using Linux filesystem hardlinks. Cool, I'm going to implement that. Start with this server first, it's got the least valuable data, just on the off chance I might mess something up. Nah, worked okay, except... the daily snapshot on the backup server was about the same size as the previous one. They should appear to have the same size, but the copy should really be tiny. But the file system was filling up big time, something apparently wasn't properly hard linked and instead copied. I checked a few random files, couldn't see anything wrong. Same file, same content, same inode number, proper hard linked. One thing I noticed while looking at this snapshot snafu was the server took 2:30 hours to get backed up. Similar servers took 2 minutes. That's... odd. Same OS, same software, same version of rsync, same custom backup script. Why on earth does the server insist on copying 400 GB of data every night when there's hardly any changes in the file system...? Ran a few more du -h to figure out where the largest amounts of data were hanging around. Err... the web host log file directories? Gigabytes over gigabytes of log data? That can't be right, there's no way I get so much traffic that the logs are this big day in and day out. Well. Turns out I had two custom config files for the logrotate daemon here. One from another server, and the one adapted for this server. I had forgotten to delete the old one after adapting. Wasn't a big deal until almost exactly one year ago when I changed the location of my IP address anonymizer script. Put the proper location into the logrotate prerotate hook - but only in the "correct" config file. I hadn't noticed that extraneous config file. That one still had the old path to the prerotate script, this path no longer existed, but by virtue of alphabetical sorting, the old and now wrong logrotate script was run before the correct one. For almost 365 days, the logrotate daemon failed to rotate any of my webserver logs on this server, dutifully logged the failure to syslog every night where I never bothered to check, and so I have amassed numerous gigabytes of access_logs, dwarfed in one particular case by an error_log that has grown to 352 gigabytes on this server. Since the logs get a few new lines every day, they need to be unlinked and transferred in the backup process, blowing snapshots completely out of proportion, and the oldest entries have had their logged IP addresses dutifully anonymized almost 365 times. And all it takes to fix was to delete one extraneous config file. As I write this, the IP address anonymizer should go through its gargantuan task one last time before the log rotation - hopefully - compresses the log files, rotates them, and now I can't wait to see my daily snapshots rotate those old logs into oblivion. You can probably tell I should also invest some time and effort into a more robust monitoring solution. On the plus side it seems I didn't need to dig into this server's Apache logs in at least a year, or else I might have noticed they're a little bigger than they need to be.

Is this "USS Forrestal #3 Cat Bug" issue (poster above), something that Heatblur will pick up and solve? And, if so, will there be notification, as the carrier is in mothballs until it is resolved. Great product otherwise. Please advise. @IronMike Bowie

CoreMods\aircraft\AircraftWeaponsPack GR66IZ (No implemented, Beluga Submunitions) GR66EG (No implemented, Beluga Submunitios) CoreMods\aircraft\chinaassetpack\shapes\vehicles GD-Load-PL5 (No implemented, GD-20 Lift Truck cargo, Missing vehicle cargo funtionality?) GD-Load-PL8 (No implemented, GD-20 Lift Truck cargo, Missing vehicle cargo funtionality?) GD-Load-SD10 (No implemented, GD-20 Lift Truck cargo, Missing vehicle cargo funtionality?) ZTZ59 (Type 59 tank, No implemented) CoreMods\aircraft\chinaassetpack\shapes\Weapons

I took from another's strike fire in the downloads section, now I can't find the file, then I ran across your script here. I will post to here, I believe this enhances yours! Strike Fire V1.1 – Mission-side utility script for DCS that lets you call precision launcher strikes via map marks ([FIRE] / [CLEAN]), with smart target selection, budgets, cooldowns, and no client mods required. Strike Fire V1.1 is a mission script that lets you call in launcher strikes by dropping a map mark like [FIRE]. It automatically finds valid enemy targets near the mark, picks the best available launchers (HIMARS, ATACMS, Iskander), and assigns them to fire one missile each. New in V1.1: Prevents rapid double-triggering (flood lock). Tracks per-unit cooldowns and ammo budgets (persist through mission). Smarter target choice (SAMs/artillery/armor first, no shooting too close to friendlies, no crazy mountain shots). Marker overrides (e.g. [FIRE R=800 B=10 FAMILY=GMLRS]). Safer ROE handling (won’t break AI settings). Expanded compatibility (vanilla + mod launchers). [CLEAN] resets all state and clears spawned units. Practical use in-mission [FIRE] → Default strike package around the mark. [FIRE R=500] → Shrinks search radius to 500m. [FIRE B=12] → Allows up to 12 shots per launcher family, per unit. [FIRE FAMILY=GMLRS] → Only task HIMARS with GMLRS. [CLEAN] → Clears all internal state and spawned groups Strike Fire V1.1.lua

I feel like we're missing modern medium utility/cargo helicopters. Troop transport, CSAR, SAR, Maritime patrol, and even more civilian type operations like HEMS, Police work, Firefighting (?). The Huey and Hip fill the role, but are better suited for an early cold war/vietnam era. The UH-60 mod currently fills this niche a bit, but given the large variety of helis in use today, why are we limited to these 3? Would anyone else be intrested in some modern versatile multirole helis? I'm thinking something like: EC-135/145 AW-139 AW-109 AS365 H225 NH-90 Modern Hueys I know many of these have civilian variants with extensive documentation available, while others are obviously more classified (NH-90 my beloved), but I feel like we're missing on a lot of really interesting operations right now.

Ship Disposition/Formation Save for Way-points: Like the preloaded Aircraft formations, but modifiable/saveable for ships. A mission Carrier Strike Group will typically operate on a 1+15 Cycle (75 min.), and consist of the following disposition: 1 - Carrier (center/guide) 1 - CG (300°R at 3,000 yds) 1 - Plane Guard DDG (171°R at 4,000 yds) 1 - Lead Destroyer DDG (010°R at 14,000 yds) 1 - Picket Destroyer DDG (090/270°R to Threat Axis at 30,000 yds) Fine for Foxtrot Corpen and the initial launch/Recovery phase of the cycle. But, after the 180° turn and sprint down wind to regain sea for the next cycle? - Carrier is fine, on reciprocal heading. - CG is on the opposite side but corrects quickly. - Plane Guard follows and corrects fairly quickly. - Lead Destroyer is 28,000 yds out of position to a Carrier sprinting at 27 kts away from it. - Picket Destroyer is 60,000 yds out of position and racing Away from the Threat Axis. A Waypoint Disposition Change - would allow: - Carrier to proceed. - CG to proceed, or remain on the same side. - Plane Guard could become Lead Destroyer, now only 10,000 yds out of position and ahead of the Carrier. - Lead Destroyer could become Plane Guard, now only 10,000 yds out of position and behind the Carrier. - Picket Destroyer could remain on the Threat Axis and simply reverse course. Pretty slick. Please consider. Bowie