MagicSlave

+1 Sent from my FP4 using Tapatalk

Bump. Are working windshield wipers going to be implemented to the Mi-8? Sent from my FP4 using Tapatalk

Especially interesting is the Gadow Airfield replica at Wittstock firing range: https://www.mil-airfields.de/de/wittstock-firing-range-gadow.htm It is a replica of a NATO airbase for bombing practice.

Been away from the Chinook for some time. I used to be able to taxi the Chinook on rear wheels, with cyclic trim 2 inches aft, AFCS both and LCTs auto. Not able to do so anymore. Did something change with the flight model or am I doing something wrong? Also, she is impossible to steer with the tail wheel steering while doing a 4 wheel taxi (AFCS Off, tried both with LCTs auto and LCTs manual full aft) Sent from my FP4 using Tapatalk

May I ask what map you used to create the images on the kneeboard? They look so good! I would like to make similar for my own missions in NTTR.

Has anyone else encountered FCR desynch issues in Apache multicrew on the latest DCS version? I hosted a private server with a friend (with him as C/PG and myself as pilot) and everything worked fine, except I could not see any FCR contacts that he saw. He was the one using the FCR. Also, I created a PFZ and a NFZ using PAN and he could not see those. I believe the latter to be a known bug, but according to the Apache forum roadmap post the FCR synch should be fixed in multiplayer. I wonder if the desynch bug could be related to the known BAM / PAN bug? Sent from my FP4 using Tapatalk

Also note that there is kind of two different mouse pointers in VR in DCS. One is in the "depth* of the cockpit (yellow cross) and the other in the depth of UI layer (white dot). They can be in somewhat different place depending on where you are looking in the cockpit. IIRC it is the white dot that interacts with the grease pencil window, since it is part of the UI rather than the cockpit. Sent from my FP4 using Tapatalk

Yes, indeed you are correct. Good point and my bad. Sent from my FP4 using Tapatalk

You can open the Miz file with a text editor (e.g. Notepad++) and copy paste map markers to another Miz file. Sent from my FP4 using Tapatalk

Dive angle 0° gives Bomb range 14 418 ft. My DCS Launcher says the game version is 2.9.15.9599 Setting the angle to -30° indeed gives a more plausible result of 6427 ft. Thanks!

Is there an error on the Bomb range calculations in the Bombing calculator or is there a bug on my DCS installation? Miz file attached. EXAMPLE Mission weather settings: Standard Day (altimeter 29.92, temperature 15°C, zero winds) Bombing calculator input: DIRECT, MK-82, 500 KTAS, Release altitude 5000 ft, Target altitude 0 ft, Dive angle 30° Bomb range output: 23 772 ft (see attached image) However: Consider the following triangle (see attached drawing), where RA = (Release altitude), BR = (Bomb range), AOD = (Aim off distance), X = (BR)+(AOD). From basic trigonometry it follows that X = RA / (tan(Dive angle)) If we input the above values we get X = 5000 / (tan(30°)) = 8660 ft It is evident that the Bomb range should be less than the distance X. So it follows that the Bomb range in the Bombing calculator output must be wrong. Edited: added missing definition of BR TEST.miz

I would settle for visual model only. Like the Aerges' Mirage F1 module has external models for different variants that do not have any additional functions. Sent from my FP4 using Tapatalk

Still seems like this doesn't work? Sent from my FP4 using Tapatalk

I adjust my head position with the forward/aft up/down commands until my head is aligned with the pilot body in VR. Feels like adjusting the seat before flight. The correct head position in VR is rather different than the default flat screen view position. Sent from my FP4 using Tapatalk

Document T.O. 1-IM-34 seems to be publicly available "The FZU-39/B (FIGURE 2-34) is a proximity sensor used on the SUU-64/B (CBU-89/B) and SUU-65/B (CBU-87/B). When activated, the FZU-39/B transmits an omnidirectional signal which it uses to measure the vertical height above ground level. When the measured height above the ground equals the preset function altitude, the sensor sends a fire pulse to the integral fuze, opening the SUU-64 dispenser (FIGURE 2-35). When the preset SUU-65/B function altitude is reached, the FZU-39/B sends a signal for fin cant, causing the dispenser to spin. Upon reaching the selected spin rate setting, the SUU-65/B opens. The pilot has the option of changing from time func tion to proximity function by arming both the nose and the tail solenoids." If I read this correctly, pilot should be able to select either time or proximity function via nose/tail setting Edit: so it seems that my prior statement was wrong Sent from my FP4 using Tapatalk