MagicSlave

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

I don't remember the reference but I read that CBU fuze time sets the minimum time to arm (to prevent own aircraft damage) and the radio altimeter height is used to trigger the function (i.e. open the canister) Sent from my FP4 using Tapatalk

There is the longitudinal stick position indicator scale for that in the front panel, pilot's side Sent from my FP4 using Tapatalk

I'm gonna have to get Iraq AND Afghanistan now... Sent from my FP4 using Tapatalk

Jester also says "Alignment complete, you can select Primary Reference now." Or something like that to let you know that the alignment is complete, he has put the INS to NAV and you can put the Reference System Selector Switch to Primary position. Sent from my FP4 using Tapatalk

Sorry, I misspoke from memory. I meant the POWER page. The EGIs are on. I don't know the problem. I'll have to try creating markpoints myself later and see if it works for me or not. Sent from my FP4 using Tapatalk

Haven't tried it myself yet. Have you turned on the EGIs? (From START page on CDU) Sent from my FP4 using Tapatalk