darkman222

Long answer short: What you see without motion smoothing in 1) and 2) is the GPU struggling to get the desired frame rate of either 60 fps or 75 fps. These are the steps. If the object is distant its steps if the object is close, bigger steps, which could be seen as blurry. Install fpsVr from steam. Otherwise you are just guessing. You will realize on the left display of fpsVr when the stutter occurs you dont reach the target frame rate. Defined by your Hz setting. 60 Hz wont do any help if your GPU cant reach it. But the chance that the GPU can reach 60 Hz (60fps) is higher than 75. And if the GPU theoretically can reach it, the CPU might be the limiting factor. Stutters will remain on any Hz setting if your rig cant reach it. Set everything to low for a test and try if your PC , GPU together with the CPU, can reach the target frame rate either at 60 and 75 hz. 4) Smart smoothing needs only half the frame rate. Thus your PC renders 45 fps a smart algorithm interpolates it up to 90 Hz. But here is what distracts me, take the F16 or F18 activate HMCS and look 90 degree over your shoulder. You see the numbers getting washed out by the algorithm. And thats the same thing it does with the bandit in a close combat dogfight. No idea concerning the brightness though. Had it few times, but seemed to be a bug and gone after restarting. Maybe try a different backlight setting in Pitool.

Like I said. I never had that. Maybe someone will recognize what it is. You can use geforce experience and press alt+F9 when it happens. It saves a video in the videos folder under your user name. You could upload that. Sorry, I have no better idea.

I am pretty sure the F16 manual does not have this procedure mentioned

Any news or progress in the SLI + VR headquarter?

How is SLI at the moment in DCS? I was about to open a thread about SLI because I am interested in that technology. But no need to ask how SLI is in DCS if it is not working currently.

If its a fast stutter it could come from the CPU or GPU failing to deliver frames. But it rather sounds like an issue with your lighthouses. I sometimes get a slow pulsating back and forward movement. Like pulses in 2 second intervals. Happens when I put the headset down, but leave the headset and the tracking running. Not using the headset but leaving it running seems to break tracking over time.

@Frederf Sure the funnel is an alternative backup system. @Spurts and @WHOGX5 thank you for the explanantion. This is why I like the community here so much. There is always someone giving the right hint. This brings up another test and a question. It seems like the pipper appears exclusively at 4000 ft distance. Regardless of my own airspeed. (see video below) I must confess I was not fully aware of the short range of the M61. You can see the pipper being displayed although the shot was kinetically impossible at a speed of 800 kts. But in the second test at a speed of 300 kts the pipper disappeared again at a distance greater than 4000 ft. Regardless of my speed. But the bullets were able to hit the target. Question: Is it realistic? Shouldnt the pipper stay visible until there is really no physical possibility for the bullets to hit? I know the second test is unrealistic, but you see that I had to guess where to fire without the pipper. Wouldnt that be a disadvantage to hide the pipper in that case? Or is it just not implemented yet and the pipper should represent if a shot opportunity is kinetically possible or not? What it is doing right now is stubbornly being displayed when under 4000 ft and hidden at distances over 4000 ft. Why would you do that and take it away from the pilot? A fighter pilot should be able to have a look at the distance in the HUD and judge by himself if the shot is possible or not, right?

I have a video and a track. Looks like if the trailing edge flaps of the F16 3D model is taken off / damaged there are polygons drawn to a very distant point in the DCS world. Happens in steam VR using a Pimax 8KX. Track: https://www.dropbox.com/s/l1cuuilqatjkum5/mobettameta's Dogfight Arena v1.24-20210725-150303 polygon bug.trk?dl=0 Video:

Ryzen 9 5900x not overclocked. And an RTX 3090. 32GB of RAM. Using FPSVR i can see most of the time the CPU being the bottleneck. Until we got the new clouds it always was the CPU being the issue.

What do you mean out of range? The ranging reticle line is solid for 1/4 only and the FCR shows 4000 ft when the pipper disappeared. I can almost throw a stone at him.

Sorry, am I missing something here? Why do you want to enter the wingspan for gunnery without target lock? The F16 is not a WW2 aircraft. If the level 5 pipper is working correctly wingspan is irrelevant.

Its still not working after July 23th hotfix.

