Mr_sukebe

Sorry, can't comment on the TM grip, as I'm a Virpil Alpha user. I've experienced no issues/conflicts between the Moza software and the Simshaker app. Maybe I've just not noticed, but don't believe that I've had a problem. As you say, there are roughly 7-8 presets, as supplied by Moza. It appears that Moza tried to pickout a decent representation for each plane type, e.g. warbird (Spitfire), helicopter (Mi24), FBW (e.g. F18), Gen 2-3 jet (F4/F14), Force Sensing (F16). Personally, I currently use the fairly generic preset for similar aircraft. So for example, I use the F18 preset with the Mirage 2000. The F4 preset with the Mirage F1, all helicopters with the Mi24 preset etc. So far, seems to work fine. There are additional presets that have been created by other users and are available to download from Moza's Discord channel. Right now, I feel that we're at a really early stage, primarily because we're at a bit of loss for really understanding what "should" be felt through the grip. People talk about the forces, but that's only part of the question. Are actions like firing the guns, dropping ordinance, lowering the flaps something you'd really feel in a jet? I've no idea. There are settings available for them, which is a good thing, but to date, I've not seen a real pilot come in and say "yes, you can feel that, but not this". That's what I'm hoping for. For all that, I do find the current presets to be more immersive and preferable to just springs in a base, so I'm very happy to have one.

Thanks, I do find it very immersive. Be aware that it has a few "compromises", i.e. that it's deliberately built to the size it is, to ensure that it'll fit in our spare room. Hence why a stock solution from say NLR was never going to work. As for negotiations with the better half, well it's been exactly that. She gets to choose the car, kitchen, bathrooms and back garden. I don't spend my free funds on drinking, smoking or fast cars. In return, I get to do roughly what I want on my key hobbies, ie. the flight sim rig and my stereo (in the lounge).

That's interesting. Haven't checked VRAM changes in my own system for that in months. I'll go have a scan later on.

Go have a check on VRAM usage changes (use, not reserved). Thats now visible on the FPS counter option in game

Here we go: the base is an 8040 aluminium frame which has “evolved” over time with additional bits hanging off it.

I read one of the books covering the Vulcan raid against Stanley and now routinely bomb at an angle of 10-20 degrees to offset the potential for drift and similar. Works a treat.

Are you using the stock USB cable supplied with the Quest? I vaguely seem to remember someone saying that it was a pretty low quality and didn't support full fat USB3.1. I bought a decent aftermarket USB cable, and have not had an issue.

There's a switch on the right hand side within the switches for the weapons called EXT. When I was re-reading Chucks guide, there was mention that when you engage that switch (fwd), that it will cool the missiles. Chuck also stated that the cooling only worked for around 20 mins. I did notice that the EXT switch was forward by default during a cold start. My suggestion is to turn it off during cold start and before loading weapons, then push it fwd when you know you're shortly about to engage someone. From what I read, takes roughly 20 seconds for the cooling to take effect. Having said all of the above, that's just my guess on what might have caused your issue. Could be something else entirely.

I seem to remember that the missiles cool for around 20 mins. Had you let them warmup again

Again, we can now see how much is RESERVED, which seems to be pretty much all of it, and how much is USED, which is clearly NOT the same. I've yet to see DCS USING more than 12GB, regardless of the amount reserved, though that is all single player. Most of my single player missions seem to USE around 6-7GB of VRAM

Open the FPS counter in DCS (twice) to bring up the more detailed version. In the last row but one, it now states how much is USED and how much is RESERVED.

A few more things to try: Ensure that you're using OpenXR Disable the "home" for your Pico. If it's anything like the Oculus "home", it'll eat a couple of GB of VRAM before you're even opened DCS Run a search for Empty VR Hangar. When you first load into DCS in VR, you'll normally be sat next to a jet. Again, that eats VRAM and adds no real value. The Empty VR hangar replaces that initial view with zilch Textures do tend to eat lots of VRAM. Another that I found was the Preload Radius. Mine is now set to around 45%. Give that a try When you're in game, open the DCS FPS counter. Open that twice and you get both the FPS count (small box) and a bigger box with more detail in it. That now displays both the USED and RESERVED VRAM usage and is worth taking a scan at. The most I've seen USED is up to around 12GB on loading a complex mission in the Chinook. In most scenarios (single player) I'm typically using sub 6GB, which "should" fit into your GPU Go checkout the DLSS4 threads. DLSS4 introduced an update to the upscaling and AA that is available to all RTX cards, including your 30 series. There's a need to use an App (free to download) called NVPI (Nvidia Profile Inspector), but it's like Nvidia really has applied some magic to the results. Use the latest DLSS profile and there's a definite improvement in frame rate/visuals IMO, VR in DCS has improved in the last few months, but that's partly a result of the above settings

The RAF versions…

All of them...

Another idea to try is lowering the polling rate on your mouse, as suggested recently by Spud. The default polling rate for my Logitech 502 was 1000 (per second). I dropped it to 125 and it did eliminate micro-stutters.

The Canberra would be a great addition, if for no other reason than the number of countries that flew it and the number of conflicts that it was involved with

Of course it might actually be useful if we had Korea as a map.

Go into the audio settings within DCS. There's a bunch of drop down options on what to output to. This overrides what's set by windows, so it needs to be done here too.

Agreed, it would be great to understand what feedback is received in real aircraft. The force comments are really useful, but what about other potentials, eg does speed influence weight (as it does in a warbird), lowering flaps, speedbrakes, wind gusts, dropping ordinance etc. There’s a mass of external factors that might in reality produce feedback in the sticks. Probably far less in a FBW fighter, but what about say a Phantom, Mirage F1?

Of course it depends on the aircraft and terrain, which is why I mentioned examples above. Just checked out Afganistan with the Chinook. Whilst jumping into the cockpit cold and dark, VRAM usage (not reserved) was over 11GB. It then dropped to sub 7GB whilst airbourne. That's with High textures for both terrain and the aircraft, and ultra settings on the clouds. Another point that most certainly DID help was to follow up on a suggestion mentioned by Spud today, i.e. the lower the polling rate on my Logitech mouse. I vaguely seem to remember doing that back on Windows 10. With the move to Win 11, didn't bother. Either way, dropped the polling rate to 125 and wow, it really did smooth things out and reduce micro-stutter.

Try using in game FPS counter within DCS. I think it’s Right Cntrl and Pause. Hit that twice and it displays a more complex summary of what’s going on. Towards the bottom of that rectangle of data, it now shows not only the VRAM reserved by DCS, but also how much is really being used. In the mission today, DCS had reserved 15.3GB, but was using under 5GB. What I don’t understand is why DCS is not making use of more of reserved VRAM?

I was out earlier in an F16 over Afghanistan. VRAM use sub 5GB. No one else wondering about this? What did occur was whether ED has reduced actual VRAM usage, meaning that DCS would need to more regularly load and unpack new textures. Could that be why we might have good FPS, that is not really smooth in delivery?

Have you enabled eye tracking in the headset itself? I vaguely seem to remember that you need to be in developer mode to be able to change the setting.

The older ones have just worn out the wiper blades. Maybe some of the new Bosch aero type will help?

I had a Pico 4, but was so unimpressed that I gave it back. Being fair, that was mainly about my inability to get it linked up, I thought the image quality was fine. On the QP: - Eye tracking on the QP does help performance. - I found the comfort to be poor as stock. It added velcro bands to mine which were very cheap resolved the issue - I honestly can’t remember if the QP has better visuals, both are good - clearly I found the Oculus software easier to deal with