Recluse

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.

. I don't know if CPL works with a TGT unless you have an AUTO mode selected for a weapon where it couples to the ASL. I just tried it an CPL doesn't appear when there is JUST a target designated. Looked at Matt Wagner's video and it does need an AUTO designation for CPL TGT (~3:36 in the video)

No fix for F/A-18 JDAM TOO programming

I can see all the HUD elements in a variety of positions. Not having spent any time (other than a few airshow and static museum displays) in a cockpit, I don't really know what looks "right" the way it does when I get into an unfamiliar car and adjust seat and mirrors to my comfort level. I usually turn the Pilot Body OFF, but I have to admit that with it ON there is a better gauge to the overall "fit". At this point, it isn't that critical. Just trying to refine the already game changing VR experience as much as possible.

Not sure where to put this...but this thread seems wide ranging enough that it won't be too much of a hijack I have been watching various cockpit videos to get an idea of WHERE to position myself in VR for the most "realistic" look. I jacked up my seat pretty high (and diddled with the camera) so that I could see over the nose and see all the attennae there. Great view, but then it seemed hard to "reach" a lot of the cockpit switches. Talking F/A-18 here, but similar questions for other modules. Usually I have myself positioned so by looking UP, I can just see the top of my helmet in the Mirror, (and can see if the airbrake is up) but in some Cockpit videos, it seems like a lot more of the helmet including visor are visible in the mirror, (higher seat position or taller pilot) while, at the same time, less of the nose is visible. Also been cranking myself farther forward to aid in the readability of displays, but not so far as to make the position of the throttle not be too far back. Wondering where others situate themselves. In particular, the Community A-4 mod makes me feel like I am deep down in the pit, but I suspect that is the way it was vs. the more modern bubble canopies with greater visibility.

The first time I saw DCS in the QUEST 2 I was hooked and can never go back. The more comfortable I get, the more flaws I find, and I still marvel at the 4K graphics in Youtube vids, but EVERY SINGLE TIME I am awed by VR. Looking back at the WireFrames of Sublogic JET, the CGA graphics of the original FALCON and up through the graphics technology tree and TrackIR innovations, I always had the willing suspension of disbelief and thought I was THERE. When I put on the headset... I REALLY AM THERE. I hope I live for the NEXT innovation that will make current VR seem like Sublogic Wireframes! P.S. Sorry we hijacked the Patch Notes thread!

Me too. My FIRST Flight (FREE FLIGHT mission) was kind of awful. Since then I get about the same performance as other maps. Some issues when on heavily populated airfields for sure, but I haven't tried it on an equally populated airfield on another map.

Assuming this applies after the NEXT OB update, or whenever the Change Log indicates the update to Mavericks?

Yes

Thanks for that!! I guessed it had something to do with it being a RE variant but I didn't know the T was for Thermally Protected!