Jump to content

Hoirtel

Members
  • Posts

    1300
  • Joined

  • Last visited

Everything posted by Hoirtel

  1. The video is about 30fps without ASW. Apparently this is smooth, I haven't tried it yet myself.
  2. Thanks, I think you are saying highest possible frame is mostly the best.. This is not my experience, I have flown like this achieving frame rates of 40-80 (80hrz) with no ASW and, to me, this is a horrible experience. Not smooth. I current lock to 40fps and ASW on and its seems buttery smooth. I can sometimes get the full 80fps which is really great but its only a small amount of the time and the flicking between on and off isn't very nice so I lock to 40 with ASW. I'm interested in trying this 90hz and 30fps with ASW off, but from my own 2yrs DCS VR experience this will be horrible. Not really sure how the 30hrz in OTT is applied if it isn't an option within the debug tool?
  3. I cant get 30fps with debug tool. If I choose disabled I get the highest possible framerate.
  4. P8 anyone...
  5. I'm glad I found this thread! I was having problems over the weekend, can't seem to get things working at all. I would have though that the single transmit button would just work whatever radio was selected, but on occasion I press transmit and it pings back to the 863 (if I wasn't trying to use that). Also had no answers or transmit message come up when using the 863. Anyone got any workarounds or info on updates?
  6. I find vsync fast an NVCP essential for flying at half or full refresh rate. It just makes the whole experience cleaner, can't rely explain it but I have tested it several times across a couple of headsets and can't fly without it.
  7. Yeah. I usually screen clip the co-ordinate boxes and paste them in a Photoshop file to export as PNG. Complete faff and not multiplayer friendly. Even if the briefing appeared on the kneeboard rather than the esc menu. That would be something at least.
  8. I've asked this before. It's been mentioned by several people over the years but nevers seems to make it in. Utterly crazy really. Not long ago they introduced a co-ordinate display so you can bring up a box of all the different types and elevation for where the mouse pointer is. Great, almost handy, except there is no where to save them to... Only the briefing. Which doesn't appear on the kneeboard... Duh. The lack of kneeboard editing is my main gripe with DCS....just seems so simple, yet never done.
  9. copy root folder. repair, then replace? workaround...
  10. I'm wondering about no 2. It would be good to somehow bind all four of these, but to a twin axis throttle I don't know how that will work...
  11. I'll look at your tracks and can make one myself no problem. The picture attached in earlier posting (razo+r) shows what I was referring to, although I haven't tested in various wind strengths.
  12. I knew he would regret that.....
  13. There is another way... I have a quest 2 and have noticed that if its not powered on DCS will load in 2D mode. It also loads the oculus software and steam VR which if you close either of these will crash DCS. DCS has on a couple of occasions crashed for me during this "forced" 2D mode (enable VR headset always selected) however this has not been recently and so may been part of some earlier OB patches. This is super handy as I basically now have the dual mode that I always wanted. If you dont use a Quest 2. I would suggest powering off/unplugging your VR headset and launch DCS normally (via desktop/start icon). Maybe for longer term ease of use you can use a USB hub with switchable ports. Probably do the same.
  14. Yes its the same thing. The added resolution is always required in VR to account for the distortion. The confusion comes from both oculus and steamvr handling this in a way that appears to be very similar to supersampling, thus when people "correct" it and match the resolution to the headsets panel specifications (which usually isn't exactly possible) they are actually undersampling.
  15. This is an unfortunate confusing point with the Q2 as it has an extra slider within the main oculus software (not debug) that allows you to control the panel res. Oculus will control this automatically which will allow for smooth use in all systems. However you can change manually. For whatever reason oculus decided to name these changes as 1.X but the X relates to some sort of system load rather than a multiplier. On my 3090 full res is 1.5 (90hz) seems on the 3070 it's 1.7. Same res, different systems. The pixel dimensions are displayed and are larger than the native res of the panels which is the pixel distortion value. All this is effectively locked at full in the rift s as there are no such controls available (I have this too).
  16. I would build it up slowly as it's almost impossible to do everything at once. You will have no idea what's working and what isn't. But if you love to tinker as you say then maybe it works for you.
  17. I run a Q2 in DCS and have no problems. Yes I'm on 3090 and I run full oculus res. However from extensive testing I know that doing this at 90hz is demanding. I prefer 80 as it gives more visual headroom. Also adding in any supersampling at this resolution is an instant cripple. Do do it. I don't need it to be honest. I can read and see everything. I wouldn't expect a 3070 with around half the cudas to be able to run a Q2 at this setting.Ido get 100% GPU usage. Not sure if this is sudden, or wrong. Is it hot. Yes. Are the fans running. Yes. Do I ever get slowdowns. Yes. But I don't see there is any problem.
  18. Any effort spent tuning tuning is worth it and using other's help will significantly shorten the time required. I'm well into the love of VR thread!! I have been on and off sims for a very long time. I used them because I want to experience flying. I went off them because I couldn't experience flying. VR is a technology that has been on the horizon for years, and I have said years ago "one day I can fly jets in VR and it will be awesome". These days I fly jets, warbirds and helis in VR and it is...awesome! Without VR I would probably do something else.
  19. I think it might be different with the powerlines as these are made up of such small textures that we are running into conflict with the pixel density of the headsets. I can't see this being fixed with a changed to rendering. Unless I'm confused and the shimmering and aliasing are seperate.
  20. Its not in any of the changelogs so its still to come.
  21. F5. Fun, fast, simple.
  22. Thanks for the supporting pic. Yeah I think it's been around for a while and to be honest I have mean meaning to report it and didn't. Not a big problem by any stretch.
  23. General minor bug I think. All map based windsocks seem to not blow in the wind, all static object placed windsocks do work. I haven't got a track but should be fairly easy to check for anyone. Open map, place static windsock next to map windsock. Add wind. You will see one blows and one doesn't. I could get a still frame if required.
  24. Tried out latest patch this last weekend. I know there was a patch note on a change to the rendering of trees and buildings, I can't exactly tell this specific change but overall I felt the sim is performing better and looks better (in VR). Hard to describe but everything seems more solid and clear. Running my own benchmark scenario I can see that the performance was very good. Great work ED!
  25. Yeah I believe HUD on DDI is the "proper" way. My own personal protocol is to change this over for the ADI as in a sim I see a backup hud as a bit pointless. I also like to have HSI on either left or right and then FCS on the middle. I only have this on as I have random failures enabled but I'm yet to experience one...
×
×
  • Create New...