serpent64

What is this program, how do you use it,.........and where the hell has it been all my life?!?!?

Problem Solved! The culprit was SimAppPro from Winwing. Not the App itself but an after effect from installation. Appearently SimAppPro installs a script that occurs within DCS to export the data to the App. I had ordered an Orion throttle to replace my Thrustmaster WH and it arrived about 10 days ago. I installed the app in order to check calibrations and functioning, but then decided it wasn't needed for my intended application. Hadn't touch it since. Late last night, I stumbled across this thread: Since I had not been running SimAppPro, it was low on my suspect list. I immediately went to the mentioned file, and sure enough, the two line of script were there. I nullified them and ran a test. CPU frame times dropped to < 8ms without a single spike to be seen. My rig is back to its old self again. Thank you all for your help.

Thank you, I am familiar with that thread and already have implimented most of the recommendations a few months ago. This morning I did try the threads recommended NVidia settings which resulted in a slight decrease in the frequency of CPU frame time spikes but overall image quality decreased. So far for me, no sound issues. Yeah, I was suspecting the cause may be a Windows update and a rollback will may be my next test. NVidia and Steam VR updates were pushed out after my problems started so I don't believe they're the cause. As for SteamVR reprojection, I'm assume you're refering to Motion Smoothing. I did try turning it off which did help slightly with the distortions but of course, all objects began to blur. If SteamVR reprojection is different from Motion Smoothing, how do I turn it off?

Hello all, Has anybody else noticed/experienced a substantial decrease in VR performance in DCS in the past week to 10 days? My set-up started to act strangely about a week ago and I can’t nail down what’s triggering it. Bottom line is I’m suddenly bottlenecked at the CPU with frame times in the mid to high 30s ms where before there was no issue. Here the background info: CPU: Intel i9-10900k OC’d to 5.1 GPU: 2080 TI w/ 11Gb VRAM RAM: 32gb @ 3200mhz Headset: Valve Index w/ Steam VR Beta DCS ver: Open Beta For months, everything ran smooth. With PD in DCS at 1.0, refresh set at 90hz, and Custom resolution at 100% Global at 150%), it ran at an average of 45fps with a few leaps up to 60fps in single and multiplayer flights. See settings below. I then came across Lucas’ now defunct vid on setting PD low in DCS and high Custom Res in Steam VR. I gave it a shot and did pick up about 5fps with no issues, so I left it there. Yes, we now know where the performance increase came from, but the bottom line is that I had no performance issues during single or multiplayer flights. Then, a few days later, I began to notice a problem when looking through the HUD (F-18) on public multiplayer servers. Not the typical stutter, this is more like a sporadic distortion similar to what you would see in a mirror at a carnival funhouse. It makes gun tracking with the pipper impossible. My FPS’ also dropped to 30. Switched everything back to my original settings. No change, still 30fps and sporadic distortions. Ran some test last night using FpsVR. In singleplayer, there are constant CPU frame times spikes up 35ms in the red zone while GPU frame times stay green at 10ms. CPU usage was only 12% max though. FPS averages about 40. Reprojection was in the 55 to 65% range. Multiplayer, as expected, things just got worse. CPU frame times did not fall below 50ms. Backed my original settings down a bit to what you see now (86% Custom Res at 80hz) and the only thing that improved reprojection dropped to 35 – 45%. CPU frame times are still high, but the frequency of spikes dropped ever so slightly. Sporadic distortions are still there. FPS still at 40. I’ve tried these steps without any improvement: 1. Updated Nvidia driver 2. Updated Steam VR beta 3. Ran repair of DCS 4. Started to throw things Can someone please tell me what am I missing here, because at this point for me, DCS is unplayable in multiplayer and borderline in single. Very frustrating.... since just a few weeks ago, life was all good.

Test

This is not integrated at this time. Hopefully it will be in the future. The AIRBOSS script is more realistic at this point.

You are correct.

LShift+U it is then. Thank you.

