METEOP

Just got a Warthog myself! And the slew is c.r.a.p. as profusely stated. However, I played around a bit in the Axis Tune section of configs and actually managed to make it not so bad at all! Now I have managed to make it progressive like a 'pointing device' on a laptop. Adjusting the deadzone and the progressiveness curve made it even better! It is much more usable now than the 'stock' axis tuning I find.

Ahah! On A10C my MFCD exports have a strange behavior also, for some reason the MAV sensor is much darker than in the main view. I perused the .lua files for some settings to na avail. Very interested in this since the MAV export is almost unusable.

I stand corrected! I also exchanged a pm with Goa about this I had a misconception about my processor. I guess what I am trying to point out is with my particular situation, the stuttering seemed purely a tracking issue when fps != vsync, and that monkeying around with affinity and priority did produce drastic improvements on my end! Now! Armed with the infinite wisdom that I possess indeed four physical cores it gives me a few ideas on how I can make it even smoother. I have always felt that departing from 2.2 and going to 2.5b, there is something that my system doesn't like very much.

Goa, I have had a similar problem to you since 2.5b I will take the time to write a longer post in the near future, but here is the short version. After many tests, and many disappointments, I started to pin down the correct symptoms: - Stuttering when framerate goes below 60hz (vsync'ed) - Framerate goes below 60hz when using sensors (A10C TGP and MAV) __with lots of speedtrees__ - Framerate goes below 60Hz when lots of enemies are aquiring (me) and firing No sync is not an option, did not appear perfectly smooth like gsync under any circumstances. My problem is aggravated by the fact i'm not running in fullscreen, I need to extend to a second monitor for a glass cockpit (Ikarus). It is also aggravated by the two exports on that second monitor for both MFCD. Another factor that aggravates the problem is that I am running in nvidia resolution factors (2x factor of 1080p but no antialiasing). I start flying, very smooth. Get to IP, still smooth, fence in, turn on TGP and MAV, mild stuttering, enemies aquiring, medium to severe stuttering (about 50fps at that moment). At this point it was pretty much unplayable. After month of tinkering with everything I could, it started to dawn on me that at 50fps, I should still be able to get a pretty playable experience (remember the 15-20 fps days :glare:) but the stuttering was making it unplayable. One time, I was about to unleash mav hell to a sorry tank company when suddenly, everything went buttery smooth! I looked at the corner with the framerate, it was about 48-52fps. Launched mavs, went to circle pattern to look at the kill and then I realized my headtracker battery was dead cause it was not panning anymore. So I came to the realization that the stuttering was not 'in the game', it seemed to be caused by some weird timing problem with the TIR STUTTERING when going under refresh rate. With the correct symptom at hand, I started looking for alternative answers. I found it in Process Lasso. The biggest positive impact was to move the processes around by core affinity and elevating process priority for the Opentrack processes. Here are my Process Lasso configs by process : I have 16Gb RAM and an i5, so two physical cores (0 and 2) and two hyperthread cores (1 and 3) DCS - affinity 2,3 - priority class: above normal - High performance process option ON Ikarus - affinity 0,1 - priority class: below normal (would sometimes hang DCS if higher) Opentrack.exe and TrackIR.exe - affinity 1,0 - priority class: High - High performance process option ON Realtime priority with Opentrack and Tir processes was even better but if the process hangs the whole computer is hung by that process and will not come back. So I dialed it back down to High. Goa, I would be curious to know what is the result from trying this on your end.

Thread back from the dead! I think I have the same issue, i'm using Ikarus for the A10C and reverting back to Helios for Su27-33 since I just bought FC3. When I switched from 2.1 OA to 2.5B I noticed a big performance hit. Thought it was something else until I messed up my export.lua path and things suddenly were so smooth it gave me a vertigo! Not sure if there is anything that can be done, but I'll try confirming nonetheles...

With two young children and a consulting business that wont quit, I'm actually training myself to sleep less so I can get some wing time. Still I manage to get about 2-4 hours a week in the pit. And ocasionally with my little guy on my lap we do a quick 30 mins instant action bit bombing session. Yeah.. I'll be proficient in about a decade or two at this pace.

Thank you for your great example of dedication I salute you.

Excellent suggestion, however it does not seem a problem on my system. According to CPU-Z I'm using the full 16x lanes @ PCIe 3.3 I would also thing that I would have issues with other games if it was a problem and that is not the case... At this point I think I will just wait for an update and see what happens. Thanks all for your help!

Thanks for your suggestion, I did try all these options and could not notice any difference. So, reading from all your suggestion, it seems Nobody else has this problem? Maybe I am crazy after all :megalol:

I searched the thread but did not find a result, did anybody translate what's being said and written in this video?

From my end everything still works as-is in 2.5

Although our stuttering issues seem ta have different causes, check my other thread at: https://forums.eagle.ru/showthread.php?t=201162 I have narrowed down my issue to TGP and NAV MFCD usage. There is a switch in graphics.lua which you might want to play with, it's the maxfps which by default is 180. Maybe briging it closer to 60 fps would balance your stuttering issue?

I did check with others on the forums and is not related to ram, please refer to the thread. Prove otherwise and I will gladly change my analysis.

Sorry about the delay and for bringing this back up again. After a good while spent testing here is some more info on the stuttering issue, I'm still on the fence as to reporting it as a bug or waiting it out. While it appears stuttering in 2.5OB can be caused by a number of issues for different pilots, I've narrowed it down (on my system at least) to electro-optical sensor usage, specifically the MAV targeting screen, and somewhat lesser of a problem is the TGP screen in the MFCD also. TO RECREATE THE PROBLEM: - Any map and mission will do, I'm running the A-10C, not sure about other airframes. Smoke compound the problem so you might take an instant action mission with smoke markers. - Line up for attack on ground target, get low about 3K-5K AGL - Turn on TGP on one MFCD, MAV on the other - At this point the stuttering should be pretty severe - Attack target, launch a MAV, gun down the target to a burning crisp - While overflying through smoke and explosions, the stuttering should be very bad ANALYSIS: I tried many benchmarking applications and finally I found the bottleneck appears in the GPU. Using nvidiainspector, I was able to point out the stuttering occurs when the GPU is saturated (100%). When flying without using the EO sensors, under any condition the GPU is running smoothly at around 60-70% usage so there is lots of overhead available. However, turning on the EO sensors, especially the MAV, will eat up up to MORE THAN 30% OF A 1070GTX GPU under any combination of graphic setting. This was not an issue in 2.2A all other things being the same. I've further narrowed down the conditions that causes the issue : THE TREES. If the sensor is not looking at trees, then the GPU usage for the sensor is about 5%, more than reasonable! It's when the sensor is looking at trees it will just eat the GPU for breakfast. So.... how to make this _playable_ ? Here's what I did, please chime in if you have some more ideas. 1. Graphic settings Here are my current graphic settings, anything else will either not affect the performance of will degrade it severely. Note that I am runing in 1080p with a second 1080p monitor for my glass cockpit. Yes I use MFCD and RWR exports to an Ikarus touchscreen cockpit, but the problem appears even without them. So I did try with no exports, only one fullscreen etc... same problem. 2. graphics.lua .../DCS/Config/graphics.lua maxfps = 64 sync = true I've found the maxfps trick in an old 1.x thread. If I put it under 60 the tracking is not so smooth, so I'm really wondering if some frames are not being dropped that are not detected by FPS meters... 64 fps is a good tradeoff for me between being smooth without sensors and playable with sensors. The thinking behind this is, it seemed to me that even though the mainscreen would drop frames, the exported MFCD would run very smooth. This appeared odd to me, since i'd rather get 10 fps in the sensor than hurting the main view... So I started looking for ways to limit the max fps of the MFCDs. I've found by default the maxfps is 180, by reducing the maxfps I am putting a hard limit on what the sensors can hog out of my GPU in worst case. Too bad I have not found a way to limit only the MFCD fps... Oddly enough, if I put some VSYNC either in DCS or the Nvidia control panel after a few minutes of flying the fps degrades severely and it's unplayable, but the sync=true switch in the config file seemed to make the image mnore stable without causing any problems. 3. MFCD mip filtering .../DCS/Mods/aircraft/A-10C/Cockpit/Scripts/MFCD/indicator/MFCD_useful_definitions.lua mip_filter_used = false Another optimisation I've discovered is disabling the mipmapping filter for the MFCDs. Turning it off seems to make thing better. RECOMMENDATIONS: I see a few options availlable to the developpers. The easiest I would think would be to limit the MFCD max FPS, or at least make them less of a priority than the main views. Another would be the speedtree algorithm, it is quite possible that the sensors for the A-10C need to be optimized to take this new algorithm into account. I sincerely hope this will become a priority in the near future, since in it current state and without the aforementionned optimisations, it is alas UNPLAYABLE for now. Even with the optimisations it is barely OK. Furthermore, I would really like to use my 30% GPU overhead that I keep free for sensor usage. The base engine is incredibly fast and beautifull so cranking up the graphics would be even better! I would like some people to test these optimisations on their end and let me know what you think about filing an official bug report?

Just had a thought... If you are running a dcs server, can't you turn off 3drender in the graphics.cfg file? Would this work?

Xen server is also open source and runs somethin like 75% of vm on the internet I've used virtualbox, vmware and xen, hyperv (microsoft) never tried it. just my opinion... Attempting a gpu passthrough would not be easy and I would not waste my time on it. But hey! If you manage to pull it off it would be quite a feat! I use virtualisation a LOT for my work and at home, mostly with xen now.

Thanks alot now I can spot ground units near the tree cover, so long SAM!

Don't give up!!! I'm not exactly sure precisely what did it but it's solved now for me. Is your stutter problem when you use electro optical sensors i.e. TAD or MAVERICKS?

I know I know... me too :noexpression:

Why the attitude? Don't you see most pilots here are trying to help? Let's try not to be condescending shall we?

Hey BIGNEWY thanks for chiming in, I'm certain that ED people are looking at the threads so I'm trying to be as constructive as I can. I've seen in another thread that upping your pagefile to 16Gb solves the MP issue for ram usage. Sorry I cannot say for myself as I don't MP, yet. 2.5 is drop dead gorgeous for sure! I just wish I could bomb something without there being major stutters.

I did manage to make it stutter less by going in control panel/ nvidia cp / physx clamped to GPU!!! It is almost enjoyable now, although passing in smoke from burning targets and SAM contrails still causes stutter, not sure if there is any way around this in this release?

:megalol: But seriously... It wasn't like this at all with 1.5 and 2.2. So it's definitely something new, to me at least.

Yes, it's a combination of different things check the beginning of the thread.

Interesting, we almost have the same computer, do you have stuttering when turning on the tgp and making low passes over enemies?