Darcaem

I've followed your lead and reducing textures to half gives a huge improvement... Of course one would need to fly it and test the feeling for a proper amount of time, but so far it does feels and sees quite ok

+1 A clear statement would be great I've been looking for it like an idiot on my singleplayer sandbox missions, since it was clearly mentioned in the newsletter...

I still have hope, there is only so many times you can say it is launching today and create hype to then delay it

+1 (again)

+1 I ended up on this post looking for how to delete a lot of units and statics. My use case is I have a crowded mission with lots of templates in FOBs, airbases, etc.; and due to the performance drop on the last patches I need to remove as many units as possible. For me, it would be perfect to been able to select with my mouse an area and maybe get a list of all units and statics in that area, order by type (ground, aircraft, helicopter, static) and select or deselect items. And then delete selected items.

In my case I think stutters are caused by the number of units. It seems in previous patches (I don't really know exactly which one, but definitively after 2.9) the game handled with good performance a way higher number of units on the map. The very same Syria sandbox mission I've been playing since forever used to run smothly (~1050 units and statis with custom scripting), and now is unplayable unless I remove most units (removing all scripts has no effect) What is more worrysome for me is that I was playing the Operation Cerberus North campaign with good performance (I was at mission 16 part2) but the very same mission is now completely unplayable (VR with G2, i9700, 64GB@3200, rtx3070 at low graphics)

EDIT: NEVERMIND! It was my fault by not removing corrently the scenery!!! But since I've already posted, I will use this post to thank you ---------- In you last template. Now Zad District Centre, the northern corner is not correctly displayed. Thank you so much for your work!

I've come back to this map after a while, to the mission editor. Is this transition a bug (I do switch regularly between VR and pancake, changing settings and maybe I've messed something up) or is it "work in progress"? It seems the layout is actually correct though acording to Google Maps, but there are buildings and streets literally cut in half...

Yep, being happening forever and still there (VR, 3070, 64, i7. G2). Has Hawkeye_UK said years ago in this same thread, most times alt-tab solves the issue, sometimes not, and I have to restart DCS. Just commenting to keep the thread alive

+1 Maybe the "Gameplay" tab could be added to the launcher's options tab. As a VR user who regularly switches to pancake for mission editting, I'm very happy with the launcher besides this bug though

+1, I've not bought the new FC2024, I got the previous FC3. Edit: Oh, after the first game launch I got an upate available for FC3, but still authorization failed after updating. It keeps showing as update available, allthough I've updated it twice Edit2: I do have access to the Su33 jejeje don't know why null

Sorry for necroposting Google tells me there is no solution yet, but just in case, is there? I have a singleplayer sandbox mission for myself and would like to differentiate radio's and target's kneeboard pages per coalition (I have some helicopters and planes present in both)

I have reverted back to 2.9.2, last Open Beta before this last unified update, and it works smoothly again. I am able to restore the pevious higher graphic settings I use to play with before (I have onl kept the 50 frames cap) With the same graphics settings that in 2.9.3: Settings textures to High and Terrain textures to High (restoring the graphics settings I use to play with)

Yeap, checking the expanded performance it seems VRAM usage might not be the cause of the problems. On the attached screenchots it is seen two different missions with terrible stutters with awful frame times and VRAM usage bellow maximum values Again, first spawn on the first mission works fine with the same exact VRAM usage that the second spawn, or the second time I launch the mission.

Nah, I've just test the Prefer no sysmem fallback option with no change. I have spawn on a Huey hot on an a irfield, everything super-smooth at low level in land, sea and landing on a ship. Then without exiting the mission spawn on a new hot Huey on the very same airfield and frame times went crazy and framerate down to 20-25 In another play session I have checked the VRAM usage. It is clear that is the problem. In the attached screenshots can be seen that when I first spawn on a Huey GPU's VRAM it is almost full, runs smoothly. After some time and an emergency landing VRAM usage has decreased a little but is still at its maximum, it stills runs perfectly smooth. After that I spawn on a F18C and the VRAM usage increases over the maximum and starts using shared memory. Then the problem starts. The thing is, after exiting the mission the VRAM seems to not been released. If I exit to the main menu, go to the mission menu again and enter the same mission, in the same Huey client spot that before ( last screenshot), the VRAM usage is over the maximum. Dedicated GPU VRAM usage is the same ~7.5GB, but the shared memory has not been released. Also, I don't know if this is really important, but I am also attaching a screenshot from other sim where the experience is as smooth as DCS (when it is smooth :P) but it is actually using shared memory (probably unrelated, as GPU VRAM is not maxed out there, probably the GPU shared memory is being used for other stuff) PS: I have a 50 framerate cap, which visually works fine for me

I haven't test it yet, thanks in advance. But I have also noticed you have low latency set to ultra. Just out of curiosity, do you feel any difference? I did try it and saw none (maybe because I have bigger problems preventing it from having a real impact), and with my little understanding and reading I assumed it was related with controller's input response time, and thus only relevant for shooters and games like that. Enviado desde mi SM-A346B mediante Tapatalk

