ravenzino

I've been doing carrier landing for quite a while. Always followed the pattern, though far from perfect, my landing is generally ok and successful for most of the time. However, whenever I trap, I always went a bit off to the right from the center line of the landing area. Sometimes one foot or two, sometimes several. The move is especially noticeable after the hook catches a wire. Is this normal? If not, what could be the reason? Btw, during final approach, I usually put the VV around the crouch at the end of the landing area. During final alignment just before touch down, I would move VV closer to the center line.

try to use the biggest JDAM to hit a bunker

Not the desired approach that I’m trying to explore, but this is certainly an interesting way. Better than the track ball as I can feel. Sent from my iPhone using Tapatalk

Oh, didn’t notice that... will try again... It could be quite useful knowing both the speeds. Just less optimal that they can’t be shown together... Sent from my iPhone using Tapatalk

Cool, thanks! Btw, once. Twice will close it up again... Sent from my iPhone using Tapatalk

I think it is relatively safe to say, that muscle memory or other practical skills doesn't negate the need of immersion, and they don't have to be "one or the other". I'm pretty sure there are people doing just fine with basic setup without VR, while people are keep on trying to get better immersion experience. Either way, the purpose of my post is to exchange and spark some further thinking by offering a new (or maybe not) method / approach to possibly create a better VR immersion experience. It might work, or maybe not at all. But it is always worthwhile and beneficial to get ideas from likeminded people. Appreciate for any constructive thoughts.:)

On a second thought, I might not proceed with that deal due to planning consideration. But anyway, thanks for the insight. And that delidding sounds quite... risky... :D

Please ignore this post as I've changed my plan. -----------original post-------------------------------------------- Have been struggling with VR performance, and now sort of convinced that my old i7-6700+z170 setup needs to be replaced to eliminate the CPU bottleneck and fully unleash my RTX 2080 Ti. I'm now having two options: 1. Costly option: go for brand new i9-9900K + z390 2. Less costly option: a friend has a spare i7-8086K + z370, which I can purchase probably in good terms. I don't use the rig to do any performance-demanding tasks other than DCS. So question is, assuming using the rig for DCS(VR) only, how much difference of the actual performance will there be between the above two options? Will i9-9900K+z390 provide any noticeable improvement over the other one? (I know when looking at the specs, there will certainly be a handful of differences, but to what extent will those difference matter to DCS?) Frequency-wise, I think i7-8086K can also boost up to 5GHz.

3DMark shows everything is good... used EVGA OC Scanner for testing VRAM, at least the tested 6G is all good...... Reinstalled SteamVR and Mixed Reality for SteamVR. And gave Nvidia graphic settings a reset. Now with Hornet instant action Cold and Dark at Caucasus, I get 45 when looking forward and about 30 when looking sideways where there're aircrafts or ground equipment, 40-45 when up in air. By using Frame Timing tool of SteamVR, I got two charts as attached. 111.png for in game, 222.png for menu screen (inside hanger with 3D flanker, solid 90 FPS). Still trying to understand it though. Another weird thing is, if I switch to F10 map view, the FPS will drop to about 30... doesn't make any sense to me... I'll probably just bear with it for the moment until upgrade some time later...

Oh dear, I'm in trouble... even when I turned basically all off, lower than Svsmokey's settings, I still can't get a solid 45, not even when I was above sea when there's basically nothing nearby other than a couple of ships and some clouds... I'm now cleaning my system by uninstalling as many applications as possible... probably start with VMWare which I seldom use...

The F2 view in non-VR will display quite a lot of flight status info at the bottom bar, which sometime could be quite useful, even just for fun. e.g. see how high your missile goes... Is there any way to see those info in VR?

Go get it. If it doesn’t work out for you, feel free to send them over ;-D Bloody money-eating game, ED must have taken a lot from the hardware manufacturers... Despite that, tbh, I would be satisfied enough as long as I can get a stable 45 under decent graphic settings... Sent from my iPhone using Tapatalk

Damn, so I really have to spent the money in replacing for: i9-9900K + CPU Cooler z390 MB 32GB RAM and probably a chassis... That's not what I thought I've signed up for when getting the VR...... :wallbash: :wallbash: :wallbash:

I'm leaning towards to believe CPU bond as well. Good to know that someone has tried this out. However, really don't understand why the CPU performance isn't maxed out. There has to be an observable bottleneck somewhere...

