Rocky49 Posted July 6, 2016 Author Posted July 6, 2016 I will re-run the setup in my rift to see if that helps. I will also check the mapping on my other modules ie F86, Huey, etc to see if it is different. Thanks for the replies :thumbup: System:Motherboard Asus ROG Strix Z390-E,Asus ROG GeForce RTX 2080Ti OC, GPU, 32GB Corsair Vengeance DDR4 Ram, Intel i9 9900K @ 5 GHz , cooled by NZXT Kraken X52, Acer XB270HU G-Sinc monitor, Windows 10 Pro, Warthog joystick and throttle with wasy extension, VBK Gunfighter Pro and MCG Pro,MFG Rudder, running on a dedicated 1TB Samsung 970 Pro M2 Nvme , Super Wheel Stand Pro, with a HP Reverb G2
SkateZilla Posted July 7, 2016 Posted July 7, 2016 So Far, what I'm seeing in every aircraft is correct, (ie Taildraggers) when looking forward, you are looking forward on the aircraft axis, therefore world will be tilted. Windows 10 Pro, Ryzen 2700X @ 4.6Ghz, 32GB DDR4-3200 GSkill (F4-3200C16D-16GTZR x2), ASRock X470 Taichi Ultimate, XFX RX6800XT Merc 310 (RX-68XTALFD9) 3x ASUS VS248HP + Oculus HMD, Thrustmaster Warthog HOTAS + MFDs
Rocky49 Posted July 7, 2016 Author Posted July 7, 2016 I re-installed my sensor and started a A10 mission. Initial position is still too close to the HUD and again to the right of center. Also slightly too high. Tried to save the position but it did not save, again using RALT and 0. Am I the only person experiencing this? Other that the A10 and F86 all the other modules Huey, Gazelle, Mi8, L39, Black Shark, M2000, P51, and Dora seem to be Okay, or at least workable. System:Motherboard Asus ROG Strix Z390-E,Asus ROG GeForce RTX 2080Ti OC, GPU, 32GB Corsair Vengeance DDR4 Ram, Intel i9 9900K @ 5 GHz , cooled by NZXT Kraken X52, Acer XB270HU G-Sinc monitor, Windows 10 Pro, Warthog joystick and throttle with wasy extension, VBK Gunfighter Pro and MCG Pro,MFG Rudder, running on a dedicated 1TB Samsung 970 Pro M2 Nvme , Super Wheel Stand Pro, with a HP Reverb G2
reilar Posted July 8, 2016 Posted July 8, 2016 I also have a problem with this in A-10C. My default starting position is very close to the HUD. If I move the viewpoint further back I will not be able to see all info in the HUD. I have to lean forward (a lot) to be able to see the whole HUD image at once.
Redeye Posted July 8, 2016 Posted July 8, 2016 Can't save the new settings. Open game and check the Options / Misc / and make sure the "User Snap-View Saving" has a check in the box.
NeilWillis Posted July 8, 2016 Posted July 8, 2016 I can confirm that the A-10C starts with the pilot too close to the HUD. I just lean forwards, press NP5, and it's fine. I would however like this to be looked at so we don't need to keep editing lua files every update. I am sure it'll get the attention it needs, and may even already be fixed for the next update, who knows? All the other modules work fine as they are for me - and I have them all.
Highwayman-Ed Posted July 8, 2016 Posted July 8, 2016 You're welcome to try using my default saved views here just extract this to your Saved Games\DCS.openbeta\Config directory. Make sure to backup your own folder if you already have some of your own default views set first! I've tweaked the default views for most DCS Aircraft to suit my personal taste with the Oculus Rift. Intel i9-9900KF @5.2GHz MSI Z390 Gaming Pro Carbon 32GB G.Skill Trident Z DDR3200 RAM MSI RTX 2080 Ti Gaming X Trio 40" Panasonic TH-40DX600U @ 4K Pimax Vision 8K Plus / Oculus Rift CV1 / HTC Vive Gametrix JetSeat with SimShaker Windows 10 64 Bit Home Edition [sIGPIC][/sIGPIC]
Rocky49 Posted July 8, 2016 Author Posted July 8, 2016 Can't save the new settings. Open game and check the Options / Misc / and make sure the "User Snap-View Saving" has a check in the box. I do have it enabled System:Motherboard Asus ROG Strix Z390-E,Asus ROG GeForce RTX 2080Ti OC, GPU, 32GB Corsair Vengeance DDR4 Ram, Intel i9 9900K @ 5 GHz , cooled by NZXT Kraken X52, Acer XB270HU G-Sinc monitor, Windows 10 Pro, Warthog joystick and throttle with wasy extension, VBK Gunfighter Pro and MCG Pro,MFG Rudder, running on a dedicated 1TB Samsung 970 Pro M2 Nvme , Super Wheel Stand Pro, with a HP Reverb G2
Sierra_three Posted July 8, 2016 Posted July 8, 2016 I recently received my CV1. Now I can't see the F10 map or the kneeboard. And when I try to change the loadout via groundcrew I can't see every load type. some just disappaer in the lower of my view. any solutions?
SkateZilla Posted July 8, 2016 Posted July 8, 2016 I recently received my CV1. Now I can't see the F10 map or the kneeboard. And when I try to change the loadout via groundcrew I can't see every load type. some just disappaer in the lower of my view. any solutions? F10 and Kneeboard not Visible are separate Issues, and have been resolved in 1.5.4. Please dont post multiple problems not pertaining to the original posters problem in the same thread. Windows 10 Pro, Ryzen 2700X @ 4.6Ghz, 32GB DDR4-3200 GSkill (F4-3200C16D-16GTZR x2), ASRock X470 Taichi Ultimate, XFX RX6800XT Merc 310 (RX-68XTALFD9) 3x ASUS VS248HP + Oculus HMD, Thrustmaster Warthog HOTAS + MFDs
SkateZilla Posted July 8, 2016 Posted July 8, 2016 I do have it enabled Not entirely sure, but I think SnapView Saving is disabled in VR. Try launching w/ VR Disabled, and editing snapviews. Windows 10 Pro, Ryzen 2700X @ 4.6Ghz, 32GB DDR4-3200 GSkill (F4-3200C16D-16GTZR x2), ASRock X470 Taichi Ultimate, XFX RX6800XT Merc 310 (RX-68XTALFD9) 3x ASUS VS248HP + Oculus HMD, Thrustmaster Warthog HOTAS + MFDs
Asset Posted January 5, 2017 Posted January 5, 2017 I also have a problem with this in A-10C. My default starting position is very close to the HUD. If I move the viewpoint further back I will not be able to see all info in the HUD. I have to lean forward (a lot) to be able to see the whole HUD image at once. ^^ this As stated simply moving backwards does not solve the problem, as the compass band at the bottom of the HUD is not visible anymore.
Recommended Posts