Recluse

It seems to be broken, or at least not functioning the way it used to and so far we are unable to get a definitive answer on whether it is being looked at or assumed correct as is. At the moment the only way to Ripple GPS guided weapons in TOO mode is to create MARKPOINTS and toggle through them to designate for each release. Currently, the UNDESIGNATE removes ALL coordinates from all stations, so the method outlined in so many videos is currently not available.

Have had this experience and usually it comes down to the axis assigned to one of the TDC SLEW directions being un-calibrated and drifting or needing more of a Center Dead Zone.

<sigh> nothing yet in the latest Open Beta

Thanks. I think I must have been wrong. I looked up some old YOUTUBE tutorials when the APKWS was added and arming screens only showed the 7 round pods. My mistake!

My recollection was we previously had 19 rocket APKWS pods as well, and now "only" 7 rounders. Same rocket with a guidance kit, right?

Thanks! They look good. In your experience do they have as big a dynamic range as the mechanical pots? As I mentioned, the ViperGear Hall sensors always had a relatively short range (or maybe I got a bad set?)

Thanks Rudel. SO... I replaced the Y Axis Hall sensor with an old Mechanical POT. Calibration works fine!! Should have tried that before posting, but I wasn't sure the old pot even worked, so it might not have been a good test. Odd that the ViperGear Hall Sensor would go bad, though since it is all pretty much solid state. I still have the VIper Gear X sensor (which I swapped out when the magnet shaft broke) so I will try that as the Y axis with the Y magnet and see what happens.

So this started happening recently. When I go to calibrate the COUGAR, I can see the RAW values increase and decrease during Y axis Calibration, but when Calibration is done, I see one of these 3 things: - Most often, (Using the COUGAR HOTAS VIEWER or FOXY JOYSTICK ANALYZER) I got full deflection when pulling stick BACK, but on pushing forward, it only deflects partially. This behavior is observed in game - After the latest teardown, I now see the opposite, with partial deflection pushing forward and NO deflection pulling back (I can see Raw Values changing) -or it is just DEAD with no deflection either way After repeated attempts, I could get it to calibrate, but now it seems totally unable. - Reflashed the firmware -Several attempts at ReStart and or/Plug/unplug For reference, my Y axis is using Viper Gear C-Muk Hall sensors. The Raw deflections have always been LOWER than the RAW values from mechanical POTS, but they ALWAYS calibrated. Was going to try and put a Mechanical POT back in, but not sure if I have one that is reliable (hence the replacement with Viper Gear). Is my Cougar Mainboard shot? Anything I can try?

Regarding: Has this been determined to be CORRECT AS IS or is there any chance it will be changed to work the way it used to work i.e. Saving coordinates during a STEP or change from TOO1 to TOO2 and not deleting all coords with an UNDESIGNATE?

You sure you are in TPOD HOTAS mode (SSS Depress 2x) rather than INS or TV when the TPOD is up?

Ahh sorry about that!! I forgot I had A-4's available in that mission and that they would be required to view the .trk Not sure you will get any more out of the .trk than what is shown in the Video (other than seeing a terrible takeoff roll!). As @AdrianL said, it is a FREE mod anyway (and really fun to fly).

