Jump to content

Fizzle

Members
  • Posts

    66
  • Joined

  • Last visited

Everything posted by Fizzle

  1. If you have moved your Saved Files from the default path, note that HaptiConnect won't find your Scripts directory correctly. It will write an export.lua and some other scripts to the default location, so you can go grab them there, copy them to the correct location, add the line to your actual export.lua, and get it working that way. This is HaptiConnect 2.3.1, the latest as of today.
  2. This weekend I also found that an unarmored SA-10 TEL took 2x282s to kill but a single 151 HE would do the job. Happy to provide a track if it would help, but it's trivially reproducible.
  3. From the most recent changelog, DCS 2.9.3.51704: Something is amiss, here. 282s used to be a completely reliable way to kill lightly armored vehicles like BRDMs, BMPs, Shilkas, etc. with a single rocket. Since the patch, it virtually always takes two. Are others seeing this?
  4. Seems unlikely this was intentional: Texaco in Mission 9a is flying at 190 knots. I sort of assumed I could refuel if I wanted to, then end the mission and move on to part 2, but having the tanker so slow made this impossible.
  5. Curious why you removed this. It was handy whenever ED shipped an update, to ensure the backup data was good when you re-installed mods post-update.
  6. Yep even a small wing rock will fix it, so you can do it pretty last-second before releasing if you have to.
  7. I’m using OpenXR and still the older varjo-foveated DFR. No OpenXR toolkit.
  8. A few days later I have had a single instance where DCS didn't start in VR with this set. So it's not a complete fix, but it's definitely a big improvement. Used to get VR starts about 20% of the time, now it's more like 90%.
  9. I'm ashamed it took this long to find this, but checking the "Enable Virtual Reality Headset" option in the VR settings fixed this for me. I've been using the --force_enable_VR switch so long I forgot that setting even existed. With this setting ticked, the startup argument is irrelevant and DCS is starting in VR every time. It looks as if the last patch introduced a race condition that affects reading launch arguments but not config settings. To avoid having to launch DCS twice now when I want it in 2D (the first time to change the setting), you can modify the ["enable"] = true value, the last line below, in [Saved Games]\Config\options.lua. It has the same effect as changing the setting in-game. options = { ["VR"] = { ["bloom"] = false, ["box_mouse_cursor"] = true, ["custom_IPD"] = "62.4", ["custom_IPD_enable"] = false, ["enable"] = true, Hope this helps somebody else.
  10. Are you overclocking? Monitoring temperature? AVX instructions can really increase temps and you could be seeing thermal throttling by the CPU.
  11. Almost certainly a DCS bug. Don't waste your time re-installing the whole OS!
  12. Not sure another anecdote is helpful in any way at this point, but I find this to be a massive improvement with a Varjo Aero at max ppd.
  13. I figured this out from info here, here, and here. Modify your existing (or create a new) steam desktop shortcut and change the URL to steam://launch/223750/option1
  14. Ah! Got it now. Thanks @LazyBoot and @A10Yoda.
  15. Sounds plausible but I can’t find it. What file inside the miz?
  16. Ah, didn't expect that and didn't even look! On the whole, that's a good thing. It's too bad you can't set preset names for the new radio there. We also now have an even weirder mish-mash now of where radio presets can potentially be set: The mission editor (Not sure where in the miz this gets saved, I couldn't find it. Probably a binary format inside the mission file, so it's opaque outside the ME.) The avionics folder inside the miz, from "prepare mission" in the editor. These are luas so editable outside the ME. The ARC_210_param.lua in the core A-10C_2 scripts, which I realize has likely IC issues and whatnot, but it's the only place to pre-set the names and freqs.
  17. Not disbelieving you, just adding info in case it's helpful. I don't have this issue with my Aero. I use native OpenXR support, vsync and reprojection both left off, highest PPD. I use the OpenXR toolkit, but just for the performance overlay info. With the MT build, I leave turbo mode off and don't bother with any of the sharpening, foveated rendering, or other post-processing stuff. If you're using it, I'd be suspicious of turbo mode causing trouble in the MT build.
  18. Any word on miz support for the new radio’s presets? I, not expecting full mission editor support anytime soon but it would be awfully nice if we could set this up with lua in a miz. I know about the script in the main game directory but that’s presumably going to have pure client validation issues and obviously isn’t mission-specific.
  19. And because the confine mouse cursor to game window option has never worked well, this (alt-enter to fullscreen) is the only reliable way to ensure clicking around your cockpit in VR won’t result in the game window losing focus.
  20. I thought there was a time when TAD threat rings were on the schedule when dev resources became available. Possible I'm misremembering. Any chance of an official statement one way or the other?
  21. I forget that on the actual throttle it’s a persistent switch. I use a hat on my throttle. It does make sense for a persistent switch so I can imagine this was actually an unpublished “fix.”
  22. Was this in patch notes and I missed it? Definitely new behavior a few patches ago.
  23. This was introduced a few patches back, when changes to the A-10C II started up again. Steps to reproduce: Make the TGP WHOT Make the maverick display SOI Boat switch forward to make symbology black. Note no change on TGP (correct) make TGP SOI. It switches to BHOT on its own. (new behavior a few patches ago) Any change applies: if the TGP starts in CCD, boat forward or aft on the maverick will change the TGP accordingly when made SOI. Short track with just this behavior attached. maverick-boat-affects-tgp-on-soi.trk
  24. Came here to see if this was already reported. Same here.
×
×
  • Create New...