Jump to content

Eldur

Members
  • Posts

    4273
  • Joined

  • Last visited

4 Followers

About Eldur

  • Birthday 03/23/1984

Personal Information

  • Flight Simulators
    My Little Pony: Clear Skies
  • Location
    On a fluffy cloud above Ponyville
  • Interests
    Being awesome
  • Occupation
    Weather Pony, Wonderbolt, Foreign Agent
  • Website
    www.smile.gov.eq

Recent Profile Visitors

31643 profile views
  1. Came back after a few updates that I didn't fly with... Title says it all, not all devices are affected, though. Can't map my Sidewinder FFB2 and Crosswind pedals anymore, anywhere. They show up in the mapping page, but all actions are greyed out for them. My previous mappings are still in the user folder (made a backup, just in case), but aren't being loaded up. I don't get any new Win/USB-GUIDs for them apparently. Any ideas? Edit: device list and sys specs in profile Edit 2: I guess I found the culprit... just tried the UH-1 and it's fine in other modules. So I bet it's being caused by the input luas, going through a repair now. Edit 3: That actually was it. Works again
  2. I hope that will also be possible through the rearm & refuel panel, the comms menu or the kneeboard during a mission while staying on the ground, ideally in a way that other devs can make use of that as well like the A-4E-C team even. Sounds great! BTW I wish the screenshot showing the menu was in higher res. Edit: Maybe I should have read the thread before... but anyways. Good to know this will be accessible during a mission!
  3. I've been having performance issues in VR for quire a while now, with two major impact points... - the first of which being somewhere in late 2020 crippling my DCS performance heavily when using a Metabookulus Quest of any kind (don't have a Pro, though) - which I couldn't solve yet - the second being a major performance impact in VR only with the 2.8 update last November, apparently only really affecting that WMR garbage with the Reverb G2 which was very promising when I still had the 1080 in the rig, but basically didn't gain any performance at all by upgrading to the 3070, plus adding a ton of WMR crashes since (still got the old cable, waaay out of warranty, and I honestly don't wanna fix that anymore while having a Q3 with way better lenses) already before taking the hit, which it only partially recovered from with the step to the MT - and now the addition of DLSS. I started typing this in the patch notes thread with this, but thought it'd be better off as a single post over here: Imagine being just barely able to run the thing at 30ish fps in the G2 at 2456x2404 per eye on a 3070 that was over a grand and then reading this... (and yes, I know the 4090 is a completely different piece of kit) Weirdly enough, I'm pretty much locked at 90fps in the CV1 at 2160x2400 per eye. Quest performance is almost similarly as bad as the G2's, I just recently was happily able to post a 90fps screenshot based on the Snapdragon Game Super Resolution thing and Synchronous Space Warp in Virtual Desktop. Only to find out later that VD displays twice the frame rate that DCS does with SSW enabled. I'm literally pegged to 180fps in pancake at 1290x1200 with the same settings, but even DLSS doesn't really seem to help in VR. My specs are in my profile, I need to update the driver versions and settings though, so here are my current ones: Running MT client with --force_enable_VR --force_OpenXR. As opposed to my settings in the profile banner, I've disabled the single pass stereo line a while ago and kept it off as it apparently doesn't make any difference anymore (it absolutely did a few years back). HAGS is off. Can't enable REBAR (requirement checker is all green-lit, but it doesn't work and basically kills all my system's S3 state capabilities), so I left that off in BIOS. I'm still on the 537.13 driver, though, but I guess I won't see any major impact through updating since I'm having the issues with the Quests which are my main target to fix for years now and no driver update ever changed that. Something kills my performance for WMR and the Quests in both (Air/Cable) Link and Virtual Desktop. Only VR that runs nice and smooth is the CV1. I'm carrying around this issue for 3 years now, went through 2 new Quest lines, a completely new rig, a GPU swap in that one and an OS reinstall as well as trying all the shenanigans and settings that others suggest both here and in various YT videos. I literally had better frames in the Reverb G2 at the default 3168x3100 with the same rig, but still the 1080 instead of the 3070 in there... I've basically tried anything except for taking the step to Win 11 and using the OpenXR toolkit. I just want to be able to really enjoy my DCS in VR again... thanks for any help in advance!
  4. VR controllers don't work for me either since the update. Tried CV1, Q2 + Pro (Air Link), Q3 + stock (Virtual Desktop) and G2. Someone else already opened up a thread saying their Index Knuckles won't show up either. So I highly suspect it's a general issue not related to any specific headset / set of controllers. It's stimply just broken currently and all we can do is patiently wait for a fix.
  5. I have it on keyboard and it doesn't work there...
  6. Same with Quest (3) controllers. They're completely gone in DCS. Edit: Same with CV1. Also: Can't recenter anymore. DCS' "VR recenter" keybind in UI Layer is dead.
  7. I'd suggest that any changes should probably result in an option selector in the difficulty settings that can be set and enforced on all clients in a multiplayer environment. This is the only way to get most of the people happy, by giving them all the options to choose from. Those should be the prior system, the current one and probably new one that's kinda a blend of both which probably should be the default one as well. Wouldn't want to have better visibility for a patch or two, only to have it taken away from me just because most of the community thinks it's not realistic and maybe even making a radar for finding bogeys superfluous (which it totally shouldn't). Ever player/simmer is different and they all have different setups. Making it possible to scale it to everyone's preference is the right way to go. It also makes it more barrier free for people with vision impairment. And making it so that a server can enforce a setting will kill any discussion about exploiting it right at the get go. We've been through that with the label thing a lot already. And I think using the label system as a substitute workaround in the past for what was added now apparenty (didn't have the chance to try it myself yet) is a thing that needs to be replaced, and the moment for that is right now with the new approach. It just needs ways to customize for best possible personal experience.
  8. This is quite literally upping my hopes of finally being able to do some air to air stuff even remotely again. I've been having A LOT of spotting issues in DCS ever since (even before my eyes went bad), the only times I didn't was back in the olden days of LOMAC running at just 800x600 or 1024x768 (remind you, Lock On did have 2x2px black dots over every object at any distance) and when the 2.0 Alpha was a thing with those impostors that actually were too big and made it too easy even for me.
  9. Am I just *bleeping* dreaming? I literally changed absolutely nothing, just kept updating DCS, my drivers occasionally and Windows regularly. My nVidia driver is 537.13 from late August (think it's the Starfield ready one, don't have that game though). The only notable thing I might have done was to wipe the driver and do a clean install that time... but I tried that without success before. I guess I'll up the res to somewhere around 2800-3100ish vertical which I already had been running my G2 at with good enough framerates (55-70ish) on that rig. Knock on wood, looks like I'm back in the 'pit again, finally! And DLSS hopefully will make it even goodererᵀᴹ! And yes, this isn't even using the Oculus runtime, but I do have the "--force_OpenXR" switch in, but had SteamVR up and active as the OpenXR runtime while trying. No OXR Toolkit installed yet either, running the MT exe. Oh, BTW. Night and Day difference with those lenses and the better FOV...
  10. Can't wait for the thing... preordered on the day after the keynote, but it hasn't left the company that I ordered it from yet, guess DHL will pick it up today and then only the princesses know how long it will take. I just had to snag it day one - the better lenses, better FOV, better audio and also the AR/MR features, the better guardian system... so many improvements over the predecessors! Can't wait for DLSS support in DCS 2.9 either. I still don't know why, but ever since somewhere around late summer / early fall 2020 my DCS performance when using Quest headsets is completely abysmal and that issue has survived a few OS reinstalls, a completely newly built PC and the switch from Quest 1 to Quest 2. I can run DCS in the CV1 at 90fps, but only getting around 20 in the Quests at literally the same rendering res, same graphics settings. Regardless of the connection I use - tried them all - wired Link, Air Link and, of course, Virtual Desktop. When I got my Q1 in March 2020, it was just brilliant, for about 3-4 months... I'd just love to get my performance back at some point... Also have been using the Reverb G2, but that one keeps making the WMR software crash way too often ever since I swapped the 1080 with the 3070. Didn't get the newer V2 cable though and I'm on a 5800x, so I guess that might be the reason for that. Just weird it never was a problem when I still had the 1080 in the same rig - which was the main reason why I never cared about trying to get the cable replacement when I still was eligible for it, by being within warranty. Should have done that anyways... And well, speaking of DLSS: In that other sim, you know, the civil one that replaced Crysis as the benchmark, I kinda miss the purpose of it, I get worse visuals thanks to the artifacts coming from scaling stuff up bases off of a lower rendering res, but I don't gain performance at all. Well, the complete opposite goes for No Man's Sky, which runs like garbage on my rig (20-25fps range at medium settings) with no AA method at all (to save performance on that stuff), but then instantly kicks up to 90fps flat with DLSS enabled on Quality setting, there's even no need to lower it down to the more performant modes. And I can't see any artificats either. It's simply just pure black magic happening there, and I love it! And that's exactly what I want it to do in my good, old, beloved DCS as well! I don't know, how this can be achieved, but ED, please, justmake it happen, somehow!
  11. This is literally the biggest reason to just use VR controllers instead, much easier to aim at stuff with those anyways. But for those that still use the regular mouse, there should be some keybind that pops some highlight animation so you'll know where the "darn thing" is hiding again. Like that "show when Ctrl is pressed" thing in Windows mouse settings (the old, better CP), just prettier.
  12. I'm literally stuck in this training mission at that point where he keps saying something "you wonder why I'm telling you all this... bla bla, good job, well done". Already found out that the IN CMD on the HUD only comes in A/G Master Mode which he mentions is being switched to if you just Castle Up. So when I have IN CMD visible on the HUD and I am in A/G to get there even, what is the instructor waiting for? Nothing happens anymore...
  13. Thx for spotting this. I just did the first training mission and thought "why not just go up and do a Mach flight now?" and I basically got four impressions: - at some point my FF went to 0 and I could go for ages. Thought something was broken and even considered unlimited fuel being active in the mission and that happening after emptying the CFTS perhaps to be a thing. - tops out at under 1.8 in level flight. Tried at the typical 36.5k and 42k as well as going down from the latter to the first with the waterline at the horizon. - trying to go over 1.8 in a dive is bad. Lost like a third of my right wing, but could at least land the thing with the DCS typical ever burning damage model. Probably was too fast too low during that dive test. - I like the module, anyways! If I'm not completely mistaken CFTs are cleared for up to M 2.0 and I've definitely seen some of the content creators do somewhere around 2.2 with no issues and I guess with the thrust alone and clean setup, it should be possible to reach that, especially when there's a CFT limit that you basically should stay within. There'd be no reason to have that if you couldn't even get there. Source: trustmebro ('cos of 1.16). Didn't even notice it basically AAR'd, because I didn't mess with the MFD pages yet
  14. Have a nice vacation, I guess Le me is now hoping that this still works with today's update... but I'll probably be going to play that Hammerwatch 2 Demo mostly instead until Moonday anyways (going to be an absolute gem for anyone who likes retro style RPGs, will release in mid August)
  15. Made my day! Currently fetching the map. Was able to update the game yesterday already. Somehow.
×
×
  • Create New...