catt42

Divide your ground speed (gs, not indicated air speed) by 60 and you get the miles you cover in a minute. It's easier if you try to maintain a ground speed that is a multiple of 60, ie 360, 420, 480, etc Inviato dal mio Redmi Note 7 utilizzando Tapatalk

I don't have kids, but thinking back to when I was younger, steep learning curves and the frustration that comes with them gave me the most rewarding experience once I could overcome them. Plus it's not something that get easier with age, as a matter of fact it's the opposite, so better start young. Are you sure that making it easy is the best thing to do? Inviato dal mio Redmi Note 7 utilizzando Tapatalk

I did some research on the subject some time ago and I noticed that publicly available radar max range information generally refer to bomber sized targets. I think that's one of those numbers companies write in brochures to make generals and kids happy, like aa missiles max range. There's a huge difference between a lateral aspect B-52's RCS and a frontal or rear aspect f-16's RCS. But I don't know whether this is emulated in DCS or not. Inviato dal mio S2 utilizzando Tapatalk

È sempre il raggio di dispersione delle schegge, per la stima dei danni collaterali, come ho scritto sopra. [emoji6] Inviato dal mio S2 utilizzando Tapatalk

È l'area di dispersione delle schegge. Varia in base al munizionamento selezionato. Inviato dal mio S2 utilizzando Tapatalk

Unfortunately cockpit parameters are not accessible via lua script. Inviato dal mio T20 utilizzando Tapatalk

Are you talking about the same rg divisions that were effectively putting down rebellions in 14 Iraqi provinces 2 week ([emoji769]) later? Anyway, I really enjoyed your representation. Inviato dal mio S2 utilizzando Tapatalk

... and by saying this he inspired the ISF leaders and soldiers so much that they immediately started feeling responsible for the security of their country. Some time passed but i still can't LMFAO. Inviato dal mio S2 utilizzando Tapatalk

Thinking about it, I don't think that your formula returns true airspeed, most likely it's some sort of 3d ground speed. You probably should take into consideration the wind vector to get tas. Anyway, that's probably where my formula error comes from. Inviato dal mio S2 utilizzando Tapatalk

I get a good approximation with this metod: The formula you wrote gives tas (3d), multiply tas by 1.94384 to get true speed in knots. Then, ias = tas * (1- (6.87535 * 10^(-6) * altitude))^2.128 Altitude is expressed in feet: local altitude = unit:getPoint().y * 3.28084 Inviato dal mio S2 utilizzando Tapatalk

+1. Couldn't say it better. Inviato dal mio S2 utilizzando Tapatalk

Just open the .miz file with winrar or something similar, open the file called mission that you will find inside, using any text editor, look for the callsign and edit it. If you want to turn Chevy 3-1 into Chevy 1-3, look for 'Chevy31' and rename it 'Chevy13'. Save it and try. Inviato dal mio S2 utilizzando Tapatalk

It varies from aircraft to aircraft. In the mirage it's the little number right underneath the locked contact in tws ans stt mode. I don't know about other aircrafts. Of course it's impossible to tell if you're flying a mig-21 or an f-5. Inviato dal mio S2 utilizzando Tapatalk

Basically if you are 40nm out and let's say your target's aspect is 15°, you'll have 40*15*100=60,000 feet of lateral separation, or 10 nm. Distance and target aspect can be obtained from the radar, most of the time. There's a CNATRA publication available online that gives more detailed information on the subject, all-weather intercept. Inviato dal mio S2 utilizzando Tapatalk

Yes, it is. getPoint requires an unit object to work, if you think about it the position of a group is formation dependant, while the position of an unit is a point. getUnits()[1] will select the group leader, even if it's a one-unit group

Hilarious!! Inviato dal mio S2 utilizzando Tapatalk

No idea on how to do it with MOOSE, anyway it's easy enough with normal DCS lua functions. function choose_your_function_name() local group_1_pos = Group.getByName('group_1'):getUnits()[1]:getPoint() local group_2_pos = Group.getByName('group_2'):getUnits()[1]:getPoint() local distance = ((group_1_pos.x - group_2_pos.x)^2 + (group_1_pos.z - group_2_pos.z)^2)^0.5 local bearing_vector = { x = group_2_pos.x - group_1_pos.x, y = group_2_pos.y - group_1_pos.y, z = group_2_pos.z - group_1_pos.z } local bearing_rad = math.atan2(bearing_vector.z, bearing_vector.x) if bearing_rad < 0 then bearing_rad = bearing_rad + (2 * math.pi) end local bearing = math.deg(bearing_rad) trigger.action.outText('enemy group bearing '..bearing..'° at '..distance, 10) end choose_your_function_name() Please note that: the bearing value is true bearing, as in the F-10 map. add/subtract local magnetic variation if you want to distance is 2D and in meters. divide by 1852 for nm all values are not rounded Have fun!

If an Amraam equipped AI fighter coming head-on breaks lock on you, let's say at 20 nm, you won't think that you are ok. You'd assume that you have one or more Amraam coming at you, and maneuver to defeat them. The AI is not doing that, it just happily runs into the threat. Inviato dal mio S2 utilizzando Tapatalk

