Honey Badger Posted December 13, 2024 Posted December 13, 2024 Having an issue where I have to keep moving my head around to see all the information on my HUD. I would move my head in all the way then zoom out a bit and it gets semi better, but then goes back to being cut off on each side anytime I zoom anywhere in the cockpit. I am sitting 19" away from my monitor so I don't think its a distance issue on my end. null Does anyone have a fix for this in settings? Thanks!! null
MAXsenna Posted December 13, 2024 Posted December 13, 2024 You can change the FoV permanently. Do you know how?Sent from my SM-A536B using Tapatalk
Honey Badger Posted December 13, 2024 Author Posted December 13, 2024 I think I remember a bunch of version prior we had a FoV function.. I don't see it anymore.. I do, however, notice there is a Scale GUI. Is that it?
MAXsenna Posted December 13, 2024 Posted December 13, 2024 I think I remember a bunch of version prior we had a FoV function.. I don't see it anymore.. I do, however, notice there is a Scale GUI. Is that it? Press Esc, and options there's a slider. Do to do it a little more accurately, you can change the head position.TURN OFF TrackIR if you use it, or it WILL get messed up. Press RCtrl+RShft+Numpad arrow keys, and use / and * to zoom back and forth.Save with RAlt+Num0.Cheers! Sent from my SM-A536B using Tapatalk
Solution Lixma 06 Posted December 13, 2024 Solution Posted December 13, 2024 (edited) You need to move your virtual head forward in the cockpit. Changing FOV won't fix it. First check that 'User Snap-View Saving' is enabled in the Misc. Options. Then turn off any head-tracking to make sure your view is perfectly centred. Now, while holding R_SHIFT and R_CTRL use the the keys * and / on the keypad to move your head back and forth. This should bring more info into view. While you're there try experimenting with R_SHIFT and R_CTRL with Num_8 and Num_2 which will raise or lower your view point. Once you're happy hit R_ALT and Numpad 0 to save the settings. Edited December 13, 2024 by Lixma 06
Honey Badger Posted December 13, 2024 Author Posted December 13, 2024 Thank you Thank you THANK YOU both!! 2
Greyman Posted January 15 Posted January 15 (edited) On 12/13/2024 at 12:53 PM, Lixma 06 said: You need to move your virtual head forward in the cockpit. Changing FOV won't fix it. First check that 'User Snap-View Saving' is enabled in the Misc. Options. Then turn off any head-tracking to make sure your view is perfectly centred. Now, while holding R_SHIFT and R_CTRL use the the keys * and / on the keypad to move your head back and forth. This should bring more info into view. While you're there try experimenting with R_SHIFT and R_CTRL with Num_8 and Num_2 which will raise or lower your view point. Once you're happy hit R_ALT and Numpad 0 to save the settings. Do you know if this should also work in VR, as it doesn't for me and it's driving me spare? I hate the hit and miss of having to stand up further back than I'm sitting and then pressing the VR camera recentre key(s) and can't think why the cockpit camera keys don't work, at least for me. Edited January 15 by Greyman
Lixma 06 Posted January 15 Posted January 15 1 minute ago, Greyman said: Do you know if this should also work in VR, as it doesn't for me and it's driving me spare? I hate the hit and miss of having to stand up further back than I'm sitting and then pressing the VR camera recentre key(s) and can't think why the keys don't work, at least for me. Sorry, I don't know - I don't use VR so I'd only be guessing.
Greyman Posted January 15 Posted January 15 Thanks anyway. In short, when in VR, the whole of the HUD information cannot be seen when in the current default seating position, in the A10C II, but when you move closer, to where you can see it all, your neck needs to be a lot younger than mine to see the controls on the side consoles, which are then behind you. I'm trying to find a compromise position, but cannot figure out how to set it, without these cockpit camera controls. The current default position seems like a bit of a compromise, but not the one I would have chosen. I have vague recollections of a few years ago, when I was last flying DCS regularly, of a utility that would allow you to move your head position and it would provide a readout of the x,y and z coordinates that you could copy into the appropriate lua file, once you had found the ideal spot. Maybe I'll just need to mess around with the numbers in that lua file, until I find some that work for me. Thanks again.
Porkbrain Posted January 16 Posted January 16 1 hour ago, Greyman said: Thanks anyway. In short, when in VR, the whole of the HUD information cannot be seen when in the current default seating position, in the A10C II, but when you move closer, to where you can see it all, your neck needs to be a lot younger than mine to see the controls on the side consoles, which are then behind you. I'm trying to find a compromise position, but cannot figure out how to set it, without these cockpit camera controls. The current default position seems like a bit of a compromise, but not the one I would have chosen. I have vague recollections of a few years ago, when I was last flying DCS regularly, of a utility that would allow you to move your head position and it would provide a readout of the x,y and z coordinates that you could copy into the appropriate lua file, once you had found the ideal spot. Maybe I'll just need to mess around with the numbers in that lua file, until I find some that work for me. Thanks again. Not quite what you were looking for but I use VR only and have hotas buttons mapped to Cockpit camera move back, Cockpit camera move forward and F1 Cockpit view for all my aircraft. Having set the VR Camera Reset key on first entering DCS then whichever plane/chopper that I use a quick press of either forward or backwards to get my ideal position for that aircraft, then if I go to external views/F10 Map etc., pressing my F1 cockpit view button returns me to the exact position that I'd set earlier. Plus if I need to access a control without breaking my neck I can use those buttons to move right back to flip side panel switches, then again to go forwards.
Greyman Posted January 16 Posted January 16 Thanks for that. I was wondering if the lack of movement on my cockpit cameras, with the default mappings to the Numeric Keypad (with Rctrl & Rshift) might be something to do with either the openXR toolkit, which should use the arrow keys, and/or my keyboard maybe treating the numeric keyboard as arrow keys, whether the num lock button is down or not. I'd tried mapping other keyboard combinations to the function, but I have a TM Warthog HOTAS, so could use the joystick pinky switch modifier along with one of the other hat switches, on the throttle or joystick, to manipulate the views. I will give that a go later, to see if I can get the cockpit cameras to move. Do you need to be in active pause to move the cockpit camera or does it work for you while fully active, when sat on the tarmac of course?
Greyman Posted January 16 Posted January 16 (edited) No. Even controller bindings won't move the cockpit camera position for me, so my keyboard doubts appear to have been a bit of a red herring. When in the bindings screen, the key and controller combinations are recognised, but not in the cockpit itself, with active pause on or off, so it just looks like I must have a setting, or something else, going on somewhere in my setup. Oh, the cockpit camera movements appear to work fine in 2d mode, so it would appear that my VR is somehow causing the issue. Edited January 16 by Greyman
Porkbrain Posted January 16 Posted January 16 2 hours ago, Greyman said: No. Even controller bindings won't move the cockpit camera position for me, so my keyboard doubts appear to have been a bit of a red herring. When in the bindings screen, the key and controller combinations are recognised, but not in the cockpit itself, with active pause on or off, so it just looks like I must have a setting, or something else, going on somewhere in my setup. Oh, the cockpit camera movements appear to work fine in 2d mode, so it would appear that my VR is somehow causing the issue. It does sound like a VR setting might be the cause. I use two Quest Pro's on two identical laptops, one with Puma X hardware, one with VKB stick & throttle, using either the Oculus link cable or Oculus Air link. I don't use openXR toolkit and haven't changed anything in Oculus pc link or Oculus debug tool apart from setting the resolution slider to 1x3 at 72hz and setting Meta Quest Link as the active OpenXR runtime. The only change to the default DCS VR settings panel is to uncheck Use Controllers. The fwd & bwd controls also work when pause and active pause are on, I've just tried it in 2d using the Hotas hat and the Rshift & Rctl keyboard keys and they work just the same. I am launching DCS from Steam using Launch DCS in Oculus VR mode, I have also tried the Launch DCS in OpenXR mode as well but both seem to work the same. And after such a long waffle from me I have to go out for the afternoon but if there are any other settings I can check let me know.
Greyman Posted January 16 Posted January 16 (edited) Just to eliminate the A10C II as being a little odd, if you have that module, are you able to use these controls? As it is based on one of, if not the, oldest modules in DCS, there might be some things that have been optimised in subsequent modules, to allow the VR position to be moved. I did notice that the rctrl&rshift 5 (on the numeric keypad) did move the screen very slightly, so maybe that is the limit of the allowed movement in the A10C II? In the meantime, I'll try it in the Hornet or Viper and see if it works there. That'd probably prove the same thing. Thanks for your help by the way. Edited January 16 by Greyman
Greyman Posted January 16 Posted January 16 (edited) I'm really sorry, as it would appear that I have wasted your time and mine. As the cockpit camera is fully functional in VR for me, when in the FA-18C or the F-16C, it would appear that the A10C II might just be an odd one out. In my defence, I've been away from DCS for a couple of years and maybe there have been changes to the A10C, that I hadn't been aware of, making it very tough to adjust the pilot's position. Either way, I've managed to get the pilots head to an acceptable place, using the Alt+numpad 0 combination, whilst my VR headset adorned head was in said position. Whether that messes up things like the HMCS in the A10C II when in VR, remains to be seen. Thanks again. EDIT: Oh, and now the A10C II works too. I can only think that something on my PC was getting in the way of this and it has now somehow corrected itself. I'll go with that explanation, as otherwise I would have to have just messed up. I'm apparently getting way too old for all of this PC stuff. Edited January 16 by Greyman 1
Greyman Posted January 16 Posted January 16 It is slower to react than I'd expected, so maybe I just didn't hold the keys/buttons for long enough? All's good now though.
guitarxe Posted January 28 Posted January 28 On 12/13/2024 at 5:53 AM, Lixma 06 said: You need to move your virtual head forward in the cockpit. Changing FOV won't fix it. First check that 'User Snap-View Saving' is enabled in the Misc. Options. Then turn off any head-tracking to make sure your view is perfectly centred. Now, while holding R_SHIFT and R_CTRL use the the keys * and / on the keypad to move your head back and forth. This should bring more info into view. While you're there try experimenting with R_SHIFT and R_CTRL with Num_8 and Num_2 which will raise or lower your view point. Once you're happy hit R_ALT and Numpad 0 to save the settings. How do you reset this once you've done it? I've tried playing around with this, but the end result is worse than the original settings (putting the head further forward to see the hud means that you are that much loser to all the instruments and seeing them from a greater angle when looking down, making it hard to see them, and you can't even see the top row of the MFCD buttons because they get obscured by the cowling).
Lixma 06 Posted January 28 Posted January 28 (edited) On 28/01/2025 at 22:40, guitarxe said: How do you reset this once you've done it? I've tried playing around with this, but the end result is worse than the original settings (putting the head further forward to see the hud means that you are that much loser to all the instruments and seeing them from a greater angle when looking down, making it hard to see them, and you can't even see the top row of the MFCD buttons because they get obscured by the cowling). OK, there's no way to explain this without eliciting the response "Are you serious? There isn't an easier way to reset the view settings? WTF?" Strap in. Quick and dirty way Go into your C:\Users\*****\Saved Games\DCS\Config\View folder and delete the 'Snapviews' file. When you hop into a mission DCS it will rebuild the file with ALL the views (all aircraft) reset to default. If you only fly the A-10 then this might be the best way. The safest way Using Notepad++ (or similar) open the Snapviews file and search for 'A-10C' or 'A-10C_2' Scroll down to 'Default View' and paste these values in A-10C [13] = {--default view viewAngle = 92.924411,--FOV viewAngleVertical= 61.248408,--VFOV hAngle = -0.010864, vAngle = -18.992676, x_trans = 0.150000, y_trans = 0.000000, z_trans = -0.000015, rollAngle = -0.000000, cockpit_version = 1, }, A-10C II [13] = {--default view viewAngle = 92.924411,--FOV viewAngleVertical= 61.248408,--VFOV hAngle = -0.010864, vAngle = -18.992676, x_trans = 0.150000, y_trans = 0.000000, z_trans = -0.000015, rollAngle = -0.000000, cockpit_version = 1, }, TIP: You don't need to restart DCS every time you edit the Snapviews file; you can edit and experiment between flights. Edited January 30 by Lixma 06 1 1
guitarxe Posted January 29 Posted January 29 22 hours ago, Lixma 06 said: OK, there's no way to explain this without eliciting the response "Are you serious? There isn't an easier way to reset the view settings? WTF?" Strap in. Quick and dirty way Go into your C:\Users\*****\Saved Games\DCS\Config\View folder and delete the 'Snapviews' file. When you hop into a mission DCS it will rebuild the file with ALL the views (all aircraft) reset to default. If you only fly the A-10 then this might be the best way. The safest way Using Notepad++ (or similar) open the Snapviews file and search for 'A-10C' or 'A-10C_2' Scroll down to 'Default View' and paste these values in A-10C }, [13] = {--default view viewAngle = 94.318233,--FOV viewAngleVertical= 62.479978,--VFOV hAngle = 0.000000, vAngle = -19.000000, x_trans = 0.150000, y_trans = 0.000000, z_trans = 0.000000, rollAngle = -0.000000, cockpit_version = 1, }, A-10C II [13] = {--default view viewAngle = 73.000000,--FOV viewAngleVertical= 0.000000,--VFOV hAngle = 0.000000, vAngle = -19.000000, x_trans = 0.150000, y_trans = 0.000000, z_trans = 0.000000, rollAngle = 0.000000, cockpit_version = 1, }, TIP: You don't need to restart DCS every time you edit the Snapviews file; you can edit and experiment between flights. I think which one is for A-10C and which is for A-10C II is in reverse in your post, but this helped me, thanks and cheers! 1
Lixma 06 Posted January 30 Posted January 30 18 hours ago, guitarxe said: I think which one is for A-10C and which is for A-10C II is in reverse in your post, but this helped me, thanks and cheers! Updated, thanks! They should be identical - I blame caffeine, or lack thereof, for not spotting it.
Recommended Posts