First off, I understand SC has been out only for a few hours in early access and I'm not sure if this is even a bug. I just want to see if I'm doing something wrong here. I've also seen all of the recent press release videos posted. Here's the scenario: DCS Wolrd Open Beta F-14 Instant action mission - Carrier Quals CVN 73 - Caucasus Map Acft loads (Hot start) in 6 pack parking. Taxi short of Cat 1 or 2. I'm aware that yellow shirt will not give the F-14 "Unfold wings signal." I sweep the wings forward while simultaneously following signals from yellow shirt to move forward/left/right. Stop acft on signal. Deploy flaps while holdback bar is attached. Kneel the acft on signal. Roll acft forward on signal. Stop acft again on signal. Retract launch bar on signal. Recieve "run up" signal. Run throttles to Mil or Max and wipe the controls. Go to comms menu, select ground crew, select "Salute." Cat officer goes through his checks, touches the deck........then NOTHING.......I'm just sitting there burning gas, making noise, and helping ship make an extra 5 knots by towing it........as my AI wingman launches of an nearby cat. Also tried selecting "Launch request" after the failed launch and no change. Sooo.........?:dunno:

I was about to record a track file this morning and oddly the problem seems to have stopped...at least for now. If and when it happens again, I'll post the file immediately.

Just wanted to know if anybody else is experiencing this. Granted I've been away from DCS for the past 2 weeks. Got the latest beta update and now I've noticed that when I jump in the Hornet in-flight or pre-started on the ground (single and multiplayer), I get a canopy warning on the Left DDI. I double check the canopy switch and sure enough, the canopy isn't fully forward and sealed. Happens every time now. When did this change happen or is it a bug. Just asking.

Wasn't reporting a definite bug, just wanted feedback from others. Next occurrence, I'll post the file. Checked Tacview, no countermeasures deployed by either bandit on approach to the merge. @Lancel & GGTharos, what both of you are saying is true for the early versions of the AIM-9, but with the introduction of the "G" model with SEAM (Sidewinder Extended Acquisition Mode), the system is a bit more intelligent and provided the AIM-9 seeker head with 2 search options. The first allowed slaving the seeker head to the radar when locked when the missile is in the Caged/Slaved mode. The seeker would look in the direction of the radar for a heat source. If it detects the target, the pilot uncages the seeker to confirm a good lock and then launches. If the seeker does not detect a good signature, it would still continue "look" in the direction of the locked target while caged. If the pilot uncages the seeker, it is free to lock on to any target within it's FOV. The second option is Caged/Uncaged Bore-sight where the seeker is fixed to a bore-sight view when caged(our current capability) or when uncaged the seeker will mechanically sweep through a wide area for a suitable signature/target to lock on. I don't know how it functions IRL F/A -18C but that's how it works for IRL for the F-16C/D and F-15C.

Ok, riddle me this - I noticed quite a few times when dog-fighting, usually on multiplayer, that the 9X seeker will not always slave to the radar locked target. Example, approaching the merge with two separate adversaries head on at about 3 miles, AIM-9s already selected. Switch to ACM Bore-sight mode and maneuver aircraft to place one bandit within the bore-sight circle on the HUD. 3 out of 5 times radar locks up intended target while seeker head tracks the other non-intended target. Unlock target and try again (bandits are now uncomfortably close now), usually same result. Maintain radar lock and re-cage and uncage seeker (bandits are now ridiculously close as I watch THEIR missiles come off THEIR rails :cry:), again usually same result. Now before anyone says,"the seeker is tracking the hotter target." Slaved means Slaved, the seeker head should follow the radar target in slaved mode. What gives? :helpsmilie:

If I was your LSO, I would have dove overboard off the platform after waving you off..LOL. Good recovery :thumbup:

That's your problem, you're too close abeam of the ship. Need to be 1.0 to 1.1 nm abeam at the 180. At that distance and 30 degrees AOB, will place you at the start of the "groove."