darkman222

I am posting here instead of in the MP section, because this happens in VR only. I am using a Pimax 8KX and a Ryzen9 5900x with a RTX 3090 and 32 GB ram. So I cant invest in better hardware at the moment, given the fact that this system already should be on the upper scale. Settings are almost everything on "low" Since we are running DCS 2.7 performance overall dropped for me. But especially on MP servers. The problem is that the CPU frame time goes up a lot. Bottlenecking my GPU. Causing stutters in VR. In the video you can see that I try to lower the resolution in Pitool and DCS to 0.5 and even down to 20% in SteamVR. But the CPU load stays the same. In the end of the video, I took the track file and played it "offline" as mission from the mission editor. You can see now that the CPU frame time is good enough to have a smooth experience. Of course you can see the stutters in VR only and not on the monitor. This happens in VR only. If I connect in 2D, without VR and the Pimax connected, I get CPU frame times of 5ms. Wich would be absolutely awesome for VR. Has someone an idea what to do about it? Why is the output in VR combined with MP gaming eating up so much CPU performance?

I think you cant compare it if you consider speed and Gs. Flying a 4G turn at 400 kts in the F16 and the F18 will result in different turn rates. That might cause the difference in spacing between the tracers. Try to compare this under the same turn rate between the jets. But I am just guessing here.

Interesting. Because the changelog did not mention any work on the FM. The changelog didnt even mention the FM for the past 2 updates, including this smaller update we had few days ago, thats what I meant.

Cant test it at the moment, so I hope Windows virus detection issues get sorted. Thanks for working on that awesome piece of software!

It was announced. Then the entire announcement was removed. Looks like ITR and onset werent ready yet, so they removed the post and did not mention it in the changelog. EDIT: Not really sure either if they worked on something on the FM but did not mention it. Feels a little different though. Cant really tell.

You can pick custom waypoints on the map via "add waypoint" Or is that not what youre looking for?

Interesting that that topic pops up. I was about to post about CCIP too. I felt that my accuracy was not as good as expected. I practiced on a server on which you'd start in a cold jet. Did a stored alignment. My bombs were off the same amount and direction on every target. Then I took the track replay, created a mission of it, and placed me starting in the air, skipping the startup procedure that way. My bomb impacts were just a little offset. Way less than they were when starting in a cold jet. So I am wondering about 2 things: Does INS alignment quality affect CCIP? Stored vs Norm? And does the CCIP system compensate for crosswind? The server has just 2-4 kts crosswind set for lower altitude, but its clearly not 0. Of course the bomb cant correct itself like guided bombs. But does the system include crosswind in its calculations or does it just assume 0 crosswind?

In deed a very intersting question. I also had that situation quite some time.

You can just open up the list->Ins page on the DED. No matter with external power connected or not. As soon as the throttle goes to "cut off" the INS is reset. At least for me.

Technically? No idea. This is how it looks like, and when you zoom in it is pretty accurate where it places the waypoints. I put the headset on a table, press center VR view. You gotta jump between DTC and DCS then like in 2D. What an awesome app!

It also works in VR. But it has a slight offset to picked waypoints. I guess because of the spherical projection you are picking the points on the map. But if used on servers youre frequently flying on, you could create a DTC for each server in 2D before. Its more accurate in 2D. Just tested it. But why is it minimizing DCS when I klick "start capture" DCS is running full screen in 2D and then minimized.

You have to set the air source to "norm" otherwise the avionics wont be cooled, causing them to overheat. I tried a cold and dark start. But the switch is already in "norm" position. If not, you would have to set it there. Maybe you accidentally set it to off. With engines are running , if you turn it off instantly the "equip hot" light illuminates. I would expect it to take some time to overheat. Dont know how far implementation goes. Just set it to norm and your Viper should be ready for the desert. EDIT: I just realized the switch is in the correct position in your screenshot. Weird.

Just tested it. Works for me, following the instructions. What an awesome tool. Really appreciate the hard work you put into it.

