Jump to content

Sprool

Members
  • Posts

    583
  • Joined

  • Last visited

1 Follower

About Sprool

  • Birthday November 2

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

  1. I think I resolvd it by plugging the X52 into a different USB port, though I have no idea why this would cause the issue.
  2. I noticed a strange issue with the rdr cursor when revisiting the sniper pod and mavericks. For slewing the cursor round in the MFD's (all modules) I use a little thumbstick on the side of the Saitex X52 Hotas throttle unit. I set the Y-sat and sensitivity way down to get a nice smooth slew rate. In the F-16 TGP and Mavericks I noticed the cursor keeps drifting vertically upwards, even when I try to fix it to a ground object. If I map this to keyboard presses (eg: U,D,L,R cursor keys) it remains steady and fixed, until I use the thumbstick for the x & y axes again. The thumbstick does not have this bug in any of the other modules (F-18, Apache, Harrier, F-15e, KA-50). I checked for any axis conflicts but there are none. Any ideas I can try?
  3. 'Post your log and track file' - is that ED's version of kicking the can down the road for another 2 years?
  4. null1. 'normal view' shows (a bit faint) the HMD centre is about 20 degrees off the horizon, too high. 2. Altered view, with the Quest 3 black interface removed so that the lens unit can be swivelled down, bringing the HMD to the correct azimuth. Note: this has no effect on the head position. Head (and VR headset) remains in same position when you tilt down the lens unit, ony the HMD display moves. This is why changing the cockpit camera vew settings will not cure this problem. Flying in a darkened room without the interface attached is not so much of a problem, but when you have light streaming in a lot of the immersion is lost. I am purchasing a different silicpne interfact to see if that improves things, but what would be good is an aligment setting in-game to resolve this problem. It's probably not a widespread issue amongst many headset brands, but its challenging for Quest 3 users - one of the most widely used cost-effective headsets currently in the market.
  5. Someone on Redditt mentioned it may be linked with the vertical resolution of the Quest 3 display, so it may well be fine in other headsets. I know due to astigmatism in my own eyes I have to have the Quest 3 lenses totally perpendicular to my eyeball alignment to get good crisp focus straight ahead, so its a particular issue for me which means the view a little above and a little below the centr line is not so well focused. Im not sure you could pick up the VR headset position in a track view? If I knew how to record in VR I could post a short clip. I can try to replicate it with a coouple of screenshots ...
  6. Well a kind person on Redditt posted a workaround, which means you have to remove the black visor thing that blocks out the light, then on the Quest 3 and Bobovr halo head strap it allows the lenses to be rotated down a small amount to bring the hMD centre back into alignment. Takes a little bit of gtting used to, flying without the visor, but at least I have a VR HMD that can be used.
  7. Never touched views.lua. No mods concerning F-18. What is interesting is if I align hmd in flat screen mode it all works fine, right int he centre of view as i look around with the mouse. When I do same in VR the HMD display remains elevated about 25 degrees too high, and changing cockpit camera viewpoint doesnt alter that.
  8. I know this thread is a few years old now but I'm just getting into VR (quest 3) and really wanting to use the HMD in the F-18 to spot ground targets. I align it but the HMD remains well above my view when Im looking straight forwards down the planes nose. Its not an alignment issue, its not a 'centre VR' issue, the HMD remains high no matte where you move the cockpit camera view. It means to use the HMD to spot ground targets I have to bury my chin in my chest to get the HMD low enough to pickle targets. Surely thee must be some way of adjusting its position (as opposed to aligning it)?
  9. I have a button bound for that, it centres the cockpit view, the HMD remains annoyingly high up, its linked tot he headset spacial position, not aligned with the cockpit.
  10. I should add - this is the Quest 3
  11. Im struggling with the HMD in VR, its way too high up. If I go through the alignment procedure, on the ground (cold start) or in the air (hot start) it still ends up way too high so I end up looking out the cockpit with my chin on my chest to move the hmd centre to pick a target. Can it be shifted downwards?null Screenshot shows me looking straight ahead before and after alignment
  12. Recalibration is not needed, all the other modules axes work fine. Sliders are also just another stepped ramp of potential from zero to one, as you move the stick axis, just as curves are, so i dont really get your point. It works fine exactly like a custom curve does but with more control
  13. Hmmm, I do adjest aileron trim in special settings. What i dont understand is if the oystick axis is set to standard curve the diamond is always offset, if I change joystick axis to slider it can be set tot he middle by tweaking the user curve
  14. Same issue as the Viggen, needed to double-click the mouse scroll wheel to toggle coickable cockpit. Annoying but fixable. in DCS/Mods/aircraft/FU-4D/Input/Mouse/ create a backup of default.lua file then add line 14 and disable or delete line 13
  15. Is the Val a 3rd party mod?
×
×
  • Create New...