dax
-
Posts
91 -
Joined
-
Last visited
Content Type
Profiles
Forums
Events
Posts posted by dax
-
-
I don't think it is possible.
But even if it is, it would make you really sick... I wouldn't recommend that.
Sent from my SM-G950F using Tapatalk
-
So I`m tired of checking any configurations in DCS. Till it would be resolved I won`t buy anything from ED and third party for DCS. I know that my voice is insignificant, especially that this issue is random and most users won`t complain. But this shows that DCS is a mess.
I have Ryzen 5 3600, RX590, SSD drives in my computer.
You're definitely not alone.
I've been buying and playing DCS modules since the original Blackshark, more than 10 years ago.
But now I stopped playing a few months ago. Just tired of spending more time trying to tweak settings to improve VR performance than really enjoying the sim.
My last purchase was the Viper, and I will definitely not buy anything else until performance gets significantly better.
-
+1 !!!!Just to be clear, please fix the perf issues in VR, I really don’t care about anything else right at the moment. -
Working fine for me, and on a pretty old rig. (6700K @4.6ghz, 1080, 16gb ram, Rift-S, msaa x2, pd 1.3)I personally cant believe people are trying to run this sim in VR on 16gb?I keep 40fps most of the time in single player.
-
Same for me.I made some tests on mp server and also single player with tomcat and viper today. my fps problem seem to have gone. I played 2-3 hours with good fps.Just played VR for 1.5h with various F16 instant action and training missions and fps seems to be back at the 2.5.5 level.
-
Not entirely true, SAM or STT or TWS develops a track. A track is a mathematical object which is smoothly interpolated at each burst of update information. It is this track and not the detection data that is displayed on HUD and MFD. And the track exists at all times, not just when new data is available. As long as the target motion is uniform updates five times per second or once every 5 seconds are indistinguishable by viewing the display. As information about the track grows it's not just linear interpolation but its first and might be second derivative.
Thanks for the detailed comment! I didn't want to write a long story yesterday... ;)
But even if track is extrapolated, and whatever the interpolation order, some error will remain. For 1st, 2nd or 3rd order, the speed, acceleration, or rate of change of the acceleration will have to remain constant for the interpolation function to extrapolate position correctly. And the higher the order, the longer parameters have to remain constant. It's very unlikely to happen in a dogfight.
That said, as I don't know neither the exact behavior of the radar, nor the implemented one, there may still have an issue in the DCS implementation. That's why I wrote "probably" in my first post.
A good test would be to track (but not in STT) a target flying straight at constant speed and check if these big bounces are still there. If yes, there may be indeed an implementation issue.
-
Yes, in STT mode, the radar beam is focused on a single target and tracks it, in order to get continuous updates.
The drawback is that you then become blind to potential other targets.
-
I noticed the same behavior, and I guess it's probably normal.
In RWS mode, the target is not illuminated continuously as in STT mode. Hence the target location is only updated when the antenna beam illuminates it.
-
Afaik, it's not really released yet. It's a Beta version.It's a fun module but I honestly think ED should have held off release for another month or so to complete more features and iron out a few more bugs.Those who prefer a fully functional (almost) bug free version, can wait for the official release version before downloading.
Then, those who want to get a taste of it asap, and are ready to accept missing features and bugs, can get it right now. And it's probably the majority of simmers.
So ED let us choose what path we prefer. I think it's nice like that.
Viper development has been quite fast. I initially didn't expect having so much, so quickly.
-
Just wondering: is there really any difference, in visual quality and/or performance between setting PD 1.5 in game and SS 1.5 in debug tool?I'm afraid your GPU is on the low side.I didn't tried Gulf Map in VR yet.
But I have 7700K, 32Go RAM, GTX 1080 Ti and I get solid 40fps and I can push details.
SS x1.5 in DebugTool, MSAA x2.
I can identify planes on parking from 10 000 ft.
M-2000C in blue sky is a dot between 6 to 7 Nm.
-
Besides the fact that there are two scenes to render, as there are two different viewpoints, setting PD to 1.4 increases the total number of pixels by 1.96, not just 1.4, as the oversampling is performed in both vertical and horizontal directions.
-
I would say exactly the same...You pays y're money and y're takes y'r choice. But I plugged in my Rift S and to borrow a quote from Jensen Huang: "It just works". I've not had most of the problems experienced by some others. One thing I have experienced which has not been 100% is very occasional white noise type screen flashes. But this does not happen very often. And the flash is gone as quick as it happened.Is it perfect? No. It is good? Yes. How does it compare to the Index and Reverb, specifically in DCS? Currently, I don't know.
-
Indeed. If it was included, it would for sure have been announced. And I don't see any significant difference.
-
Nineline just said: "In the move to the 2.5.5 branch, the VR performance for the ED maps, unfortunately, did not transfer over correctly. The team is aware and will be working to move this optimization to 2.5.5 as soon as possible."
I guess we'll have to wait a bit more than expected...
-
Indeed.
Caucasus is far nicer than Nevada... but more taxing on hardware also :)
-
Honestly, although every little improvement is good to have, I don't expect this to be a game changer.
Even a 50% improvement only allow to go from pd 1.2 to between 1.4 and 1.5, all other things being equal. That's not really a massive improvement. :)
-
Many discussions everywhere about this...On my first two days with the Rift S I didn`t see those white flashes while playing DCS. Yesterday I saw them about 4-5 times in one hour flying.Could someone be so kind to point me to a thread, maybe in the Oculus forums, where this problem is addressed?
https://forums.oculusvr.com/community/discussion/76168/white-static-flashes-in-rift-s
-
I have it plugged in a blue USB since the beginning, and have occasionally both white flashes and black screen issues. So I don't think it is related to the port type.I was getting black screen in my Rift S after taking off and closing Oculus Home and then putting back on. Had to restart the Oculus Service 2-3 times to get it back.Had my USB plugged into the red port, changed over to blue and it seems to have helped it immensely. At least so far, I only did this yesterday afternoon.
However, both issues seem to happen randomly and not often... so far it doesn't bother me that much.
-
Another interesting thing I discovered is that even with this gaming rig and its 1070 and I7 9600K running at only 4.7Ghz I am still getting a solid 40+ FPS in DCS with pretty middle of the road settings. I never thought I could reliably play in VR on this rig but so far its doing really well.
I think for those with less than killer gaming rigs, the Rift-S really scales well!
Madmatt
Hmmm, just a minor comment: 9600K @ 4.7GHz is about one of the fastest CPU available for single threaded applications... which DCS is almost. Fastest single thread CPUs are @ 5GHz with good watercooling. So less than 10% faster than your 9600K.
Therefore it's not such a big surprise that DCS runs fine. :)
-
Not sure about the exact root cause, but I'm pretty sure, your hardware cannot run VR at PD=2 and msaa 2x simultaneously!So i just brought the rift S, Updated the software, APP, And the firmwire, Installed blah blah set it all up no problem
After 5 mins DCS stutters and my desktop stutters. I then need to restart my pc for it to function properly again. Could i be lacking PSU power?Jump in DCS most settings being high or max from trackir
I go into dcs VR options
Sytem settings:
PSU: CX850M
GPU: GeForce RTX 2080 Ti
CPU: Intel® Core i7-6700K CPU @ 4.00GHz
Memory: 32 GB RAM (31.94 GB RAM usable)
Current resolution: 3840 x 2160, 60Hz
That's quite a massive load and you're clearly limited by the CPU.
Try at least to lower PD to 1.2 and even disable msaa in a first instance, just to reduce load and check.
-
That's probably the reason you see stuttering...Ok, It shows 20hz and again, my chin is literally on the top of the "dashboard" of the F-18.You should decrease graphics to get around 40fps. First disable msaa (or set it at 2x maximum). Set shadows to low, and tick the "flat shadows" box. Visibility range to high, at most. Disable motion blur. And try, if possible to install DCS on an SSD drive.
I think that's the most fps impacting settings.
-
Thank you for the re-center advice - will try that. Lighting could be an issue - it is a bit dim but I mean it is a lit room. I'm in a very small studio in the woods.
Let me ask - as far as lighting, I have some lamps I can direct but overall, they don't totally light the room. Should I point them at the wall that my desk faces to illuminate that?
As far as FPS, how do I check that?
Thanks Again,
Dooz
I would indeed try the wall in front of you... but that's just a guess.
To show fps: left ctrl + pause
-
Maybe some tracking issue?So, I'm pretty new to DCS and totally new to VR. Just got the Rift S. I originally had the "fog" problem and found out it was (as someone else noted) just heat/steam. I aim a fan at my face now and it's corrected. I still have a few issues....One is that sometimes (seems random) the DCS menu screen (and ultimately the cockpit) appears to be 2 inches from my face. In the cockpit, my face is literally against the front of the canopy. Sometimes I'm shifted to the right... One time, I was actually viewing the plane from the center of the canopy - if i leaned right a few inches I was outside the cockpit. Mostly, though, when I start the game, I'm way too far forward.
Second issue is the "jitter". Everything is "shakey", i.e. a "tremble" of everything I'm looking at.
I have seen a few moments of absolute awesomeness but that is quite rare, unfortunately. I'm hoping that these are basic setup features - anyone else experience this or have advice?
I'm running an Alienware laptop. i9, 32GB ram, 1080 GPU.
Thanks!
Is there enough light in your room?
By the way, to re-center the VR view use numpad 5
And any idea about your fps? Are you well around 40 or much below?
-
Are you sure you tightened it correctly?Thanks some1.I've tried all different IPD to see if there would be a difference, didn't see any.
When I hold with my hand the HDM in the sweet spot for both eyes with no blurriness I see at best a 20% improvement compared to the CV1...but I can't keep holding it and moving it back in place.
I wish I could say the positive things being said here about the 'S' but I can't. There is some improvement in cockpit reading but very little outside the cockpit, so for me it's just not enough to warrant keeping it.
For me, once tightened, it doesn't move at all...
VR FPS
in Bugs and Problems
Posted
After a few tests I can confirm that Textures on High is definitely killing fps.
With my usual settings, I get 45fps with all modules, in my Reverb G2.
In the Apache, I'm only around 20-25. Simply changing Textures to Medium and I get 45fps in the Apache too.
(Intel 11900k, RTX 3080TI, 32Gb Ram)
Sent from my SM-G950F using Tapatalk