Zergburger

its not the radars that are the limiting factor, its the missile guidance.....it should be climbing to 15-25km+ in altitude and coming down onto the target from above.....right now it just flies in a basic pronav

any chance of an updated list? pretty please

Basically what the title says, purchased, paid, receipt received, no module, not showing in launcher, not showing in game, attempting to guess the module ID so i can DL via CMD, but that aint working either. ID's i have tried: null all not working...wanna help me out? 00000.153 --- Log file: C:\Program Files\Eagle Dynamics\DCS World OpenBeta\autoupdate_log.txt 00000.000 === Log opened UTC 2025-03-20 03:16:47 00000.024 INFO : DCS_Updater/2.17.3.11 (Windows NT 10.0.26100; Win64; en-US) 00000.025 INFO : src-id: 9b8ee0590e8fa6db99ff8a8f75512059145d26e1, lib-id: b88ea51ae2210987a3865f77cc1802548216d7a8 00000.026 INFO : cmdline: "C:\Program Files\Eagle Dynamics\DCS World OpenBeta\bin\DCS_updater.exe" apply 89933d51-9f98-4edb-8596-1916a1b2c0ec 148980 00000.078 STATUS: Initializing... 00000.138 INFO : basedir: C:\Program Files\Eagle Dynamics\DCS World OpenBeta 00000.139 INFO : variant: openbeta 00000.142 INFO : Command: repair 00000.153 INFO : DCS/2.9.14.8222 (x86_64; EN; WORLD,CAUCASUS_terrain,MARIANAISLANDS_terrain,A-10C,A-10C_2,A10C-PIERCING_FURY_campaign,A10C-REDFLAG_campaign,A10C-STONE_SHIELD_campaign,AERGES_MIRAGE-F1,AH-64D,AJS37,AVIODEV_C-101,BALTICDRAGON_A10C-ENEMY_WITHIN_3_campaign,BALTICDRAGON_FA-18C_RAVEN_ONE_DOMINANT_FURY_campaign,BALTICDRAGON_FA18C_RAVEN_ONE_campaign,BALTICDRAGON_M2000C-REDFLAG_campaign,BF-109K4,CA,DEKA_JF-17,F-16C,F-5E,F-86F,FA-18C,FW-190D9,HEATBLUR_F-14,KA-50,KA-50_3,L-39,MI-24P,MI-8MTV2,MIG-15BIS,MIG-21BIS,NEVADA_terrain,NORMANDY_terrain,P-51D,P47D30,P51D-HIGHSTAKES_campaign,PERSIANGULF_terrain,POLYCHOPSIM_SA342,RAZBAM_AV8BNA,RAZBAM_M-2000C,RAZBAM_MIG19P,SPITFIRE-MKIX,SPITFIRE-MKIX-OPERATIONEPSOM_campaign,SUPERCARRIER,SYRIA_terrain,WWII-ARMOUR,RAZBAM_F-15E,SINAIMAP_terrain,HEATBLUR_F-4E,A-10A,SU-25A,F-15C,MIG-29,SU-27,SU-33) 00000.153 INFO : branch: openbeta 00000.154 STATUS: Downloading version info... 00000.609 INFO : Showing the repair mode dialog 00007.889 STATUS: Verifying installed files... 00022.215 INFO : 0 files are changed or missing. 00023.607 STATUS: Preparing download... 00023.608 STATUS: Checking downloads... 00023.610 STATUS: Scanning existing files... 00023.610 INFO : To download: 0 bytes in 0 files 00023.611 STATUS: Searching for local copies... 00023.612 INFO : Found 0 local source(s). 00023.612 INFO : To download: 0 bytes in 0 files 00023.674 STATUS: Removing obsolete files... 00023.885 INFO : Removed 0 files. 00024.331 INFO : Kept 115016 files. 00024.331 INFO : Nothing to install. 00024.355 STATUS: Installing runtimes... 00024.673 INFO : distr/vc_redist.x64.exe succeeded with code 1638 00024.680 STATUS: Cleaning up... 00025.056 STATUS: Successfully repaired version 2.9.14.8222@openbeta 00027.581 === Log closed. 00000.000 === Log opened UTC 2025-03-20 03:32:17 00000.025 INFO : DCS_Updater/2.17.3.11 (Windows NT 10.0.26100; Win64; en-US) 00000.025 INFO : src-id: 9b8ee0590e8fa6db99ff8a8f75512059145d26e1, lib-id: b88ea51ae2210987a3865f77cc1802548216d7a8 00000.027 INFO : cmdline: "C:\Program Files\Eagle Dynamics\DCS World OpenBeta\bin\DCS_updater.exe" apply b94d67ba-a705-4a39-85d5-3a2fc151055f 149212 00000.078 STATUS: Initializing... 00000.138 INFO : basedir: C:\Program Files\Eagle Dynamics\DCS World OpenBeta\ 00000.138 INFO : variant: openbeta 00000.141 INFO : Command: install BALTIC_DRAGON_FA-18C_THE_RAMPAGERS_campaign 00000.141 INFO : DCS/2.9.14.8222 (x86_64; EN; WORLD,CAUCASUS_terrain,MARIANAISLANDS_terrain,A-10C,A-10C_2,A10C-PIERCING_FURY_campaign,A10C-REDFLAG_campaign,A10C-STONE_SHIELD_campaign,AERGES_MIRAGE-F1,AH-64D,AJS37,AVIODEV_C-101,BALTICDRAGON_A10C-ENEMY_WITHIN_3_campaign,BALTICDRAGON_FA-18C_RAVEN_ONE_DOMINANT_FURY_campaign,BALTICDRAGON_FA18C_RAVEN_ONE_campaign,BALTICDRAGON_M2000C-REDFLAG_campaign,BF-109K4,CA,DEKA_JF-17,F-16C,F-5E,F-86F,FA-18C,FW-190D9,HEATBLUR_F-14,KA-50,KA-50_3,L-39,MI-24P,MI-8MTV2,MIG-15BIS,MIG-21BIS,NEVADA_terrain,NORMANDY_terrain,P-51D,P47D30,P51D-HIGHSTAKES_campaign,PERSIANGULF_terrain,POLYCHOPSIM_SA342,RAZBAM_AV8BNA,RAZBAM_M-2000C,RAZBAM_MIG19P,SPITFIRE-MKIX,SPITFIRE-MKIX-OPERATIONEPSOM_campaign,SUPERCARRIER,SYRIA_terrain,WWII-ARMOUR,RAZBAM_F-15E,SINAIMAP_terrain,HEATBLUR_F-4E,A-10A,SU-25A,F-15C,MIG-29,SU-27,SU-33) 00000.141 INFO : branch: openbeta 00000.142 STATUS: Downloading version info... 00000.338 STATUS: Preparing to install BALTIC_DRAGON_FA-18C_THE_RAMPAGERS_campaign ... 00000.341 STATUS: Unknown module BALTIC_DRAGON_FA-18C_THE_RAMPAGERS_campaign 00005.282 === Log closed. 00000.000 === Log opened UTC 2025-03-20 03:35:41 00000.024 INFO : DCS_Updater/2.17.3.11 (Windows NT 10.0.26100; Win64; en-US) 00000.024 INFO : src-id: 9b8ee0590e8fa6db99ff8a8f75512059145d26e1, lib-id: b88ea51ae2210987a3865f77cc1802548216d7a8 00000.026 INFO : cmdline: "C:\Program Files\Eagle Dynamics\DCS World OpenBeta\bin\DCS_updater.exe" apply 93da5f3a-c1f5-4894-898d-48dca136ed25 152360 00000.078 STATUS: Initializing... 00000.137 INFO : basedir: C:\Program Files\Eagle Dynamics\DCS World OpenBeta\ 00000.137 INFO : variant: openbeta 00000.140 INFO : Command: install BALTIC_DRAGON_FA-18C_RAMPAGERS_campaign 00000.141 INFO : DCS/2.9.14.8222 (x86_64; EN; WORLD,CAUCASUS_terrain,MARIANAISLANDS_terrain,A-10C,A-10C_2,A10C-PIERCING_FURY_campaign,A10C-REDFLAG_campaign,A10C-STONE_SHIELD_campaign,AERGES_MIRAGE-F1,AH-64D,AJS37,AVIODEV_C-101,BALTICDRAGON_A10C-ENEMY_WITHIN_3_campaign,BALTICDRAGON_FA-18C_RAVEN_ONE_DOMINANT_FURY_campaign,BALTICDRAGON_FA18C_RAVEN_ONE_campaign,BALTICDRAGON_M2000C-REDFLAG_campaign,BF-109K4,CA,DEKA_JF-17,F-16C,F-5E,F-86F,FA-18C,FW-190D9,HEATBLUR_F-14,KA-50,KA-50_3,L-39,MI-24P,MI-8MTV2,MIG-15BIS,MIG-21BIS,NEVADA_terrain,NORMANDY_terrain,P-51D,P47D30,P51D-HIGHSTAKES_campaign,PERSIANGULF_terrain,POLYCHOPSIM_SA342,RAZBAM_AV8BNA,RAZBAM_M-2000C,RAZBAM_MIG19P,SPITFIRE-MKIX,SPITFIRE-MKIX-OPERATIONEPSOM_campaign,SUPERCARRIER,SYRIA_terrain,WWII-ARMOUR,RAZBAM_F-15E,SINAIMAP_terrain,HEATBLUR_F-4E,A-10A,SU-25A,F-15C,MIG-29,SU-27,SU-33) 00000.141 INFO : branch: openbeta 00000.142 STATUS: Downloading version info... 00000.327 STATUS: Preparing to install BALTIC_DRAGON_FA-18C_RAMPAGERS_campaign ... 00000.329 STATUS: Unknown module BALTIC_DRAGON_FA-18C_RAMPAGERS_campaign 00002.789 === Log closed.

