Jump to content

Blackhawk163

Members
  • Posts

    260
  • Joined

  • Last visited

Everything posted by Blackhawk163

  1. Ah yes woke. That magical catch all word that when truly pressed can't be clearly defined. You said it a lot nicer than I was going to. Anyway, I'm going to send ED my complaint about the lighting issue, but I seriously doubt it will get much traction. If one of their top campaign contributors can't move the needle after a year, I doubt I will be able. But you got to try So how about it @BIGNEWY any news on this?
  2. Oh, I found the Column just fine, as another method I used was just to fly heading 336. I'm just saying that if I followed the prompts as given to me, I turn 330 when told, then I slew within the FCR or HSD for 336/57 and mark the location it will steer you to the area just south of Murmansk. I'm also not fully up to speed on the F16 having mostly used the a10 so I'm learning as I go with this my first f16 campaign, So I know I'm doing something wrong. But this mission was perfect for me, and I actually had a laugh at the end. First, I started it late last night, I was already a bit tired but figured this wouldn't take too long, then all that happens, So I option the bad radio route, refueling goes horribly (I'm like dead tired at that point) but I get it done. Coming home that thing happens, and I'm like, I'm so done. Bravo? Sure, why not? I have such a hard landing that I briefly black out, I get so mad at myself and am about to rage quit (I don't play with that invulnerability function enabled), when I see I'm about to go off-road so I fight to bring it back to center and come to a stop. Mission should be called Murph lol
  3. Wait, is this Emily? Because for the life of me I tried using the reference on the FCR as 336/57 and put me way off from where I needed to actually be which was (I'm spit balling here) more like 330/110 or something like that. There is a way to do this via the FCR, I just don't remember how
  4. I started DCS on a 55-inch display which was great, then I got a track IR and thought this is wonderful. Later decided on VR and got the crystal light, blown away. First week of VR and I'll admit, I had a bit of motion sickness to start. Your brain works a bit overtime processing this. That whole sat at a traffic light but the bloke besides you starts moving and all of a sudden you feel that motion too, so you slam the brakes even though you're already on them. Yeah, that's how it felt for me. Quickly got over that. Now I have a 55-inch display that just gets turned on to login (I use the virtual desktop experience in pimax play) when playing the various sims, and the track IR needs to be sold. Don't get me wrong, having a 55-inch display is great, but its relevance really does depend on its primary use case and ultimately, you.
  5. I used to have it as my master arm. Master arm off in the down position and on in the fully up. But this is mainly used for the F14 and F4. All other modules I just use a switch on a throttle. I have big hands and would accidentally trigger/arm it. Not that it matters, as it’s a game so use it or don’t. Maybe as a refueling door switch?
  6. Thanks! DCS and Pimax play are the only things that are open aside from whatever is running natively in the background. I’m in VR and don’t record my sessions nor am able to watch YouTube on the pc. If I’m stuck in a mission that I can’t hack, I’ll just pick up me phone and launch YouTube and watch it on there either while in AP or just pause outright
  7. The whole HAGS thing leaves me head spinning. Some say on, others say off. Is this a processor dependent thing, GPU driven? I've left mine on with no ill effects.
  8. Yeah, soon as I saw that video I did the same even though I solved my issues I figured that this couldn't hurt anything.
  9. Device-> General-> OPENXR Runtime SET PIMAX OPENXR RUNTIME AS OPENXR RUNTIME make sure that's enabled.
  10. Okay I’m glad I stumbled on this thread. I was curious if there’s a way to set shift states for any and all buttons. any help with this would be greatly appreciated. So in the VPC software there are currently only 5 shift states with buttons already populated in these states (67-71) in order to set the encoders to a shift state I have to sacrifice a push button that’s been shifted? Can I just turn the encoders to normal buttons and have them be shifted? lol I’m so confused. Oh wow, it really was simple to do this. I’m pleasantly surprised at how versatile this throttle is.
  11. I’m about to load up the new update, hopefully this doesn’t bring back any issues. What a weird issue this is. Seems that there’s no one fix for it all. I guess that’s the nature of pc gaming as a whole, so many different variables.
  12. The Crystal light appears to have a port near where the display port connects to the hmd. Is that an actual connection waiting for a use case or just a dummy slot?
  13. I didn’t get that from his video at all (about not getting a review sample), unless I just watched a different video, but more so from the way Mark from GYGO was treated by the customer service at Pimax for his troubles and ongoing quality control issues. Which, to be fair, is sound advice. I have an ongoing issue with their customer service with some after sales stuff where one of their CSR agents straight out lied to me about a promotion. Lie about the small you lie about it all. In any case I usually wait for a consensus of multiple YouTube reviews and the DCS and other flight-sim community reviews as well.
  14. Both work for me. I could give you my complete settings for both DCS opxrtk etc. just shoot me a pm and you can do your own tests from there
  15. Oh don’t I know it! My response was more to the person who used the Iraq map to highlight the stuttering. What I should’ve written is exactly with what you responded with. I’m stutter free for the most part. The only time I get any stuttering is when I become GPU bound and the fps drop causing my frame times to react simultaneously. So I’m good now. It was crazy to just cruise and peer over the sides and watch and see the landscape below me stutter the way it did. Hopefully everyone still getting theirs in relatively tame parts of their respective maps find a solution to their woes. Mine, however unconventional as it might be, required the simultaneous running of QV and FFR.* I can repeat this 100% of the time now. *also whatever graphical setting that I have selected in dcs/pimax/opxrtb
  16. So on waypoint three (?) of the f16 free flight mission over Baghdad, it’s a stutter mess. My fps drop from 72 (Pimax locked) to 53-55 and choppy. There simply too much being rendered for my 4080. If I look straight it’s smooth at 65-72. Once out of there and flying towards and past the airport everything goes back to normal and I’m back to 72 locked with no side window stutters.
  17. Okay I had an opportunity and a bit of bravery to tinker with my settings. I disabled Quadviews in Pimax xr and loaded up. Not only did the stutter return, but I lost 10fps as I had 72 before disabling and 62 when disabled. In my use case it’s quantifiable.The settings I had in FFR looked horrible btw without having QV activated. I restarted DCS with it (QV) back on, and then disabled FFR in opxrtk, it looked great but stutter city when looking out the sides. Turned FFR (it’s great that you can do this is real time btw) and after a few seconds, stutter gone. Is this the fix? No, idea, but this is what’s working for me. Despite the author of the app saying don’t run them in tandem, I am, and will continue to do so. Good luck to all in search of their fix.
  18. There might be. I dunno, but since implementing that one line I quoted from you, it seems my system has settled into a really good rhythm of sorts. The only time I get stutters is when over densely populated areas (think Baghdad) which was my normal anyway even outside cities. Now when that happens It takes a second or to but goes back to smooth side views. Gone, presto whammo lol Maybe something else is happening, dunno, but for now you get the credit at least for my case.
  19. Yup I have openxr tool kit, pimax xr with quadviews checked and QV companion with my settings. Zero issues.
  20. I thought the same and yet I have none (problems)
  21. Disable Power Throttling. Local Group Policy Editor > Administrative Templates > System > Power Management > Power Throttling Settings > Turn off Power Throttling > Enabled Reducing Latency and Interupts:PowerSettingsExplorer: Processor performance Time Check Interval -> 5.000 for active Power scheme I guess technically two things. But that’s what I did.
  22. Whelp, my stutter is mostly gone, I made one change to my setup up, and I'm not touching anything else. I set the PCL to 72 because that's where I get the most consistent FPS. For me I'm chasing a balance of visuals and smooth consistent performance render to .78 (in dcs it's still 1.0). I'm running Quadviews XR in conjunction with FFR in openxr toolkit. NIS on and with a 1 inner 1/6 medium 1/6 outer ring in FFR settings. I've been running this setup for weeks and I mostly hover between 70-72fps (I always test after the BFM in Tarinkot quick mission either in the 14 or the F4, orbit over the airfield at about 15 units @400kts and 200ft) In the past I'd get the same issue, smooth out the front with that slight annoying stutter off the sides. I made one change today as I was curious to see if @Ready is a pulling a King Tantalous or if he's on to something: Disable Power Throttling. Local Group Policy Editor > Administrative Templates > System > Power Management > Power Throttling Settings > Turn off Power Throttling > Enabled Reducing Latency and Interupts: PowerSettingsExplorer: Processor performance Time Check Interval -> 5.000 for active Power scheme I did that, and just that. I don't run process lasso, I'm just OC'd to 5.4ghz -30 curve,1.225v max, expo on, SMT on, MB limits on the PBO side. My meager 4080s has its factory OC plus my Msi afterburner oc on top of that at 150 for the clock and 1000+ for memory. All this and still had the stutter before today. Now it's mostly gone only appearing for a second or two should I get a quick dip from say 72-67fps, and then it's gone.
  23. But why would you even need to? IRL you are PTT anyway, this is barely any different. This is also a godsend in VR, especially when the pass through is horrendous like the Pimax CL.
×
×
  • Create New...