Mosley

I found one part of the issue, for the performance loss of going from 90fps to as low as the 60's this was being caused by Process Lasso's Pro Balance feature. This was changing the priority of the game to a lower setting which was causing the fps to drop. After turning the feature off now it runs at a smooth 90fps but i get a stutter a couple of times a minute. Half way there I guess, now to look into the stuttering.

dcs.logDxDiag.txt This morning I did the panzer mission but i added rain, ran fine , fired on the AAA/Sam group with the fcr worked fine , got locked by aaa i missed turned away from target got hit and lost a engine then fps dropped to the 50-60 range. This has been a issue for me thru several different nvidia drivers and some amd drivers as well. I dont have this isssue with other flight sims. I see you mentioned Vram optimization and I thought it might be something similar since vram usage seems to be 90%+ on the settings i use normally but when i set everything to low Vram was around 6gb and still had the stutter effect. Im curious why alt tabbing out of the game causes the stuttering to stop, but when alt tabbing back in it starts within seconds. I could understand the fps dropping if the Gpu was at 100% but it maxes out around 80-85%. Its not 90fps to 80 then back to 90 its more like 90 to 0 to 90. Gpu usage will do 80%-0%-80%. I thought maybe thermal throttling but temps are fine and system handles long handbrake encodes using all cores and gpu stress test like furmark. I also use process lasso to put dcs on the first 6 cores and virtual desktop on the last 6 cores. Noticed this in the log at the end 2025-02-07 17:48:51.803 ERROR VISUALIZER (Main): rendering thread is stopping unexpectedly long time Another issue that pops up is when i click quit to desktop or quit sometimes it does and sometimes it doesnt. Dcs goes not responding and I have to close it,

Issue : When I load into the Mountain Coin mission for pg in the apache it will be running fine in vr at a smooth 90fps thru vitual desktop, while starting up the apache it will start to stutter, sometimes after a stutter the fps drops and all the times on the fps counter go up (frame, sim, etc). Then i will be around 60fps but instead of the 3 bars being somewhat smooth at the bottom of fps counter they go up higher and fluctuate up and down (looking like a saw tooth in task manager). the times listed also go up as well with mouseover fps counter. I have seen this while using the caucus map, pg, nevada and mariana Oddities that I have noticed : After stuttering thru the startup sometimes it will stutter and the fps will go back to 90 fps and run smooth again for a duration. Another odd one is when i got into the area where the targets are in the mission it was stuttering and if i alt tabbed so it showed game out of focus stuttering stops. When tabbing back in it starts again. I have also had it doing the alt tabbing will sometimes bring back the 90 fps. I also have a mission from the user files with the Apache and the a10 and I dont have the issues when using the a10. Things I have tried : Changing settings to Low makes no difference. I loaded Windows Performance Recorder/Analyzer and recorded a 10 minute or so session I did with the panzer mission for the Apache and Nevada map. While looking at process lasso and task managers usage I can see that none of the resources are maxed, they are around 80% and when a stutter happens video card and cpu shows a drop to 0% usage then back to 80%. The performance analyzer shows a spike in the nvidia driver kernel modules time ( at least thats what chatgpt said ) at the same time the FPS tanks. Being that I can use the A10 on the same mission and I dont have the performance issues it would lead me to think its something with the Apache, but tabbing out of focus and it stops plus the nvidia driver issue has me lost Any Ideas? System Specs : 7900x3d 64gb DDR56000Mhz 2Tb WD Black M2 Asus 4070Ti Quest 3

approach plates is another name for it

Try playing with the ipd setting on the vr page, i remember setting it to a weird number and the a10 stick and throttle looked like 1/4 sized. like a child's toy. From my understanding or lack thereof the ipd setting in game is independent of whatever your vr device is using, i think it had more to do with the way the game renders. Give it a shot and let us know.

Any word on if the numbers will change back next patch or will they leave them the same?

What do you mean by custom device settings? Just curious.

When I was messing with it earlier I binded the nws button. It was added to the Lua file. I think checked the syntax of the nws section and it was the same as the old Lua.

Checked the config folder in the game folder and it seems to be mostly default settings. The other thing is that If i rebind the keys, for example the nosewheel steering button its added to the users saved games folder lua file. However copying the old lua into the new one, copy/paste, and loading profiles does nothing. Like I said its not a big deal but its something i'm sure they either want to be aware of or say something like all keys have to be redone with this patch. Well to be fair, my flaps and gear still work on the joystick. Can someone check if the flaps and gear info is in the new lua file? overwrote mine. Something odd i noticed. If i copy the old lua's over to the config folder almost all of the commands dont show up in bindings, the flaps and gear still do.

Several people in the forums have updated and not been able to load the old Lua files. Might want to wait or plan on rebinding what's missing.

have you been able to do this? Others have tried but no luck.

Copy and pasted my 3 lua's and overwrote just fine.

Should the lua files have most of the options listed and no buttons listed as assigned? I loaded the lua that doesnt have the bindings I had before the update and there is not much to it. Pov hat commands deadzone, etc. The filesize is half of the other lua with all my binds. I checked the syntax from the updated and my old lua file for the nosewheel button and its the same. Same as others, I have tried loading profiles in the settings and nothing changes. Copied lua files from a backup image from before the patch and nothing changes. The file sizes for the joystick lua go from 3k to 6k but none of the buttons work.

