TZeer

@Flappie But what is your GPU usage? I went from 63 fps and up to 320 fps without changing any settings.

Thats because you are not keeping your crosshair on point the time it takes the CPG to slew the TADS over to it. I did the same mistake at first. The system slaves to wherever the pilots LOS is. If you move this point before the CPG has been able to complete the slew. It wont look where you gave the command. Since you don't move the head, but use the whole chopper this becomes a problem. As you struggle to keep it steady, this makes George slaving the TADS all over the place.

Ok, but what was the utilisation of your GPU. Is it at 40% or 90%? And are you refeering to your first track posted in response to me? I guess 56FPS was with your normal settings then, and 180 was with reduced settings? And do you have any max framerate active on driver levels? I had Nvidia before, and I know there is a setting somewhere for maximum FPS.

@Flappie You could try put a single unit into a very very deserted area of Caucasus or Nevada. Any map that is a low resource hog. Also on a part of the map that is not used yet. No buildings, no trees etc. You should then be able to get the most out of the card. My guess is that you need to have quite a bit of extra "horsepower" left for this to trigger. Only the map, I would get 64 FPS. With the Huey cockpit roughly the same. A-10CII moved it up to about 70 FPS, and F/A-18C gave me about 90 FPS. The more intensive the cockpit/scene was to render. The higher the FPS went. Thats why I got such an extreme difference on the apache cockpit and external view. I was not able to reach or go past the limit of 180 FPS with the apache cockpit. You need to see how much GPU usage you get from your 1080Ti when running 180 FPS.

@DmitriKozlowsky Had a look at your track file. Some observations. - You are not stable when you are firing. - This again makes it hard for the CPG (George & Human) to keep the laser stable on the target. - You can see this on your TSD and the CPG's LOS/Cursor. It jumps up and down the screen. This tells me that the laser is missing the tank/object and hitting whatever is behind it. From the angle you are firing and shooting the laser, the laser hits the terrain behind the target. When you tell the CPG to target something, he finds the target, but he is always a little off, and uses a few seconds to finetune the aim. You see this in the TADS. The crosshair from the TADS uses a few seconds to align perfectly on top of your target. This is perfectly normal, is it simulates a real person lining up the laser on target. - Many of your missiles are missing due to the simple fact that after the missile is fired, the laser stops lasing the target and hits something behind, due to the mentioned unstable flight/hover. This again throws the seeker in the missile off. Laser comes back to target, but then the missile has already passed the seekers contraint in the missile. And it just flies dumb far above the target and into the sunset. - Last observations. Easy on the George AI. You are slaving, de-slaving nonstop. Put the center crosshair of your IHADSS on the spot you want George to search. One simple command and he should come up with a target list. From what I could see you are not running Track IR or anything, and few of the times you where giving the command, the center crosshair was pointing into a forrest or ground before the mountain. Giving you no targets. Hope this helps.

@Hiob & @Flappie That worked!! Thanks Hiob. External FPS in Nevada went to over 300 FPS! FPS inside Huey, A-10CII and F/A-18C went skyhigh! And @Flappie, the testtrack with the Patriot radar went to around 320 FPS or something!!

@Flappie Tested it. And the FPS did not change. But I think you misunderstood me. My point is, the FPS should have been much higher! Something is making DCS not use all resources it has available and dumps the FPS. It's very easy to replicate. Please have a look at the test track. It's of the Apache in Nevada. Cockpit view from CPG, 150+ FPS. External view 60-70 FPS. Also have a look at your resource use on your computer if it behaves the same. When I go external, my CPU usage and GPU usage drops significantly!! When I move to cocpit view again, my GPU and CPU usage goes up again. cockpit_external_test.trk Edit: I just did a quick test with the Huey, F/A-18C and A-10CII. None of them are able to get above 100 FPS. The Huey was stuck at 63 FPS, A-10 around 70 FPS, and the F/A-18 was dipping around 70-90 FPS. And both my GPU and CPU was far away from their max utilisation. Something strange is going on.

This is the utilisation of my system during the screenshots. Cockpit CPG with TADS - 156 FPS - GPU Usage: 99% ,CPU@4,3GHz External View Apache - 56 FPS - GPU Usage: 21%, CPU@2,4GHz

Here are some more examples. External view in Nevada of the Apache: 58 FPS. Cockpit view from the CPG seat with TADS running: 156 FPS You can basically look at the same scenery and get completely different FPS. Based upon if you are inside the cockpit, or in F2 view.

