mtuckner Posted March 6, 2011 Posted March 6, 2011 Never had the problem before this patch. Seems like whenever switched to guns it gives me CCIP invalid and no reticle. I've cycled through with the Master mode button and it doesn't help. I have switched the IFCC on and off and it did come on but after shooting a mav it went back to being screwy. Am I missing something? :helpsmilie:
tdar Posted March 6, 2011 Posted March 6, 2011 hmm, i had the same thing happen to me yesterday. However, in CCIP guns mode there was a 'wagon-wheel' similar to the Maverick wagon wheel, and the gun rounds were impacting at the centre of this wheel.
mtuckner Posted March 6, 2011 Author Posted March 6, 2011 I'm looking for the typical gun pipper, big circle with the dot and range indication. I still have the "bore" x that shows where they fly straight out and that works fine when danger close, but I don't want to get that damned close unless its just trucks! It's driving me nuts lol. I'm Alt-Tabbed waiting for a response because I can't get close enough for gun runs on these bmps without the CCIP reticles.
E61-v1T1 Posted March 6, 2011 Posted March 6, 2011 Maybe you are missing this; http://forums.eagle.ru/showpost.php?p=1115789&postcount=19 2 [sIGPIC][/sIGPIC] Hotas TM Warthog | Saitek Pro Flight Rudder | Oculus Rift | MSI Z97 Gaming 3| i5-4690K oc 4.5Ghz | 16Gb ddr3 | GTX 1080 Ti | W10 64Bits
CrashEd Posted March 6, 2011 Posted March 6, 2011 (edited) Maybe you are missing this; http://forums.eagle.ru/showpost.php?p=1115789&postcount=19 Can anyone elaborate on what this actually does? It's nice to know how to fix the problem but I'd like to know why. Presumably you can change between a pilot selectable elevation (using the data up and down keys) or a pre-determined waypoint elevation from (DTS) using the SEL keys... Now, during a cold start it defaults to the pilot selectable elevation rather than the DTS which contains the correct elevation data. Is this the reason why we get the CCIP Invalid message? The pipper must be using this, incorrect, elevation and hence the error? Edited March 6, 2011 by CrashEd
CrashEd Posted March 7, 2011 Posted March 7, 2011 Anyone? I suspect only the devs can answer this as there doesn't appear to be any detailed info in the manual about it.
Nate--IRL-- Posted March 7, 2011 Posted March 7, 2011 I suspect it has to do with the DTSAS (Digital Terrain System Application Software) system, see Pg 205 of the manual. It seems that in some missions the DTSAS is in the Coordinate ranging submode rather than the Normal DTSAS mode. Nate Ka-50 AutoPilot/stabilisation system description and operation by IvanK- Essential Reading
CrashEd Posted March 7, 2011 Posted March 7, 2011 Many thanks Nate :thumbup: This would explain the problems we were having in the CSAR multiplayer mission the other day.
effte Posted March 7, 2011 Posted March 7, 2011 You are essentially telling the systems to use the digital terrain model for ground elevation when doing the ballistics for the gun, rather than to use the waypoint elevation which is way off. Another reason to use target elevations for mission waypoints, rather than planned flight altitudes. ----- Introduction to UTM/MGRS - Trying to get your head around what trim is, how it works and how to use it? - DCS helos vs the real world.
RichardG Posted March 9, 2011 Posted March 9, 2011 (edited) I'm having this problem, but I'm trying to shoot a SPI with guns or rockets, not a waypoint. Wouldn't the TGP know the slant angle and range to a target you were looking at? Edited March 9, 2011 by RichardG
StrongHarm Posted March 10, 2011 Posted March 10, 2011 Read here It's a good thing that this is Early Access and we've all volunteered to help test and enhance this work in progress... despite the frustrations inherent in the task with even the simplest of software... otherwise people might not understand that this incredibly complex unfinished module is unfinished. /light-hearted sarcasm
Recommended Posts