Recluse

Hollywood is not constrained by reality in any way, shape or form. LOL neither is DCS, but at least it TRIES.

True Lies is not a documentary

As posted above, this has not happened to me since turning BYPASS PROXIMITY SENSOR CHECK - ON in Oculus Debug Tool at the start of every session. I am using AIRLINK (with cable connection for power) 90 Hz and OPENXR Toolkit with MT executable.

I think that file in the CONFIG folder gets created automatically and contains the HOTKEY information (which is taken from the LUA file in the HOOKS Folder) I think the HOTKEY can be changed in either place, but I usually edit the LUA file in HOOKS.

Thanks, and Sorry

Reported Here already, but I wasn't sure if this got the attention of ED folks and whether it was a Ugra Media Map issue or an ED issue The Track I posted in this thread might have mods in it, so here is a vanilla one.. - Tried to request taxi, no answer on 250.85 or 122.2 - Took off, tried to request Inbound, no answer on 250.85 or 122.2 - As positive control, contacted Aleppo and got immediate response. AbualDuhur.trk

I would suggest for such ELINT missions using SCRATCHPAD/SCRATCHPAD PLUS to take down coordinates (or pull them directly off the F10 Map, though you may wish to have it come from onboard sensors for Realismtm ) In that case, Scratchpad provides a handy way to enter the observed coordinates and it will actually persist even if DCS closes in the Scratchpad Text file.

Hi BIGNEWY, Try this one... At night so the HUD symbology can be clearly seen. - In this case: OPEN BETA, Regular exe (non-MT) non-VR - Typically I fly in VR with MT and OPEN XR but did this to be the most vanilla - Lock up target with AA Radar - Switch to AG MODE (AA Symbology persists) -LOCK up AG Target in FLIR. (AA Symbology persists) - Unlock AA Target in AA mode, Symbology gone in both AA and AG (as noted sometimes flying MP, the AA HUD symbology seems to persist in AG mode even in this case.) AA Symbology2.trk

I posted this here, and it seems to be a bug. Screenshot above and trk attached. (also attached in original post). Steps to reproduce: Go to AA mode and lock a target. Switch to AG mode and observe AA symbology still showing. In the TRK, I could get it to disappear when Undesignating, but many times in Multiplayer it seems to keep the last locked target even when no target is locked when returning to AA Mode. (No TRK for this behavior) AA Symbology.trk

I use the Oculus Tray Tool with a Profile for DCS/MT which turns ASW off on every start. I know it is off because I can see the frame rate is not locked to 50% of the Hz setting as it is with ASW. If MSAA is on, I will still get the F10 bug.

It clearly doesn't work for everyone, but for me, turning off MSAA in the options fixed the problem about 90%. Happens occasionally still but seems less correlated to F10/F1 switching and more random. QUEST 2 user here. I use OpenXR toolkit as well. Typically I connect via AIRLINK with the LINK cable connected for power, but I have also just used the LINK Cable. No apparent difference on the issue (before turning MSAA off. - I have had ASW set to NO for a long time, and I still saw the problem with MSAA on.

Thanks! Is anyone else seeing this?? And should I repost in the Bugs forum or is it sufficient to be here?

I had the same question. When I saw the thread title here, I posted my response. I am guessing it is an ED issue, but I don't know where the dividing line is.

I noticed this last night and I honestly don't recall whether it was always this way and I never noticed or something new, maybe with the last patch, or just a temporary glitch. See attached screenshot. Just wanted to see if anyone else noticed this before making a Bug Report: Will follow up with more evidence shortly if I can reproduce. - Going to AG Mode with or without Target Designation (I did verify just now that creating a Ground Designation did not remove the AA block) - HUD not only shows the distance to AG target, (if one exists) but also has symbology block for an Air target including Vc and Range - Last night, I couldn't get it to go away even when switching to AA Radar and making sure nothing was locked but today switching to AA radar and dropping the lock DID remove the symbology. - Didn't affect AG operation, just distracting. -Added a track file, but, honestly I just wanted someone to say: "Yeah this is how it is" or "Yeah this is a bug" at which point I would have posted the Track File in the BUGS forum. AA Symbology.trk

Can confirm this with F/A-18C and AV8BNA. On both UHF and VHF (250.45/122.20) ALSO noticed that the label for Abu Al Duhur on the radio menu reads Abu "Ad-Duhur" not Al-Duhur. This seems recent (last patch that fixed some comms referring to airfields on different maps) as I don't recall seeing this in the past. Al Duhur Comms and label.trk

Let me also give you a big Thank You for these missions. We've played through them all a few times in Multiplayer. Vegas Power seems to be the easiest and I also use that as a Single Player training mission, taking up different aircraft in the AA and AG roles to try out various things in a RELATIVELY low threat, but active environment.