@Chizh Any thoughts or updates on this concept?

let BOOM = dist <= min || (d(dist)/d(t) <= 0 && dist <= max) When missile range to target reduces beneath the stated initial proximity fuse range [MAX] (50m for this example). The fuse then begins to take measurements of range over time for comparison, creating a rate. When the range rate is found to decrease under zero then trigger the fuse. This can make use of Kalman filtering to throw out any garbage positional updates that would prematurely indicate a negative closure. Once the missile either stops closing (decreases below zero or an other minimum closure threshold) towards the target, or the missile hits a set minimum range (for example, the previous 9m) it will detonate. This will mean that if a missile for example gets within the initial 50m range to the target, and makes it as close as for example 20m, it will detonate as soon as it stops closing with the target. The missile will now detonate, causing less significant damage instead of flying past harmlessly. This means realistic missile avoidance maneuvers that increase the missiles miss distance will be effective, possibly making a missile hit non-fatal. This allows for missiles that are near-misses to then become at least partially viable instead of a trashed shot. So here we have a system where missile avoidance maneuvers are still viable in reducing the lethality of incoming shots, but also a system where missiles that would have been worthless now still pose some sort of risk for the aircraft. I have included some documents on the history of proximity fuses [1] and an explanation of modern use FFTs for ranging of proximity fuses [2] 1. https://www.ijert.org/research/recent-advancements-in-proximity-fuzes-technology-IJERTV4IS041400.pdf 2. https://ieeexplore.ieee.org/document/10418854 Also, Thank you Coxy for your extremely valuable contribution to this discussion

