Jump to content

TED

Members
  • Posts

    412
  • Joined

  • Last visited

Everything posted by TED

  1. I'm really not sure what's going on. To be honest I'm very happy with VD and it was more our of curiosity to try link. I have OXRTK disabled so theoretically I'm running the same resolution, however it looks very different. I think if nothing else this just kind of proves the power of vd as an amazing product in that it just works with minimal fuss. I may have another look later at link and try to see where its going wrong. I noticed as well that I can't seem to get dynamic foviated rendering working properly in link. No problem at all with VD. This shouldn't affect the difference I'm seeing anyway as the fixed foviated render is working in link. I'm even starting to wonder if the oculus debug tool is actually doing anything. If I adjust the resolution up and down in link it is a clear difference but when I set default resolution in link, the 1.73 in oculus debug it looked like very low res.
  2. Thanks again. Tested the cable. All is good. Used the exact same settings as you and still just looks terrible compared to vd. Looks very low resolution too. Something is not right somewhere in my settings. Probably i will just stick to vd as it just seems to work without any messing about.
  3. I have an aftermarket usb c cable I bought that is good quality. Im not sure what else could be accounting for such a large discrepancy in quality. The main difference is in smoothness. Link just seems very choppy compared to vd. Would u mind posting your odt settings?
  4. Yep. I found it. Thanks. Had a good test of link and in my opinion VD is just way better. It seems much clearer, much better performance and more user friendly. Not sure why this is. When I set and compare both like for like - 72fps no asw, HEVC/H265, godlike resolution and 1.0 in oculus debug - VD is very smooth, with a much better image and no stutters. Link just is not. It looks worse with less clarity and quite stuttery.
  5. Stupid question, but where the hell is the oculus debug too?
  6. Im currently using a quest pro and have always used VD as my previous Pico 4 worked great with vd. Considering trying quest link out of curiosity. Will QVFR and DFR still work with link?
  7. I've just picked up a quest pro and no issues for me with eye tracking. I do not have developer mode enabled. It seems like that's not required anymore.
  8. So now after flying a bit I am getting used to it and can compare the pico and quest a bit more. There were a few things i was slightly worried about before i got the headset after reading lots of reviews, such as lower resolution, screen door effect and comfort. I can now say after a few hours of flying, none of these are an issue at all. Screen door effect - I cannot see it at all, even when looking for it. Total non issue and that’s it. End of discussion there. The same for resolution. Whilst being on paper lower resolution than the pico, the image quality is definitely much nicer in better colors and clarity, as well as true edge to edge clarity. The lower resolution is absolutely not noticeable at all. Comfort - I actually find this headset sits quite well on my head and don’t find any real discomfort after a couple of hours flying. Overall for anyone considering and upgrade from a pico 4, I would say yes it’s worth it as long as you are not paying full price. The pico 4 is an absolutely amazing headset for the money. I’ve had very few complaints with it at all. It replaced my 8kx and was better in every way. The quest pro is the next step up. The colours are wonderful, with local dimming really making the blacks nice and dark. The contrast and warmer colour gives a really nice look. I find as well there is a much better visual representation of straight lines, being far less jaggy and more natural. The whole image is just wonderfully clear, sharp, well balanced and natural. It’s a considerable improvement hard to describe if you haven’t seen it. Finally, and the main reason I went for this, the eye tracking. This really does make a difference. It significantly offloads the gpu, allowing me to really make the most of the graphics settings. In general the way the quest pro interacts with VD seems to be slightly different to the pico. I don’t know how or why, but the experience is smoother. The overall performance is just exactly what I wanted and I’m very impressed and pleased with the upgrade.
  9. To be honest its really not a complaint. We will always have a limiting factor. The 5800x3d is a fantastic cpu, and to be limited to around 72fps in only a very few rare busy situations is nothing to complain about. It means i can set 72fps on the QP and never have an FPS drop basically. This is a real quality of life improvement for me, basically now never really being GPU limited, especially with qvfr now in place. My GPU has no problem maintaining 90fps on maxed out settings once I'm above very low level.
  10. 7900xtx, 5800x3d, 64gb ram, 2tb SSD. With this I'm actually cpu limited. I can max everything and in the air i keep a steady 90fps but closer to the ground and once in a furball of fighter its drops to around 70 due to cpu limits.
  11. Thanks. Yep worked it out. Wasn't difficult, I was just rushing and being stupid. I forgot to tick the box in VD for forward tracking or something like that. Now all works great. The pro looks wonderful. I'm very pleased. I'll write up a more detailed comparison later once my excitement dies down a bit and I've got time. Needless to say tooling around now at 80fps steady in all phases smooth and clear with really high settings is wonderful.
  12. Yes i did. Although developer mode dpesnt seem to be needed for that now. I did the calibration and test in the headset and ot was following my eyes. Additionally setting up a developer account seems a real pain. Requiring id, business doc verification and the like.
  13. Got it all setup in DCS and looks great! The only thing is I'm not sure the eye tracking is working. I've installed quad views but seems like it's only giving me fixed foviated rendering. Not sure why. Eye tracking is set up and calibrated on the headset.
  14. Yep. Definitely.
  15. I pulled the trigger and will get the pro today, so hopefully get to test everything in the next few days. I got it unused, still packaged in the box for a reasonable price. I probably could have got it slightly cheaper if I shopped around a bit but the convenience of getting it quickly and the seller seemed like a good guy made it fairly easy. Very much looking forward to testing it all out.
  16. i had a bit of difficulty following the benchmark stats! What kind of performance increase would one likely expect using DFR over FFR? My setup is a 7900xtx, 5800x3d, 64gb ddr4.
  17. Kind of a subjective question i suspect, but in what ways is the QP better in your experience?
  18. The only things really that bother me a bit with the Pico are some of the visuals - straight edges are not great, there's quite a bit of ghosting and the compression artifacts can be a bit distracting sometimes.
  19. whats the issue with passthrough?
  20. I have the chance to pick up a used quest pro for a reasonable price - less than a new q3, and was considering upgrading my Pico 4. Has anybody used both and is it a worthy upgrade? I've been very happy with the Pico 4, especially considering what I paid for it, however the QP with eye tracking seems very tempting. Any and all opinions welcome. It's only for use in DCS.
  21. Yep - steamvr runtime. I always hated steamvr before and had pretty bad time with it but it seems very good now. The first time you run dcs in Pico connect to you will need to change the runtime probably. After that close all things steam and steamvr related, the open dcs only via your desktop shortcut whilst inside the pico. It will then open steamvr itself. I'm now running 175% steam resolution and ultra in Pico.
  22. For those pico users out there, I’d recommend having a go with the native pico connect streaming assistant again as an alternative to virtual desktop. I’ve been a bit back and forward for the last year, but generally preferred VD, however the latest update to pico connect has brought me back. I’m getting very nice performance with it, with less compression artifacts and very smooth play, better colors and seems just generally nicer visuals overall. it seems like there have been quite a few tweaks in the last updates and it’s definitely a viable alternative now and well worth trying.
  23. Ahh that makes sense. I actually didn't realise there was that generation gap between the two fighters in dcs.
  24. I’m fairly new to the spit and getting into the details of performance and management now. While doing an instant action escort mission, the bombers and escort are at 18000’ when we get bumped by some 109’s at the same altitude. Of course at the higher altitude and lower density the lift vectors are less and airspeed all the more important, however it does seem like the 109’s have impossibly good performance at this altitude and trying to turn and maneuver to fight with the spit is extremely challenging. I was always under the impression the mk ix had a good advantage at high altitudes and up to 25000’ should be very doable. Am I missing anything key here or any good tips to see me right?
  25. As the title says - I'm doing a simple mission with an ai wingman as nr 2. We take off from Hawkinge. I get airborne, gear up and look back and he's just gone wing into the ground on the takeoff roll. No idea why and it's not every time but probably 70%. I know the spit is a bit twitchy but if I can manage it I'm sure ai should be able to. Any ideas what causes this?
×
×
  • Create New...