Thanks for the new feedback guys! I did test with all graphic settings set to bare minimum, just to see what happened, and the result was the same (also, before the unified update, playing beta version I could play smoothly with the settings I posted on the first comment) But I have realized that the problem is not actually the ghosting itself, is that it only happens "sometimes". The first time I launch a mission I can play super-smoothly, even more than in the previous DCS Beta version with the same graphic settings. But, if I exit the mission the frame times start going crazy. If I launch the very same mission, is unplayable. Even on the menus it happens (weirdly, it happens on all menus, mission selection, campaigns, settings... but not on the main screen). Sometimes after I quit and relaunch DCS it works smoothly the first mission, and sometimes I need to restart the PC. Also, sometimes when on the very same mission I change to a different client aircraft it happens, sometimes I can change without problems. I've been following some threads on the game performance bug section and I do believe there is something with my computer's setup that is causing troubles with this specific version of DCS Edit: btw, thanks @Nedum for the detailed explanation

Meh, I was hoping to be able to play this weekend finally but changing cpu's affinity does not work anymore, frame times are peaking all over the place, even on the menu screen

It turned out to be solved with the change "cpu affinity fix"!! I can finally play again with the same graphic settings I played before, even with high terrain textures, and even in South Atlantic!! I don't really understand it, but in my case if I alt-tab to the task manager and remove all DCS's cores affinity but core 1, alt-tab to DCS, alt-tab again, and set back affinity to all cores then DCS runs smother than ever Thanks to all for your pointers and suggestions

Ok, another thing, which I know it sounds absurd... I have realized that when I launch DCS if I don't do anything and just enter a night cold start on Incirlik test mission (I'm using now for testing the M15 part 1 of Cerberus North campaign to be sure no mod nor custom lua code I have writen may be affecting) I get now 57-60 fps (which feels fine for me). But if I exit the mission and go system settings, even if I do not change any value whatsoever, and enter again the same mission, now I get 33-38 fps with ghosting The same is happening with the instant action free flght F18 Syria map. If I start the mission right away after launching DCS, I get around 70fps. If I start the mission after having test the other night test mission. I get 38-43 fps with ghosting

Thanks guys I do not use motion reprojection, and do use OpenXR Toolkit with fixed foveated rendering set to preset / quality / wide (I also test with these with no difference) I've follow your suggestions and clearly, as all of you say, this is bound to low frame rates. When I achieve 45 fps the problem disappears. But what have changed in this last version? Why I was able to play with my settings before but not now? In case it rings a bell for any of you, I have noticed that the ghosting only happens with "ground stuff" (buildings, lights, walls when inside a hardened parking spot, etc.) but not with planes passing by either flying nor taxiing on the ground, and only when I move my head. I am using the Free fligh F18 Syria map instant action mission, and a custom one set at night when I start cold on Incirlik. In the instant action mission the other F18 passes by perfectly, but I do have ghosting with buildings on the ground. On my custom mission other hornet turns on its lights and taxi right by me perfectly, but I have ghosting with the airbase lights and shelter's walls

I'm having a lot of ghosting while moving my head mainly on the ground since the unified version update and last nvidia driver (both were updated at the same time). It only happens on DCS (not on the other "civil sim") and I didn't change anything. The fps shown on the DCS little analysis window are the same as before (I play at around 30-50 fps on the ground with a fairly old rig), but now when I move my head I see a huge effect of ghosting without fps reduction shown on the graphic My specs: i7 9700k 64GB dd4 RTX3070 2TB m2 HP G2 null What I've tried: Reduce graphic settings: even with everything at minimum the ghosting is the same Disable DLSS Try all antaliasing options Set low latency mode to on and ultra (I have it off by default) Disable hot plug on controls Full screen checkbox checked and unchecked Remove all mods Rollback to the previous nvidia driver (current version for me is 551.61 from 02/22, I tried rolling back to the previous one Verify DCS main install and save games folders were excluded from windows defender "Unpark cores" Just in case, for the sake of testing anything... What do you suggest? I assume it has to be some problem on my end, maybe some key setting that has been reseted on the update and I have forgotten, since the update seems to have improved performance for anyone else dcs.log DxDiag.txt

Hi Using Moose's SPAWNSTATIC module I'm trying to spawn smoke on demand on a specific location, but I'm doing something wrong as it always spawns at 0 feet. To test it I tried to spawn a random static plane, and it does spawn correctly at ground level. This is the code I'm using function userCreatedMarker(Event) trigger.action.outText(Event.pos.x..", "..Event.pos.y..", "..Event.pos.z, 15) SPAWNSTATIC:NewFromStatic("Static smoke and fire small-1-1")--Static MQ-1A Predator-2") :SpawnFromCoordinate(COORDINATE:New(Event.pos.x, Event.pos.y, Event.pos.z)) end When using the smoke's static name ("Static smoke and fire small-1-1") it spaws at 0 feet. Using the random static unit ("Static MQ-1A Predator-2") it spawns correctly at ground level. For testing it, the above function is called on a handler when a new marker is created on the F10 map. And when testing the random static plane, where it works fine: Do you see what I'm missing?

As soon as I start the mission, it triggers. It gives me 69 score if I exit at this moment. I haven't play the mission yet, so I don't know if this will break it or the rest of the mission will work properly. I'm playing OB I'm enjoying a lot the campaign and the briefings, all the little details (not the "non-refueling-needed" policy though jejejeje), thanks!

Did you find any workaround to set unit's fuel? Even if you finally did it in any other way, I would love to know. I'm trying to start a mission with the same fuel level I had on my previous playthrough and I'm out of ideas