Doppler? theres no doppler involved here, its just an IC measuring rate of change of the values coming in on the proximity fuze? If you got doppler ideas from @NytHawk, he was referring to the navy's VT fuze which used doppler for a few select reasons: 1. It was like 2 vacuum tubes and a coathanger antenna, about as simple as a radar could possibly get. It was easier to measure frequency changes. 2. It made sure the fuze would work (read: not detonate on a false target) when shot at low angles against planes coming in for torpedo drops or ramming attacks. We have integrated circuits and all kinds of fantastical gadgets now, so we can make a TDD to do whatever we want.

EXACTLY A 50lbs warhead exploding 60ft from you aircraft may not cause immediate violent disassembly, but it sure as <profanity> would have an effect. I am very much inclined to believe that with modern target detect devices, a generous proximity fuse setting is given for the inital tripping, and then if the range continues to measurably decrease, the detonation is held. How else would you design a missile that must engage everything from drones to large bombers with length and wingspans over 30m?

Has the idea that the AIM-54 was designed to kill large bombers and large supersonic cruise missiles, whilst the amraam was designed to kill fighters and other small to medium sized air breathing targets been considered. To explain further, could it be possible that the 15m kill radius is correct for both, with respect to their differing use cases. I think that there is some decent evidence to suggest aim-120 proximity fuzed (could) be lethal to fighters at 15m. The same logic was used when determining the size of aircraft gun armament. In times of old when aircraft were small, the guns that were used to destroy them were small.Whilst cannons were used on bombers. Now we have fighters that are the size of WW2 bombers, and as such, the machine guns of old have given way to cannons, most of them 25mm to 30mm. However as a separate issue, i believe modern proximity fuses do not use simple logic in determining detonation criteria. If I were to design a missile proximity fuze system, i would certainly create a logic gate that would take multiple reading over time and if the range to target continues to decrease, there would be no reason to detonate. Once the initial firing circuit is tripped the missile should detonate only when closure falls under a certain rate. This simple logic gating would allow a fairly generous range for initial proximity fusing, whilst still maintaining lethality that a shorter range could afford. My understanding is that the sidewinder was upgraded to an active laser proximity fuse to employ this very concept Is there any reason why the amraam, with all its ADVANCED-ness would not have this feature? @Default774 Might have something to say in regards to this point methinks.

