Recluse

@Muchocracker Should this be 20m burst height?

Should I be seeing that Overlay in VR? I don't see it. But I am using OXRTK and I see THAT overlay. Never mind... I do see the overlay in 2D, so I guess that is better to not clutter up my VR view any more.

Hey @Draken35: Does your current Full replacement include the UH-60L support that someone else did? I think I did a compare on both .lua files and hacked it into one of your recent versions that fixed the Apache bug and was the last fix for the Strike Eagle..

If this is the same thing, I reported this a year ago. Never saw it get fixed and it still occurs for me. In the reported case, it is the HUD that shows target information for locked (TWS) air targets when in AG mode. Don't know if the posted track still works with the latest build. If needed I can generate another one.

Not sure its a Tucano thing. Seems to happen to us in Multiplayer almost all the time with AWACS comms in just about all aircraft. Sometimes it's fine, sometimes static. Haven't noticed it in SP.

ASW is OFF in OTT.... In the Menus, I get 72 FPS (and got 90 when set to 90 Hz). In the mission I used for Testing... Various aircraft taking of from Melez on the Sinai map, I get about 50-60 FPS at the default, about 25-35 at Preset F and about 35-45 with Preset E. Everything else remains the same. Using OTT and OXRTK, so there is room for tweaking, but for the purposes of the test the DLSS preset was the only variable. ASW should not be kicking in at all, but when it was on, indeed I get about 50% of the set Hz (at max).

Thanks for this. Just going to give my experience for what it is worth. I tried forcing Profile E and F. Couldn't really tell much difference graphically, but I did seem to see a decrease in Frame Rate with both E and F. For now, I'm sticking with the default as the best compromise. I got rid of most of my ghosting (and got a lot more stability) by moving from 90 Hz to 72 Hz (Quest 2, RTX 3070) so thankfully that was no longer an issue. Of course there are endless things to tweak and it is nice to have this additional option. Using DLSS Quality in DCS, currently so maybe moving down to BALANCED and changing DLSS profiles is something I am going to try.

Have to think about it, but off the top of my head, i think there is always an ownedBy or similar flag that has a value based on the Ownership? (RED, BLUE, NEUTRAL) some combination of the ownedby flag value and a list of the "random" selections might work. Could be a lot of work to account for every possiblity... but maybe there is a way to do the randomization more elegantly only when only those bases with an ownedBy with an instantaneous certain value are considered. One example from the manual picked at ....errrrr....RANDOM

@cfrag Thanks.. I did quote the manual in my post It was clear to me as is, but I was confused when @DD_Friar mentioned SSBClient Zones, and then I read further in the manual and saw they were available for use. I was keying on the part that said SSBClient did basic slot blocking AUTOMATICALLY.

@cfrag Based on @DD_Friar's comment above on having an SSBClient zone. can you comment on/confirm the use of SSBClient for general slot blocking (without using OPEN or CLOSE flags and the like). Is it sufficient to just have it loaded and running without any zones created (unless other than default config options are needed)? I have been following the advice to load slotty for SP slot blocking and have SSB running whenever I host, and advise other hosts to run it as well when a DML slot blocking mission is in use. Maybe in this case SSBClient isn't even necessary, but doesn't hurt to run?

Thanks for this! Along with the other diagrams in the download. LOL I didn't realize the AOA indexers FAST/SLOW indications were opposite for Russian and Western aircraft.

LOL... I just tried it, but jumped in for a quick 2D instead of VR. I crashed the UH-60L short of the troop pickup!! It is quite possible I abandoned the mission when they wouldn't get picked up, but I have a recollection of flying it in the UH-60L. The mission will be much better with a DML re-write!! Troops In Contact is flown in a Player APACHE and the AI UH-60A does the troop transport. Troops in Contact_UH60L was meant to be a Mulitplayer mission where humans flew the APACHE and the UH-60L for troop transport. PRETTY sure I tested the UH-60L troop transport in Single Player, but maybe it never worked and I dropped it. Also happy to stand corrected on this! Both versions probably need some polishing... EDIT: JUST TRIED IT... I AM WRONG, YOU ARE RIGHT.. UH-60L DOESN'T SEEM TO BE RECOGNIZED. I landed really close and no Embarkation and no Menu Item for it either. Now that I look at the missions, I could not get the UH-60L to pick up the troops, so I created the little TEST pickup, which, ultimately failed. Rewriting now with DML to allow UH-60L to do the CASEVAC...

As you know I am also a big Proponent of DML, but I have gotten the standard DCS troop embarking/disembarking working with the UH-60L with no problem (other than the usual problems getting everything setup right!) (At least I think so! Have to go fly that mission and double check) OOPS, no.. see below

