All Activity

As far as I know, per combat employment manual, all slant ranging is done by either laser or radar altimeter elevation method ( like Mi-24)

You put a link to it from a file sharing service like Google Drive or Microsoft Onedrive. Cheers!

A few posts up really. Enigma has become critical of DCS and just fine and totally understandable, while it doesn't make him omniscient of how ED works ans their plans. Cheers!

Something more than the FOV got changed. You may need to delete your snapview.lua and start over. -Ryan

BS! Probably be true for you though. I remember flying the EF2K and others over Kali in ≈96/97. Lots of fun it was.

According to PC the Kiowa will never be on trial nor sales due to the licensing agreement. Pretty sure it will change down the line at some point though.

I don’t notice that BATC has any significant hardware requirements. The main obstacle I think DCS would face is simply not having enough users to fund such an add-on. And again these are actually subscriptions not just a buy once product. As cool as BATC is and it’s very cool, I wonder how many gamers in DCS who just blast off down the taxiways are willing to write down and read back taxi instructions

Ahhh… I get what you meant now. Yes, I should’ve read that more carefully. Also, I found the “Night After Christmas” poem in the FM file. Freakin’ hilarious.

But ....based on the limited documentation out there I believe IRL you cannot actually set a target elevation preflight into the INS/WCS. Though the DTC allows it and the DTC capability is being used to neatly simulate data entry by the ground crew on the ground , IRL there just isn't provision for any altitude entry into the system. Happy to be corrected here. I guess if there is documentation that shows that Baro ranging can be used then that would settle the issue ... just haven't seen that in the Docs I can source. Though I guess changing the QNH to a dodgy value (aka target area QFE) might work ??

I like the new George interface. I think it provides a very quick and efficient way to instruct George. I particularly like the Scan TADS LoS* (Long S), which makes it possible to rescan for targets without having to point the same location (as is the case with Petrovich (mi24) which is a minor annoyance).

I tried to upload the track file but its 259,202kb in size..... How can I get it to you when I can't upload it?

Is it possible to fly a F14 in this campaign as a multiplayer pilot and RIO? Do both players need to own the campaign for multiplayer to work?

Works great, thanks! Reason is that real planes in ground parking postion have much better damage effects than structures. When releasing a 2000 pound bomb near structure planes you get only some cluster damages (i.e. holes in the fuselage) - seems very unrealistic for me. Real planes are exlpoding in a more realistic way!

AIM-9 issues continue... I'm not sure of this is related but in the last month, at least 6 AIM-9s on the F-4 have veered off sharply, usually to the right: Is anyone able to look at these bugs?

It is my belief that there is no Baro ranging in the Mig29A. All you have is laser and radalt. Going through the available ( limited) documentation IRL there is no way to input target elevation ( preflight) into the INS/WCS so the system has no knowledge of target altitude. (Happy to be corrected here). The displayed solution is first bomb of the stick not the centre. So to centre the stick you need to pickle short... easy in CCIP ... dont know how you would achieve that in a CCRP release.

умничай по спокойней ЕД сейчас сделало так что включив РЛС на излучение запирается СПО с ППС пока не переключишь переключатель в квази-режим, и тогда СПО отпирается и не реагирует ни как на включение РЛС скажем для замера дальности ! Считаю что Л006Л запирается согласно алгоритма запирания/отпирания приемника самой Н019 на момент импульса, естественно должна быть разовая команда ,так как это быстрее всего "есть" или "нет" характеристики сигнала не знаю 100 кГц или 500 кГц при 0.1 В или 400 В ... ЗЫ делать не рабочей СПО со все полусферы ППС (а это 180 градусов) на все время работы своей БРЛС ,то есть на весь воздушный бой это полная глупость ! ! !

A software-only workaround is possible using vjoy+joystick gremlin. Vjoy can be used to create a new virtual device that will show up in DCS. Joystick gremlin can do a lot of stuff, including remapping your ejection handle pull to "3 pushes of button 1 on the virtual device". Then in DCS map "virtual device button 1" to the ejection control

This is the one startup element which requires me to use the mouse, which is very annoying. Everything else is bound in my cockpit.

Set QNH for ground atttck presumably, otherwise there would be no need for setting a target point elevation. This also assumes that, by design, you must ensure the target is co-located as closely as possible with your current Waypoint.

Sorry, missed that part. [emoji1] Sent from my SM-A536B using Tapatalk

Thank you for the response. In the track, I demonstrate both L&S automated interrogation, AUTO INT automated interrogation, and manual interrogation. The result is the same in all three cases: friendlies do not reliably respond positively to F/F interrogation. As regards Link 16, yes it is on (you can take control during track play to confirm), although I suspect IFF should be able to operate independently from Link 16. Or am I wrong?

