aleader
-
Posts
299 -
Joined
-
Last visited
Content Type
Profiles
Forums
Events
Posts posted by aleader
-
-
Confirmed:
spacehamster [2024-03-18 21:58:42]Dear customer, sorry for the confusion. And yes, the KA-50 is end of life.
-
Has anyone had a RECENT order from Virpil to Canada from the US store? Do you still need to pay the exorbitant duties/brokerage fees that I've been reading about? I was going to get a Winwing Ka-50 collective, but missed the boat as they are no longer making them. They haven't really ever been in stock either. Total cost to me would have been less than $450 CAD. With the Virpil I'm looking at $650 CAD with shipping, not including any additional fees/taxes/duties. Also do they ship separately or wait until both parts are in stock as they never seem to have stock of one item or the other? Thanks.
-
9 hours ago, MustangSally said:
I have one with the counter weight (etsy). Excellent collective
I didn't even know such a thing existed. Which one?
-
I've been waiting to see it in stock since long before Xmas, but I found this post on reddit:
Got this email from Winwing. Just want to let people know about the KA-50 Black Shark Grip end of life.
If true, that sucks as the Virpil collectives are insanely overpriced, especially so if you don't live in the US (more than double the cost of the Winwing for me in Canada). The only response I received from Winwing was a garbled reply about not knowing when they will do another production run, but that was prior to this response. They should take the product page down if they aren't going to make any more of them. -
First of all, specs: 4070ti/5600X/32GB/W10, using a FASGEAR USB C to C cable, 2.5 - 2.8 GBps when I tested. Default MT, standalone, openbeta.
I've been playing around with the OXR Toolkit and in-game settings. It's been a struggle, and although quite annoying having to constantly restart, I admit that I often enjoy optimizing a game more than actually playing it
I've read/watched countless videos and threads now, and still don't know what I should be trying. One says use all the debug/toolkits available, the next video two weeks later revises it and says they cause more issues than they solve.
From my limited testing so far, the biggest gain to smoothness/fps was the Turbo mode or DFR (I found that you can't have them both enabled at the same time as it crashes DCS). When set to DFR Quality/Wide, I don't even notice it. Are there any other DFR settings that are critical, or is it ok just to leave it at the presets?
As others have stated, shadows and terrain textures seem to kill FPS the most, although it clearly depends on the map. This isn't my game PC, so I don't have screenshots of settings, but I tried MSAA 4X (2X was just horrible aliasing and shimmer) and DLAA/DLSS Quality with at least 0.5 sharpening and PD set to 1.35 in-game. I didn't see any difference setting PD through the Oculus app. The cockpit is about the same clarity either way, but DLSS does perform better, and I don't get the 'ghosting/trailing' effect at these settings.
The one thing that still bothers me (other than the inconsistent performance) is the general dark, greyness about everything. I've increased the gamma and that helps a bit, but is there anything that can be done to increase the 'brightness' of the scene?
Also, is the Debug tool dead now, or does it have a use in my case?
-
1 hour ago, Sezai said:
Anyone who considers Quest 3, please give a read.
I bought a Quest 3 a few days ago and I must say I was amazed by the clarity and head tracking vs Reverb G2. However I noticed a dead pixel and returned the item to replace with the new one. Oh my God!!. How can 2 headsets could be so different. the 2nd headset had no dead pixel but the glare was unbearable, fan was so noisy (with the 1st one I did not even notice there was a fan and there were no glare at all). Besides all of these, it stuttered a lot. Tomorrow I will have the 2nd headset replaced with the 3rd one, and hoping the 3rd one would be the charm. So if you are looking to renew your headset with a Quest 3, these may be the frustrations you may face. If you contact Meta customer support they will tell you the glare is normal, but don't believe them. I see 2 same mode and there was no noticeable glare with the 1st one. If the 3rd one also does not work, I will get a full refund and go for a Pimax Crystal.
I recently sent back my Q2 and bought the Q3 instead, even though it cost more than double ($275 CAD vs $650 CAD). It's my first foray into VR. The blurriness on the Q2 was really annoying and was giving me a lot of dizziness. It's greatly reduced with the Q3, and yes, the clarity is a lot better. I didn't have any of the issues you are describing (I'm not even sure what this 'glare' is that everyone refers to?). Where are you ordering these from? Comparing it to a headset like the Pimax that costs 5 times as much (to play games
) is patently ridiculous though.
-
On 1/20/2024 at 6:16 PM, 71st_Mastiff said:
for got to mention, all Resolutions hrz set at 90. refresh rate. PiMax Crystal, monitor, and in game capped at 90hrz.
Just having a look at these as I also have a 4071ti/5600X (Quest 3) and I'm getting tired of adjusting settings already. Do you enable Turbo mode in OpenXR Toolkit? I'm most interested in gauge clarity, but also want to maximize performance too. What CPU do you have?
-
I'm just figuring this stuff out now, and have looked at 'Snuten's' settings on Page 15. Do these still apply with all of the recent updates? I read on one thread that you don't need to bother with anything OpenXR related (i.e. the toolkit) yet another says it's essential. Same with the 'debug tool'. I assume this is 'ODT'? I also keep seeing 'OBT'. Is this a typo? I have a Q2 and 4070ti/5600X. I'm assuming these settings should also help with the awful visuals I'm seeing?
-
9 hours ago, Lange_666 said:
That's not entirely true. You can't run ST and MT versions of the game from the same single shortcut. It doesn't give you the option to do so.
Same goes for VR and non VR mode. You don't have the option to set either VR or 2D when running by the means of the installed shortcut.
If the game was previously ran and closed in VR mode and you want it to run in 2D, with only one shortcut you need to start the game which will launch in VR. You then need to unselect VR and by confirmation, the game will close and re-open in 2D.
You can overcome these "smaller" problems by using multiple shortcuts.Yah, I get all that. All I was originally asking though was if I was in the MT version by default. I'm not sure why anyone would want to run in ST now?
-
4 hours ago, Phantom711 said:
Hmm...well...yeah...and that simply is a shortcut to the dcs_updater.exe...
I don`t know where that comes from when I explicitly said, that you don`t have to run seperate shortcuts a few posts above.
No kidding that you need at least one shortcut to run the game...that's pretty obvious
. You said that it isn't a big hassle to have separate shortcuts and also explicitly said that you didn't know if they were required. I'm simply clarifying for anyone interested (as there is obviously still confusion) that you do not in fact need to make any other shortcuts other than the one the game automatically installs.
-
18 hours ago, Phantom711 said:
Because you go through the folder path everytime to get to the respective dcs.exe instead of having a shortcut on the desktop?
No idea what you're talking about. I download the open beta, it puts an icon on the desktop, I double-click it. You seem fixated on this shortcut thing. If you want to keep doing that, nobody is stopping you.
-
It does get a little confusing. People were having issues that they were getting ST thinking they had MT for a long time and sometime this fall they changed the default to now run MT rather than ST which confused people again (the default icon now launches MT). And depending if you had made your own icon direct to the ST.exe or MT.exe things might not have changed .
So apparently the default now...no need for shortcuts.
-
3 minutes ago, rob10 said:
Yes. When it has 'multithreading preview 2.9XXX' at the bottom right you are getting MT, so however you're doing it is working.
Ok, that's what I figured. I did nothing...just downloaded it from the site and installed. I assumed I had to do shortcuts, but apparently that isn't a thing anymore.
-
Thanks, I will try these and I will set the refresh back to 72. I've read on other threads that the 'shimmering' is a known AA issue because of the old DCS engine. I'll try DLAA/DLSS and see if it helps. I'm asking about the MT thing on another thread so I can get it straight from ED.
EDIT:
This is a response I received: "Yes. When it has 'multithreading preview 2.9XXX' at the bottom right you are getting MT, so however you're doing it is working."
This is in the ED graphics thread (from Nineline): "These options (upscaling) are not available for the Single Thread version of DCS."
So it seems they released it to the 'default' without telling anyone?
-
I have a question that nobody can seem to answer and I see it's still unclear to some. Is the 'default' open beta that you download (new install) using multithreading now? I got a new motherboard a while ago, so I recently reinstalled DCS (standalone). I have the upscaling options available and it does say 'multithreading preview 2.9XXX' at the bottom right of the home screen. I assume this means I am using MT without having to create separate shortcuts??
-
11 minutes ago, Phantom711 said:
There are no nuances…
.
If your FPS are equal to the refresh rate of the headset the movements are smooth.
Yes…if you could run the respective game at even higher refresh rate with the matching FPS it would be even smoother.
examples:
72 FPS at 72Hz —> smooth
90 FPS at 90Hz —> even smoother
85 FPS at 90Hz —> not smooth
For the 120Hz…well I don‘t know. Maybe they lock their FPS to 60 so that every frame is shown twice which would also be smooth. Or they use motion reprojection a whole lot.
The Dcs.updater.exe is used to look for updates of the game but yeah…it also starts the game which I find annoying. No idea if it starts the MT or ST version.
To be sure use the dcs.exe from the bin-mt folder.
I guess first I should confirm what fps it's running at when I adjust settings, then set the refresh?
Then I need to run a separate .exe for VR and 2D do I not? That's a hassle I'd like to avoid if possible. Is that not true, that without MT your upscaling options wouldn't show up?
-
18 minutes ago, Qcumber said:
Make sure you use the max output resolution from the oculus app and then add 1.3 from oculus tray tool/oculus debug tool. This should give you better visuals. Use DLAA to control aliasing. It's better than MSSA and little performance hit. If you want more performance use DLSS but you will get a softer image.
Performance isn't the issue, it just looks terrible. I'll have a look and try your suggestions, thanks.
2 minutes ago, Phantom711 said:I would always recommend the lowest possible Refresh rate on the headset. It is far easier for your GPU to deliver FPS at native refresh rate and provide a smooth gameplay. I find 72Hz smooth enough. For tze occasional drops below I use ASW on auto.
I don't understand the nuances of that enough, but I will put it down to 72Hz. I've read that some keep it on 120 (with lesser hardware) and seem to have better results, but I don't see how that is possible.
About the MT, am I using MT in-game or not? From what I read if you don't have upscaling available, you're not 'in' MT?
-
14 hours ago, PawlaczGMD said:
MT is a different .exe
ST is in bin folder, and MT is in bin-mt folder.
This is separate from open beta.
You definitely want MT, I am unable to play in VR without it, as there is horrible stuttering.
You need to adjust your expectations for the graphics. Q2 is an old budget headset with relatively low resolution. In-game settings can't overcome this issue. I tried playing with Q2 and also found the graphics to be too bad to have fun, just a proof of concept. I purchased Pimax Crystal which has significantly higher res, and the visuals are a LOT better, but still have room to go. DCS is extremely demanding on VR, as you need to be looking both at cockpit up close, and spot objects very far away. I just don't think Q2 is usable for DCS. If you like the VR experience, at least get the Q3.
I was expecting to, but I didn't look for any of that in any folders, just went to the ED website and installed the open beta, as I always have. I have DLSS available in-game (and all of the upscaling options), and it says '2.9XXX multithreading preview' in the lower right corner of the screen, 2D and in VR. My .exe is the 'DCS.update.exe'. Does that not indicate that I am using MT?
The stuttering only happened to me the first time I loaded it (F18 on the ramp) and taxied to the runway. Every other playthrough it didn't stutter at all, and was very smooth. Now, this is just in instant action with a few other planes flying around. I also had bumped it up to 90Hz/1.1 res in the oculus app, but I have MSAA at x2. I'll bump that up next. The shimmering and AA are very noticeable and annoying.
Lol, the Rift S was an 'old budget headset' but I recall people on here crowing about how wonderful it was in VR. I'm pretty sure a lot of others have been using the Q2 with DCS since it came out, so it's obviously 'usable', or they would have quit using it. It's like the guys on here saying DCS is 'unplayable' at anything other than 4K
. I will never spend that much just to play in VR (Pimax - $2,900 CAD!!). But yes, I may get a Q3 if I can 'get my VR legs' with the Q2.
Also, it's clear from the now thousands of threads here and on Reddit and Steam trying to figure out how to set the graphics in DCS VR that's it's a DCS problem...the ARMA of flight sims
. Pretty much every other game I've tried now in PCVR looks quite good on my system, even the old Half Life 2 (VR mods). The fresnel lenses are annoying, but from what I've read the center-view problem is fixed in the Q3 with the pancake lenses.
I'm going to start the tweaking process now that everyone else needs to do with this and see if I can get the graphics to something that are not from 1998. I'm obviously exaggerating, but it's a stark change going from 1440p very high graphics, 143 fps to VR in this game.
Of note, if anyone is interested, the FASGEAR cable is working well. Obviously I can't comment on the long-term viability, but so far, so good, and it keeps the headset 'almost' fully charged while playing.
-
1 hour ago, Phantom711 said:
What are you talking about? Why would MT have been „moved to Open Beta“? Moved from where?
As the default option. I thought you needed to make a shortcut to run MT? As I said in my above post. I haven't played DCS for a long while, so I just installed it a few weeks ago.
I've been playing it a bit now, and the graphics are terrible. Lots of aliasing and 'shimmering' (as I've heard it described). I assume I now need to figure out settings for my 4070ti/5600X. It would be nice though if I could find a few screenshots of what I should be expecting it to look like in-game with my hardware. I'll have to look. The first time I moved to the runway in the F18 I had some hard stutters every 5 or 10 seconds. That seems to have stopped now, but makes me think I've got something set way off.
-
Also, I don't see any threads or anyone talking about it, but did they move Mutlithreading to the open beta? I have DLSS available, and I didn't make any special shortcuts. It also shows 'mutithreading' at the bottom right, so I'm assuming it's 'on'.
-
On 12/29/2023 at 1:12 AM, PawlaczGMD said:
It's debatable whether airlink or VD is better TBH. Start with airlink. Quest link = cable. Air link = no cable. VD = third party app, no cable.
Turn on airlink in headset options, install oculus on PC, pair it, enter airlink and launch the game. It should just work, really, but if not, just buy VD, it's more intuitive to set up.
Then, you can either try to launch the DCS .exe directly through the toolbar, which doesn't always work. Or, you can launch steam VR, and launch DCS through that, which should work. You can add standalone DCS as a non-Steam VR game to Steam.
Just trying this now. I tried VTOL VR with Steamlink and it runs great...started right up, no lag or stutters. DCS...not so much.
I now have my cable hooked up (USB C to C...Questlink test app says 2.8 GBps). I tried launching it through the Questlink toolbar, and I just get the 3 circles endlessly cycling, DCS never launches, but I can hear menu sound in the background. What I read here is that I need to launch Questlink (it won't allow me to just start up DCS on the 2D screen without first launching Questlink), then launch SteamVR...through the 2D desktop I'm assuming, after I somehow add standalone to it?
EDIT: Got it to work by launching it outside of the toolbar (i.e. on the 2D desktop) while Questlink was running.
-
19 hours ago, PawlaczGMD said:
The one I had didn't have to 90 deg, but it's still fine. In theory, any USB 3.0 to USB C will work, the headset doesn't need crazy speed. It's more about the physical quality of the cable.
I has to be USB C on one side because that's what your headset has, right?
I think all these cables are good.
When you play in VR, your monitor just mirrors the VR view. It doesn't rerender a 2D view in a different resolution. So the in-game res should not matter at all for performance.
I just ordered the Fasgear one as it was only $22, seems to have power, mostly passed the fake reviews check, has a 90 deg (apparently easier on the port and less chance of breaking?), and is USB C to C, which theoretically should not bottleneck anything. I can always upgrade to a 'better' one later if I see the need.
I still don't really understand how your video card can show something on your monitor and not use resources, but I'll take everyone's word for it
I guess you have to anyways, so it's a moot point.
I'm going to finally try this probably today or tomorrow, just haven't set the time aside yet.
-
9 minutes ago, Phantom711 said:
I think you need a monitor for PCVR.
It also seems to be common understanding, that this does not actually impact performance really.
I didn‘t want to take any chances with the cable and bought the official Oculus link cable. You need to check, that the respective cable is capable of providing data and power at the same time.
So if I set my game settings to my usual 1440p settings (adjusted down for VR obviously), it has no impact running my monitor and headset?
The official cable is like $110 here, which I am not going to pay. Something like these?:
Or this is supposedly good, but a lot more: https://us.vrcover.com/products/premium-usb-c-cable-for-oculus™-quest-2-5m
-
9 hours ago, Lange_666 said:
In the VR settings in DCS there is an option to confine the mouse cursor to stay within the DCS window on your screen.
This has pro's and con's:
- Mouse stays within DCS, that way you don't loose the mouse cursor in VR when it moves out of the DCS VR mirror window on your screen. But as long as DCS is active you can't move the mouse out of that window, even if you want too (used to work fine, don't know about now because i have this option un-ticked).
However, if you use a second monitor and want to look something up this option can be frustrating because you can't move the mouse out of DCS.
- Mouse can move out of the DCS VR mirror window and with the headset on, it can be frustrating to get your cursor back into the window for you to use it when needed.
You can prevent this by keeping the resolution of the mirror window the same as the resolution of your monitor + DCS will give a message in your headset that the DCS window is out of focus if you move it to your second monitor or if you move it out of a smaller DCS window.Ok. So I take it then there is no way to keep your monitor off completely so it doesn't waste resources? I'm sure I've seen videos of guys playing without a monitor physically installed in their setup?
Track IR 5 ProClip - Possible solution for erratic tracking due to light interference
in Input Devices
Posted · Edited by aleader
Good tip. I am always fighting with sunlight and have to play at night. What exactly did you buy and from where?
purchased: Gila® Privacy Black Static Cling Residential DIY Window Film.
EDIT: Doh, didn't even see that you have it in the description!