Thanks, guys! (BTW I confirmed the SU-33 got SuperCarrier Comms with one of the BLUE Super Carriers, so I figured it was a KUZ limitation not an FC3/2024 limitation)

..which should be FAQ's but I just cannot find the answers anywhere: - Which Kuznetsov is the SuperCarrier Kuznetsov. Thinking it is the 2017 one. -Neither Kuznetsov seems to give SuperCarrier COMMS. Granted I was trying with an SU-33 (as one would expect for the Kuz). Is this the current state of things? New Kuznetsov model came with the SuperCarrier package, but does not communicate like a SuperCarrier? Thanks... Sorry if I couldn't find this in my FORUM searches.

I have seen this quoted many times (LITENING not cleared for Carrier operations) but have never seen any OFFICIAL indication that this is a true limitation, while it is true that the Navy does use ATFLIR for Carrier Ops, it doesn't seem like a technical issue, just a procurement preference. And reading this, it seems like outfitting carrier based aircraft with LITENING would have been a possibility. https://apps.dtic.mil/sti/pdfs/ADA498288.pdf

I don't think this is confined to the M2000. Have experienced it in other aircraft (F/A-18, AV8B) as well. I think it is generalized MP bug these days

@cfrag (or other DML'ers) EDIT: Leaving this up in case it helps someone, but indeed, I got it all working with wiper!! Had some anxious moments before I realized that I was trying use delayTimer without loading delayFlags!!!! Got various messages about the deprecated wipe? flag for CloneZones, but it all worked. I had some issues with my Messenger settings (as I guessed) so maybe despawn? would have worked as well. Quick question: I am trying to debug some Messenger and delay timers that trigger when all the current units in a CloneZone are dead. Scenario is basically, a delay before the respawn, with concomitant messages: "All units destroyed, respawn in xxx seconds..." triggered by the delay time initiator flag from empty!, "Units respawned in xxx zone" triggered by the clone? flag sent by the delayTimer. Trying to debug it but I cannot find a good way to just destroy the units for testing. I think my problems stem from the naming scheme stuff. - tried the despawn? flag, but realized as stated that empty! won't fire in that case. - I tried using the IDENTICAL flag and just setting a radio option to EXPLODE all the UNITS (names from template). DCS crashed on me when I tried this!! - Thinking maybe Wiper would work for this with the wipeCategory for units... but I am too tired for more testing tonight. Don't know how wiper works with empty! and general cloneZone actions. Ideas? I guess I should just suck it up and destroy them myself, but I know I have some Messenger issues and it would be quicker to debug if I could just set off the destruction quickly. Thanks!

That is odd because targeting JDAMS is probably the #1 use I make of ScratchPad Waypoints! I am sure you know, but for JDAMS: - Make sure each station is set to TOO - With one station selected, do a WP DESG - Change Stations, Increment WP, WP DESG - Repeat as necessary - If you have 2 bombs per station, remember to change to TOO2 when you designate for the second bomb on that station and be careful when DROPPING them that the right TOO is selected. I ALWAYS screw this up so: - For 4 JDAM (2 per station) I usually program one bomb per station, then increment the WP but leave it as WP. When IN ZONE, I pickle off 2, then WP DESG, PICKLE, Increment WP, WP DESG, PICKLE and usually all 4 go where I want them. OF course if targeting vehicles, they may move on you between drops...but that's another story.

One thing, in order to load the script properly, you should shut down DCS completely, make the change and restart. I forgot to do this and saw no change. When I did, with TICS at 20, it was PAINFULLY SLOW, but didn't error out. (My 2D FPS was ~130). Ticks at 5 was passable, but I think I could have gone down to 3 without error. IN VR, I leave it at 1, but I have to admit I haven't tried it since the last update. EDIT: Just tried VR TICS=1 Worked fine. FPS = 58-61

I leave VR at the Default of 1 and it works. I seldom get more than 60-65 Fps MAX in the cockpit, and usually LESS.

LOL... I guess my suggestion of 3 was way too low

Ahh.. you might be running into the "frame rate is too high" issue. Try editing the local TICKS = 1 -- To slow down processing, increase this number In the 02-QWERTY_KB and Load Coordinates.lua to a higher number (try 3) In VR we almost never get a framerate too high, but it 2D it is very possible!

That version should work fine. Make sure, if you installed it over a previous version that you replaced all the files in the appropriate folders. The correct folder placement is encoded into the zip file.

Are you using the latest version? I do this exact thing, starting with WP10 and it works every time. The ORIGINAL version and maybe some versions after automatically skipped the first WP assuming it was being used for BULLSEYE. There has been a lot of editing done.. but if you grab this one, upthread, it should work for you. ( YOu might want to grab the updated 02-QWERTY KEYBOARD and LOAD COORDINATEs.lua extension a few posts up as well.