Great! Glad it is starting to come together. I made a little video (rough, but it tells the story) in the Marianas using the various FLIR modes (VVSLV, SNPLW, WPDESG) and sometimes it is pretty GREEN and washed out when pointing directly at the cloudless sky or ocean surface, but that is expected. Once there is SOMETHING with a little IR contrast you start making things out (even if it is part of your aircraft when the gimbals are pointing there). Still uploading to YOUTUBE, so I will link it when ready if you have an interest. Meanwhile you can watch a .trk, but without the explanations. - Take off (poorly) - Head toward target area -Unstow FLIR to VVSLV mode with NWS/Undesignate 2x (I said Sensor Control Switch in the video... that was wrong) - NWS/undesignate 2x to SNWPLW mode (I said Sensor Control Switch again... WRONG!) - Then WPDSG to slew FLIR to ground target - Then turn FLIR off and start again to show that WPDSG will unstow automatically and point to target (In the TRK and VIDEO, I turned the FLIR all the way to OFF. I didn't mean to, I just clicked the wrong mouse button. Meant to just go STBY and then back ON) - Engage with Maverick FLIR_Marianas.trk

Well that is strange. I don't know what is going on there. It did not happen to me no matter what I tried. Never seen a designation jump like that.

I tried every way possible: Designate a spot on the ground using FLIR by SLEW and TDC Depress VVSLV lock on the FLIR TDC in the HUD and designation. Slew the FLIR onto a different target. (not shown in this video) Everything works exactly the same for me. Designation remains as MODE cycles between AUTO and CCIP Sorry.. the video is in slo-mo I always forget that ALT-Z to invoke GeForce Experience for recording is the same as the time decrease! Please post a .TRK of what you are seeing and maybe we can figure it out.

Not my experience. See the little video below I just made. AG MODE - > Mk 82 to CCIP ->FLIR UP -> WPDESG ->MK82 goes to AUTO --> Switch back to CCIP -> Zooming in to show FLIR still has target. ->Switch to AUTO -> Switch Back to CCIP. This is the way I do it all the time if I need to switch from AUTO back to CCIP Hmmm I suppose in this case it was the WP Designation not the FLIR designation keeping the target, but I have done it after moving the FLIR and re-designating. I just tried it again using only FLIR VVSLV to designate a target. Same process works as in the video above.

One thing to check is the WYPT you are slaving to. Is it at GROUND level or is it up in the air somewhere??? You can check the elevation of the WYPT in the DATA screen of the HSI, and, from there you can also EDIT the elevation with the UFC option. Usually -0 (hit zero twice) works, but you can get the actual elevation from the F10 map as well and enter it in Feet or Meters. Also, ARE YOU SURE you are in SNOWPLOW mode or WPDESG mode? When the FLIR is first brought online it is Stowed. Double click NWS brings you to VVSLV and another Double CLick brings you to SNOWPLOW. (or you can use the buttons). When stowed, it is all green with no imagery. WPDSG will unstow and point to the Waypoint without the intermediate unstowage, but you might try it. It would help if you posted a .trk file.

Some people want realism down to the rivet. Some people want a detailed simulation they can work to master and still enjoy, some people want a game they can play. The Community isn't monolithic.

Yeah, I think his question was less about true BORESIGHTING and more about slaving to a designated target. I really HATED the Boresighting procedure in BMS (largely because after a lot of work it still didn't work very well) so I am not looking forward to seeing it in the Harrier or Hornet, though I gather it is implemented in the DCS F-16 or soon will be. Not sure if there is any REAL LIFE differences between the platforms that would make it optional in the Harrier/Hornet. The "Boresighting" I am referring to is needing to adjust the aimpoint of the TPOD to the AImpoint of the Maverick Seeker by correlating them to some standard point (e.g. some building that is easy to see with both seekers) so that the TPOD (or DMT) and Maverick Sensor are aligned. Currently in the Harrier and Hornet they are aligned automatically. No idea if this is real life or not in those platforms

I have not had to Undesignate the target. Just switch AUTO back to CCIP on the Stores page. Whether correct or not, it allows reversion to CCIP pipper with the target diamond available for reference. This also allows Visual bombing of another target near the designation point if you happen to see something else that needs bombing, or if your designation was a little off and you need to adjust the CCIP aimpoint as you get closer.

I don't think you can currently use them for separate targets as the coordinates will be overwritten without the ability to UNDESIGNATE. Select TOO1: Designate Select TOO2: Designate Now there are different coordinates for each TOO. If you cycle back to T001 to drop, the TOO2 coordinates will over-write what was there. The videos you have seen are probably OLD.

Then Why on Earth are there TOO1 and TOO2 options when multiple JDAM are carried on a station if you cannot use them as separate targets?? Or is this wrong as well?

I had this happen recently. Was going crazy trying to figure it out. What I think was happening is that the axis I had mapped for TDC slew was wandering and taking the cursor along with it. After some fiddling I got it re-center. Not sure that is what is happening for you, but definitely check your axis drift.

It should work exactly the same. Designate a target with either DMT or TPOD, THEN uncage and the Maverick should snap to the target. When uncaging without a system designation, it will just be Boresighted straight ahead. Designate the target first and then UNCAGE. If you slew the seeker independently before designating a target it will not snap to it. You have to CAGE, Undesignate, re-designate. Uncage to start again.

Yes. All is working as designed now. Teacypher's video is perfect! It is unfortunately not documented in the manual which has yet to catch up, but was posted on the forum and has a complete explanation.

Reported here, but Haven't seen any updates.