Noticed this on 2D mode while messing around in the mission editor. Normally I fly VR. My specs: AMD 5800X 32 Gb Ram SSD Drives AMD RX6900XT For some reason when moving the camera around, the FPS behaves crazy. I can have 170-200 FPS looking down at an area, turn the camera slightly, and the frames drops to 50-60 FPS. At the same time the GPU utilisation drops from 80-100% and down 16-20%. Turn camera again, and the frames and GPU usage comes back up again. I have attached 2 screenshots, almost the same. The one with blue skies in the horizon has 75 FPS. The one with a slightly more angled down view, has 179 FPS. Now, you could say it's due to more "horizon" in the view of the first one. But here's the kicker. If I zoom in on the radar of the patriot site in the background. I get..... 50 FPS. Looking straight down on nothing but the radar. I would expect HIGHER FPS. As it should be easier to draw a single patriot radar, then the entire scene. I can have the same issue inside cockpit vs external view. Inside Apache cockpit, 150-180 FPS. Move to F2 view, 60-70 FPS. Back into the cockpit again, 170 FPS. This is the "top down" view on the patriot radar, gives me 50-60 FPS. I have noticed this on different maps, Nevada, Caucasus, Gulf and Syria. Scenes where you would expect lower frames are pushing out 140-190 FPS easily. Change to a single UH-60 external view in Nevada. Tanks down to 60 FPS. Goes back to internal view in the Apace, shoots right back into 140-170... I use Skatezillas tool to do the patching and cleaning of the DCS install everytime.

Are you sure your joystick bindings are working ok? With so much problems you could have hardwareproblems with the buttons. Like "sticky" buttons, or lack of contact when pressing. Reason I mention this was your "3 buttons" binding to make 1 simple command. It can work, but you have 3 potential places where you can get errors. The correct way to do multiple commands from same trigger is to set up a separate button as a "modifier". This is used to toggle the function of the buttons you want multiple functions from.

Hmm, am I seeing this correct? You need 3 different buttons pressed at any given time to make George do anything? Anyway, from my experience. All I need to do is: Activate George Menu - Whatever button you have it slaved to Tell him where to look - Up Scroll to correct target - Up/Down Activate Target - Right Consent to FIre Weapon (If state in yellow) - This I have mapped to my trigger+whatever button you use for creating secondary commands. You do not want to select missiles youself. If you do the above before messing with any other settings you should have no problem.

This post gives very little info om what you are doing, and where it goes wrong for you. Need some more info.

1- The pedals has a very distinct deadzone in the middle. If you open up the VPC Joystick tester, and move the pedals from one side to the other in one smooth motion, you will easily see the deadzone on the curves. It wasn't very noticable when flying with default pedals and settings. But after the dampener mod and no need to recenter after trim, it became very noticable. Specially trying to do tiny corrections near center. Default it was set at 5% on mine. This deadzone can be adjusted inside the VPC configuration tool. See attached picture. 2- Install the dampener mod. No need to drill any holes. And no need to move the spacer as mentioned in the video. You can simply unscrew the one from the bottom, and replace it with a longer screw, since the spacer is threaded. Took me max 20 min to install once I had gather the few bits and peices. After you have installed the dampener, don't do as I did, and put the restriction at the lowest. This will make the "stickines"/"grip" from the cylinder very noticable. Instead turn restriction slightly up. This will make you use more force. But the "stickiness" is gone. Since the force you need to apply easily overcomes the initial "grip" on the cylinder before it moves. And since there is more restriction, the pedals will not "overshoot" as it did with minimum restriction setting.

Thank you for the idea @firefox121, I tried it but wasn't for me. But I think I have come up with a solution. I increased the stiffness in the damper. I thought it would be best with minimum restriction. But that made the normal "stickiness" from the cylinder very dominant on small corrections. Increasing the restriction made the "stickiness" go away and much easier to do fine adjustments. Will have to do until they adjust the FM.

I have had some saturation on it, but not much. And It has not been to much of a problem while flying. Although it is quite sensitive I have been able to fly, hover etc. But on the ground it's just mental, I guess they'll come around to fix it sometime. I will try to add even more saturation on it, and see if it helps.

So, I modded my virpil pedals with a damper and took of the springs. This way I don't have to recenter my rudderpedals between trimming. Yes, I also changed the settings in DCS to pedals without springs etc. Here is the kicker. I'm able to fly around, go into hover and all that jazz, but when landed and trying to taxi down the runway, helicopter is a complete "ass". Slight inputs on the rudder/torque to turn makes the whole tail to kick out, try and counter it with a slight touch, and it overshoots like crazy. Makes it impossible to taxi either out on a runway or back to parking after landed. I'm also seing some strange behaviour with the SCAS on the torque. When collective is completely down, no hand on stick, and everything is centered, I can see the green indicator for the SCAS is working. It's not enought to make the chopper turn. But any input on rudders make the tail kick out, trim release pushed or not. Is this normal? I know it's WIP, but the way it behaves on the ground is just crazy.