I cant judge whats happening in @PicklePicklePickle 's case. But have you watched the videos I posted in my thread in the bugs section? No high aspect chase maybe you can call it a high speed chase. But I dont think 500 kts is too fast for a gun solution though. You can see me pulling 1,5 G the bandit maybe the same. The pipper drives around even below the 9 G line which is clearly not correct. At second 5 in the video you see the pipper describing a circle around the bottom of the HUD which does look totally wrong as necessary lead for me. Thats why I said I have a feeling when to trust the pipper and when not. But this is not how its supposed to work, I hope. Weird stuff happening I would say every one out of five guns engagement. So it can really happen that you stop believing in your abilities... Track:https://www.dropbox.com/s/iibpqwjmknsvyzb/mobettameta's Dogfight Arena v1.20-20210520-002317 gun pipper1.trk?dl=0 Video:

I gave it a super quick try right now. I was undervolting as much as MSI afterburner allows. If undervolting would make an impact I on my rig I should have experienced it in tonights DCS session. But unfortunately there was no relief for the CPU. FPS VR just showed the same patterns of the CPU bottlenecking in multiplayer.

That sounds very interesting but logical on the other hand too. I have a lot of CPU frame time issues. Most of them seem to come from multiplayer CPU load. I almost gave up and my weapon of choice became 60 Hz mode for the Pimax. I never really thought about overclocking the GPU because I know the CPU is bottlenecking my system. But going the other way underclocking sounds interesting. I might want to give it a try when I have time for that. Thanks for the detailed post so far.

There is a DCS Pimax thread out: You might want to read through the last 8 or 10 pages. Maybe check my posts for CPU frame time that might bottleneck your rig. I have a comparable system and multiplayer kills CPU performance. Long story short: If you are up for pure performance, the lowest chance of stutters: Everything to low, except shadows and textures. And try 60 Hz mode.

I would consider it a general issue. But as you say it only happens in the F16. I cant think of anything that makes the F16 different from the other modules. As a desperate try to help: you might try if the tinted canopy or the clear one in the Viper options menu make a difference, but I doubt it. Well I guess you'd have to wait until other VR users get the same issue then...

Since when do you have the issue? I have issues since the 21.07. update. But no shaking instead the polygons of the F16 are partially drawn towards the virtual camera. I am still investigating when that happens. Does not sound like the two things are related though.

What headset do you use? I use DCS in VR only (pimax) and did not have issues. You can install fpsVR from steam to see if the stutters come from low CPU frame times. Which means the CPU bottlenecking the GPU. There are aircraft which have a bigger impact on CPU frame time. But the F16 is none of them.

The level 5 pipper (dot) is the only thing that is as precise as the "cross" in the F14. But the thing is twitchy like the pipper in the Hornet was in its early days. It is kinda bugged. It only works if the target is not maneuvering too much and if you are not too fast. I have the feeling it is unreliable over 400 kts, starts to jump around, then disappears. The difference between MP and SP is that human opponents tend to try outrunning or jinking like crazy if they get locked. Unlinke AI aircraft that will do their nice and steady unrealistic flying which supports the pipper in its current state. Meanwhile I developed a feeling when the pipper will come up and when it will disappear again. Or better, when to trust it and when not. I already posted it in the bug section and it is being investigated. EDIT: I watched Wags video above, and it has been ages now when I think I remember the pipper being as stable as in the video. Seems like it got bugged while the F16 is being updated over time.

No idea whats wrong on my end. I cant use the finger to push buttons ins any module. F16 F18... does not work for me.

@Fisu_MADhow did you get it working that you can actually touch buttons with your finger instead of using the fist as laser pointer? Even after yesterdays update I cant do it. It looks maybe a checkbox is missing in the option for leap motion. I have "enable" and "arm visible" activated.

If it is not your mission, you can modify the steerpoint using the number 4 button on the ICP. Set the steerpoint to its actual elevation checking it out on the map before. But you need a targetpod then to use the cursor zero CZ function then to get the CCRP target back on ground.

Technical discussion aside. The only problem is a thing called user experience. Something that used to work before is not working anymore costs the user time to investigate and to evaluate if he is doing something wrong or if something was changed or even if something is bugged now. I am totally fine with it being changed for realism. As the manual says "The HARM may be loaded on stations 3, 4, 6, or 7, but is only flight-certified for stations 3 and 7." Could be a little more clearer if it said something like "therefore it cant be employed". I dont know if I missed it, but mentioning it in the changelog would be nice too.

SAM (staying in CRM) mode does not alert the RWS of the bogey. STT will. Tested it some versions earlier. If it does now, its a bug then. Looks like its only a thing affecting the target designator box in the HUD or JHMCS. Next update it'll be fixed. Fingers crossed