Whisper Posted November 20, 2016 Posted November 20, 2016 Quick question: I do not see the PI button appear? TAS and RS are selected. Your selected waypoint must be the IP one, with offset configured. Without offset on the currently active waypoint, the IP option does not appear. Whisper of old OFP & C6 forums, now Kalbuth. Specs : i7 6700K / MSI 1070 / 32G RAM / SSD / Rift S / Virpil MongooseT50 / Virpil T50 CM2 Throttle / MFG Crosswind. All but Viggen, Yak52 & F16
jojo Posted November 20, 2016 Posted November 20, 2016 :megalol:Quick question: I do not see the PI button appear? TAS and RS are selected. "PI" option appears on PCA only if "BAD" data is fed to selected DEST waypoint in PCN. Maybe it's the problem. Edit: Whisper has been faster :thumbup: Mirage fanatic ! I7-7700K/ MSI RTX3080/ RAM 64 Go/ SSD / TM Hornet stick-Virpil WarBRD + Virpil CM3 Throttle + MFG Crosswind + Reverb G2. Flickr gallery: https://www.flickr.com/gp/71068385@N02/728Hbi
zaelu Posted November 20, 2016 Posted November 20, 2016 Question. This sequence: 1. Select the weapon that you want to use: BL1/BF1/BF4/BF8/EL1. (See Bomb Codes note) 2. Set Master Arm On. System switches to Ground Attack mode. Is mandatory? I mean if you press first the Master Arm it will not work anymore? Because I am trying to do in 2.04 this and it simply doesn't work and thinking about what I could do wrong I remembered I pressed Master Arm first. [sIGPIC][/sIGPIC] I5 4670k, 32GB, GTX 1070, Thrustmaster TFRP, G940 Throttle extremely modded with Bodnar 0836X and Bu0836A, Warthog Joystick with F-18 grip, Oculus Rift S - Almost all is made from gifts from friends, the most expensive parts at least
tflash Posted November 20, 2016 Posted November 20, 2016 OK thanks both! I thought it was the other way around, now it works! [sIGPIC][/sIGPIC]
zaelu Posted November 21, 2016 Posted November 21, 2016 So can someone that tried in 2.04 confirm that it works? For me the bombs are released immediately as I press and hold the trigger. The cross on the ground doesn't update. I can't enter altitude for 00 waypoint (not the offset BAD) [sIGPIC][/sIGPIC] I5 4670k, 32GB, GTX 1070, Thrustmaster TFRP, G940 Throttle extremely modded with Bodnar 0836X and Bu0836A, Warthog Joystick with F-18 grip, Oculus Rift S - Almost all is made from gifts from friends, the most expensive parts at least
Whisper Posted November 21, 2016 Posted November 21, 2016 I can't enter altitude for 00 waypoint (not the offset BAD) I don't get that last part WP 00 is your current postion, why would you want to update it? During align procedure? For your other Qs, I'm on 1.55 unfortunately, can't tell for 2.04 Whisper of old OFP & C6 forums, now Kalbuth. Specs : i7 6700K / MSI 1070 / 32G RAM / SSD / Rift S / Virpil MongooseT50 / Virpil T50 CM2 Throttle / MFG Crosswind. All but Viggen, Yak52 & F16
zaelu Posted November 21, 2016 Posted November 21, 2016 Well... for the same reasons we change the coordinates of 00 Waypoint... it shows an error of 1-2 meters at the cold start. I thought maybe it's important to start with a first waypoint as precise as possible. But apparently you can't change that altitude. You can try to edit it but when you press "insert" it reverts to the preexistent number. [sIGPIC][/sIGPIC] I5 4670k, 32GB, GTX 1070, Thrustmaster TFRP, G940 Throttle extremely modded with Bodnar 0836X and Bu0836A, Warthog Joystick with F-18 grip, Oculus Rift S - Almost all is made from gifts from friends, the most expensive parts at least
Whisper Posted November 21, 2016 Posted November 21, 2016 Maybe it's not an error but the actual height of the INS system inside the airframe, counting the height of the aircraft? :) I don't know, I don't know if height correction is part of alignment procedure Whisper of old OFP & C6 forums, now Kalbuth. Specs : i7 6700K / MSI 1070 / 32G RAM / SSD / Rift S / Virpil MongooseT50 / Virpil T50 CM2 Throttle / MFG Crosswind. All but Viggen, Yak52 & F16
zaelu Posted November 21, 2016 Posted November 21, 2016 Could be. I don't remember to be in the manual but I think I saw something about it in some tutorial, maybe I understood wrong that. Anyway. in 2.04 I tried to INS bomb and no go. When I see the cue I press and hold but the bombs are instantly released. [sIGPIC][/sIGPIC] I5 4670k, 32GB, GTX 1070, Thrustmaster TFRP, G940 Throttle extremely modded with Bodnar 0836X and Bu0836A, Warthog Joystick with F-18 grip, Oculus Rift S - Almost all is made from gifts from friends, the most expensive parts at least
Frederf Posted November 21, 2016 Posted November 21, 2016 I don't get that last part WP 00 is your current postion, why would you want to update it? During align procedure? For your other Qs, I'm on 1.55 unfortunately, can't tell for 2.04 You can type in a new altitude for 00. But there are sometimes problems where only meters works or feet (but not the other one). And you must enter altitude data with all digits so 123 meters is entered with 0-0-0-1-2-3 (or however many leading zeros is needed to fill the display). And yes if you knew your altitude and it was different from INS you can type in a more accurate number in the ground or air.
tflash Posted November 26, 2016 Posted November 26, 2016 I managed to score a direct hit! I made a target with a FARP and some barracks, in a circular zone about 30 meters in diameter. After really precise measurement in the ME of the altitudes, distance from IP and bearing I got a big hit ! This works great!!!! [sIGPIC][/sIGPIC]
Joni Posted July 30, 2017 Posted July 30, 2017 The INS can be used for precision bombing of fixed targets on the ground. The use of the INS simplifies targeting calculations, specially the target altitude (ground altitude). INS should not be used for bombing moving objects. REQUIREMENTS: 1. A Flight plant that includes the target area. 2. A waypoint (BUT) that is to be used as the bombing run inital point (IP). 3. An offset (BAD) to the IP that is where the target is located. Note: As you can see the target is NOT on the waypoint but offset to it. The target offset can be set as follows: a. In x/y coordinates by using ΔL/ΔG: ΔL = Distance difference between the IP Latitude and the BAD Latitude expressed in kilometers to the North or South. (True North is used) ΔG = Distance difference between the IP Longitude and the BAD Longitude expressed in kilometers to the East or West. (True North is used) b. In polar ρ/θ (Rho/Theta) coordinates: ρ (Rho) = distance to the BAD position from the IP expressed in Nautical Miles. θ (Theta) = True North Bearing from the IP towards the BAD. c. ΔAlt is required. ΔAlt = Altitude difference between the IP altitude and the BAD altitude: + will add the value to the IP altitude. - will subtract the value from the IP altitude. NOTE: IP altitude MUST be ground altitude. I.E: The altitude of the ground surface above the sea level at the waypoint position. Procedures: CHECK THE FOLLOWING: 1. Radar is ON and Emitting. 2. Radar Altimeter is ON. BEFORE REACHING THE WAYPOINT/IP 1. Select the weapon that you want to use: BL1/BF1/BF4/BF8/EL1. (See Bomb Codes note) 2. Set Master Arm On. System switches to Ground Attack mode. 3. Check that both TAS and RS are selected. 4. Click on PI (Point Initial) button in the PCA. This will designate current waypoint as the IP. 5. The following cues will appear on the HUD: - A diamond at the bottom of the HUD for IP position update purposes (Radar needs to be in TAS for this option. The diamond represents the radar LOS while in TAS mode) - Normal NAV cues: "House" track error cue and "Cross" position cue when distance is below 10 NM. - HSI will display bearing and distance to IP. 6. Update IP position by using the diamond to determine distance to IP (See TAS Position Update Note). HUD will display radar range to IP. You can keep updating IP position as many times as you wish to increase accuracy. 7. IF BL1/EL1 were selected, wings will appear on the FPM --O-- after the 1st IP position update. The wings will provide steering cues towards the BAD. 8. BAD, REC and VAL lights turn on in the PCN when IP is selected. DO NOT CLICK ON VAL UNTIL AFTER WEAPONS RELEASE OTHERWISE TARGETING CALCULATIONS WILL BE OFF. 9. Fly towards the IP by following NAV cues. OVERFLYING THE WAYPOINT/IP 1. HUD radar diamond disappears. 2. Radar range is replaced by range to target (BAD). 2. NAV cues shift towards BAD position. 4. HSI will display bearing and distance to BAD. WEAPONS RELEASE: 1. BL1/EL1 - CCRP: 1.1. Release cues appear in the HUD when in range for pull up. 1.2. Pull UP with full aft stick for max range release. The later/ the slower the pull up is, the closer will the release happen and the lower will be the release angle. 1.3. Press the trigger for weapons release consent. 1.4. Keep the wings level with your FPM during the climb --o-- 1.5. The bombs will be automatically released when the release cue cross the target cue (FPM). 1.6. Release the trigger. 2. BF1/BF4/BF8 - CCIP 2.1. Align the CCIP with the target "Cross". 2.2. Press the trigger when the CCIP cue is over the "Cross" AFTER WEAPONS RELEASE 1. HUD returns to IP designation mode. - HUD NAV cues point towards the IP. - HSI will display bearing and distance to IP. 2. Click on VAL por INS position update if desired. 3. Set Master Arm Off to return to NAV mode. 4. PCN BAD, REC and VAL lights turn off. NOTES: Bomb Codes: BL1 = Mk-82 BF1 = Mk-82S Snakeye BF4 = BLG-66 Belouga (Mk-20 Rockeye stand-in) BF8 = BAP-100 EL1 = GBU-12, GBU-16, GBU-24 TAS Position Update: To update the IP position you must: 1. Place the diamond over the IP true position. The Cross can be offset to it. 2. Click on the Radar Position Update HOTAS Key. The INS will update the IP position. Cross will center on the IP. 3. PCN Display will show: 3.1: If parameter knob is in ΔL/ΔG, the distance (Km) to the IP in x/y format. 3.2: If parameter knob is not in ΔL/ΔG, the distance in NM and the bearing to the IP. 4. DO NOT CLICK ON VAL. The system automatically uses this distance for target calculation. Example: The IP is located on top of a water tower. The HUD Cross is located away from the tower. Place the tower on the diamond and click on radar position update. The cross will be now centered on the water tower. ATTENTION: If for any reason the radar is not available, the INS will extrapolate range to IP based on radar altimeter values with subsequent loss of precision. Hi, I cannot get this to work. Every time the CCRP release cue appears I press the pickle button and the bombs fall away, they dont wait until the cue centers with FPM as always. Is this broken or something? Thanks! Intel Core i5-8600k + Cooler Master Hyper 212 EVO | Gigabyte GTX 1070 Aorus 8G | 32GB DDR4 Corsair Vengance LPX Black 3200MHz | Gigabyte Z370 Aorus Gaming 3 | WD Black SN750 NVMe 500GB | Samsung 850 EVO 250GB | WD Green 240GB | WD Caviar Black 1TB SATA 3 | WD Caviar Blue 500GB SATA 3 | EVGA 650 GQ 80+ Gold | Samsung CF391 Curved 32" | Corsair 400C | Steelseries Arctis 5 --- Razer Kraken X Lite | Logitech G305 | Redragon Dyaus 2 K509 | Xbox 360 | Saitek X-52 Pro | Thrustmaster TWCS | TrackIR 5
Nero.ger Posted November 15, 2017 Posted November 15, 2017 Hi, I cannot get this to work. Every time the CCRP release cue appears I press the pickle button and the bombs fall away, they dont wait until the cue centers with FPM as always. Is this broken or something? Thanks! i have experienced exactly the same, also i dont have a clue when to pull up 'controlling' the Ka50 feels like a discussion with the Autopilot and trim system about the flight direction.
Joni Posted November 15, 2017 Posted November 15, 2017 Its broken a lot of time ago Intel Core i5-8600k + Cooler Master Hyper 212 EVO | Gigabyte GTX 1070 Aorus 8G | 32GB DDR4 Corsair Vengance LPX Black 3200MHz | Gigabyte Z370 Aorus Gaming 3 | WD Black SN750 NVMe 500GB | Samsung 850 EVO 250GB | WD Green 240GB | WD Caviar Black 1TB SATA 3 | WD Caviar Blue 500GB SATA 3 | EVGA 650 GQ 80+ Gold | Samsung CF391 Curved 32" | Corsair 400C | Steelseries Arctis 5 --- Razer Kraken X Lite | Logitech G305 | Redragon Dyaus 2 K509 | Xbox 360 | Saitek X-52 Pro | Thrustmaster TWCS | TrackIR 5
Recommended Posts