At work now, but had same issue with my Reverb G2 with new drivers. Intense strobing effect. It seems to do half refreshrate of what is actually set in the settings. 90Hz gave slightly more strobing then default 60Hz, and 60 Hz gave some intense strobing effect. Makes me think that sometimes 90Hz give 45 Hz, and 60Hz gives 30Hz.... And like you, it's a hit and miss of the VR set actually works. Have to restart WMR multiple times until image is ok in WMR. And sometimes it's just black....

It's actually a bug on the PNVS system right now. It's very noticeable when flying VR. Although the TADS is not as fast as the PNVS, it's much smoother and more comfortable to use. The PNVS in VR has a very distinct stutter when moving your head around, making it impossible to use in any meaningful way.

Clear out all axis settings on your setup. And then assign each axis to its appropriate input. I don't think I have ever installed a module where one or two axises have not had two different inputs assigned to it. Specially true on rudders/pedals. As DCS likes to auto assign some rudder/pedal commands to analog inputs located on the throttle or stick.

Helicopter AI in general tends to be lacking But yeah, I don't think ED has said anything about the helicopter AI at this time.

That's actually wrong. With 90 Hz you can run 30 as well. I have done it multiple times. I have also run with 60 Hz with no MR with FPS mostly on 60 FPS. But sometimes it drops, and that just breaks immersion for me. I actually have it on unlocked now. Just messing around in Nevada to get the stutter to a bare minimum. I can easily reproduce the effect by simply doing what I mentioned in earlier post in Nevada as well, but it is greatly reduced. What I'm asking is if someone else is having the same experience. Simply turning the head 90 degrees, looking out, induces stutter. If you lock the MR to 45 FPS, one can see the framerate dropping below 45 while your GPU and CPU frametime is staying well below the 22ms limit. CPU is often around 10-12 ms while GPU is 16-19ms. Yet I get "Target missed". I can actually see the stutter getting better as I move my head gradually back to center in my AH-64. Which I find strange, as I would think getting more of the detailed cockpit in view would increase load, compared to just looking out to the side into the forest. It's just as much forest looking forward... Trying to figure out if it's actually the CPU missing the target, or if it's lack of VRAM that is triggering the stutter.

Ok, so have slight "issue" going on. Maybe someone else has seen this behavior. Flying the AH-64 in a area with a lot of forest. Looking straight ahead everything is smooth. 45 FPS in the toolkit overlay. Looking left/right and instant "stutter". I even see the FPS goes down to 40-43 FPS. It also shows "Target Missed" quite often. But at the same time my frametimes for my CPU and GPU are well below the 22ms needed for 45 FPS. Looking at my VRAM it's maxed out. I'm running RX6900XT OC @ 2600mhz. Also using 0.8 FSR and simplex mod. Clouds to medium. Is it simply due to my VRAM getting maxed out?

@Anhel big difference in visual quality of the cockpit with that mod? Even though I run a RX6900XT, I'm always maxed out on the VRAM usage. And when I'm flying over forest area, for some reason I get smooth frames looking straight ahead. But turning my head 90 degrees left/right I always experience stutters. Not so much in dessert areas. I can also see this behavior on my FPS. Having the OpenXR toolkit open I can see the reported framerate is 45 FPS. But turning my head it starts dipping down to 40-43, inducing stutter. Toolkit also report "Target Missed" even though my frametime on the CPU and the GPU is nowhere near the limit of 22ms for 45 FPS. CPU is is usually around 10-12 ms telling me I have 60-70% pverhead while the GPU is often around 16-19 ms.

From what you are typing, you are either using the system in a non-optimal way, you are fighting against it. Or you have some bugs. - I don't think I have ever been "beeped" at while flying, if it has, it's so rare that I have not noticed it. Wich is a way for the system to tell you that you SCAS is at it's limits of where it can operate, it's saturated. - I'm not sure if there was any hold modes for hover before this latest patch. As Wags/ED stated that the hold modes was not implemented at launch. I tried using it myself, but didn't feel it did much. As much of the work was trimming out the chopper as you transitioned into hover. Hitting the ATT HOLD after that was done did not give me much. Except a box around the speed indicator I might be wrong, but I never noticed anything. I just came to think of some things. Have you mapped all 4 trim (5 if you use trim reset) buttons? Force Trim Release (Normal Trim), ATT Hold, ALT Hold ( Not implented yet) and dissengage trim. The last one is not the same as trim reset. As it dissengage all HOLD Modes, ATT and ALT. Trim Reset resets all active trimsettings made by using Force Trim Release. When you trim in normal flight, do you remember to center your stick and pedals before applying new inputs? This could explain you "beeps" if you for example forget to recenter pedals, as it will saturate you SCAS on the tailrotor, since you are not applying inputs because pedals has not been recentered after you have used trim. I did it myself a few times in the beginning. Hitting trim, centering my stick, but forgetting my feet. Just to experience nothing happening when trying to apply some torque to the tailrotor