Somehow managed to successfully run FCAT with my WMR. The chart from FCAT Analyzer doesn't help much as I can't find a way to show anything other than the frametime. However, the captured data file looks interesting. Total GPU render time (ms): is typically around 27-32 Compositor idle time (ms): is typically around 1.2-11. This looks like the time taken by CPU. Client Frame Interval (ms): is typically around 41-52 while it can also go down to 38 or up to 82 Submit frame (ms): is typically 0.11 - 0.22. That article suggested that "not near-zero indicates driver issue", not sure if this value can be considered near-zero or not... Frame start (ms) between 2 frames can be around 42-56 (ms), sounds pretty bad, the actual in game FPS at the same time was averaged at about 30. Not sure how that gap between frames translated into this FPS... Anyway, still confused by the data...... and feels like the problem is more at my GPU side? I've attached the captured data file as well as a screen shot, appreciate if you can shed some light on this. Also copy-pasted some content below as well: Frame Index Frame start (ms) Render end (ms) Warp end (ms) HMD sample start (ms) Number Times Presented Number Dropped Frames App Miss Count Number Mis Presented Reprojection Flags Scene render GPU time (ms) Total GPU render time (ms) Compositor GPU render time (ms) Compositor CPU render time (ms) Compositor idle time (ms) Client Frame Interval (ms) Present call CPU (ms) Wait for present CPU (ms) Submit frame (ms) New poses ready(ms) New frame ready(ms) Compositor update start(ms) Compositor update end(ms) Compositor render start(ms) ProcessID API version 31182 402213.9436 402241.2736 402241.4877 402174.6313 1 0 0 0 4 27.32998466 27.54406548 0.01408 0.345600009 1.684100032 42.59149933 0.121800005 0.0067 0.195499986 402181.9143 402223.46 402223.5136 402223.5549 402224.7464 25052 0 31183 402262.9523 402291.8839 402292.0984 402224.533 1 0 0 0 4 28.93152046 29.14611244 0.014592 0.283100009 7.881199837 46.62889862 0.115000002 0.0063 0.2333 402227.0389 402272.7399 402272.7616 402272.7899 402273.8292 25052 0 31184 402315.2778 402342.6761 402342.8905 402273.679 1 0 0 0 4 27.39830399 27.61267281 0.014368 0.363599986 11.89529991 43.57130051 0.119999997 0.009000001 0.150000006 402282.215 402324.6607 402324.7136 402324.7371 402326.0592 25052 0 31185 402371.2049 402399.4182 402399.6406 402325.7976 1 0 0 0 4 28.2132473 28.43571281 0.022464002 0.374300033 11.04770088 43.1371994 0.176400006 0.0067 0.168300003 402338.5551 402380.3275 402380.4326 402380.4774 402381.9621 25052 0 2019-04-17 01-30-22_OpenVR.zip

Why don't you consider using head tracking (Track IR)? That's probably the most popular solution, allowing you to look at anywhere via your monitor(s).

Thanks for the awesome advice. Not sure if it works with WMR, but I certainly will give it a try as much as I can to find the problem. The CPU does have a boosting feature, I can’t control it though. Dell’s MB greyed overclocking option. But will try your suggested settings and see if that helps. Sent from my iPhone using Tapatalk

Thanks, but how do I tell whether that’s actually happening? Any figure that I should look at? Sent from my iPhone using Tapatalk

For real? :excited:

having same question

tbh, I don't know. But I guess it doesn't matter much, similar to LGBs. The higher and faster the better. We are dealing with kinetic energy after all, simple physics :D btw, my attempts so far were at about angels 18-24. Forgot the speed but should be around 300kts to 350kts. Good question...... However, since that just means some extra dive at the end of the path, it would surprise me if there's any significant reduce. It should also be possible to compensate that reduction, if any significant, by flying at a higher altitude and faster speed. And maybe a bit upward pitch as well. Maybe... Those circles are dynamically adjusted to your current height and speed. That somehow looks good enough to me...... Haven't tried multiple drops in one go... will see~

No direct experience here. But: 1. guess posting your hardware spec might help the discussion to be more tailored. 2. if I would host a mission for a group, I wound use a dedicated PC/Server with the now available Dedicated Server feature, so that won't impact anyone's FPS.

A couple of tips from my experience so far: 1. Try to set the ANG (vertical attacking angle) to 90 as Wags did in his video. I find it quite helpful. 2. Allow enough time for INS alignment. There was a time when I was carrying two types of JDAM. When I switch from one to the other before the INS alignment is done, the timer will restart from 10min... 3. Get your coordinates right. I used to constantly drop the JDAM a couple of meters short from a same target. It turns out that the coordinates I put in was wrong by one digit when I get it from ME. I then achieved multiple fairly accurate hits after correction. I even did an accurate drop on a parked Mi-8. 4. I would wait a few seconds after seeing the In Range Cue to make sure the bomb gets enough room for any adjustment it might need. I mostly use the biggest one (I think it is the GBU-31xxx), as Hornet can only carry 4 of JDAM so far regardless the model... so why bother using the small ones :D

The chassis is a bit stressed after I throw in the new beefy graphic card and replacing for a slightly bigger PSU. Will CPU throttle itself on high temperature? Is some 70 degrees enough to trigger that? It haven’t shown any degradation over hours of lengthy use in DCS VR though... Sent from my iPhone using Tapatalk

Yea, I know. Looked at their website, they said no modifications would left after uninstalling, but what I saw suggested differently... However, I think it did an Ok job. I tried reinstall it last night and force DCS to run on one single core. That core was immediately maxed out, DCS FPS dropped from 20 to single digit (on a populated Stannis). Re-enabling it on all the cores brought FPS back to 20. Sent from my iPhone using Tapatalk