Jump to content

Panzerlang

Members
  • Posts

    484
  • Joined

  • Last visited

Everything posted by Panzerlang

  1. Nope, not for DCS. I intend to down-sample my Super, because there sure isn't any benefit to be had by chucking more pixels (5090 for a Super at native res) into the already maxed-out Render Thread of my 13900k. IL2, however, will see a huge benefit from a 5090, down sampled Super, so yep. Lol.
  2. Lol. Pretty much a debate over semantics. However, I like this line: " people just state things with certainty when it passed their subjective threshold" Indeed. I believe it has passed my subjective threshold that NVidia are a bunch of lying crooks who are now asking obscene prices for a GPU not significantly more powerful than the previous generation. But huh, define "significantly". If 30% greater rasterization grunt (5090 vs 4090), that's a third more power. If 20%... Then use-case. With a top-end VR headset and CPU the 5090 will be a total waste of money in DCS. The best CPUs already can't keep up with the 4090. However, a 5090 will definitely make a difference in IL2.
  3. I finally got around to trying the 120hz and capping the frames to 50%, no go on my rig. Not a suprise really, it's always the CPU being flogged on at least one core to 100% that causes the issue (and it's the "Main Thread", not the "Render Thread").
  4. Ya. Along with the line "Coo, why ain't DCS running betterer with my 5090?!"
  5. Super, now "Q1". Progress Update January 20
  6. Those most easily impressed are those least worth impressing.
  7. This seems to be reasonably believable. Around 3000 Euros for the 5090s. Obscene. Like, properly obscene. Anyone who believes any amount of R&D and blah blah blah for consumer-grade electronic components can justify or explain such a price needs their head tested. Custom GeForce RTX 5080 and RTX 5090 pricing emerges: made for gamers with deep pockets - VideoCardz.com
  8. I reckon the frame-capping etc uses CPU cycles and as DCS is already flogging one or two of my cores at 100% it just adds to the burden. Using the DCS FPS counter I see very low spikes, so I think Frame time is decent. My stutter is very minimal, I have to look for it to see it.
  9. I've yet to find/use an OpenXR frametime app. 90hz. I've tried all the frame-capping, lower Hz, re-projection, on their own and in combos, they all made the stutter worse.
  10. There was a bunch of components on the cargo plane that crashed a few months ago, that's why the Flanker grip got so badly delayed.
  11. I know, just can't remember his name. Yeah, he'd thrive on a shady car-lot, selling old beaters. "This old Toyota Prius, we tweaked the ECU and now it can go as fast as a Ferrari!"
  12. No matter what you do, you won't be able to completely eradicate micro-stutter/jerking, no matter your graphics settings. Having said that, you can reduce them with settings and Windows and hardware tweaks. Regarding resolution (OG Crystal here with 13900k and 4090), I run the headset at native resolution (1.0) and DCS Pixel Density at 1.0. I've had the headset at 0.75 and could barely tell any visual difference (image quality) but as it made no further improvement to the stutter I put it back to 1.0. Why does 1.0 and 0.75 have so little difference on image quality? Somebody elsewhere pointed out what might be obvious to some (if correct) and that's that the game itself has a limit on how high the resolution of the objects (planes etc) can be. If the hardware is set beyond that limit, you won't see the 'expected' improvement. So, 0.75 Headset and 1.0 DCS PD with my set up, with a 4070Ti YMMV.
  13. The SimHaptic line in the lua file vanished by itself in my case. Reinstall SimHaptic.
  14. I was rather interested in his detailed description of dialling in the physical fit, which seemed to eradicate most of the issues MRTV described (who didn't mention any of that). Could it have been that simple?
  15. Couldn't be more opposite to MRTV's one.
  16. No, I don't. But I have no idea how the Quest Pro works in that regard. I never used to have to re-centre the headset, now I have to do it every time I fire it up. It's pretty quick, just hold down the Pimax logoed button on the controller, wait for the green circle thing to do it's turn, keep the button pressed until the short vibe indicates the controller is shutting down and carry on.
  17. Cynicism alert...I have little doubt NVidia has their tech one or two (or three...) generations ahead of what they're currently selling. They trickle it out like treacle to maximise revenue. I reckon.
  18. With me (Pimax OG Crystal), that happens until I centre the headset (that's separate from centering VR and/or NeckSafer). It's not a bug in NeckSafer.
  19. For the squished XRNS panel issue right click on its desktop icon, then: Properties -> Compatibility -> High DPI Settings -> Override scaling behavior performed by System. Simple tool to check your six - Page 29 - Virtual Reality and VR Controllers - IL-2 Sturmovik Forum
  20. And this is the company that asks people not to send parcels with signature required. Red flags anyone? Or just me, being 'paranoid' again. Where's Calvin these days?
  21. I covered my definition in this video (posted in this thread a few days ago).
  22. Four days for my parcel to be 'security checked' at Frankfurt. I expect they'll now fly it to china before it gets here to Japan.
  23. Now delayed to late Feb or March.
  24. Thanks man, good to know. By printer cable, you mean a USB that has a square connector on one end?
×
×
  • Create New...