obious
-
Posts
572 -
Joined
-
Last visited
Content Type
Profiles
Forums
Events
Posts posted by obious
-
-
22 hours ago, rob10 said:
Hornet is designed to "crash" land on the carrier so you're much less likely to get bounce than say a F-16 because it's designed to absorb the shock of a hard landing. Having said that, I have bounced the Hornet on a runway landing before.
I understanding how a hornet is supposed to ‘crash’ into the deck of a carrier but there’s no ‘give’ at all in the current suspension physics.
-
What has this got to do with Clouds & Weather?
-
I thought I saw a while ago that the Hornet would be getting an update to its landing gear mech.
I was doing some field ops last night and I noticed that when I touched down (albeit pretty hard), the plane just stuck to the tarmac and didn't bounce around or move at all. As such, it makes landing someone trivial and trying to keep it on the runway a bit of a nonstarter (even more so with double ugly loadouts).
-
When trying to dial in my FPS (inc. any headroom needed to complex missions/scenarios), using the built-in FPS counter/graph isn't enough (especially in VR). Ideally, we'd have a CUP & GPU frame time counter much like we have in the Open XR Toolkit.
-
1
-
-
I recently had a LG C2 42" which was quite possibly the best image I've ever seeen in real life. Was also great for running DCS in pancake mode but after about 6 months I had an issue with green strips becoming visible on the display/image which I hear is a common issue. I returned to Amazon with no problem and will most likely pick up the newer C3 soon
-
Turn on Turbo Mode in the OpenXR Toolkit, that’s the only way to fix stutter currently
-
2 minutes ago, SMH said:
It's dependent on the Mission settings, I believe. But it's likely one of the shadow settings that's causing the frame rate drop. Try fiddling with those in DCS' graphics options page.
Yea I've done that but there currently isn't a setting that I can change that'll prevent the flood lights from coming on past dusk
-
I've just got my VR settings to where I want them but the only thing that seems to throw a spanner in the works and knock me down to 45fps is when the flood lights on the SC come on. Anyone know if its possible to turn them off via a config file etc etc?
Thanks
-
On 9/24/2023 at 7:26 AM, Jimmy8x said:
Got my new Aero set up today, the clarity is unbelievable but the vertical FOV is dreadful, to the point of making me consider a return/refund.
Some of you will think I'm trolling or being paid by ByteDance but in many ways I prefer my Pico4. Huge lenses, way better binocular overlap, wireless (blessing and a curse, compression means the image will always be messy), instant access to passthrough camera to take care of random things in the real world... it is not the slam dunk clear cut upgrade I was hoping for, despite the massive increase in resolution and clarity. I will probably keep the Aero but at this point I'm undecided. Either way I'll be upgrading again in 2024
This is exactly the same reaction I had. The clarity truly is mind blowing but the FoV was quite honestly shocking. I returned mine, Varjo were great about it.
-
1
-
-
4 minutes ago, Hartsblade said:
Just watched it as well. So tempting, but rumor mill keeps hinting at an imminent Valve reveal. I'm going to wait a bit longer.
Totally agree. I just returned mine after struggling with the motion blur and red shift issue. I wonder if they’re knocking the price down to get rid of units ahead of a ‘V2’?
-
1
-
-
I've had my Aero for about an hour now and whilst the clarity truly is stunning, I'm really struggling with the 'other' things (bear in mind that I'm coming from a Quest Pro).
When looking striaght ahead (this isn't just a DCS thing for me, I see it in the 'home' screen also) I can see the flat bottom edge of the display. I've tried to adjust the strap but that doesn't really help.
There's also clear 'warping'/bending/distortion of the image whenever I look at something at the edges of the display and I move my head in that direction.
I'm getting serious Reverb G2 vibes after using this headset for the past 30 mins. Anyone else feel the same?
-
16 minutes ago, Burt said:
Absolutely no M R for me. On a few multiplayer servers that are really loaded with static objects I find that locking to 45 fps in VB only helps the fight with it trying to get 90 fps. The graph lines are smoother. Single player I disable the lock, let roll. This seems to work very very well with my rig and my Aero running at 39 ppd so crisp ! and smooth. Running DFR/FR is truly amazing.
Thanks. I have my Aero coming in a few weeks and was curious as to how people are running them (I’m coming from a QP at 90fps)
-
1
-
-
27 minutes ago, dburne said:
45 vsync on in Varjo Base.
With your rig (I have the same graphics card), have you tried 90fps? I’m assuming performance (or lack there of it) is the reason that you’re locking to 45fps?
-
1
-
-
@dburne are you running at 90fps or 45fps? I
-
1 hour ago, Maksim Savelev said:
Hello everyone!
Just recently got my Quest Pro. Coming from almost everything that had been released (CV1, Rift S, HPreverb, Index, Pimax 8KX, HP G2, Varjo (what a piece of sh...), Pico4) found that Quest Pro is almost perfect. Add some resolution on top of all it has to offer and it would The Best and The only must have headset for flying.
Since all of you gentlemen have quite of experience with this headset could you please help me with one thing I'm having troubles with. Its fun, but using Quad-view is causing some stutters and when I have it deleted/uninstalled everything is smooth. Did someone of you have anything like this?
Try turning on Turbo Mode in OKRTK, that removed all the stutters I was having with MT and my QP
-
Hi All,
Simply put, I’m having a difficult time just simply using the CDIP mode when trying to drop some iron bombs on some random buildings mid-flight. It doesn’t matter what I do in CDIP mode (1/STA, STEP etc), the Mk82s simply won’t come off the rack instantaneously when pushing the weapon release button when I’m have a nose down attitude unless I go into external view mode (via F2).
When I’m in the cockpit and I press the weapon release, the aircraft is designating wherever the piper is as a TGT and the horizontal TTL bar appears but by the time I’m due to release, I’ve overflown the target.
Why is the aircraft designating where’ve the piper is as an AUTO target instead of just releasing the ordnance?
-
43 minutes ago, Tepnox said:
Quest Pro user here. Well nothing you can do about it right now. MT needs more optimization from ED - right now MT only works well with Turbo Mode on with Quest / Quest Pro. ASW is still usable but it often breaks when there is too much headroom left for the gpu and the frames run uncapped in that moment.
It is tolerable - at least for me.
My approach for optimization was: Tuning your settings in ST to you liking and after that switching to MT with Turbo Mode enabled. A nice bonus of MT is that the GPU load is 10-15 % less than with ST for the same frames with a 4090 - so clearly a performance gain gpu-wise.
Only downside of Turbo Mode for me is that sometimes DCS VR freezes / lock up when you pause your VR session and put down your headset and want to continue after a break. Let's hope for MT improvements "in the future"! ;D
Hmmm do you mean to say that the Quest Pro only works well with Turbo Mode on in MT or that MT only works well with the the Quest Pro?
-
2 hours ago, Willdass said:
If both headsets were priced the same, I would pick the Aero every single time.
Good to know, thanks for the feedback. Out of interest, did you experience a perf diff between the QP and Aero?
-
Anyone here have a Quest Pro along with their Aero (or those that have an Aero and have tried a QP), how does both the vertical and horizontal FoV compare?
I’ve heard some quite bad things about the vertical FoV and before I pull the trigger on a headset during their sale I’d like to get peoples input
-
4 hours ago, Pride37 said:
Hi obious,
I have to report the exact same behavior on my side, micro-stuttering in MT instances. ST is butter smooth as well, but I clearly loose some performances then: most of the time at 45fps in MT with some instances at 30 (reprojection on), while in ST mode I'm most of the time at 30fps. And as for you, those stutters don't appear in the framerate recorder...
I don't think it's related to the CPU, when I first launched MT version, I was running a Z390 MB / 9900ks CPU, but I switched few mounths ago to a B650 MB / 7800X3D, with a whole new fresh install of Win11 and DCS, and noticed the exact same behaviour.
I tried HAGS on and off, resizable bar, nothing chages. The other difference between ST and MT versions is the loading screens disappeared in MT, it's just black!
I may have a look at the ressource monitor to check the app priority, or the VR pre-rendered frame in NVCP, may be that'll help.
I've tried a bunch of stuff also to no avail. I also don't think its just limited to my headset as I tried with my OG Reverb and get the same experience.
@BIGNEWY any chance you could test this out on your end please (just to make sure I'm not going crazy)? The experiment is to simply fly the NTTR F-18 free flight mission and toggle OKRTK Turbo Mode on and off to see if you get the micro stuttering that I'm reporting here. Simply rock the aircraft gently right to left whilst looking at the terrain and you should get the same experience. Then also try the ST instance, this issue doesn't present itself, turbo mode or not
-
FYI, I think this is defo an issue with the MT instance of DCS:
-
Ok, so I have done more testing and I'm pretty confident this time that there is an issue with the MT version of DCS. With exact same DCS, OXRTK and Oculus settings, I get pretty evident micro strutting when just rolling the aircraft gently/slowly let to right and looking either left or right at the terrain (it appears at first glance as though this is simply my system not able to keep up with the frame times but this isn't the case as I have around 30% GPU headroom as reported in MSI Afterburner).
After launching the ST version of DCS (again with the exact same settings), and loading the same free flight mission, the image is buttery smooth (even through aggressive turns, banks, rolls etc etc). If I jump out of ST and load up MT, the issue immiedently comes back. As I've said a few times, the only way to remove this in MT is to use OXRTK Turob Mode. I've even tried this by turning of MSAA and lowering the render resolution in the Oculus app via the slider to native (ie 1x) and I still get the issue (even with an image so grainy and pixelated that looks like its being rendered through an OG Rift).
My DCS instance is up to date as is my copy of Windows 10 and my Nvidia drivers. Its also worth noting that I tried this on a fresh install on Windows 11 and the same thing happens
Anyone got any ideas?
-
3 hours ago, Parrotnut said:
Today i got a mail from Varjo. It's a good time if you want the Aero for 25% of. No sign of a V2
I got the same email, it’s a great offer and I wonder if they’re doing it to shift units prior to a new headset coming out?
3 hours ago, dburne said:It is only now starting to approach 2 years since release and still is considered a top of the line headset even by today's standards. Have not seen any info giving any clue on a V2 so I expect it will be a while if ever.
I’m willing to accept a while but if ever? Why would they stop at the V1?
-
I’ve had a Quest Pro for around 6 months and whilst its a great headset, its not without its issues. I’m thinking of pulling the trigger on a Varjo Aero but am slightly apprehensive given its been out for a while.
Anyone know if there are any rumours around an Aero V2 and what, if any, the improvements could be (I for one would be hoping for pancake lenses)?
Realistic Landing Gear/Suspension Physics
in Wish List
Posted
Look like this has been marked as WiP so it should be in hand