Recluse

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.

The current ScratchPad v0.7 that Draken posted combines the utility of the Scratchpad + Keyboard with the Scratchpad PLUS ability to enter coordinates into various aircraft. The README explains it and you can look for YOUTUBE videos for the general process in pulling COORDS off the F10 Map. The current iteration combining the two looks slightly different, but the concept and basic mechanics are the same In the current iteration, insertion into the JET is via the LOAD WAYPOINTS button: null Ideally the COORDS are pulled off the MAP, but, with the Keyboard, you can enter them as well Note that COORDS are formatted based on the current aircraft, as coordinate systems may differ. For the F/A-18, you should go to HSI-->DATA and box PRECISE before loading for WP's in the DD.MM.mmmm format If you are programming PP JDAM's, note the coordinates in the Hornet are DD.MM.SS.ss which are also handily provided though cannot be instered automatically.

Glad it worked out for you!! I fly mostly in VR and don't have the issue as frame rates and thus timing are much lower, but I occasionally have still seen the glitch in the initial Waypoint. LOL, my Callsign/Handle was self-bestowed and came from my early days of discovering Flight Sims where I would spend my entire weekend in front of the computer and never venture out of the house. Era of MPS original Gunship circa 1987. Maybe even earlier than that.

You can try increasing the TICKS parameter COULD be a timing issue. I have seen something similar on occasion The "fix" for me, if you can call it that, was to delete all but the first Waypoint and re-insert it in the WP1 position. Second time it seemed to work.

OK that does sound like some Windows 11 strangeness. As far as I can recall, the folder was created automatically, but I have been using ScratchPad in it's many iterations for so long that I cannot be 100% sure that I didn't create it at some point. Important thing is that it is working now!!

Better late than never!! Welcome to the party! It is a great tool ESPECIALLY in VR.. @TheRustyTigger I can confirm it still works and is persistent in the location indicated by @AdrianL (Windows 10, though, but I think you just had the wrong location null

Based on the terrain and the orbit, I have found that occasionally the Predator AFAC will drop the laser designation based on LOS, but usually it is high enough that this is not an issue. If it is consistently dropping right after firing vs. a coincidental loss of LOS then something else is going on. I haven't experienced this, though.

Well, when I started making the Video, I got errors, and, as posted above, I realized that I was re-using coordinates I had captured from another aircraft (MIRAGE) and the non-Precise coordinates seemed to transfer correctly into the Hornet without changing timing. I will still do a video one of these days Still having issues getting ANYTHING to work in the M2000, though. Odd..

OK, I just tried it again, and you DEFINITELY will have to edit the TICKS parameter to slow things down. (Or fly in VR) It originally worked for me because I used the coordinates I generated in the Mirage 2000 which were NOT precise, and they entered into the HORNET correctly with no errors even in 2D. When I generated coordinates starting from the HORNET, I did get the PRECISE coordinates and it ERRORED out when loading. I had exactly the same issue with SP Plus, actually, but @Draken35 made some edits to the lua to add delays. EDIT: Our posts crossed. Glad you got it working!!!!!

I will make a short video. MEANWHILE, you should know that there are TIMING issues that come into play sometimes with very fast framerates, that error condition occurs. Usually I fly in VR, and it isn't an issue, but in 2D I would often get the errors. Oddly enough, I tested in 2D, and everything worked fine. You can try adding a delay by editing the first line of the 02-QWERTY_KB and Load Coordinates.lua file int he Scratchpad\Extensions folder Will upload video shortly

I tried it in the Hornet using exactly the same process as I used with SP Plus. Worked for me just fine. I didn't use the WSS or WDES parameters, just set the HSI to my desired start WP and let her rip since:

Thanks for the info!! I was going by this image in the manual which seemed to show a SPIN parameter on the CBU-97 Mainly a Hornet/Harrier driver so the CBU-97 is a shiny new toy with much greater capability than the Mk.20 or CBU-99. The MIRAGE 2000 Belouga's are similarly better than the Rockeye/CBU-99 but a bit more difficult to deliver accurately, though ACCURATE and CLUSTER BOMB should not necessarily need to be uttered together. Have had a little experience with the A-10C CBU-97/103/105 but have barely flown the Warthog.

A good trick I learned in one of the videos is to cycle through the available TIME fuzing choices until it disappears, then you can use burst height only. Or so it seems. Worked well for me when I tried it. Note: using CBU-97 I never did see the SPIN option.

A few recent videos with good information on Markpoints!

Just a quick sanity check.. (LOL...that's dangerous where I am concerned...but I digress....) When turning on a TACAN and selecting TACAN steering in the HSI, I still get the pointer (Heading Command Bug) in the HUD pointing to the selected Steerpoint NOT the TACAN. Is this CORRECT AS IS? OR did I forget some setting. I get all the TACAN steering information in the HUD DATA block and the TACAN location and either CDI or PLAN CRS line in the HSI, only the HUD indicator is pointing elsewhere. Thanks.. EDIT: OOPS!!! RTFM!! (this is in the ADI section, but I assume it applies to the HUD as well) P age 217

Yes, so a sequence can have 15 Waypoints, but the database of Waypoints and Markpoints can be scrolled through continuously. As in the video below, I scroll through 60 WP's (I guess 59 +0) and 10 Markpoints. There is only a single SEQUENCE (with 15 WP's) but I can still scroll through the entire database when the Sequence is not SELECTED, so this method of creating multiple small sequences and selecting them should definitely help.

You might be right that it is a DCS'ism.. It just struck me as odd that most of the other aircraft allow you to directly input the WP of choice and I got to wondering why the Hornet (that we have) does not. I have to say that I have seen sequences with many more than 9 Waypoints. Specifically, in the FOOTHOLD Dynamic mission we fly, there are at least 40 WP's in the default sequence. but I tend to create TARGET WAYPOINTS by over-writing a range of WP's that I am not using for the particular part of the map I am on, but then I might need to Divert to another WP earlier or later in the sequence, or toggle back to WP 0 to return to HOME PLATE (if there is no TACAN ) and that is a lot of TOGGLING. Creating a new sequence with a subset of WP's seems like it would work.