Dugong Posted October 7, 2016 Posted October 7, 2016 I know it's not strictly CCIP, but not sure of the correct term. Previously this worked for guns and rockets, now the pipper is stuck in boresight position.
BadHabit Posted October 7, 2016 Posted October 7, 2016 Rockets and bombs Solutions work fine. It even calculates wind for you which I think many mentioned it shouldn't. The Gun is not stuck in boresight. Once in range it will calculate range. Watch your scales and LA & Break lights. Also try to use Radar Beam Mode for more accurate ranging. The only thing that goes too much off for me is the AA Gun Piipper, witch is way too sensitive on maneuvering, on average speeds and G's and the Radar tracking is horrible. "These are not the bugs you are looking for..":pilotfly: [sIGPIC][/sIGPIC] My YouTube channel SPECS -AMD FX8370 8 Core Processor 4.2 ghz -GIGABYTE 970A-UD3P -GTX 1050 TI Windforce 4g -16 GB RAM -Saitek X 52 -FaceNOIRtrack - 3 point clip Red Led
Madbrood Posted October 7, 2016 Posted October 7, 2016 To be fair, I was not seeing any change on my scales or my LA/Break lights doing anything the other day, but I'm new to the bird so I may have missed something... i7-4770k | EVGA GTX 980 SC | 16GB DDR3 | TrackIR 5, TM Warthog HOTAS, Saitek Pro Flight Rudder Pedals DCS: F-16C, F/A-18C, F-14A/B, AV-8B, FC3, A-10C, Black Shark II, UH-1H, F-86F, MiG-21bis, Mirage 2000C, AJS-37, F-5E :pilotfly:
Art-J Posted October 7, 2016 Posted October 7, 2016 The ASP gunsight should not compute impact point for any weapons, only the optimal, fixed pipper depression for chosen weapon and distance to target. Using distance scale pointer plus "launch" and "break" lights should yield pretty good accuracy, as long as You stick to optimal speed and dive angle ranges mentioned in real manual (and it does when using rockets, not so much when using gun). So the current operation is closer to what it should be. Still not perfect, but it's getting there. LN's manual is somewhat outdated now, as it describes a bit unrealistic sight's operation (full CCIP) as it worked back when the module was released. i7 9700K @ stock speed, single GTX1070, 32 gigs of RAM, TH Warthog, MFG Crosswind, Win10.
Dugong Posted October 10, 2016 Author Posted October 10, 2016 fixed pipper depression for chosen weapon and distance to target. Distance to target is dynamic so how can the above be correct? Or are you saying we can dial in a chosen range somehow?
Art-J Posted October 12, 2016 Posted October 12, 2016 Distance to target is dynamic so how can the above be correct? Or are you saying we can dial in a chosen range somehow? Yes, the distance changes and for every weapon type, there's only one theoretical pipper depression angle, and one launching distance, which combined with chosen dive speed and angle makes the projectiles land exactly on target. Modern sights can calculate these parameters continuously, the old ones could not. For example, in DCS Mi-8, You have to dial in the depression in PKI sight manually (from relevant tables for every weapon type), and estimate launch distance Yourself (using markings on the fixed net). Same thing with A-4 sight in F-86 in rockets mode. In bombing modes You get either automatic pipper depression (still fixed though) and manual release, or auto depression and auto release, depending on bomb delivery method. The ASP gunsight in the MiG was something in between - depending on weapon type, it switched to optimal depression and using ranging either from radar or barometric slant range unit, it gave the pilot continuous distance information, plus the optimal "launch" moment (indicated by the light). As long as pilot followed suggested cannon/rockets dive attack pattern (30-35 degrees and 800 km/h TAS or 20-25 degrees and 900 km/h TAS) and kept his eye on "launch" and "break attack" lights, he could engage targets with intended accuracy. The procedure didn't work for bombing though, as sight was unable to calculate parameters for that and one could only use manual pipper adjustment and release moment estimation. i7 9700K @ stock speed, single GTX1070, 32 gigs of RAM, TH Warthog, MFG Crosswind, Win10.
Dugong Posted October 14, 2016 Author Posted October 14, 2016 Okay, As it currently stands in game the A/G guns solution is behaving as if it's in manual mode even though it's in auto mode, and the target size knob has zero effect, in contrast to the R/L manual.
Frederf Posted October 14, 2016 Posted October 14, 2016 A lot about the ASP still isn't right as you say. The manual/auto switch is not changing between behaviors as expected. The reticle size is not responding correctly to span-range relationships.
Recommended Posts