Recluse

Seems to work perfectly for me. Maybe you can make a video or something? Seems like you are doing everything right. When I hit the +L/L button, the coordinates captured represent the position of the dot. I have been successfully dropping JDAMS since 2.9 using these coordinates, so it is definitely working.

Seems like the change in scripting in 2.9 that affected many of the persistent missions has hit the *Power missions as well. Fired up Vegas Power and it was fine for the first run, but when the Save was loaded for the next run, it reported nothing operational, BLUEFOR and OPFOR as well. EDIT: It looks like putting in the latest MOOSE.LUA into the mission has fixed it.

Yeah, I think the script was Dzsekeb's original with some updates by OBI for the Marianas flavor. I hope they see fit to fix it. Pretty sure that there are more instances throughout the Foothold scripts managing that stuff. More challenging when we aren't collecting points for our successes!!

THANKS for the info...

Yeah, I realize that, but I am not skilled enough in scripting to know if it is affected. All I know is that after the update all of our Foothold missions ceased to work in the ways they had just before. If it is any diagnostic help, this (to the best of my limited ability to discern) is the kind of script that seems to be failing: I can see the UNIT.CATEGORY.AIRPLANE and following code that seems similar. function BattleCommander:startRewardPlayerContribution(defaultReward, rewards) self.playerRewardsOn = true self.rewards = rewards self.defaultReward = defaultReward local ev = {} ev.context = self ev.rewards = rewards ev.default = defaultReward function ev:onEvent(event) local unit = event.initiator if unit and unit:getCategory() == Object.Category.UNIT and (unit:getDesc().category == Unit.Category.AIRPLANE or unit:getDesc().category == Unit.Category.HELICOPTER)then local side = unit:getCoalition() local groupid = unit:getGroup():getID() local pname = unit:getPlayerName() if pname then if (event.id==6) then --pilot ejected if self.context.playerContributions[side][pname] ~= nil and self.context.playerContributions[side][pname]>0 then local tenp = math.floor(self.context.playerContributions[side][pname]*0.25) self.context:addFunds(side, tenp) trigger.action.outTextForCoalition(side, '['..pname..'] ejected. +'..tenp..' credits (25% of earnings). Kill statistics lost.', 5) self.context:addStat(pname, 'Points', tenp) self.context.playerContributions[side][pname] = 0 end end if (event.id==15) then -- spawned self.context.playerContributions[side][pname] = 0 self.context:resetTempStats(pname) end if (event.id==28) then --killed unit if event.target.getCoalition and side ~= event.target:getCoalition() then if self.context.playerContributions[side][pname] ~= nil then local earning,message,stat = self.context:objectToRewardPoints2(event.target) if earning and message then trigger.action.outTextForGroup(groupid,'['..pname..'] '..message, 5) self.context.playerContributions[side][pname] = self.context.playerContributions[side][pname] + earning end if stat then self.context:addTempStat(pname,stat,1) end end end end if (event.id==4) then --landed if self.context.playerContributions[side][pname] and self.context.playerContributions[side][pname] > 0 then for i,v in ipairs(self.context:getZones()) do if side==v.side and Utils.isInZone(unit, v.zone) then trigger.action.outTextForGroup(groupid, '['..pname..'] landed at '..v.zone..'.\nWait 10 seconds to claim credits...', 5) local claimfunc = function(context, zone, player, unitname) local un = Unit.getByName(unitname) if un and Utils.isInZone(un,zone.zone) and Utils.isLanded(un, true) and un:getPlayerName()==player then if un:getLife() > 0 then context:addFunds(zone.side, context.playerContributions[zone.side][player]) trigger.action.outTextForCoalition(zone.side, '['..player..'] redeemed '..context.playerContributions[zone.side][player]..' credits', 5) context:printTempStats(zone.side,player) context:addTempStat(player, 'Points', context.playerContributions[zone.side][player]) context:commitTempStats(player) context.playerContributions[zone.side][player] = 0 context:saveToDisk() -- save persistance data to enable ending mission after cashing money end end end mist.scheduleFunction(claimfunc, {self.context, v, pname, unit:getName() }, timer.getTime()+10) break end end end end end end end Thanks for confirming!

I think we ran into this. We play the FOOTHOLD dynamic persistent missions and all of a sudden things stopped working (granting of credits for kills) and we did get some Script error messages that seemed related to this. I noticed it tonight on Marianas Foothold, and then I fired up the Foothold Caucasus 1.4.4 and the same thing happened (no credits granted nor message). I didn't fly that long enough to get a script error. I know a lot of people run various Foothold flavors on their servers. Have you noticed this happening?

Ok Just installed it. Are you recommending the setting as shown, or pointing it out as a potential issue not ALLOWING SYSMEM fallback from VRAM to SYSTEM Memory?

Interesting. I don't have that setting nullI have to say, however, that I haven't had this issue since turning off MSAA pre-2.9 Still do get occasional FPS drops and VRAM overflows but doesn't seem as correlated to F10 map as it once was.

Yes they do, but not the dedicated binds in the module controls for Radio1 VOIP and Radio 2 VOIP as in other modules useful if you want to have different commands per module based on other bindings. null

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