The GBU-24 won't track anyway. The in-game Mirage is fully capable of level-flight or toss bombing, all you have to do is designate a point in front of the actual target, because all LGBs tend to glide a lot. If you accurately designate the target position, the bomb could glide past it without picking up the laser. Depending on your release altitude and speed, you can designate 3nm in front of the target and still hit it, probably not super-realistic, but it works. If you want to use the gbu-24 with the Mirage, paste this code at the end of the \DCS World OpenBeta\Scripts\Database\Weapons\bombs_table.lua file (before 'end'): declare_paveway_2("GBU_24", _("GBU-24"), "GBU-24", wsType_Bomb_Guided, "bomb-paveway-II-afm", { fm = { mass = 1050.0, caliber = 0.457000, cx_coeff = {1.000000, 0.390000, 0.60000, 0.1680000, 1.310000}, L = 4.368, wind_sigma = windCoeff * 220.0, Sw = 2 * 1.75 * math.pow(24 * 2.45 * 0.01 / math.sin(2 * math.pi / 6), 2) / 2.5, A = 0.6, maxAoa = math.rad(7), finsTau = 0.1 }, bang_bang_autopilot = { omegaDumpingK = 0.30 }, warhead = warheads["Mk_84"], }, { char_time = 20.34 }, "wAmmunitionLaserHoming" ); Or, if you want to use a GBU-24 with BLU-109 penetration bomb for hardened targets, paste this code declare_paveway_2("GBU_24", _("GBU-24"), "GBU-24", wsType_Bomb_Guided, "bomb-paveway-II-afm", { fm = { mass = 944.0, caliber = 0.457000, cx_coeff = {1.000000, 0.390000, 0.60000, 0.1680000, 1.310000}, L = 4.368, wind_sigma = windCoeff * 220.0, Sw = 2 * 1.75 * math.pow(24 * 2.45 * 0.01 / math.sin(2 * math.pi / 6), 2) / 2.5, A = 0.6, maxAoa = math.rad(7), finsTau = 0.1 }, bang_bang_autopilot = { omegaDumpingK = 0.30 }, warhead = warheads["BLU_109"], }, { char_time = 20.34 }, "wAmmunitionLaserHoming" ); The GBU-24 is not already present in the file, I guess this is why it won't work. I wrote the code using info from GBU-16, GBU-10 and MK-84 in bombs_table.lua, plus some open source info on the mass (which are probably not accurate).

30-87.975 is the band used by vhf sincgars radios, mostly for short range, line of sight tactical comms between ground forces. it's fm only because in this specific scenario fm is less susceptible than am to interference. Inviato dal mio S2 utilizzando Tapatalk

good for you!!! Inviato dal mio S2 utilizzando Tapatalk

have you considered that the whole misunderstanding could just be a cultural issue? you see, i work with procedures everyday day too, but the same sentence quoted by CheckSim applies to every single procedure, directive or doctrine publication I deal with. reading how you describe the rigid revision workflow that you use in your line of work, i can assure that this is not how it works where I'm from, where top-down directives are mostly general policy, while the "how to apply the policy to the problem at hand" is a low level responsibility. maybe you would be luckier with Soviet Navy Case III procedures. Inviato dal mio S2 utilizzando Tapatalk

impostare un time on target che funzioni è quasi impossibile. puoi impostare un tot per ogni waypoint, ma ciò che il sistema fa è semplicemente dividere la distanza dal wp precedente per il tempo, calcolando quindi la ground speed che il velivolo dovrà mantenere. quindi, se l'aereo in questione è impostato su late activation, i calcoli saltano. saltano anche se l'aereo parte da un aeroporto, perché la Σ non tiene conto dei tempi di accensione, taxi, raggiungimento della velocità prevista, ecc. praticamente funziona solo per aerei che vengono attivati a inizio missione, sono già in volo e non cambiano velocità e quota per tutto il percorso. quello che puoi fare è impostare un orbit sul waypoint precedente e annullarlo (stop condition in alto a dx nella finestra del task orbit) calcolando manualmente il tempo necessario per raggiungere il wp desiderato, come avviene nelle 3 campagne red flag. ma anche così, mentre orbita l'aereo si allontana dal wp, e perde tempo per virare e mettersi sulla rotta corretta una volta che l'orbit è annullato, e non arriva mai esattamente in orario. l'unica soluzione potrebbe essere utilizzare lua, ma diventa un casino. peccato, perché in ambito militare il tot è usato praticamente in ogni missione (come in falcon) Inviato dal mio S2 utilizzando Tapatalk

or... he completely failed to understand what victory205 meant, that when trying to land a real aircraft at night, with the real you on it and other real aircraft with real people all around you, it's probably unsafe to accept being ten second late, and you should strive to be exactly on time. no epistemology as you can see, just common sense. Inviato dal mio S2 utilizzando Tapatalk

I'm pretty sure that the Bible concurs with Victory205 too, the book of John deals with Case III, if I'm not mistaken. Inviato dal mio S2 utilizzando Tapatalk