Hey guys, didn't see a thread of this nature yet and i have some questions of my own, so hopefully we can make @Wags and @BIGNEWY 's lives easier by consolidating. QUESTIONS: 1. The changelog mentions REDFOR vipers having lower precision on their GPS. What does REDFOR mean specifically in this case? If I have a US viper on red team do i get the higher or lower accuracy? does this refer to the multiplayer team color, the nation, or the blufor/redfor set by the map creator in the mission editor? 2. What advantages does the standard alignment confer over a stored alignment given the changes, if any? Specifications for GPS/non-GPS eras would be great 3. What dictates the GPS vs non-GPS era? (i know this has been answered before, thought it might be useful to have it here) more to come....

to be clear, boresighting mavs on the ground is not realistic. Part of the reason you are required to boresight them is the jostling from taxi/takeoff. The intention is that you boresight them in the air. Generally a viper will ahve a steerpoint on large landmark (large solo building / bridge / etc.) before the IP/TGT area so that it can be used for boresighting and INS drift calibrations.

would greatly appreciate a link to the version history page on the git in the online manual, for quick reference; TYVM!

Feature Request for Manual: Please include some sort of very basic changelog for new material or large reworks. Obviously a notation of every spelling error corrected or other small edits would not really have much benefit, but being able to check the online version for updates, and see which sections have new/updated material would be great for people trying to keep up with the aircraft as post-release development continues. Keep up the good work Heatblur.

how to tell if airbrake is deployed? turn your head?

Hey buddy, call this a tentative fix, but i think i solved my issue, and i encourage you to try the same fix. I reverted my Nvidia drivers a full version (Current is 531.XX) back to February's drivers (528.XX).

my 6 year old build is on its last legs, (8700k, 1080ti, ROG maximus formula board, 32GB RAM, custom water loop). I am totally at a loss between a 13900k build and a 7800X3D build, the delta in price is about $300-$400 higher for intel. I am unfamiliar with the intricacies of modern AMD builds so i am somewhat hesitant; while intel seems to always be pretty trouble-free and bring satisfactory performance. Can anyone give me some advice, or show some DCS benchmark comparisons for the 13900k vs the modern X3D chips?