Recluse

Just chiming in with exactly this issue on Oculus QUEST 2 + OpenXR + MT. EDIT: I taped over my QUEST 2 Proximity Sensor as described in one of the posts above and it SEEMS to be a good workaround. Would be nice to fix the issue so it wasn't necessary, but for now, it does the trick.

BUMP!

Thanks for the continued attention to MT fixes. Haven't done any extensive testing, but I did notice the GMT Radar (F/A-18) is still not working right . Shows the MAP returns which makes it hard to see the actual moving targets. Messing the GAIN is a workaround, but still an issue.

Depending on the Aircraft.. For example, Harrier Floodlights don't seem to work in MT (though honestly my VR Harrier pit seems to be OK)

Hoping for more MT optimization/fixes (e.g. Lighting, IR pointers, Hornet GMT mode)

Set your Laser Code (obviously) and on the WPN page set the ACQ to SKR. You will see a little cross when the Missile Seeker picks up the LASER Spot. You will need some point of reference (Waypoint etc..) to gauge the exact range to know when to fire for effect but this will cue you to the object being lased by the drone.

I have been playing with this and have come to these observations: both Markpoints and TargetPoints (18 target points via ATHS, so I assume the same for TOO, which, honestly should be PLENTY), are limited in number, so it is good to have the option. IN THEORY Markpoints are more versatile (you can move them around and create offsets like Waypoints) IN PRACTICE, some of the functionality seems to be broken (e.g. Making OFFSETS). Target points are more useful for assigning multiple targets to JDAMs in Absolute Mode, so that is one advantage of them over Markpoints.

Yes, I have done it exactly this way when making Waypoint Offsets. The problem is that if a MARKPOINT is selected, clicking WYPT in the ODU just toggles to TGPT NOT to W/OS as it does for Waypoints. At least I have not managed to get it to do so. Thanks for the tip on using numbers >100 for Meter offsets!! I think I remember reading it somewhere NOW but it had totally escaped me. Here's a little video. Sorry it's a little blurry in full screen. I forget to update my capture resolution for YOUTUBE. Might render in higher res after awhile. Let me know if you see something else in your testing.

I am creating this post because I started the discussion in another post about Offsets in the Mission Editor, which kind of spammed that post. SORRY! In Chuck's guide, and as several helpful responses in the aforementioned thread stated, you should be able to make OFFSETS to MARKPOINTS as you can with Waypoints. I have NOT been able to figure out the process. With a MARKPOINT selected, the only option in the ODU is WYPT (as it is for WP OFFSET) and clicking it only toggles between WYPT and TGPT. Just wondering if you can make OFFSETS to MKPOINTS and if so, how. NOTE: My original reason for wanting to do this was to find targets offset from e.g. SMOKE MARKERS, but it seems that WP OFFSETS can only be made in units of Nautical Miles vs. Meters, which makes them less than useful. So, another question is can the units for WP/MKPT offsets be changed? Thanks for your kind assistance and advice.

Thanks for the clarification. However, last night I tried it with MARKPOINTS and I could not make an offset to a MARKPOINT either. i selected the Markpoint, went to DATA and in the ODU only WYPT showed just kept toggling between WYPT and TGPT with no O/S as works with WP's. HOWEVER, I was able to hit TOO and create a true WAYPOINT by selecting in on the ODU which COULD have an OFFSET. Unfortunately, I could only create an Offset in units of nautical miles, so it was still pretty useless for the particular case where I needed meters. Quite possibly I am missing something obvious here with the OFFSET switchology...

Also commonly used for BULLSEYE reference navigation. If you have a WP on the BULLSEYE, and you get a call about something a certain Range and Bearing from BULLSEYE you can create a WP Offset to quickly navigate to that position.

This Thread Resurrection because I am reacting to this: (emphasis on targetpoint) Last night I was trying to create (in flight) an Offset to a Target Point (TOO). It was not possible. There is no T/O equivalent to the ODU W/O. I have no doubt this is "CORRECT AS IS" but it seems like it would be a really nice feature. The specific scenario was a Smoke Marker with directions to Bearing and Range to a target. I could grab the Smoke in DMT or TPOD and create a Target Point, but could not easily create an offset point. (TPOD Yardstick and 2D Yardstick were used instead). It got me wondering and then I noticed that first sentence and wondered if it SHOULD be possible. I realize this post was specific to the MISSION Editor not the In Flight option, but I am curious

