noisy_lightning
-
Posts
369 -
Joined
-
Last visited
Content Type
Profiles
Forums
Events
Posts posted by noisy_lightning
-
-
Indeed had that before and I have a tool to restore old GUID numbers. Those all match what the dcs files have. In addition none of the game settings were carried over either which is strange.
Is there a registry entry that points to this stuff?
-
Have recently just built a new machine, and as I have in the past with all other re-installs I backed up my save games files for binds etc.
Installed the game, copied back the save game files as previously, checked the device ID's against my Stick/Throttle/Rudder etc all match in game and in the binding file name, all good.
Go in game and nothing is being loaded by default as it should be. Just not picking anything up from the Config-Input folders for each module.I can manually add these files in game by importing profiles, this is time consuming though.
Any idea how to resolve the automated import of the existing profiles?
-
16 hours ago, AKULA_OPTIMUS said:
Sadly this doesn´t work for me, once I spawn, and go to the task manager to switch CPU affinity to just one core. But if i get back to the game it becomes veeeery slow, and if I go back to the task manager again, and activate all cores, the game crash. I just dont know what to do, cant play DCS properly since 2.9
You don't need to go back into the game. Just change the affinity to cpu0 press OK. Then change it back to all cores. Has the same effect.
I went an hour last night with no problems then out of nowhere the stuttering came back (Self built Strike eagle training mission) but changing the affinity again solved it a further time.
Clearly something in the games code just doesn't play nice. Couldn't pin point last night what thr cause was sadly but the game continued to run lag free for another 45min till I chose to quit out.
-
1
-
-
This solution has solved my issue entirely!
-
1
-
-
17 hours ago, SteelSlav said:
Non-forum user here, since 2.9.0 OB was introduced I started getting massive freezes every 4-5 seconds which do last about 5 seconds each time. I've never had issues running dcs on medium-high settings, but after 2.9.0 it became unplayable. I found one way in particular to fix it and (besides installing Lasso as @Checkmate suggested), everytime I spawn in an aicraft I have to switch my CPU affinity (got 4 cores, i5-7500) from 4 to 1 core. Having done this, I enter the game back in and have to alt-tab again and set CPU affinity again to 4 cores and I have no issues thereafter, almost running smoother than I usually did. ED, or whoever is responsible for tweaking this kind of stuff, please fix this soon because one of my friends is facing the same issue. I also have a crash log from the last mission I did and if useful and requested, I'll drop it here. Please, someone help me with this programming hell.
This worked for me, solved the problems I have had since 2.9 dropped. Thank you so much!!
-
1
-
-
So glad i bumped into this thread, going to try the affinity solution tonight, fingers crossed!
-
1
-
-
1 hour ago, BIGNEWY said:
Ive spoken to the team this morning and in future patches we will have tweaks for how textures are handled by multithreading. Again we will need to gather feedback to see how this helps.
thank you
Will any of these changed be included in the patch dropping today?
-
Can confirm that shadows are the fault of the stuttering. With them turned off I have zero issues.
How do we go about diagnosing the issue for you guys@NineLine
-
2
-
-
On 11/1/2023 at 4:22 PM, Tigh said:
And more: which led me to think about turning shadows off. No more issues at all. It's shadows causing the problems.
I have played about with shadows but not disabled them entirely. I will give that a go tonight!
-
1 hour ago, Hiob said:
It should be better on a second launch then, when all the freshly compiled shaders are cashed. Have you tried to run the mission a second time?
I ran the F16 Instant Action Mission (Free Flight) on Syria three times in total and flew in different cardinal directions from spawn each time. First Straight south into Israel landing at Ramat David, Then directly East and then as far North as I could before running out of fuel. Only thing I change other than flight direction was turning on DLAA and SSS for the final flight. Stuttering increased initially for the first few minutes and then settled down so the point it was non-existent in the cockpit. Had stuttering on external views, still but again, the more time I spent in external view the less the stuttering appeared.
I will repeat the same tonight with the same mission, module and map, then see if how it compares with a different module.
-
Significant improvement now for me, not completely gone but now playable at least.
Syria, F16, instant action free flight mission, on launch it stuttered like mad but after 30 minutes of flying around it almost completely resolved itself.
Yet to fly other maps in different modules, so can't say for certain, but may well be a shader rebuild issue...?
-
Not had chance to try yet, but has the hotfix changed anything with this stuttering?
-
9 hours ago, DroptheHammer said:
are most of you guys on windows 10 or 11?
Win10 for me
-
6 hours ago, Lange_666 said:
That's nothing new, loading unused objects/textures like flares or explosions has been causing stutters since the very beginning of DCS.
Not for me, up till last week 2.8 ran immaculately. I would rather sacrifice the uplift of 15-20% "Fps" in 2.9 I am getting now to get rid of the stutters which are new.
-
1
-
-
Some further testing tonight, and my previous post on input from devices causing it I no longer think is the cause.
VRAM is the cause. Whenever new textures are being loaded into the game such as flares or explosions its causing the problem. If for example I am flying low level in a valley and pop up, stuttering occurs, this is as it loads new textures in. I have tried lower preload settings though, and lower texture settings and nothing solves it.
To clarify, my 3070ti (8gb) ran 2.8 perfectly, with the same VRAM being capped out fully by DCS, it used to just spill over seamlessly to RAM, but now I seeing DCS not use all my system ram and stuttering like mad when it runs out of VRAM.
Never thought i would say this, but guess I am going to have to shelve DCS and stick with FS2020 till ED sort this out.
-
1
-
-
I have done some testing tonight. Nothing I change settings wise has made it worse or better.
When I crashed though and had no aircraft to see I used my mouse scroll wheel to move the camera back and forth and it triggered all sorts of frame timing issues. I have free spinning wheel on my mouse so it can send constant commands, and that triggered the stuttering.
In addition, with zero aircraft loaded and still at the crash camera, any large input on my stick (virpil cm2 base with CA grip) and I got the same.
Its now my belief that my stuttering is coming from the usb devices saturating dcs. Enabling or disabling hotplug did nothing to fix it.
-
Hardware: I5 10600K (OC), 3070TI, 32gb DDR4 3200 CL14, DCS on a Samsung 980Pro NVME. Running at 1440P. After updating I cleared the FXO and Metashaders2 folders as I normally do.
Updated to 2.9 last night, and tested with a mix of settings, DLSS on (with DLAA and without and tested most of the settings, qual, perf etc), DLSS Off with various AA options chosen. SSS was on throughout all testing.
The issue is not performance specifically. I was using the same Instant Action mission each test performance with each change in a "controlled" environment (F15E - Low Level (Day)). My FPS is high, and usually between 80-100fps. But the issue is significant and random frame time stuttering, which will last up to 1.5 seconds or so then continue back with the high FPS.
Disabling Vsync helped a little, but hasn't stopped it. The only thing I have yet to do is to update my drivers, but they are no older than 8 weeks at the most....
Any ideas for solutions? As with this stuttering it brings an otherwise flawlessly performing gaming session to being unplayable.
Edit: The in game FPS window says I am not bound by either CPU or GPU as it flicks between both equally.
-
I don't have access to logs right now but I would like to also echo my very slow load and shut down times. DCS is on a dedicated Samsung 980pro nvme drive, so no slouch, and load times on both ST and MT have gone from ~30sec to in excess of five minutes on one occasion.
-
On the contrary I found last night the aircraft to be much more twitchy and unstable in the hover, taking off was a PITA and transitioning to a hover was much more all over the place. It was like I was starting all over again. I do concur it feels heavier now in certain flight regimes, if I try and evade a missile in the hover its much slower to react to input, but I am not sure if thats the SCAS fighting me or a change to the FM overall.
Its not even that my stick is cheap, I have a Virpil CM2 with a 200mm extension. The only thing that changed is the patch yesterday.
-
3
-
-
nineline mentioned in another thread that Syria has a known memory leak which they are working on. Could be this given that Caucasus doesnt do the same?
-
2
-
-
On 4/20/2022 at 5:40 PM, LooseSeal said:
I finally just got my CM3 throttle, and I cannot for the life of me figure out how to do this... I am completely clueless when it comes to stuff like setting up stick configurations. I usually just go for whatever it is out-of-the-box.
Is there just a basic step-by-step guide for idiots like me that explains how to create a virtual axis that can be used for the zoom function in DCS? Particularly I'd like to use the encoder dial on the right side of the throttle for it.
Unfortunately, in this thread the guy had already apparently set up his 'virtual axis' - I don't even know how to get to that point! I've watched the relevant Havoc Company Youtube videos but can't find a clear explanation there - as useful as those videos are! Again - I am fully a hardware idiot.
Something to be aware of with these devices is how they number their buttons etc. There are physical buttons, and logical buttons. Physical buttons are the raw data that the device sees when you press something. Logical is what it sends to Windows, and is the button number which will show up in DCS when you press something. These do not always match up!
- On the main software screen click the axis button on the left to take you to the Axis screen.
- Find the next new blank line under your existing axis and double click it.
- For the first encoder Under "Joystick Logical (output)" set it to Dial next to Axis Name. If you want to setup both encoder dials then the second one needs to be set to "Slider" in this pull down menu, when you repeat this entire guide for the second Encoder.
- "Axis Source (Input)" Select Virtual for Type and set Smoothing to x8.
- "Button to Axis" - This section is where you say which buttons you want to control the axis with. For example 61, 62, 63 for Encoder 1 (E1 -as printed on the throttle) and 64, 65 & 66 for E2. These numbers are the physical buttons, NOT LOGICAL.
- To work out which button number you need to use for Up, Down and Button RESET, open the VPC Config tool (button bottom of the main window). Then rotate the dial and make a note of the number that turns blue.
- Set the Up, Down and reset values to the button numbers you established from the step above.
- In the latest software version from 0% to 100% on the virtual axis is based on a value of 60000. If you want each notch on the Virtual Axis to be 5% set the step value to "3000" and if you want it to be 10% set it to be 6000. Set "Reset Value" to 30000" which will set it to 50% when you depress the encoder, if you want the reset to be 0% set it to 0, if you want to 100% set this to 60000.
- Leave everything else as it is as default. Press Save at the bottom.
- Hit the big green button at the top "Save VPC Device" and let the software save the profile to your throttle.
- When the software reloads press "VPC Joy Tester" at the bottom of the main window and test the Axis is working properly.
-
1
-
You need to set the encoder as a virtual axis.
https://forum.virpil.com/index.php?/topic/7764-encoder-to-virtual-axis/
-
There is also a mod called scratchpad which allows you to click on the map, and shows the co-ordinates in a popup window which is persistent from the F10 to the cockpit. For me it saves grabbing a pen and writing them down on paper, then typing them into the aircraft.
-
There is also the remove before flight tag on the lower left in the pilot seat. And the lapel strap on the seat belt near the head rest also moves about (no pilot body visible). Nice dash board shimmy as well when in cruise.
Lost Binds after Re-install
in Installation Problems
Posted
Resolved it this morning. Minor issue with the hardware for the virpil sticks, when installing the virpil software it flashed new firmware and built a new profile. I have restored my old profile and now, the binds work.
Cheers for the help everyone.