ARM505

Hi, yes, I've also had it recover, and as you say, its not always that step, just most often at that step. I am on Windows 11, but not getting any CTD's - if it does run, it runs reliably at least.

Same. Recently, DCS dies on the 'loadTerrain' step of mission loading. One core is at 100%, everything else is idling. Repeat until the heat death of the universe (or I force close it from task manager). It hasn't always been on this step, but that's the most common. I've only managed to load into actual gameplay about 10% of the time. Pretty much unusable at the moment for me.

Not only that, but requiring login each and every time I run from the launcher - doing system/fps testing, a lot of system changes require a restart (changing VR settings as well). Can we not just assume the login is still legit because I logged in 60 seconds ago?! It would alleviate a little load on their authentication end as well.

There are several mouse cursor customisable options that could be made. Here's a few suggestions: - Bring the cursor in view, centered (as suggested in this thread) - Cursor sizing/fading options (ie. start big, then become smaller after x seconds to find it) - Cursor relative position options (this has been suggested before, a lot, but basically; keeping the cursors position relative to VIEW direction, or COCKPIT position. For example, if you left the cursor on a specific switch, then looked around, the cursor would still be sitting on that switch despite you having looked around - this eliminates the tiny amount of 'jiggling' that can be experienced with position sensing in VR, allows accurate button presses, keeps cursor on a rotary as you scroll your mouse wheel, etc) - Cursor colours, transparency, shape etc The cursor relative position as a selectable option is my personal favourite.

I have a 4090. It has a pretty decent helping of VRAM. The Chinook is the only one that tanks the fps when playing multiplayer - and playing in VR, 'tanks the fps' means literally halves it. Funnily enough, the sim never recovers unless I kind of 'reset' the headset by taking it off (turning it to standby) and putting it back on again, so kind of a reset. I assume textures get a little 'flush' when that's done, because it doesn't recover without that. Then again, it's a Quest 3, and the Meta software is garbage. 'yOu nEEd tO ReSet yOur BoUNdArY'....no. I don't.

I'm not making this up in my head, I promise. I, too, had the same thought as you. See this thread: They work. Sometimes they don't. I'm not sure of the common denominator when they don't work, but they do work. Edit to add: Oh, and I only play DCS in VR. So yes, they work in VR. And to be absolutely clear, by 'work' I mean both move, AND clear water droplets.

Amazingly, and this was a sneak update for me, but the wipers in (at least) the Hind and Apache now work. I didn't see it if it was indeed put in a patch note, but there's something. And yes, having played enough with rain now, it is a bit 'oily'. IRL it tends to coagulate into little rivulets and streak off a little better than currently in DCS - which does, admittedly, look very good in certain situations, so they're moving in the right direction.

Not entirely unrealistic

R Ctrl R Shift P?

Weird. I literally just tried it after reading your first comment and the Apache 100% did NOT do it. Is it map dependant? I tried the Hind on the Caucasus map, and the Apache in Dubai. Sorry, I know this is off topic, but strange that one has it work, and somebody else doesn't (same version of course, we've all got the CH47 and MT I'm assuming). Edit to add: For testing, right now, I loaded the exact same mission and ran it. The Apache's wipers worked. F***** if I know what was happening last night. For some reason, the exact same mission (I just spawned into an empty, raining map, no changes since I did it last night) and the damn things worked fine. Sorry, just weird. I'm curious when this was changed, because I tried wipers very recently and none of them did anything (hence my original comment) In another oddity, in the Dubai map, for some reason the front seater wipers in the Mi24 wouldn't work at all (tried AH64 and Mi24 on Dubai and Caucuses, both spawned hot). Anyway, cancel everything I said, sorry again for OT. Weird.

Yes, in both aircraft they physically move, but only the Hinds wipers will actually clear rain off the windshield. I think it's the only DCS aircraft which has wipers that actually work? Last I checked, the Huey's don't actually move water yet either. The Apache's wipers move, but don't affect the rain. So...the CH47's wipers probably aren't high on the list, but you never know.

It wouldn't really matter anyway, as wipers in DCS don't actually clear rain off the windshields.

Based on what I observed online last night, the CH47 is *amazing* at aerobatics

I too tried TelemFFB and frankly some of the effects are outright ridiculous (easy to turn off of course). The ground 'rumble' just threw the stick all over the place and is way over the top, 'G Effects' are ridiculous IMHO (G force doesn't increase stick force, stick-force-per-g is kind of constant)......apart from tuning some effects (ETL was hugely overstated based on my experience, but again it can just be turned down, same with the 'gear extended' effect, also vastly overstated, if needed at all), some (most?) effects really should just be turned off. Elevator droop is cool and realistic, but has to be turned down to near useless levels to allow the effect of slipstream over the elevator in the warbirds to overcome it and actually lift the elevator (based on personal experience, I'd like the slipstream effect to actually be more pronounced, so that's on the DCS side I'd say). Just my 2c. I've actually also gone back to using the stick without TelemFFB. The buzzing to let you know flaps and gear in transit was quite useful (if not really realistic). My biggest problem with a lot of the effects is that (UNLIKE the real thing) the shaking affects your control inputs. In the real thing, the whole machine is shaking, you're just feeling it through the stick (and your ass of course). In an FFB device, the thing that's doing your control inputs is the only thing shaking, so your inputs are moving as well - for the ground rumble effect, gear deployed effect etc, this seriously affects your control inputs during flying, as well as takeoff and landing. /long off topic section Back on topic - also no stick force on the CH47, 'to be implemented later' no doubt. Edit to add: All just my opinion of course! I've never flown a Mustang (the closest to a warbird I've come to flying is the Harvard/T6 Texan, along with several thousand hours in light aircraft instruction, but that's like Cessna's etc The only helicopter I've flown personally is a Robbie R22, which is definitely a vibration machine!) I'm using a Virpil 20cm extension with a Mongoose grip, and the 11 degree throw limiters in the Rhino....this may well affect the experience.