I took a closer look ... here're suggestions for Germany and the UK, just WW2. I went over all the bombs, rockets and checked the data. WW2-US-ordnance will follow. I tested all the stuff and "my" values in single-player DCS-test-missions. Using your script in server-missions for me never resulted in differences to single-player. So hopefully testing in SP is good enough. The values for the explosives are copied from the sources and show kg of the original explosive fillers. There was no conversion into any kind of "TNT-equivalent". If there's a need to balance blast- and fragmentation-damage via the weight of explosives it's up to you, please. In three cases I did changes myself. The German cluster-bomblets got an explosives-upgrade and the British AP-rocket a small charge, too. There's a remark in the comment. The other rockets need an adaption certainly. Newcomer bomb from Fw-190 A8: ["SC_250_T3_J"] = { explosive = 127 }, --SC Minenbombe, thin-walled, blast damage, general purpose Newcomer rocket from Fw-190 D9: ["R4M"] = { explosive = 0.5 }, --Germany, R4M Rakete 4kg Minenkopf, 4 kg rocket, ca. 1kg thin-walled warhead, 0.5 kg explosives, blast Suggestion for the WW2-chapter: ... explTable = { --*** WWII BOMBS *** ["British_GP_250LB_Bomb_Mk1"] = { explosive = 31 }, --UK, general purpose, blast and fragmentation ["British_GP_250LB_Bomb_Mk4"] = { explosive = 31 }, --UK, general purpose, blast and fragmentation ["British_GP_250LB_Bomb_Mk5"] = { explosive = 31 }, --UK, general purpose, blast and fragmentation ["British_GP_500LB_Bomb_Mk1"] = { explosive = 65 }, --UK, general purpose, blast and fragmentation ["British_GP_500LB_Bomb_Mk4"] = { explosive = 65 }, --UK, general purpose, blast and fragmentation ["British_GP_500LB_Bomb_Mk4_Short"] = { explosive = 65 }, --UK, general purpose, blast and fragmentation ["British_GP_500LB_Bomb_Mk5"] = { explosive = 65 }, --UK, general purpose, blast and fragmentation ["British_MC_250LB_Bomb_Mk1"] = { explosive = 51 }, --UK, medium capacity, blast over fragmentation ["British_MC_250LB_Bomb_Mk2"] = { explosive = 51 }, --UK, medium capacity, blast over fragmentation ["British_MC_500LB_Bomb_Mk1_Short"] = { explosive = 102 }, --UK, medium capacity, blast over fragmentation ["British_MC_500LB_Bomb_Mk2"] = { explosive = 102 }, --UK, medium capacity, blast over fragmentation ["British_SAP_250LB_Bomb_Mk5"] = { explosive = 19 }, --UK, semi armour piercing, penetration, fragmentation over blast ["British_SAP_500LB_Bomb_Mk5"] = { explosive = 41 }, --UK, semi armour piercing, penetration, fragmentation over blast ["SC_50"] = { explosive = 25 }, --SC Minenbombe, thin-walled, blast damage, general purpose ["ER_4_SC50"] = { explosive = 25 }, --SC Minenbombe, thin-walled, blast damage, general purpose, 4 bombs in ER-4-bomb-rack ["SC_250_T1_L2"] = { explosive = 127 }, --SC Minenbombe, thin-walled, blast damage, general purpose ["SC_250_T3_J"] = { explosive = 127 }, --SC Minenbombe, thin-walled, blast damage, general purpose ["SC_501_SC250"] = { explosive = 127 }, --SC Minenbombe, thin-walled, blast damage, general purpose, fits to SC-500-bomb-rack ["Schloss500XIIC1_SC_250_T3_J"] = { explosive = 127 }, --SC Minenbombe, thin-walled, blast damage, general purpose, fits to SC-500-bomb-rack ["SC_501_SC500"] = { explosive = 255 }, --SC Minenbombe, thin-walled, blast damage, general purpose, fits to SC-500-bomb-rack ["SC_500_L2"] = { explosive = 255 }, --SC Minenbombe, thin-walled, blast damage, general purpose, ["SC_500_J"] = { explosive = 255 }, --SC Minenbombe, thin-walled, blast damage, general purpose, ["SD_250_Stg"] = { explosive = 80 }, --SD Splitterbombe, thick-walled, Stg Stahlguss cast steel; penetration capable, fragmentation over blast ["SD_500_A"] = { explosive = 180 }, --SD Splitterbombe, thick-walled; penetration capable, fragmentation over blast --*** WWII CBU *** (moved to cluster) -- ["AB_250_2_SD_2"] = { explosive = 100 }, -- ["AB_250_2_SD_10A"] = { explosive = 100 }, -- ["AB_500_1_SD_10A"] = { explosive = 213 }, --*** WWII ROCKETS *** ["3xM8_ROCKETS_IN_TUBES"] = { explosive = 2 }, --USA, 18 kg 4.5-inch-rocket, ca. 13 kg warhead, 2 kg explosives, fragmentation ["WGr21"] = { explosive = 10 }, --Germany, WGr21 WerferGranate 21 cm, 110 kg rocket, 39 kg warhead, 10 kg explosives, fragmentation and blast ["R4M"] = { explosive = 0.5 }, --Germany, R4M Rakete 4kg Minenkopf, 4 kg rocket, ca. 1kg thin-walled warhead, 0.5 kg explosives, blast ["British_AP_25LBNo1_3INCHNo1"] = { explosive = 1 }, --UK, RP-3, 29 kg rocket, AP-1 11 kg steel penetration warhead, no explosives, kinetic, original no explosive ["British_HE_60LBSAPNo2_3INCHNo1"] = { explosive = 6 }, --UK, RP-3, 45 kg rocket, 27 kg SAP HE warhead, 6 kg explosives, blast and fragmentation ["British_HE_60LBFNo1_3INCHNo1"] = { explosive = 2 }, --UK, RP-3, 44 kg rocket, 21 kg fragmentation warhead, 1.5 kg explosives, fragmentation ... --*** CLUSTER BOMBS (CBU) *** ... ["AB_250_2_SD_2"] = { explosive = 0, cluster = true, submunition_count = 144, submunition_explosive = 1, submunition_name = "SD-2" }, --WW2 Germany 144 SD-2 fragmentation bomblets, original explosive 0.2 kg ["AB_250_2_SD_10A"] = { explosive = 0, cluster = true, submunition_count = 17, submunition_explosive = 5, submunition_name = "SD-10A" }, --WW2 Germany 17 SD-10A fragmentation bomblets, original explosive 1 kg ["AB_500_1_SD_10A"] = { explosive = 0, cluster = true, submunition_count = 37, submunition_explosive = 5, submunition_name = "SD-10A" }, --WW2 Germany 37 SD-10A fragmentation bomblets, original explosive 1 kg ... --Table for cluster submunitions clusterSubMunTable = { ... ["SD-2"] = { explosive = 1 }, --WW2 German cluster bomblet 0.225 kg explosives; AB_250_2_SD_2=144 bomblets; fragmentation, original explosive 0.2 kg ["SD-10A"] = { explosive = 5 }, --WW2 German cluster bomblet 0.9 kg explosives; AB_500_1_SD_10A=37 bomblets, AB_250_1_SD_10A=17 bomblets; fragmentation, original explosive 1 kg ... Somewhat work in progress for me are the cluster-bombs. First of all: the German-WW2-cluster-bombs are somewhat effective now and useful finally - THANK YOU! I adapted your settings for tests with the German-WW2-cluster and the cold-war BL-755-cluster. All these CBU don't use a rotation of the container to spread the sub-munition. Resulting in a lengthy distribution pattern, 2:1 to 3:1 in real-life. Unless you decide to use different spread pattern for different types of cluster-bombs some "square-"settings might offer a compromise. ... ["cluster_enabled"] = true, ["cluster_base_length"] = 150, --Base forward spread (meters) ["cluster_base_width"] = 150, --Base lateral spread (meters) ["cluster_max_length"] = 300, --Max forward spread (meters) ["cluster_max_width"] = 300, --Max lateral spread (meters) ["cluster_min_length"] = 80, --Min forward spread ["cluster_min_width"] = 80, --Min lateral spread ["cluster_bomblet_reductionmodifier"] = true, --Use equation to reduce number of bomblets (to make it look better) ["cluster_bomblet_damage_modifier"] = 1.3, --Adjustable global modifier for bomblet explosive power ... With that settings your script-produced "cluster-display" is a bit better in line with the (usually) more dense and concentrated cluster-pattern produced by DCS. The DCS-cluster-spread-pattern imho are far from real-world-data, too. It's all we have ... Looks like your script-produced "cluster-display" is lagging behind a bit, usually. The DCS-cluster-centre mostly seems to be in the forward 25 - 33 % of the splash-damage-script. No deviation to the sides and maybe more obvious with smaller cluster bomblets ... any idea why?

That‘s what I meant, yeah.

Here's a simple and cheap solution to make a button input pulse with no software, arduinos, etc. https://forum.dcs.world/topic/299916-guide-simple-cheap-standalone-electronic-solution-for-single-pull-ejection/

And we should set barometric altitude to QFE or QNH for the Mig-29 regarding ground attack?