I dont know if anybody else noticed. But before the new clouds most of the dogfight servers had no clouds preset. Since we have it, some servers also use the new clouds. But instead of them causing my GPU to suffer the CPU frame times increase so the CPU cant deliver the frames quick enough for the GPU to render. Which causes awful stutters in VR. I suspect that syncing the clouds between clients causes that. Before the new clouds were used on that server dogfighting against 4 -6 other aircraft was no real issue for the CPU. More than 6 aircraft was the limit for my rig. But now it already bottlenecks with 2 other aircraft or when I am getting closer to one. Do the clouds add to network, and CPU demands due to syncing etc? Any idea? In singleplayer there is no additional CPU load just an increase in GPU load which is okay and expected. I own the worst rig with a Ryze9 5900x and a RTX 3090. Of course the Pimax vR headset is demanding. But again, its CPU frame time whats my problem.

Same for me. I had a TGP and Mavs. The Mav was stuck in VIS too. I could not find a workaround. Also not sure if its correct and I am doing something wrong either.

Dont know what you want to do specifically and how you are using symbology in VR anyway. Time and again I check the progress in VR in general. Crosshair / pipper are still not workling correctly even though they fixed the axis. Dont now how you want to lase if you can even aim. Switch to high video quality to see the crosshair:

Man, what should I say. I started with the Viper 28 years ago in Strike Commander (which was a pretty underestimated sim these times) , then Falcon 4.0 and BMS. I tried out a lot of different aircraft in DCS too. Before we had the Viper I was like: yeah the F18 will be a nice subsitute for the Viper until we get it. Systems work quite similar. I learnt quite a lot about the F18 which is also an amazing aircraft. But now as we have a Viper, I just realized again how well designed an pilot friendly the F16 is. Never fely any urge to jump in the F18 again.

Especially with a Warthog stick you can map exactly like the real jet. Just cycling through the MFD pages with DMS left and right works like a charm.

Exactly- thats why everything is set to low, no oversampling. You wont notice edges anyway when fighting. And avoid motionsmoothing at any cost. It just smears everything.

What exactly is the problem? I mean I have a great gaming PC but DCS and the 8KX is still way too much load on the PC so everything that smoothes the images is turned down or off in my settings for maximum performance and framerate without motion smoothing. Guess thats the way it is now until in 5 years with Vulkan and an RTX 5090 Ti

Yes Bignewy you are right. No G lock discussions here. Flying on both currently available dogfight servers I'd say the Viper feels more agile like you would expect her to be.. And commonly known Viper tactics and Viper BFM starting to work much better right now. And if it does thats a sign that the FM is going in the right direction. Maintaining airspeed works a lot better and is a lot more rewarding. Also gaining airspeed back is much easier.

Common ED really? Why? I also tried to edit the new LUA file that came with the update. Does not work either. I like to fly on a dogfight server where you'd jump in a new aircraft every 5 minutes because you dont live for a long time. It takes longer to program the CMS profile than actually having a missile dogfight. Please unprotect that file until we have a DTC, honestly.

I would not expect lots of improvement in precision. If it seems quirky in DCS then test the same motion with the cube demo app by leap. It will have the same results. Usability like fading the hands out when using the stick etc, thats stuff that ED can implement. But the rest relies on the leap motion code I am afraid.

I dont understand why people keep asking. People at ED work on it, they know about it and they wont release anything until it is done and rock solid. If someone finds new errors again this endless discusion will start all over again. Nobody here wants that and nobody at ED wants that for sure either. The most important question is if the Viper pilot also gets an updated G behavior. Because if not, a more accurate FM will also help to make the pilot blackout earlier.

Okay, threads being merged. Thats fine. But it was my orignal thread I started months ago in the bug section being merged into this new one, and the orginal title and tags got lost. So it has now a very undescriptive and misleading title like "egg mode" but it was about difficult locking behavior of the ACM modes including JHCMS. Maybe that should be corrected. Like I said , the tags are misleading now too, there are a lot of track files and videos about the issue and it also was moved out of the bug section that way. EDIT: I changed the topic back to the original one, as I was the thread starter