Draken35

Well it looked closer in VR...That's a M4/203 soldier. 1.1.15 smoking after been hit. Latest DCS versions.

Seconded

Gazelle added. Only the extension is needed but, extension and full package attached for convenience From the readme dcs-scratchpad (Draken35)-0.7.0.240922a.zip 02-QWERTY_KB and Load Coordinates.lua

Yes it is... I messaged @SPAS79 back in June about it, but he hasn't logged back it into the forum. So, let's make it official... I included SPAS79's UH-60 code, For instructions go to his github posted above, somewhere...

CH-47F VERY basic functionality added. Important to notice that the waypoint will load in the reverse order in to the CDU (wp 1 will be loaded last, but it will be wp 1) Full replacement. In MP, it should follow the seat you are on... But untested. dcs-scratchpad (Draken35)-0.7.0.240917a.zip

Not much to go on, but chances are that you put something in the wrong place... I would suggest deleting the Scratchpad folder from your scripts folder (<your path>\Saved games\DCS\Scripts\Scratchpad) and the scratchpad-hook.lua file in <your path>\Saved games\DCS\Scripts\Hooks. After that, download from here: The zip files contains the proper folder structure. Test it, and if works, gets the updated extension from here: It goes here: <your path>\Saved games\DCS\Scripts\Scratchpad\Extensions Watch @Maddaawg 's video above...

LOL... No worries I do that all of the time... I see want you mean, basically create a mission list with one mission, and load the others via SLMOD ... I just manage to de-sanitize SLMOD (missions requirements) ... I'll test this method since it is more flexible than the menu in the missions, after the first mission load. I really appreciate the help, thank you!

@Maverick87Shaka not an empty mission list, just preventing starting any mission (last one played) . I was actually looking at a dummy mission with either a menu system or SLMOD but couldn't figure out how to always start that mission. Now, I don't see a server.cfg in my saved games / config or anywhere else. What would the location and syntax be ? And thank you!

I might be missing something obvious here, but I run a dedicated, on demand server and I will like the server to start without loading any mission, so I can choose which one to run from the Web GUI. Is this possible?

The reticle for the Eotech looks very washed out, almost white in all lighting conditions in VR. This is with an Quest 3. Most likely is some in my side. All other colors looks fine to me. Any ideas of what could the issue be?

Can it? Yes... Will it? Maybe, perhaps, eventually ... The CH-47 is too new and I expect internal changes that will break the coordinates input ... It happened with the Mudhen several times and once, so far, with the Kiowa, so I will wait until it is more stable and I actually fly it to do it.

Fly in hilly terrain and you will understand ...

No takers?

No.

Part of the issue, when the script outruns the jet, is that you might have wrong coordinates / altitude due to "missing" key strokes ... I saw this when I tested earlier in 2D with the Hornet and that was why I slowed it down to actually see the keypresses

100 is A LOT.... In my PC anyway... The script has no way to detect if it is in VR or not, so it cannot adjust itself if that is what you mean.

That depends on the specs of the PC running it... But 100 gave me like 10-15 seconds between presses...

@Maddaawg , @Recluse is correct about the high speed issue... I was able to reproduce it in 2D, changed TICKS to 100, to slow it down to a crawl so I could follow the key presses and it is entering the data correctly... I must assume that the Hornet UFC key process got slowed down in a recent patch and cannot longer keep up with the default settings of the script

I've been working on an ELINT script that uses getDetectedTargets() by the RWR of the unit and found an issue when the emissions of SAM's SR/TR radars are turned off and on with enableEmissions(). If the SR/TR starts the mission with emissions enabled, they are detected with out issues by getDetectedTargets() (with or without the RWR option), and stop been detectded, as expected, when enableEmissions(false) is issued. Problem is, that after that point it will never be detected again after enabling their emission again. Attached is a simple mission to illustrate this behavior. It has an SA-3 simplified site (1 SR, 1 TR and 1 LN) and an E-3 AWACS doing the detection. The radars start ON, and they are cycled ON and OFF every 10 seconds... This is the script driving it: RWR Bug Report.miz

Had the same behavior today, in MP and latest version to date. Only difference was that it happen with Moose Mantis and an SA-6 that I had selected going offline before I attacked with CBU-105's (tacviews shows all the units in the SA-6 group way after this happened, so, they were not destroyed). Cursor disappeared from the HAD and reappeared after TMS down. After that, the TGP moved away from any SPI I set about 20 seconds after setting it... Couldn't figure out where it was going... Unfortunately, track is not usable.

little bump so we don't forget

null

I'm running VD with VDXR as the OpenXR runtime... No issues with the controllers.

Foghorn misses the period when typing the 147.4 frequency.

Good catch! The role name changed from "pilot" to "Pilot" in the last patch... That affected the Apache and Strike Eagle as well. Attached is the fixed extension . 02-QWERTY_KB and Load Coordinates.lua