Recluse

Well, I just tried it and I can confirm that the continuous transmit of the AI Radio Menu DOES NOT AFFECT TRANSMIT ON VOIP, as indicated by the Transmit indicator on the VOIP panel. I agree with the SHORT and LONG press. It is implemented in the special options for the Mirage2000 and I have used it successfully with SRS

Right I understood, but you were saying that the continuous transmit when you call the radio menu might mess up the VOICE CHAT, and I was saying it WOULDN'T because the keys are different so you are not keying the Voice Chat with the Radio Menu button But for what it is worth, I can confirm your observation about the continuous T when calling up the Radio menu. The Hornet works the same way as you describe the F16C, where the transmit symbology only happens when selecting a menu item, so I do think this might be a bug.

The VOIP PTT commands are (and must be) different binds from the Radio PTT so it really wouldn't matter.

Same issue here. Tried it last night. Tried the keyboard commands and also set my WinWing throttle handles full back and also set them to issue a SHIFT-END and ALT-END when pulled full back, but I could not get the training to proceed. Throttles full back worked (IIRC even before the additional programming) for the Baltic Dragon Cold Start training. Will try it again. I might have some curve/saturation changes on my throttles which might explain it based on the trigger setting)

Right, I meant you cannot save them with a particular NAME, from within the game, but, yes if you initially create the BLANK files as MISSION 1, MISSION 2 etc.. then those will be autosaved. when changed.

I will add another observation, though it may be a different issue altogether: (VR, Quest2, AirLink RTX3070 Core i7 10700K 32 GB RAM) Recently (after 2.9, but I cannot say for sure it didn't happen previously, but now it is more repeatable) everything is fine, flying around with 40-50 fps (Multiplayer, reasonably complex mission) and then after about 70-90 min of flying, my frames will drop to 10-12 in cockpit view and no amount of ALT TAB seems to fix it. My VRAM is sitting at about 50% usage. When I go into the F10 map, I see FPS go back up to ~39-40 but switching back to F1, they are back to 10-12. Only way to fix seems to be complete exit from DCS and restart (usually I restart the Quest 2 as well for good measure). (Seems independent of aircraft flown)

This has happened to me when accidentally moving and getting the "HEY WHAT ARE YOU DOING?". When that happens I usually repeat the rearming and stay put until it is done. USUALLY fixes it.

Glad you got it sorted! Was about to post that it works fine for me in 2.9, but I am having some VR graphical issues with blurriness of the cockpit console. Honestly having that issue with all the aircraft, but got it most tweaked for them, Still tweaking for the UH-60L. @Kinkkujuustovoileipä replied to this on the Discord, so I will be tweaking my settings.

null Yep, that could work. You could put several files in the Scratchpad folder and toggle through them with the arrows: I don't know that you can SAVE AS from within ScratchPad, so, again, some User interaction needed to save outside of DCS null

Right, it would require a lot of USER intervention to enable/disable based on the MISSION/MAP. Easier (IMHO) to just replot your WP's.

Yep.. 8 GB.. slip of the keyboard... EDIT: Actually, the reason for that "slip" was Open XR Toolkit shows me at 100% VRAM usage at 6 GB.... so no wonder I had that in my head. Er...any idea why it is not seeing all 8? Some setting I am missing, or is OXRTK capped at 6 GB for reporting? I wondered why sometimes I do see 104% usage.. Edit Apparently 2 GB of VRAM are reserved for the SYSTEM and not available to applications, so for all intents and purposes I only have 6 GB for DCS

Potentially, couldn't you edit out the @[#] at the beginning of a line to exclude that line from entry and then add it back? Since the coordinates are persistent in the txt file, they will be there assuming no CLEAR was done. Seems to be a bit of a pain to me but maybe? I know this works with ScratchPad PLUS by editing out the * at the beginning of the line, but don't know if it applies to ScratchPad.

I use OpenXR Toolkit overlay which also gives me a VRAM usage value, so I use that. Oddly enough, sometimes I am pushing 100% (only 6 GB on my 3070 ) but frames remain steady and performance is smooth. Alternatively, sometimes VRAM usage looks OK but the frames plummet, which can also (sometimes) be remedied with an ALT-TAB.

Did you make sure the ROUTE or POINTS were showing either in NAV or TGT mode of the TSD? Click on the ROUTE OSB and add the points to the route if necessary. Might just be a display mis-selection on the TSD. Here is a little video I made showing it operating correctly. Please excuse my fumbling around. It has been awhile since I operated the AH-64D TSD!! I should have just increased the TSD scale to show all the points instead of PANNING.. Oh well.. been awhile! Important thing is that SCRATCHPAD correctly imported the Waypoints.

I have found that when I get VRAM full and frame rates decrease I CAN sometimes regain it after an ALT TAB, but not always. Have to try it Pre-Emptively as described. Thanks for the tip.

As the title says. Loaded two LMAVs, fired them off and the LMAV page stayed up. Only way I could get rid of it was to toggle out of AG mode and then back. I searched through the forums and couldn't find anything on this, though, oddly enough when I went to save the .trk, I found an old track of mine from 2021 with the name "LMAV_PAGE_STAYS_UP" so maybe I reported it back then? Anyway, new track below. Bug or as intended? LMavPage.trk

Works in the Mirage 2000, (and I believe in the F-15E, though I haven't tested it there myself) so must be something peculiar to the Harrier... not Razbam.. Cut them some slack

BUMP! Still present in the big 2.9 Open Beta update

I just tried it and entered 10 Target points from ScratchPad. They all went in fine. (I noted each one as T1, T2, T3,T4 etc..)

OOPS.. Apologies from my end too.. Not enough coffee yet

I wasn't thread Hijacking, I was ANSWERING YOUR QUESTION (WHAT IS THE WAY)... If you don't want answers, then don't post questions.

The WAY is another app for entering waypoints directly. It does NOT work in VR though there are some recent updates that at least allow mapping of HotKeys to do some of the work in VR, but the Interface is not VR visible. IMHO ScratchPad is the far better solution for VR users. THE WAY: https://github.com/aronCiucu/DCSTheWay

Ahh I forgot that. This is the more likely scenario!

You might be getting bitten by the timing bug that happens when framerate is too fast. IF you are using the Modded Scratchpad by Draken: Edit the line: local TICKS = 1 -- To slow down processing, increase this number in the file "02-QWERTY_KB and Load Coordinates.lua" in the "C:\Users\<username>\Saved Games\DCS[OpenBeta]\Scripts\Scratchpad\Extensions" folder Increase the 1 to something higher. Depending on your framerate, it could vary. I would start with 3 and work your way down/up from there.

Thanks, I will add something to the mix which might be tied into the broken release logic: 2 x 3 Mk-82 QTY 2 Mult 2 CCIP Expected one salvo of 2 Mk.82 (one from each pylon) Got: 2 off of each Pylon for a total of 4. According to Chuck's Guide and the TACMAN, the QTY setting should be the TOTAL number of bombs dropped QTYMult.trk