dorianR666

Yes it is, but thats not what you are supposed to calculate. X increased by 33% is 1.33*X - thats the number of interest. You are computing 33% from the end result, which is something completely unrelated. A third of the base will be different amount than a third of the result.

That math is wrong though. Override makes G limit increased by 33%. 9G with 33% increase is 11.97G. Not 13G. Besides, thats still wrong, because its counted from the current normal G limit, which can be maximally 7.5G, not 9G. NATOPS says: Maximum allowed g-limit increased by 33% (allows a 10g command at 7.5g Nz REF). 13G should not be possible.

its not implemented

User Ziptie said that in 2019. Though question is what he bases it on...

You dont need radio to open the rearm-refuel menu. Just open canopy is enough iirc. Also your comm1 should work with just battery. But you cant change channel.

Radar mapping the ground simply emits the radar beam around and displays the amount of reflected energy. Light = highly reflective, dark = poorly reflective. This is how MAP mode works, no doppler filtering involved. The problem is that the radar beam is fairly wide (say, 1 degree) - this is a technical limitation of the radar hardware. Which means that if you want to zoom in onto an area (EXP modes), the beam is just too wide and you wouldnt see any detail in the image. It would be just a blob. This is where Doppler Beam Sharpening (DBS) post-processing technique comes in. The radar still emits its wide beam, however when you emit the beam, say, 45 degrees to the side of the aircraft's axis, different parts of the beam will be *differently* Doppler-shifted by the ground (because the ground is moving on the axis where the plane is pointing, not on the axis where the beam is emitted). This means that if you measure the returned signal as many combinations of Doppler shifted frequency and its reflected energy, you can divide the wide beam into many tiny "subbeams" so to speak. This way you have image of much higher resolution. This is why DBS doesnt work when emitting straight ahead of you. The Doppler shift within parts of the wide beam would be roughly the same for all parts of the beam. So you cant distinguish returns for each "subbeam". So you cant render EXP3 of an area in front of your plane.

you put two dashes in front of the line with sanitizeModule('os') in file MissionScripting.lua. if i remember right, its in MissionEditor folder in DCS root folder.

why not post the trackfile...

That only influences the angle with which the AI plane makes the turn (thus exactly flying over the point or not). Nothing else. Solution is trivial. You add one more waypoint before the landing waypoint. Once the AI reaches the last normal waypoint, it automatically goes RTB. Once AI is in "going home" mode, it ignores everything else (even enemies). This cancels your racetrack. Its probably a bug but you have to count with this unexpected behaviour. Btw next time please remove the unrelated stuff like the heli blocking the cats for 5 minutes on each mission start.

big HARM update is scheduled for end of march, so we'll see. no explicit mention of this problem so far though.

Are you sure your radar sees it? The correlated HAFU and Surveillance track look exactly the same, except the number is missing in Surveillance tracks and they are 75% the size. They both have the upper and bottom half. Picture attached is a track NOT seen by your radar.

It is SSLR. Water uses SSLR regardless of that setting.

it probably was never fixed

no it doesnt work yet

isnt it 1994? if you mean gps

you are required to post a trackfile otherwise nobody can help you

Maybe IRL, but is it simulated in DCS? As far as i know, the game simply rolls a dice for each flare if it's within missile seeker's FOV.

Interesting. Though the mission i made in which it happened a few times is in june, with temperature of 20C. So it may not be the only trigger of the bug.

binding issue for sure. if its slewing by itself it means you havent configured a deadzone

you have to post a trackfile.

confirmed. there is no other occurance of "HSD".

thats chucks guide. its not an official manual for IRL plane or from ED. its literally just one ordinary DCS player making these PDFs in his free time. regarding STEP, iirc there is currently a bug where trackfile ranks on radar page and on SA are sometimes different. so that might be a bit disfunctional.

you can convert stable into OB inplace with the updater btw. not sure why your problem occurs tho. whats more weird is that you wouldnt have the option to install even more so now that free-to-play event is going on, and everybody can install and run any module. maybe try installing it manually in command line using the updater.

Wrong section? This is DCS world bugs section.

no, DCS trackfile. others can run the trackfile in DCS and see everything thats going on (cockpit clicking, cockpit display contents, mission scripting, ...) its a file with .trk suffix, you can save it in debriefing screen.