Since I got the update to V55, I noticed that the Oculus Debug Tool now has an option to Bypass the Proximity Sensor Check . It does not "stick" and has to be enabled every time you bring up the Debug tool. I took the tape off my Prox Sensor and used this option and it seems to work (unless something else got fixed by the update). No need to go to Developer Mode null

Depending on your controller, you might be able to map the Key combo to a button. I know you can do it directly with Thrustmaster software (TARGET/FOXY). I have a WinWing and while the SIMAPPPRO doesn't allow this to be done directly, I have used Joystick Gremlin/vJoy to accomplish this. Lately, I have been using FoxVox voice activation software (similar to Voice Attack and similar) to do this along with other command which are useful in VR and save me from mapping additional HOTAS buttons.

All is good for me as well. In fact we tested in the Apache this morning and it worked fine for both of us. There must be a remnant of an old Scratchpad somewhere. I recall once when I was having trouble with ScratchPad extensions, I found that at some point I had inadvertently installed to the SCRIPTS folder on the Main DCS Installation rather than SAVED GAMES. Double check that to see if there are any scratchpad remnants there even though you cleaned up and re-installed in the correct location in SAVED GAMES. Also it would be very odd to be limited to the APACHE. Try another aircraft, but I am sure it will show the same.

And good news for Mullticrew!! We tested in the Apache and the F-15E and coordinate entry works from both the Front and Back Seats with the correct cockpit UFC/TSD and appears to be well synchronized between cockpits.

Referring to the latest fork by @Draken35 combining features of Scratchpad and ScratchPad PLUS posted earlier in this thread. - The original Scratchpad let you enter or pull coordinates from the map that you had to then manually enter in the jet - Scratchpad PLUS included a feature to automatically insert the pulled coordinates into certain aircraft NAV systems - The new fork combines and extends these capabilities - There are .lua scripts underlying the ScratchPad functionality

Just posting this for general information to Strike Eagle drivers. I was messing around with the Strike Eagle Steerpoint manipulation and was tearing my hair out (what little I have left) trying to figure out why it was failing to over-write Steerpoints. Finally realized that some of the points were TARGET POINTS. When the script automates button pushes and entries, it assumes "normal" steerpoints, but if a point is a TARGET POINT the selection will fail because there is no decimal point following it. So be careful if you are trying to overwrite a sequence that includes Target Points, or set them back to normal steerpoints first. Also note that currently, the script will only run correctly on the FRONT SEAT UFC, so the WSO can't enter points. (At least it doesn't use the WSO UFC, I did not check to see if invoking the script from the WSO cockpit still worked by manipulating the Front Seat UFC. YOU can run the WP LOAD from the WSO cockpit, but operations will take place on the Front Seat UFC. The Pilot will have to make sure the UFC is in MENU1 while the WSO loads the SteerPoints. The WSO will not see the actions on his/her own UFC, but it is evident on the TSD. NOTE: I tested this only in Single Player from the WSO seat. Did not test in Multicrew. Maybe someone can and report back?

Also note that the WSS and WDES parameters only (CURRENTLY) apply to the Harrier and Strike Eagle. In the Hornet, Viper and Mirage2000, you select your starting WP in the aircraft and the WP's will load starting from that point. P.S. I'm an old man too

Correct!! This is how you would do it for adding a single WP (the WDES parameter) But let's say you want to add 5 Waypoints starting at WP 4. You don't have to edit each one, just use the @<#> (WSS parameter) button to enter this line in the file and edit it to @<4> This will set the starting WP so that the 5 Waypoints you have entered will go in as 4,5,6,7,8 Note that when editing in the Scratchpad, the FOCUS may stay in the Scratchpad so you might not be able to get back to the cockpit from the Map using F1. You should either click outside the Scratchpad edit area or hit ESC to remove the focus. This has bitten me a few times

There is a readme file - AV-8B Waypoint Sequence Start can be used to specify a startup waypoint and route. Default is 1 Examples: Set WSS to point 3 : @<3> Waypoint Designation (WDes). If # is present then Scratchpad will attempt to load the steerpoint in next point in the sequence , otherwise it will use the value as the waypoint number. If that waypoint already exist, it will override it, if not it will attempt to create it. Important: AV-8B waypoint creation rules are followed. (WDes) can be used to override an existing waypoint (if it does not exist a new one will be created at the end of the sequence, its number might not match the WDes). Also, it can be use to create or modify target points (using DMS, so accuracy will suffer) Examples: @|3|N 41°39'50"|E 041°50'45"|2462| -> will load in the point No.3 (if exists, if not a WP will be created and the end of the sequence) @|T3|N 41°39'50"|E 041°50'45"|2462| -> create or modify Target point 3 As I found out, you cannot specify a WP that cannot be created, e.g. If your Harrier has 3 WP's and you specify WP5, it won't do it because you can't skip WP's. I believe in that case it would create WP 4 as in the bolded text above.