Draken35

@greyeagle787 Not much different than mine \ I wonder why yours keep saying "creating" the 0000.txt file after several tries. Not sure if it has anything to do, but can you verify that you the file was actually created? EDIT: Actually, see that after creating it, it doesn't find it (nothing after loading pages). If it is not there, try to create it manually outside of DCS

That line is omitted when the script does not support the selected plane. The plane type on the API used by the script is populated AFTER the plane spawns, when you are in that screen, the plane does not exists.

My pleasure but I've only contributed a little bit to it. Plenty of others had doe a lot for it too. TBH not sure what it is going on there... Check your dcs log and scratchpad log just after loading to see if there are any clues there.

The take notes and capture coordinates features of Scratchpad work in all modules but it can only load the coordinates in a selected few. The JF-17 is not one of those. Since this module does have a native way to load waypoints from the F10 map, I'm not sure that I will add the functionality.

Make sure that the hook script is this one: The hide is there:

That (should) be se on my fork if you are using it, so, perhaps you missed the script in the hook folder?

Just read the Intel Briefing... Awesome! Thank you for this demo and hope the situation resolves in the near future so we can the full campaign! Will be an instant buy for me.

While there might be something to this, I think it is headset related. I have a Sim Fab chair and a Quest 2 and a 3. The center of mass of the Q2 is farther away from the face than the Q3, causing it to feel heavier but, the IHADSS (and Viper/Hornet HMDs) are centered in my LOS in the Q2 but not in the Q3.

Somebody had to do it! Overall I'm happy with the map. Looks really good in VR and performance over Bagdad is very decent. This map has a lot of potential. Good job !

Here is the updated extension with the CH-47 fix. 02-QWERTY_KB and Load Coordinates.lua

The codes for the CDU buttons in the CH-47 changed in the last update. I got the new codes in and provided that there aren't any other changes, I should post the updated extension later today (after I have a chance of testing it).

Copy that. I’ll check it when I get a chance

I've never seen them before... First time today... Turns out that the AI decide to launch a plane from cat 3 and its jest blast barrier was up... I was so distracted with the flares that I did not see that until it was too late...No waveoff signal for me

I haven't flown it yet, but I've opened a couple of old mission and with remastered enabled and disabled, and all seems normal, except for the liveries (which don't matter much to me any way - I'm sure the community will come with new ones and with a way to covert the old ones)

Correct. What I was not expecting was that the remastered would override the legacy, which is cool in some aspects but not in others. I was expecting a situation like the Ka-50 1, 2 & 3 or the A-10C & II... Granted, there is no systems changes in the remastered.

Just disable the remastered in the modules manager and the old skins will be available. I just tested it.

even custom skins are not showing.

Are the old custom liveries compatible with the remastered version? I don't see any of them .

Do you mean like buying a second license of the module during a sale?

I use these https://a.co/d/dEZy9wy

"Requested by player" gets my vote. It shouldn't be too hard to add an option to the Ground Crew menu to do this.

UH-60 Support added thanks to @SPAS79 (If you are up to date, only the extension is needed) dcs-scratchpad (Draken35)-0.7.0.241110a.zip 02-QWERTY_KB and Load Coordinates.lua

@Captain Orso increasing TICKS will only slow it down. All the timing (TICKS and delays) is based on frame counts, so the more FPS you have the faster the input (because of less wait in between "keystrokes"). @Invictus 1-1 I noticed that too but the current code, does not differentiate between lat and long and therefore cannot have different delays. I suspect something changed in the Hornet internally. I'm currently running TICKS = 1 and delay = 40 for the Hornet (I'm in VR at ~72fps) and it is still faster than I can do... Usually, after I start the load I go to the F10 map and study the route or target area to pass the time. Keep in mind that the Hornet code in scratchpad has not been touched almost from release... I might separate the code for the lat and long in the future, but other than providing a extra place to tweak, it will give no guaranties that it will actually fix anything, and, who knows, the Hornet might change again in the next patch

Another bump

Still happening...