Bacab

I have just tested it. Setting the alarm state to green do nothing for artillery units. On SCUD it causes them to actually get ready to depart. Setting the alarm state to red actually achieves what I am trying to do for SCUD and part of what I am trying to do for artillery: the artillery unit actually deploys but in the absence of a target the gun stays horizontal whereas by setting a "fire at point" and then deactivating the AI the unit actually points upward its gun; showing a more ready state.

Thank you very much ! It works as intended and allows me to strike threatening SCUD pointing at the sky or artillery positions that look like they are ready to fire. It's a small thing but with that I can reproduce targets as they are depicted on IRL reconnaissance pictures that I have.

Hi everyone, I have made several missions where I use artillery units (with L118 Light artillery guns or SCUD TEL for instance) as targets. These units spawn in a towed position, ready to move, but since I want to depict units ready to fire I would rather have them in a deployed position. Is there a way to command them to deploy in the ME ? The only way I have found until now is to order them to fire at a point continuously (when they are done with the "fire at point" task they return to there towed position) but then the endless stream of gun fire log is cluttering my debriefing window + they are more easily spotted during the mission. So the question is, is there another way ? Thank you in advance for your answer.

You are missing the point: the issue is not to say that it doesn't work in Loft or in Offset, just to say that Jester does not automatically set the VIP upon overflying it even if you press the bomb button as a pilot (even if you have told him the correct offset through the bombing calculator). When overflying the VIP you have to take the role of WSO, press the "Freeze Signal and Target Insert Signal buttons" yourself and then upon returning to the pilot position you will be guided to the release point and everything will work as intended.

I am sorry to insist but I have the same issue : upon overflying the VIP the manual tells us "the WSO simultaneously presses the Freeze Signal and Target Insert Signal buttons on the Cursor Control Panel; doing so initiates INS target tracking." From your answer I guess Jester should do those two actions when I press the bomb button as a pilot, however I think this is not the case currently. Indeed, when overflying the VIP, when I press the bomb button, the flight director still sends me to my next waypoint, not to the offset I told Jester to set. I have done a track although I think opening the bombing calculator in flight seems to brake it. EDIT : If you manually do the pressing of the Freeze signal and Target insert as the WSO when overflying the VIP, then it works fine. F-4E_Offset_bombing_no_luck_v2.trk

This is a good solution that I will try on the F-16, F-18 and AV-8. I will try it as soon as my build is finish : I have just eradicated the last bug from the software and I am in the process of finalising the box that contains all my flight instruments. Once that is done I will try the solution you offer. On a side note, just in case someone is interested in building a compass for DCS Bios : - A-10C: export the HSI heading, values are reversed so 360° to 180° is 0 to 32 768. Displays the magnetic heading - AJS-37: export the CI heading, the exported values are in degrees. Displays the true heading - F-86: export the heading value, the exported values are in degrees. Displays the magnetic heading -L-39: export the HSI heading, values are NOT reversed so 360° to 180° is 65535 to 32 768. Displays the true heading -M2000C: export the HSI heading, values are NOT reversed so 360° to 180° is 65535 to 32 768. Displays the magnetic heading -MiG-21: export the HSI heading, values are reversed so 360° to 180° is 0 to 32 768. Displays the true heading -All WWII aircrafts: export the DI GAUGE (directional gyro) instead of the compass. Their compass are too wobbly (and not accurate at start so you can't rely on them to deduce the magnetic variation) so it will lead to erratic, very fast movements, of the stepper motor which the stepper does not like at all ! Though it is not a direct reading of the magnetic heading it is generally synced to the magnetic heading at start and before all navigation and their output is a lot more stable. All values are between 0 and 65535 but I have not played enough with them to sort if they are reversed or not (they don't seem to be reversed though). -UH-1H: export the GMC heading, values are NOT reversed so 360° to 180° is 0 to 32 768. Displays the magnetic heading (if manually sync) Thank you for your help.

Thank you very much for the help. I would have preferred the heading from the EHSI but i understand from what I read it currently behaves like a screen and it can't be exported as a gauge. I will test the whole thing today and keep you updated. PS: I have seen your talk on git hub. I can tell you the F-5 compass is also reversed. However it is very easy to solve, so not a big deal.

Indeed ! thank you very much !

Thank you for your answer. If they are no solution, I'll wait.

Thank you for your answer but I am not sure you understand what I am trying to do. Since DCS Bios export the true heading for all aircrafts but not the magnetic heading (for instance for the F-16, yes for the P-51 you have access to the magnetic heading), I was trying to find a way to convert this true heading to a magnetic heading (the link between the two being the magnetic variation). However since the magnetic variation is not exported as it seems, this solution can't be done. So the question is : is there a way to get the heading value from the F-16, F-18 and AV-8BNA ? Or to otherwise retrieve the actual magnetic variation.

Thank you for your answer. I would prefer an automatic way to do it. Otherwise it is very cumbersome.

Hello Several weeks ago I began designing my own flight instrument panel, expecting to use it with several modules. It is now nearly complete : To drive the compass I would have liked to use the magnetic heading. However some modules, for instance the F-16, do not appear to export this parameter. Am I missing something ? Is there a way around to otherwise export the magnetic heading ? (I thought about using the true heading, exported through the common data set, with the mag var. to retrieve the magnetic heading but the mag var seems to not be exported either). Thank you in advance for your answers.

Hello everyone, I noticed that I had a very hard time dealing any kind of damage to even unarmoured targets using the Mk 20 Rockeye. So I did a test mission with ideal conditions and tried to destroy some trucks with the Mk 20, to no avail. Here are two of my attempts (see attached tracks). Graphically speaking it seems at least one truck should be destroyed in both case but no "hit" event is even logged by DCS. Could someone have a look ? It seems a lot of cluster bombs are not working correctly currently but I failed to find a report specific to the Mk 20 so here it is. I apologise if this bug has been previously reported. Thank you in advance. Mk20_bug.trk Mk20_bug_2.trk

Technically any RF sensor using Doppler processing to discriminate signals of interests among ground clutter is susceptible to a beam manoeuvre performed by its target (albeit at low altitude and in look down). In this regard the Sparrow is not different. This being said I do not know the particularity of this seeker, I only answer from a general perspective about radar seeker.

I am doing the Caucasus campaign and I like it very much so far. I have just done mission 5 ("The traitor") and have a few questions : Thank you in advance for your answer.