Thanks for the confirmation!

I hesitate to call this an MT issue, more likely a LOCAL issue of some kind, but wondering if anyone else has seen this. Ever since the MT patch, all was working well, and it continued to work well for a ~2.5 h session on Friday after the hotfix. (with several long trips to the F10 map throughout the session) Today, on two different servers I had an issue where when I went into the F10 map for an "extended" period, say 5 min or more, my frame rates plummeted upon return to the Cockpit or any other view and never recovered. 45-60 in cockpit down to a stuttery 11-16. Exiting out and restarting DCS returned to normal, but going back into the map killed the frames again. Quest 2, running MT exe and OpenXR. RTX 3070, i7-10700K 32 GB RAM.

St. Paddy's day liveries????

Same here! All good! BOTH Scratchpad and ScratchPad Plus. I did have a question about ScratchPad Plus's insert functionality Works great for me (IN VR..... in 2D mode I think higher framerates mess up the insertions). For the Hornet,. when I insert multiple WP's, it skips one (as detailed in the Readme) but then all subsequent WP's are in order. For example, if I set my HSI to WP 0, the initial WP inserted is WP 2, but subsequent WP's are 3,4,5 etc. In the Mirage, however, each subsequent WP skips one as well, so if I have BUT 01 selected, and I insert 3 new BUTs from ScratchPad Plus, I end up with 3,5,7. Wondering if anyone else experiences this? Note: Not related to the new Open Beta or MT. IT was doing this before as well. Edit: Still happening with the new 0.5 release

Appreciate your willingness to work on this, but let me do some more testing and wait to hear from others before you go down a rabbit hole of more work for what MIGHT be MY problem.

LOL I could not find the single DLL download (finally did!) so I just downloaded the entire hotfix version. Working OK. I am seeing a strange thing in VR in the tutorials where the little boxes that are used to highlight HUD elements are doubled (seem to be rendered in each eye) and separated so they don't show over the actual element they are supposed to be showing. Worked OK on other parts of the cockpit, just not the HUD. Between the new MT patch and my tweaking with OPENXR, and all the other VR variables, I am not calling this a bug just yet... but I wondered if anyone else had seen it

I can also confirm that the MT .exe launches OPEN XR by default on Quest 2. I have been using OPEN XR, so I don't mind, but I created a test shortcut to the bin-MT/DCS.exe with NO command line parameters and my Open XR overlay came up in game. Overlay doesn't show up when I launch the original shortcut to bin/UPDATER.EXE Hmmmm..... or is it THIS setting that is doing it in the companion app? EDIT: NOPE.. I made a new shortcut to bin/DCS.exe with no command line params and it did not show the OXRTK overlay.

Heh! I just downloaded the 5.2 version of the A-29 too. I did see this note on the GITHUB, so a new version might be out soon, or maybe he means once a STABLE version is released.

Yes, thanks! At first those 1Drive links were not working for me, but now they are.

@Rudel_chwWill your updated training missions be available for download at User Files, or just released along with the next update of the mod? Ahh never mind! I read the note above about them being available when the set is completed

I'm glad it was helpful. Another related thing I have noticed: For the first AGM-65F fired, when you SCS to put TDC on the MAV WPN page, it automatically uncages the seeker. For subsequent shots, you often have to manually uncage the seeker. I think this is what gave me the clue to CAGE/UNCAGE even when it seemed like the seeker was looking at something.

Are you doing a TDC depress on the FLIR when you slew to the second target? If you don't it won't re-cue the Maverick. I find sometimes even if I do Target Designate, I need to CAGE/UNCAGE the Maverick seeker once to get it to re-cue. Though it is problematic with the Maverick Seeker resolution, you might have better success slewing the Maverick Seeker directly to the second target since it is close. On the first UNDESIGNATE, the MAV seeker remains Ground Stabilized so you could Slew it sllightly and let it lock up the next target. I also prefer using the TPOD for the better resolution, but I often run out of time.

Thanks for following up!! I thought I searched but didn't find those threads at least its not just me