Recluse
-
Posts
1144 -
Joined
-
Last visited
Content Type
Profiles
Forums
Events
Everything posted by Recluse
-
So as I have been learning the F-15E, I am reminded that of the aircraft I fly, the Mudhen, the Harrier, the Mirage (don't recall the A-10C) all have a mechanism to punch in a desired Waypoint and jump straight to it for Navigation. Pretty sure the VIPER can too (from my BMS days) I have not found such a mechanism in the Hornet!! IN some missions we fly (e.g. FOOTHOLD) there are MANY MANY waypoints and it is annoying and cumbersome to have to scroll up and down with the appropriate PB to get to the desired WP. Is there a way to do this via the UFC that I have been missing all this time?? Seems like an odd omission for a modern aircraft when it is present in so many others.
-
Thanks for the response and for the clarification!! I was thinking the mod randomly spawned clients of the selected mods for use. I guess I was over thinking things.
-
Tape/Post-it over the sensor. Problem solved (for now...it would be nice to fix it on the DCS end) Just be sure to shut down the headset manually when you are done with it.
-
So, I can confirm this as well. FOR ME, TRIM RIGHT activates the animation of the START/STOP/REWIND button (but doesn't actually seem to perform the function) Similarly, TRIM DOWN activates the animation of the CLOCK TIME Adjustment switch, but unlike a mouse click, it doesn't stay in that position, just toggles. I do not see TRIM adjustments when I mouse click the knob/switch though. (WINWING ORION F-18 HOTAS)
-
Indeed. A temporary workaround is all.
-
Interesting!!! I have used the ALT-TAB trick in the past for FPS decreases, but it never seemed to work for me with the F10 issue. Not sure how long I held it for, but usually, I would wait until I observed the FPS coming back and then switch back to DCS. FOR ME, the F10 issue totally disappeared when MSAA was turned off (though that is not everyone's experience).
-
I have been looking for the expansion script referred to in the documentation (FIGHTERS MOD) to configure the addon mods I have downloaded. I cannot seem to find the .lua file to download or edit. Or do I need to create it? Sorry if I am being dense. I looked through the .zip file and in the Trigger's section and couldn't find it. Thanks for pointing me in the right direction. Hehe: I found it in the zip file for the OTHER TTI maps. It was not present in the Las Vegas TTI .zip! The .lua I found in the Persian Gulf and Marianas TTI zip files didn't seem to have the UH60L in it. Will it work if I just add the lines for the UH60L and then plug that expansion into the Las Vegas TTI?
-
Since turning off MSAA, I haven't had this issue on my QUEST 2. Generally, though, I didn't get the black screen in the headset, just stuttering and single digit frame rate.
-
Same on Oculus Quest 2 + Open XR +MT Semi-randomly after spending time on F10 map, return to cockpit results in drastically decreased Frame rate . Sometimes freezing and crashing, but usually just unplayable (single digit) frames. Compared to other instances where frame rate may be recoverable by ALT-TABBING or switching views, this seems un-recoverable. EDIT: Setting MSAA to OFF seems to have helped with this issue. I was pretty sure I saw this issue even with it OFF, and I had reset it recently. I turned it off again and in some limited testing, prolonged F10 excursions didn't seem to cause the issue. I only tested in Single Player and the problem seemed more prevalent in Multiplayer scenarios, so will keep testing.
-
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????
-
In-Game Scratchpad Mod Available - Works Great In VR!
Recluse replied to Fubarbrickdust's topic in Virtual Reality
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
