Draken35

@Str][ker @Recluse Since I hear you two volunteering for testing... This involves a replacement of the hooks script and the 2 extensions. The procedure (that I tested in SP) is: In a clear screen type @{type} were "type" is the type of airplane (list bellow), it is case sensitive. Hit the "Load Wypts" button Clear the screen and work normally @{RESET} in a clear screen restores normal functionality. Types list: RESET AV8BNA F-15ESE A-10C_2 A-10C FA-18C_hornet M-2000C Mirage-F1EE F-16C_50 AH-64D_BLK_II OH58D UH-60L SH60B MH-60R CH-47Fbl1 SA342 * Working is a clear is probably not necessary as long as @{type} is the top most command. Obviously, any coordinates already capture in the screen will not change if you change the plane. Have fun EDIT: Files removed. Will repost when Hornet issue reported below is fixed

Maybe. I'll think about it

And you guys are absolutely right... 12 drops from active pause, all short. Fairly easy to reproduce test viper ccip.miz

The screenshot doesn't seem to reflect that but that is just a handful of drops, but it thy are always (or just favor) falling short, then that's a bug. I'll setup a test of my own... Been a while since I dropped dumbs from a Viper

What was the release altitude (yes, I know it is in the track, but I cannot download it right now) and what is the CEP of the mk.82 ? (JDAM is 5m, I have not been able to find any info for the mk.80 series) A more consistent test would be to dive, active pause and drop 1 bomb with unlimited ammo, once reloaded, drop again (this eliminates the station as a variable) and keep alt, speed and dive angle constant... I definitely do not expect the bomb to hit exactly on the piper every single time... If ccrp is doing that, then ccrp is buggy

@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