Bahger Posted November 5, 2010 Posted November 5, 2010 Yeah, that is a good video, but you'll find that skipping the above step is much easier. Instead of the above, simply rotate the STEER PT dial to MARK to make the markpoints show up on the HUD. Interesting. Novice question but here goes anyway: where is the STEER PT dial? So far, I've been cycling steerpoints either with DMS UP SHORT (when HUD is SOI) or on the UFC rocker switch.
power5 Posted November 5, 2010 Posted November 5, 2010 Behind the CDU keypad on the right panel. [sIGPIC][/sIGPIC] Aaron i7 2600k@4.4ghz, GTX1060-6gb, 16gb DDR3, T16000m, Track IR5 BS2-A10C-UH1-FC3-M2000-F18C-A4E-F14B-BF109
Bahger Posted November 5, 2010 Posted November 5, 2010 Behind the CDU keypad on the right panel. Thanks! That would make things faster. Presumably I'd still use DMS UP SHORT to cycle the mark points in the HUD on the bomb run?
Woots Posted November 5, 2010 Posted November 5, 2010 (edited) Presumably I'd still use DMS UP SHORT to cycle the mark points in the HUD on the bomb run? Yes, you still cycle the markpoints with DMS UP SHORT. Return the STEER PT dial back to FLT PLAN and you're back to cycling steerpoints. Edited November 5, 2010 by Woots [sIGPIC][/sIGPIC]
STP Dragon Posted November 6, 2010 Author Posted November 6, 2010 (edited) It's working!!!! You really have to set the SPI before you add the markpoints. Many thanks guys! :thumbup: Edited November 6, 2010 by =STP= Dragon Homepage: Spare-Time-Pilots DCS:BlackShark v1.0.2: BLINDSPOTs EditorMod DRAGONs ArmA2-Sounds DRAGONs BS1 TRAININGPACK DRAGONs MISSIONPACK [bS & FC2] DCS:World: TM WARTHOG PROFIL FOR BS2 DRAGONs BS2_TRAININGPACK DRAGONs TRAININGPACK DRAGONs MISSIONPACK
jazzinman Posted November 7, 2010 Posted November 7, 2010 I noticed I get correct markpoint with infrared pointer but not laser until within about 10nm of target. Could the laser have a range limit?
coolts Posted November 7, 2010 Posted November 7, 2010 It sure does. [sIGPIC][/sIGPIC] i7 9700k | 32gb DDR4 | Geforce 2080ti | TrackIR 5 | Rift S | HOTAS WARTHOG | CH PRO Pedals
pyates2104 Posted November 8, 2010 Posted November 8, 2010 JDAM multiple Thats it! Eureka! I thought this was a bug at first, I stand corrected. Method: (Ish) 1. Laser in latch mode 2. Acquire Target in TDC (Range is about 25 Km at this point) (Point or area mode) 3. Laser on 4. TMS forward long to set as SPI 5. TMS right short to set as mark point. The mark point is NOT the SPI its a point in the air set as you set the mark point. If you carry out the same procedure as above but omit steps 1 and 3 (Latch and laser on) the mark point is set correctly. Problem is, using this method at this range, your mark point is usually off by at lease 20 feet. So am I correct in saying that you wont get a good SPI inertial point unless your within about 10 km of the target?
takamba Posted November 8, 2010 Posted November 8, 2010 (edited) Try the same in Nevada. You will be surprised, I promise. In Nevada my Mark Points are allways on target. In the old DCS-Terrain my Mark Points are ALLWAYS off the target. Independent on laser using and range to target. Btw, if your laser dont get a range, your mark point is set to your actual position. Because the "measured" range is zero. As soon as you get a laser range, the mark points are all in the way they should, on the ground not in the air. Edited November 8, 2010 by takamba DCS Rafale - please :thumbup:
pyates2104 Posted November 8, 2010 Posted November 8, 2010 Try the same in Nevada. You will be surprised, I promise. In Nevada my Mark Points are allways on target. In the old DCS-Terrain my Mark Points are ALLWAYS off the target. Independent on laser using and range to target. Btw, if your laser dont get a range, your mark point is set to your actual position. Because the "measured" range is zero. As soon as you get a laser range, the mark points are all in the way they should, on the ground not in the air. This WAS in Nevada, I'm thinking it was the slant range and angle 20KM + that was causing the inaccuracy.
takamba Posted November 8, 2010 Posted November 8, 2010 (edited) Shame on me :spam_laser: Inaccuracy is the result of not using (not be able to use) the laser. Same behaviour here. Edited November 8, 2010 by takamba DCS Rafale - please :thumbup:
jazzinman Posted November 8, 2010 Posted November 8, 2010 Dragon, I played your track last nite, took control just after you set your first mark, then waited until target was within 10nm commanded tms right short and the mark was on the ground. I usually have the ccu repeater on the right mfd and verify altitude of mark.
Pixel Posted November 8, 2010 Posted November 8, 2010 I tried to read this thread as good as possible as I had also trouble with creating markpoints. Unfortunatly my english is not so good - so maybe I didn't understand everything correctly (so sorry for allready written posts). One of the problems was, that creating a markpoint in the TGP (with TMS short right) was fine when using NO laser. It didn't work, when I activated the laser. After a little confusion I found out that the calculated distance was 0 => Thats why the markpoint was created exactly at my planes location. After playing around a little bit more I discovered that the laser is working only up to a distance to (exactly) 8.0 in allmost every case. Can someone confirm this behaviour, or am I doing something wrong?
Frederf Posted November 8, 2010 Posted November 8, 2010 Shouldn't the A-10C be able to work out offset markpoint without laser rangefinding using the terrain database and ownship position?
pyates2104 Posted November 9, 2010 Posted November 9, 2010 Shouldn't the A-10C be able to work out offset markpoint without laser rangefinding using the terrain database and ownship position? I tried to read this thread as good as possible as I had also trouble with creating markpoints. Unfortunatly my english is not so good - so maybe I didn't understand everything correctly (so sorry for allready written posts). One of the problems was, that creating a markpoint in the TGP (with TMS short right) was fine when using NO laser. It didn't work, when I activated the laser. After a little confusion I found out that the calculated distance was 0 => Thats why the markpoint was created exactly at my planes location. After playing around a little bit more I discovered that the laser is working only up to a distance to (exactly) 8.0 in allmost every case. Can someone confirm this behaviour, or am I doing something wrong? Pixel, It's the slant range that counts. It really depends on how high you are, at lower altitudes the laser range will be up to a maximum of 10 km. If you don't lase, you can get a mark point at far greater range but it will based on LOS (Line of sight) and will not be as accurate. Frederf, Yes, but.... as I said, it will not be as accurate. The more oblique the angle, the less accurate the mark point. I've been fiddling with this scenario for the last few days, this is what I've determined. 1. If you get a good range using the laser range finder (usually inside 10 km) this is by far the most accurate method of marking targets. 2. If you want to mark outside of 10Km, you will not be able to use the Laser, The mark point is based on a LOS calculation and will usually be behind the target. It's best to select area mode and mark just in front of the target, this is in effect, you compensating for the LOS deviation.
Frederf Posted November 9, 2010 Posted November 9, 2010 Yup, since saying that I watched the headspace video about JDAMs, SPI, and ranging and it confirms that the A-10 has a rough ranging with angles and terrain database and precise ranging with active laser use.
GumidekCZ Posted November 28, 2010 Posted November 28, 2010 Hi I have already written this somewhere in the forum, but I want to be mentioned here in this thread. Why all my waypoints after made in CDU from markpoints are about 20m sideways (not behind) my target?? Have someone the same experience?? I will post saved track today.
NoJoe Posted November 28, 2010 Posted November 28, 2010 Hi I have already written this somewhere in the forum, but I want to be mentioned here in this thread. Why all my waypoints after made in CDU from markpoints are about 20m sideways (not behind) my target?? Have someone the same experience?? I will post saved track today. Yeah, I get that too. Try approaching from each of the cardinal directions (North, South, East, then West) and see that the markpoint is always created on the same side, regardless of which direction you approached. Other people have mentioned this too, so hopefully it's a known bug? (or undocumented feature :P ) --NoJoe
Recommended Posts