It's not that big a deal, but what if it's changed or reverted next patch and it's back to the settings for a bit.

Crap maybe they will merge the two, well at least its not just me.

F18 Keybinds after 07/18/18 Update Applied the update today and for some reason most my bindings for joystick/throttle/rudder pedals are gone. I Tried loading the profiles that I backed up just in case but nothing loads. I can manually go in and do it all again. Cage/Uncage, trim, g override, designate/nosewheel, radar controls, speed break, weapons release button as well as gun. Modes for aim 120, aim 7, sidewinder, gun are gone, acm modes gone as well. Only thing I could find that still worked was landing gear and flaps. Any idea if something changed with the controls for the f18 where an old profile wouldn't work? By old I mean before today's update. Loaded the A10 and all the controls are still there.

Totally different angle but, why ask for a variant just to add more work to the dev team during updates and changes. Not bashing the dev team and what not, but for example say one aim9 breaks one way and the other variant has a problem in a different way. If its smoke trail/color/blah, etc just adds more work for not a lot of difference. How many times in the change logs do you see working again... Just saying I would rather have something that works as it should and if its broke its not 5 variants to fix but 1. In war nothing is equal for both sides. Better to learn your weapons capabilities and use them in the best way possible imo.

Decided to update today, downloaded the update and then it crashed after downloading. In my case it was because I had around 3gb of disk space left. I thought hey maybe the ssd doesn't have enough room to apply the update. Uninstalled another game and it worked fine. It would be better if it just reported that there wasn't enough space to perform the requested operation than for the updater to crash. Just a heads up.

Both sides have points. But in the end there are bugs that have been around for so long its pretty sad. My favorite is whoever said that the cbu 97's/105's work fine as long as you drop 4 instead of 1. I got a good chuckle out of that one. IMO the cbu's have been messed up since they switched them from the 87 style to the proper 97. Then its been messed up, really messed up, ctd when droping them, etc. They have never been fixed properly. I too am of the opinion lets get the bugs fixed. However I am expecting a slew of new bugs once edge is released which is normal but those have to be fixed, then move on to fixing the bugs in new products, then something else, then getting back to the basic bugs that have plagued this sim for years. In the end its lets push out more product to make money ( which I completely understand ) but at some point which seems to be when the bug breaks the game is the only time its fixed. Been through this same thing year or two ago and in the end nothing changes. I play single play when I feel like it, havnt bought a module since.

Just a guess but if you are flying to low I think you will get invalid fuzing. If the HOF is set at 1500 for the cbu105 and you are below it you will get the above error msg. Decrease the HOF or fly a little higher and see if this fixes the problem.

Is the mws in dcs a10 different than whats in the military a10? I thought I read somewhere it was. I remember when I was at an air show looking in the cockpit the a10 had a digital radio stack that took up like a 1/3rd of the space. Wouldn't supprise me if there were other upgrades to different components as well that cant be included in dcs a-10. I thought one was the mws, or it could be the rwr I don't remember it was rather vague... like my post...

Keep this in mind as well. I have been locked up by a Shilka and semi auto was dealing with that. Not with the man pad that had been fired. For this reason I run manual all the time and switch between programs I and J and use accordingly.

How many times have you replayed back a track to end with gun runs into the ground with no target it sight or fly off into the distance for no reason. No offense to ED but the replay system is not up to par. If this system was modified to save all the different variables as some have mentioned you would more than likely get a different variant of your save than what is actually going on in the sim. ED would also have to implement some sort of way to re insert all the destroyed objects. Think bridges, buildings, aircraft, vehicles, etc. For me these become landmarks or references to the current fight. Should they be simply left out? In theory this type of stuff should be easy to put back in sim. At cord x,y place destroyed t-80 tank, but in the end the sim was not designed with the "Save" feature in mind and would require a lot of work to get this working right. Not to mention the time added to get the replay system working properly. Also as other's have mentioned the LUA scripting would have to save all those variables plus older ones if they effect the newer variables. Personally I would rather them fix the bugs that we currently have such as CBU's causing slideshows or the 97's ganging on up 1-2 targets among other things. Continue working on EDGE and eventually pick back up development on the dedicated server would be time better spent imo. Also keep in mind, quite a few 3rd party projects are being released and ED has to help these guys as well. Their plate is simply so full this "Save" feature would be at the bottom of the list. I guess we can hope they wanted to add something like this and are working to add it to a EDGE version because if not I doubt it will ever happen. Its a small team and they are doing what they can but it all takes time.

The track system in Dcs World does have its fair share of problems. Some work great others don't. Personally after watching my a10 do gun runs into the ground I have given up on the internal track system. I have noticed that while playing a mission if you use time compression and speed things up this can create all kinds of problems with the tracks. Also the longer the track is the more it gets messed up toward the end. Sometimes... With just recording user inputs this doesn't supprise me. If you are wanting to watch the replays to learn from mistakes and what not Tacview is a better option. The tracks for tacview are much larger and I have yet to see something happen that I didn't do in sim. IMO the internal track system is only usefull for submitting a 3-5 min track for bug reporting purposes. Its just a little to squirly for me.

I was really nice for a while, but my paitence is wearing thin. Obviously you dont play online much.