Mr_sukebe

I’m currently using x3 Anker 10 port units. It’s called 10, but 3 are charging only (not data). So in reality it’s only 7 per unit. None have failed as yet, which is why I’ve ended up with multiple units

If I remember, I’ll upload a mission late that I use. That mission has: - no air threats - a bunch of static ground targets - a flight of 4 aircraft for each weapon type for each aircraft already in the air, roughly 20-30 miles from the target The implications being that if I want to practice say laser GBUs in an F18, that I just jump into one of the 4 of that flight called F18 - GBUs. It’s already in air, waypoints in place. So all I need to do is jump in, ready the weapons and drop them. No mucking about with startup or lengthy flight times. When that aircraft is out of weapons, just jump into the next aircraft of the same flight, which also has the same weapons. It takes a bit of setting up, as some aircraft have upto 10 ground attack weapon types and I have a lot of aircraft. However, once done, it’s done

Isn’t that what FC3 are for, along with the “game” mode that is in the options?

It’s worth remembering that whilst it’s possible to absolutely load up the A10, that it typically wasn’t used that way in for example the Gulf. From what I’ve read, during the Gulf war, loadouts were often limited to no more than one weapon per pylon. The reason was to maintain a level of agility that is lost when loaded to the max

My first suggestion is to run a search. Others have experienced the same and there’s plenty of recommendations. As a starting point, limit the preload to around 45% and set you Textures (scenery) to low

+1, pretty please

Cfag> Fair enough. As long as that’s the reason as against to use it to batter the developer for not meeting proposed deadlines, then sure.

If you have a scan in options/controls you can see all of the bindings for devices (eg joysticks), keyboard and mouse. in my bindings and for most aircraft, I had a red notation against for example the Screenshot command. My assumption is that this keyboard setting is used elsewhere, eg for the UI Layer or General. Chances are that it’s not important. I’m curious enough to ask

A question for ED. Yesterday I conducted some maintenance on my control bindings, partly to remove the unwanted "default" bindings that have been applied to my new joystick. Whilst cleaning things up, I couldn't help but notice that most modules had several "conflicts" within their bindings. e.g. - Screenshots keybinding in many - Change weapon using an Oculus controller on some The worst appeared to be the SA342, which had maybe 6-10 conflicts. As mentioned, I've deleted all of the potential conflicts. My question is whether we should be concerned about these? Clearly not for myself as mine are now fine. However, for others who might be completely unaware, could these conflicts result in any logic issues, e.g. whilst trying to update controls during flight?

I use MSAA x2. No, it’s far from perfect. I’m hoping that when DLSS arrives the option of DLAA (a sub mode of DLSS) will help. DLAA made a huge improvement to shimmering in another sim and for me was much better than MSAA.

Unless the comments like “spaghetti code” is from the devs themselves, I’d be careful about the assumptions. After all, most of us have little genuine understanding of building applications and systems and the implications and typical processes. For all we know, the MT update is a clean sheet rebuild of parts of the code and unless a dev says otherwise, it’s just speculation. What I do know is that I also have other aerial combat sims and a couple of the best know Civ sims. From my perspective, DCS: - looks better, eg significantly more detailed than the other combat sims. I was out in the big Civ sim yesterday and in helicopter, low to the ground, many of the buildings like like melted marshmallows. Sure, it looked great at 10.000’, but it was awful low down. - since the MT update, runs better than the others in VR, even more so with dynamic foveated rendering. I’m amazed that there’s not more noise about the big Civ sim for how badly it runs. Quite clearly it needed MT. At least DCS players won’t have to wait until 2024 and then pay again to get it - we know that Vulkan is coming and will hopefully further enhance things - I assume that I’m not alone in loving how much effort it takes to fly an aircraft in DCS. I find it quite confusing to jump into other sims where I can’t touch things in the cockpit In short, I also own most of the other flight sims currently available, and for me, they look worse, run worse and feel a bit pants to be in when compared. Don’t get me wrong, I really want Vulkan and other things (eg AA accuracy to be resolved), but generally, I think that we’re in a great place

I was thinking much closer to our south Atlantic map. I know some don’t rate it, but I think that it’s really good

My thanks to those who’ve included their timezones

I already have a centre mounted stick. Ive just added a left mounted stick (Virpil) for use with targeting pods and similar. Once up and running, the first thing I did was to remove all of the initial load controls that DCS assigned. Next day, I go back in to setup the new assignments, only to find that DCD has re-applied the same assignments that I didn’t want in the first place (eg control of the cyclic in my Apache, which is therefore also duplicating my centre mounted stick. Any suggestions or workarounds?

Sure: https://imgur.com/a/mqg4t9U

I didn’t get on with the Pico4. Good visuals, but their software drove me nuts. I recently moved from a Rift S to a Quest Pro. Much better visuals and it’s eye tracking has allowed the use of dynamic foveated rendering, which is like having a GPU upgrade. The cons are: - crap audio. My solution is a pair of Koss KSC75s - really really uncomfortable by default. Again, I have a solution, ie a pack of 4 Zeltauto elasticated cinch straps (£11 in the UK). I use three of them side to side and it changes it from truly awful to “what headset”?

I was just having a play this evening with some settings, whilst flying the Apache over Vegas using the QP. It did appear that I was able to use what I'd consider to be fairly "aggressive" settings for the DFR using OpenXR Toolkit. I had it down to 15% for the centre at x1 and whilst I could kind of sense the fuzziness, it seemed acceptable. Definitely going to have to play with that some more Had another play with the ASW. Using ASW seemed to induce regular judder. Locking the framerate to 36hz seemed to me to work well Anyone else? One other question, within the Oculus page in the section where you can change the default framerate from 72 to 80 or 90hz, I couldn't help but notice that rendering resolution changed, depending upon the refresh rate, despite the multiplier staying at x1. Why would that be?

Yep, read that. My comment wasn't just aimed at the OP.

I’ve got to ask, for those with VRAM concerns, have you set your terrain textures to low? I did and that helped a lot.

agreed. If you both want to experience the use of a trainer aircraft, then I’ll happily vote for the CC101, but really, it’s not needed.

Ingenious. I’ll give that a go, thanks

Fine here and I was out in the Gazelle last night. Couple of thoughts to check: Ensure that you've no duplicated axis controls Checkout the new trim button. Works just like it does in the Huey now, i.e. very well

Another solid patch with a good bunch of fixes. My thanks to the support team

I watched that to, interesting stuff

Good call, like it