Jump to content

Sporg

Members
  • Posts

    1122
  • Joined

  • Last visited

  • Days Won

    3

Everything posted by Sporg

  1. The trick is to get a soft light in the room, not necessarily a strong one. In my gaming room I use the same light as I used for my Oculus Quest 1: In the evening, one LED lamp pointed oblique upwards towards the wall in front of me. In the daytime light comes from windows to the side of me, if it gets too strong, I pull down the blinds. This has worked perfectly with both headsets. I do try to avoid reflective surfaces, since I know that the G2 is sensitive to that. If I play in the living room, I have to cover the TV. (This isn't necessary with the Quest.) Here I use a ceiling lamp with a light damper, so I get a soft light there as well. In the daytime there's light from windows at two sides, also here I put blinds if it is too strong.
  2. Hi Could you add me to the waiting list as well? Thanks in advance.
  3. 1.5 V is confirmed by a HP employee here: I've seen it confirmed at other places as well. There are 1.5 V NiZn rechargeables out there, but they are described as unreliable, and they require that you buy (yet another) special charger for them. One guy describes a mod to run the controllers at other voltages, using a cheap voltage converter, but that demands some soldering skills, and that you are willing to take your new controllers apart: Another guy performed the mod here: https://www.reddit.com/r/HPReverb/comments/i8y3nb/hp_reverb_controllers_mod_the_battery_will_last/ All in all I am extremely disappointed that HP/Microsoft has not solved this problem for us in this day an age, with the big prevalence of 1.2 V NiMH batteries. My Oculus touch controllers run perfectly with 1.2 V NiMH, and are able to show correct remaining charge as well. I am very much tempted to perform the above mod, since I'm not afraid of neither tinkering, nor using a soldering iron. ;)
  4. I have had some success setting terrain shadows to flat instead of default. That reduced stuttering a lot. I have not tried reducing terrain textures yet.
  5. Thanks, nice to hear. :thumbup: Yes, there is no helipad at the hotel, just a nice platform in the map, would be nice if you could land on it. ;)
  6. The approach beacons for Aleppo runway 27 floats in midair: At the Adana Hotel "Seraton" there's a pad that can be fun to land on with helicopter, but you sink halfway through:
  7. I can confirm that the helipad is still not working. Actually it's the whole roof of the hospital that does not have collision, I sank through the roof when I tried to land at the front end instead.
  8. I solved the problem by having a table in front of me. I put my controllers there, so the gloves "disappear" behind the instrument panel. That way they are always available when I need them. I use the controllers instead of mouse. I am using Oculus Touch controllers.
  9. It looks like it. But then they are not really of any use, because you could do this with debug Tool already. Oculus Tray Tool is only really necessary because you can't set Pixel Density via Link without it. Debug Tool only sets it temporarily, on next reboot it's gone. So if you want it to just be set in the background, you need OTT to set it at every bootup.
  10. In the new v19 software, Oculus has added an extra Link quality related "Graphics Preference" option, under the Devices -> "Oculus and Touch" menu. It contains four options: "Automatic" "Prioritise Quality" "Prioritise Performance" "Balanced" Default it is set to "Automatic". I tested out "Automatic" with my manual settings as described in the guide (Resolution 3648, PD 1.3, Distortion curvature Low) and then "Prioritise Performance" with Oculus Tray Tool switched off. In windows there didn't seem to be much difference, however DCS seemed a bit more blurred in the distance when using "Prioritise Performance" alone. I checked with Oculus Debug tool also, and it said that Resolution and distortion curvature stayed set as I had set manually, however Pixel Density was still at 1.0 with the "Prioritise Performance" setting. So it seems that only when using Oculus Tray Tool you get the Pixel Density set higher. So eventually I decided to keep my manual OTT settings, which still works when keeping the "Automatic" setting in "Graphics Preference". But feel free to experiment for yourself how it works for you. At least it's an improvement that people can take an easier approach and at least get somewhat better quality with a simple setting.
  11. If you want to save money, get the i7 9700K instead. You don't gain anything by buying the i9 after what I read from people who upgraded.
  12. It's only partly provided. Pixel Density doesn't stick when set there, so you will need to do it every time you boot up your pc. Resolution does stick, but I don't know about the other settings.
  13. I wish they were as careful with releases. ;) Problems have been reported before. And immediately after release of v19 firmware reports are beginning to appear from people who get their headset "drowned" by a mysterious "device error log", that writes 60+ lines every time they try to use their headset. Reboot or even total factory resets don't help, it seems. I'm a little vary of testing v19 right now. (Edit: Issue might be related to Oculus Browser needing update.) But otherwise you are of course right. I am happy that they are starting to implement better Link graphics settings. What I wish for is just that they also make an advanced settings section, on your own responsibility of course, where you manually can set and tweak Link resolution, PD and ASW, as you want it. Maybe even with per game profiles. OTT has that, and for instance SteamVR has that kind of settings as well.
  14. Check. :thumbup: I will wait until v19 is finally released and then test it. I suspect that I will want to keep OTT if it keeps working, unless Oculus provides manual settings for Link as well, because Oculus recommends lower PD settings than what OTT recommends (and than what I use). According to their v12 recommendations they use Resolution 2912 and PD 1.2 for RTX 2070 GPUs and up. I use OTTs recommended settings of Resolution 3648 and PD 1.3 for my GTX 1080TI (RTX 2080+ equivalent) I use the same PD in DCS and the same resolution in SteamVR and both results in a very good and clear picture quality. HL: Alyx in SteamVR runs the maximum 72 FPS with these settings, DCS around 30-36 FPS and up.
  15. Issue: Oculus Tray Tool not starting up with Windows I got an issue with Oculus Tray Tool no longer starting up with Windows after the new Oculus software update. It seems to be an old bug, but it can be fixed: The developer said, you need to go into settings and switch startup with Windows off, then on again. I did this, and it starts up again as it should, and works fine with the new version 18. In other news: Oculus are planning some prefix settings for Resolution, Pixel per Display override (PD) and Distortion Curvature, so you might not need to set them in tray Tool, unless you want special settings adapted to your own setup. It's in the current v19 beta, so I guess it could release with next major version. https://forums.oculusvr.com/community/discussion/90944/v19-ptc-pc-software-release-notes/p1
  16. Galinette, I got the recommendation from Oculus' own release notes for the software version 12, so you should ask them which setting is correct and which setting does what. I link to that very page in the references in the last page of the guide. You can read for yourself here: https://forums.oculusvr.com/community/discussion/83561/oculus-link-resolution-with-v12/p1 Oculus Tray Tool seems to more or less follow the same recommendations. But you can always change the settings to your own liking. PS: Upon re-reading your comment, it falls in line with Oculus' recommendations: On low (normal) resolution use "Default". On medium resolution use "High" and increased pixel density. Only on high resolution you should use "Low" and an even higher pixel density.
  17. Thanks. :) Sadly, I haven't tried Virtual Desktop, so I can't do a guide on that. Have you tried running the Quest with cable instead of Virtual Desktop? Maybe the performance would be sufficiently good then? Personally I wouldn't be able to live with lower resolution than the Quest, to be honest.
  18. A slight addition to the guide: It seems that as of software version 17.0 Oculus has added the possibility to use a USB 2.0 cable, like the charger cable the Quest comes with, for Oculus link. I have only tested it shortly, it seemed to give increased lag, so not so useful. But give it a try if you want.
  19. The P-40 has one thing going for it, besides a good dive ability: It had a surprisingly superior roll rate. I found that while researching some old documentation. Also, AFAIK it was still in use later in the war, as a ground attack and support aircraft.
  20. I use Quest in room mode, I just draw the Guardian area on the floor big enough to include the desk. You need to take care of your hands yourself though, but it works fine here. I start DCS from a shortcut on the desktop, that works fine here. If you want, you can check the guide I made on using Quest Link and DCS, there's also some optimization on picture quality. I'm using same GPU as you, so you should be able to get some improvement like I did. https://forums.eagle.ru/showthread.php?t=276595
  21. To be honest, I think you just got default ASW, and now it works. Not to say "I told you so", but, I told you so.. :P :D Good you got it working. :) :thumbup:
  22. About ASW: I don't recommend switching it off. Very few, if any, can reach 72 fps, and that will mostly likely only be with very low graphics settings. I run it at Auto, that works fine here. I've tried the fixed settings, but I didn't feel I gained much out of them, so I eventually set it back to Auto. That's also why I recommend leaving it be in OTT. Try with Auto if it works well for you, it should. Also, 30 fps is in the low end, you don't have much margin for drops. If you can be at 36 fps it's generally better. But see what works best for you. About "Out of focus" messages: Do you perchance run SRS , Simple Radio Standalone? That's a known phenomenon with that. You need to switch off the window it automatically starts when you connect to a server. Otherwise you'll have to leave DCS, click with your mouse in the DCS window on your monitor, and then go back again. I got tired of that, so switched it off for now.
  23. Sad to hear your experience. It sounds like you may have gotten a bad sample. I'm running DCS with Quest, and it runs really well here. Using the recommended Anker USB cable, and have had a no problem neither with Wi-Fi nor with Link connection. I got the Quest because I had too high IPD for both the Reverb and the Rift S, so I'm happy I was able to get it to run well.
  24. Thank you. Finally a definitive answer. Then my guess would be that DCS works best if it is set to the same PD as OTT already forces. That makes sense to me.
  25. Very interesting, I will try that. I have been trying the new P-47, in Caucasus I had around 36-51 fps, but in the new Channel Map it fell to 24-30, which is a tad too low. I'll see if it helps to switch Terrain shadows to Default.
×
×
  • Create New...