ianick

looks like it s working ty m8

-- load the DCS ExportScript for DAC and Ikarus dofile(lfs.writedir()..[[Scripts\DCS-ExportScript\ExportScript.lua]]) -- load the DCS ExportScript for DAC and Ikarus dofile(lfs.writedir()..[[Scripts\DCS-ExportScript\ExportScript.lua]]) pcall(function() local dcsSr=require('lfs');dofile(dcsSr.writedir()..[[Mods\Services\DCS-SRS\Scripts\DCS-SimpleRadioStandalone.lua]]); end,nil) this export.lua file is causing the <profanity> when i delete it everything back to normal but streamdeck & srs does not workin anymore please advise

repair and mods removing done but no change I ve also tested affinity core thing (good advices m8) , no success but after a lot a tests it appeared it is the off/on RWR switch when it s starting and going from "bit/sys pass" to "active" It s tricky because in the video above i thought in first intention it was when i switched the APU on, in fact it was when the RWR finished starting it s mad thing:/ any idea, anyone?

ok i ve done few tests, it s happening in SP as well : when the mission starts with warn engine it s bugged, and when i decrease the power throttle the GPU is back to work normally so i stopped completly (GPU at 98-100%) and started the APU again, when the power of the APU rise enough to enlight the screen, the GPU activity fell to 60-50%

not in SP only on certain servers on MP For example it does not happen to me on Tempest's server but on other few servers

I have done a cleaning and repair but no change (even a windows reinstallation)

it s a multiplayer mission As far as i know i am the only one to experience that issue how a script or action can decrease the gpu usage o0

Operation-SandBlast_20231102-20231112-101040.trk

Hi Title says it all and in the link for video attached you will see on the upper right that GPU activity is just linked to APU start It is nice that the GPU is triggered by the APU switch of the AH64 however not the main purpose of it, i suppose

any ED help? (...)

It looks like it appears only on AH64D's start up as far as i tested with F18 and had no such performance degradation

Hi I have a pb and i see some people having the same: i got good fps (around 80 on mp server) however i have an horrible stuttering/ghosting when i move the head w/ TIR. I managed to run DCS a lil smoother with decreasing refreshing to 60hz (even if it is 4k monitor with 120hz ability) However, as you can see on pics it runs quite fine for few minutes then GPu load decrease from 100% to an up/down around 70% and big stuttering appeared. Hame was quite unplayable even with 50 fps All parameters of the videocard changed and dont return to normal. 4080/ 9900k/ win11 / 64gb ram/ havent touch to pagefile yet/ any ideas? br

+1 TWS is quite useless nowadays

hi Both

nop, still experiencing that flickering I tried vsync onoff , lot of nividia features gsync onoff, windowed or fullscreen, to change resolution of the small screens etc.. no luck

here are my settings in file(in case of somone find an error in it): _ = function(p) return p; end; name = _('TV x2'); Description = 'Left MFCD on the left monitor,Right MFCD on the right and camera on the center' Viewports = { Center = { x = 0; y = 0; width = 3840; height = 2160; viewDx = 0; viewDy = 0; aspect = 16/9; } } LEFT_MFCD = { x = 4002; y = 0; width = 700; height = 700; aspect = 4/3; } RIGHT_MFCD = { x = 5026; y = 0; width = 700; height = 700; aspect = 4/3; } F18_AMPCD = { x = 3316; y = 758; width = 400; height = 380; aspect = 16/9; } F18_IFEI = { x = 2525; y = 744; width = 550; height = 400; aspect = 16/9; } F18_UFC = { x = 3260; y = 152; width = 520; height = 490; aspect = 16/9; } F18_TEWS = { x = 4170; y = 756; width = 200; height = 200; aspect = 16/9; } F14_DDD = { x = 3925; y = 320; width = 400; height = 260; aspect = 16/9; } INU_M2000 = { x = 3925; y = 195; width = 400; height = 150; aspect = 16/9; } INU_BUT_M2000 = { x = 3925; y = 305; width = 400; height = 120; aspect = 16/9; } RADIO_UHF_M2000 = { x = 2705; y = 210; width = 400; height = 150; aspect = 16/9; } RADIO_VHF_M2000 = { x = 3318; y = 155; width = 210; height = 65; aspect = 16/9; } PCA_H_M2000 = { x = 2705; y = 337; width = 400; height = 150; aspect = 16/9; } PCA_B_M2000 = { x = 2707; y = 450; width = 400; height = 150; aspect = 16/9; } FUEL_CONSO_M2000 = { x = 2735; y = 760; width = 100; height = 100; aspect = 16/9; } PVI_KA50 = { x = 2705; y = 195; width = 300; height = 200; aspect = 16/9; } ABRIS_KA50 = { x = 3940; y = 215; width = 370; height = 370; aspect = 16/9; } UFCD_JF17_LIGNE1 = { x = 3580; y = 166; width = 140; height = 60; aspect = 16/9; } UFCD_JF17_LIGNE2 = { x = 3580; y = 268; width = 140; height = 60; aspect = 16/9; } UFCD_JF17_LIGNE3 = { x = 3580; y = 371; width = 140; height = 60; aspect = 16/9; } UFCD_JF17_LIGNE4 = { x = 3580; y = 476; width = 140; height = 60; aspect = 16/9; } LEFT_MFCD_JF17 = { x = 2705; y = 208; width = 390; height = 380; aspect = 16/9; } RIGHT_MFCD_JF17 = { x = 3925; y = 208; width = 390; height = 380; aspect = 16/9; } JF17_AMPCD = { x = 3316; y = 755; width = 380; height = 380; aspect = 16/9; } --CDU_EXPORT UIMainView = Viewports.Center UIMainView = Viewports.Center

FYI W/ the first version last week of MT the pb of MCFD flickering disapeared for A10c & AH64d (another pb for f18) but then w/ the friday "hotfix" it reappered. MFCDs are flickering again BR

cf pic ALREADY REPORTED

Ty a lot idd i m not using helios Restauration didn t do anything on flickering but on realtek drivers

In fact, changing my 3080 to 4080 made that thing to appear so.. my tv is gsync indeed but what do you mean by response setting, is it low latency thingy like?

yes i tried but with no luck, ty It s associated with little clicks sometimes. i suspect an audio driver pb, i tried to install last realtek audio drivers but i get worse so i uninstalled it with windows audio driver utilisation for now.

Hi Since i change my cg and done a proper install of the last drivers, my two mfcds are horribly flickering. Both at the same frequency. I tried a lot +/- vsync, +/- gsync, gsync windowed not windowed etc please advise BR IMG_2267.MOV

well i ve just tested the pb remains the same

that might end like this because looks like no "hotas" way to make it tx

Hi, Something's bothering me, i often use the ACM mode in F18 and i also regulary switch from StandBy and ON.. The problem is when you set, let's say, a LHAQ mode in StandBy mode and turn it ON, it exits ACM mode and return to a scanning mode. Eventually you lose time, you re dead.. Is it realistic? i mean when in combat can you go silent? Can it be set to "when i turn the radar on, i keep the settings of how i wanna use it?" Please advise BR