Curious that the update required an OS reboot - that's the first time I recall seeing DCS need that.

It's ridiculous having to constantly battle with Meta's rubbish software, or the feeling that cable is somehow an 'afterthought' - why can we use hand tracking/passthrough view in the Quests native OS, but not in the Link software? Why is there even separate Link software? What exactly is Meta smoking? Who knows..... For me also, cable crushes all the silliness associated with getting a fast, stable, reliable wifi signal - having to buy a dedicated router is ridiculous, I luckily had a spare to test with, but of course the simple USB cable is miles easier and better. And I'm just getting warmed up.....why does the Quest not manage to charge despite being connected to a cable? Why does.... /ten deep breaths. Calm...inner peace..... I am greatly, greatly disillusioned with modern large software companies. It's like they've started inhaling their own.... I'll stop now.

I've never seen a response, but could easily have missed it.

I got mine today. It was surprisingly easy to set up. The software seems excellent, everything worked first try with my Virpil stick and extension. Helicopters are great now, the smooth feeling and excellent damping is really impressive on all aircraft - some of the modern ones are of course a bit weird with default settings - for example, the F16 is very light in the pitch axis, but stiffer in the roll axis....and of course is completely unrealistic with anything but a dedicated F16 stick anyway. The F4 is quite 'light' as well with default settings. All force can be immediately ramped up on the fly with the software, or (even easier) with the rotary controller on the stick. I haven't had anything go wrong, including switching between all types (warbird, cold war, modern, helo) in a single mission. Anyway, more playing to do, there are a lot of settings to play with. I haven't even touched that TelemFFB thing yet. It's expensive, and the Rhino will probably remain pretty niche given that it's not from a major hardware manufacturer (the build quality is great in my opinion, no issues with the print/box at all, very neat). And as mentioned, I've found the software to be excellent. It remains to be seen what Moza/Winwing/Virpil do, but this is a great product and I've been impressed so far.

You're not the first to ask...

I'm not an expert on modifying the .cfg anymore, but the Canopy Reflections is now a slider in the in game UI (and of course the new launchers settings) with a variable setting range from 0 to 1, in 0.05 unit increments. Maybe that has something to do with the old settings removal?

If you're talking about right clicking on the dropdown for the device and selecting 'clear all', or having saved, then reloading the settings, then yes? Otherwise I'm all ears! Speaking of saving, I'd also like an option to save ALL bindings (not just as a per-device save) for each aircraft. Edit, to add: I see your answer above, yes, familiar with that. Definitely works......shouldn't be necessary IMHO, but I'll live with it.

Good day, This seems simple enough, but I'm not sure what the general consensus is: Unless you have the most basic of flight controls, and even then I don't see how it'll always get it right, no software can correctly assign functions to all buttons and axes on a newly detected device. So, I respectfully wonder if there is any point at all of assigning anything by default. I'm kind of tired of having to go and clear everything from every device (I have six - joystick, throttle, button box, rudders, F16MFD 1 and 2) when the control assignments get scrambled, or windows does some USB device ID scrambling (whatever the problem might be, but it happens). I'd rather start from scratch each time, as DCS's default assignments literally never get anything right. Assigning pitch and roll axes to throttles, pedals etc is just a waster of time. I've seen the argument that 'new players need basic assignments', but to be honest, it's most likely going to add even further confusion as their aircraft thunders off the side of the runway because their throttle axis is also randomly their rudder axis. tl;dr - please DO NOT assign any controls to any controllers axis or button by default.

I remember this discussion in a certain hardcore tank simulators forums (SB) - the guy in charge responded that they thought it was kind of pointless to have simulations inside a simulator. Then again, the overriding ethos there was 'does it have training value?' and to them, the answer was no. DCS is a different story.

I wouldn't know what it's like in a fighters bubble canopy without rain removal, but I've had to go around in real life in heavy rain WITH WIPERS on high (in a Boeing 737-800) because the wipers simply couldn't clear the torrent of water that is coming in, and the runway lights turn into a giant blurry mess that you can't use to land. It was like trying to land with a fire hose directed at the windscreen. But really, no idea how that translates onto a bubble canopy. Do they have rain repellent, or bleed air rain removal or something? I confess to complete ignorance on what (if anything) fighters actually do! I have to say, that video looks realistic to me (again, zero real life fighter experience!)

Full sequence of actions, but I don't think they made a difference: - Installed patch last night, ran it, and modules were disabled as per the problem we all know. - This morning, ran the launcher again, same issue with 5 files showing as available, but nothing in the list. - Ran a cleanup (deleted all but screenshots) and a repair (I don't think this had any effect, listed only for completeness) - Ran DCS, no warning on launch, all FC3 modules available, flew the F15C without issue (except control bindings were gone?!) - On exiting the mission editor, the module managed in DCS showed FC3 as available - 'installed' it, but nothing was downloaded, only file integrity verified. - Flew the Su25, again no issue (control bindings all there, no problems) tl;dr - I did a cleanup and repair via the launcher, really don't think that was the issue.