Helios1138 Posted October 25, 2019 Share Posted October 25, 2019 I've looked through the open-beta changelog here on the forum and didn't find any mention of this (maybe I've missed something?) but in open-beta, the default head position is moved up significantly, so that now I have to tilt my head down to be able to see through the gunsight (or re-center the view while standing up a little, then sit down to lower it to somewhat match the stable version behavior). Is this an intentional change or a bug? I had never sat in a real Spitfire, so obviously I have no idea where the head should be located (for an average-height person) :) Link to comment Share on other sites More sharing options...
ED Team BIGNEWY Posted November 2, 2019 ED Team Share Posted November 2, 2019 hi Helios1138 welcome to our forums. As far as I am aware nothing has been adjusted regarding views, I will ask the team on Monday. You can adjust your head position by using RCtrl + Rshift * or / for back and forth and then numpad 2,4,8,6 for up down laeft and right. I hope that helps. Forum rules - DCS Crashing? Try this first - Cleanup and Repair - Discord BIGNEWY#8703 - Youtube - Patch Status Windows 11, NVIDIA MSI RTX 3090, Intel® i9-10900K 3.70GHz, 5.30GHz Turbo, Corsair Hydro Series H150i Pro, 64GB DDR @3200, ASUS ROG Strix Z490-F Gaming, HP Reverb G2 Link to comment Share on other sites More sharing options...
Helios1138 Posted November 2, 2019 Author Share Posted November 2, 2019 (edited) BIGNEWY, thanks for looking into it. Moving the head using the keyboard isn't really convenient in VR since I would have to do this every time after re-centering (and in VR you usually have to do this more than once during flight). I've also checked non-VR mode and it seems that this issue is not present there. Only in VR. By the way, I have since noticed a similar issue in Yak-52. In it, it seems the default head center view has been moved a little bit forward (again, compared to stable version). It is possible that other planes are also affected, hadn't checked them all. I use Oculus Rift CV1. Please let me know if there is any other information I can provide. I did make a couple of screenshots to demonstrate the issue: (screenshots made immediately after re-centering, so I press '5' and then 'F12' to take a screenshot while looking directly ahead) Spitfire (stable) Spitfire (openbeta) Yak-25 (stable) Yak-25 (openbeta) Edited November 2, 2019 by Helios1138 Link to comment Share on other sites More sharing options...
ED Team BIGNEWY Posted November 2, 2019 ED Team Share Posted November 2, 2019 Thanks for the info, I will ask the team on Monday if any changes have been made. thanks Forum rules - DCS Crashing? Try this first - Cleanup and Repair - Discord BIGNEWY#8703 - Youtube - Patch Status Windows 11, NVIDIA MSI RTX 3090, Intel® i9-10900K 3.70GHz, 5.30GHz Turbo, Corsair Hydro Series H150i Pro, 64GB DDR @3200, ASUS ROG Strix Z490-F Gaming, HP Reverb G2 Link to comment Share on other sites More sharing options...
wuffman Posted November 2, 2019 Share Posted November 2, 2019 Helios1138 You can save the modified position in VR , there is a key combination. It worked for me after I noticed the same thing. Now it is just where I put it by default. Please try this, because I know what you mean. Link to comment Share on other sites More sharing options...
X93355 Posted November 3, 2019 Share Posted November 3, 2019 Thanks for the info, I will ask the team on Monday if any changes have been made. thanks If you could that would be good as I noticed this little bug about 2 updates ago. Was posted under Bugs and Problems for the Spitfire here: https://forums.eagle.ru/showthread.php?p=4066759#post4066759 InWin S Frame with Asus Z170 | i7-6700K @ 4.5 Water Cooled CPU and Graphics | 16GB DDR4 | GTX1070 | 240GB M.2 SSD | Warthog Hotas | MFG Crosswind | 40" Samsung 4K | CV1 | Replica MB Mk10 Ejection Seat with Gametrix 908 Link to comment Share on other sites More sharing options...
Helios1138 Posted November 10, 2019 Author Share Posted November 10, 2019 BIGNEWY, any news? Link to comment Share on other sites More sharing options...
wuffman Posted December 5, 2019 Share Posted December 5, 2019 (edited) BIGNEWY, any news? In VR, Can be moved and saved ( ralt + 0 ) while paused. I saved it once and it is there by default every time I re-center. What are we missing here? https://forums.eagle.ru/showthread.php?t=164892 Edited December 11, 2019 by wuffman Trying really hard to help Helios1138 Link to comment Share on other sites More sharing options...
Helios1138 Posted December 11, 2019 Author Share Posted December 11, 2019 It seems that this was fixed a few updates back, so the issue is gone as quietly as it appeared (meaning I did not see anything about this in the changelog), at least for Spitfire. I did not check other aircraft yet. BIGNEWY, can you confirm that this was indeed looked at and fixed and it wasn't just a problem that randomly appeared and then disappeared? Link to comment Share on other sites More sharing options...
speed-of-heat Posted December 27, 2019 Share Posted December 27, 2019 (edited) It was still there yesterday in the current open Beta https://forums.eagle.ru/showthread.php?t=251228 Edited December 27, 2019 by speed-of-heat SYSTEM SPECS: Hardware Intel Corei7-12700KF @ 5.1/5.3p & 3.8e GHz, 64Gb RAM, 4090 FE, Dell S2716DG, Virpil T50CM3 Throttle, WinWIng Orion 2 & F-16EX + MFG Crosswinds V2, Varjo Aero SOFTWARE: Microsoft Windows 11, VoiceAttack & VAICOM PRO Link to comment Share on other sites More sharing options...
Simon1279 Posted December 27, 2019 Share Posted December 27, 2019 i had the same issue with the two FW-190 ( D9 and A8 ), this issue has been solved by deleting a file named views.lua which you can find under: X:\Eagle Dynamics\DCS World\Mods\aircraft\FW-190A8 and X:\Eagle Dynamics\DCS World\Mods\aircraft\FW-190D9 or in your case: X:\Eagle Dynamics\DCS World\Mods\aircraft\SpitfireLFMkIX, where X: is the letter identificating your disk. this solved this long time problem with the FWs i hope this helps with the spitfire as well [sIGPIC][/sIGPIC] I7 8700K @ 4.9 ghz, SSD 850 evo, MSI Z370 Gaming Pro, GTX 1080Ti, F/A-18C in the garage, F-16C in the backyard, F-14B in the garden Link to comment Share on other sites More sharing options...
speed-of-heat Posted December 27, 2019 Share Posted December 27, 2019 (edited) i had the same issue with the two FW-190 ( D9 and A8 ), this issue has been solved by deleting a file named views.lua which you can find under: X:\Eagle Dynamics\DCS World\Mods\aircraft\FW-190A8 and X:\Eagle Dynamics\DCS World\Mods\aircraft\FW-190D9 or in your case: X:\Eagle Dynamics\DCS World\Mods\aircraft\SpitfireLFMkIX, where X: is the letter identificating your disk. this solved this long time problem with the FWs i hope this helps with the spitfire as well thanks for the tip, however, this causes the spitfire module to not load … which is suboptimal -- update actually even any changes to this file cause the module not to load... However this did get me thinking, I deleted the old snap view file C:\Users\<your username>\Saved Games\DCS\Config\Views\SnapViews.lua and recreated it with the default settings and then went in search of spitfires.... and found this under default view... [13] = {--default view viewAngle = 80.000000,--FOV hAngle = 0.000000, vAngle = 0.000000, x_trans = 0.075000, y_trans = 0.000000, z_trans = 0.000000, rollAngle = 0.000000, cockpit_version = 0, }, [14] = {--default view - VR viewAngle = 80.000000,--FOV hAngle = 0.030919, vAngle = -5.618282, x_trans = 0.075061, y_trans = 0.065373, z_trans = 0.000203, rollAngle = 0.851972, cockpit_version = 0, what is very interesting is that clipped wing spit has this ... [13] = {--default view viewAngle = 80.000000,--FOV hAngle = 0.000000, vAngle = 0.000000, x_trans = 0.075000, y_trans = 0.000000, z_trans = 0.000000, rollAngle = 0.000000, cockpit_version = 0, }, [14] = {--default view - VR viewAngle = 80.000000,--FOV hAngle = 0.000000, vAngle = 0.000000, x_trans = 0.075000, y_trans = 0.065000, z_trans = 0.000000, rollAngle = 0.000000, cockpit_version = 0, so I changed the spitfire non clipped wing to match... and now perfect views if I had to guess i'd say someone made a mistake in testing an saved their personal defaults rather than the correct ones Edited December 27, 2019 by speed-of-heat SYSTEM SPECS: Hardware Intel Corei7-12700KF @ 5.1/5.3p & 3.8e GHz, 64Gb RAM, 4090 FE, Dell S2716DG, Virpil T50CM3 Throttle, WinWIng Orion 2 & F-16EX + MFG Crosswinds V2, Varjo Aero SOFTWARE: Microsoft Windows 11, VoiceAttack & VAICOM PRO Link to comment Share on other sites More sharing options...
Helios1138 Posted December 31, 2019 Author Share Posted December 31, 2019 It seems that this was fixed Ok, scratch that, apparently I simply saved an altered position for myself. THIS ISSUE IS STILL PRESENT. I've bought a few more modules since then and the issue pops up almost everywhere. It's especially obvious in aircraft which have pilot body modeled, so you can roughly see where the pilot's head is supposed to be, and the VR head center point DOES NOT MATCH it. I think this is a very major issue for VR users in many aircraft. Link to comment Share on other sites More sharing options...
speed-of-heat Posted December 31, 2019 Share Posted December 31, 2019 Ok, scratch that, apparently I simply saved an altered position for myself. THIS ISSUE IS STILL PRESENT. I've bought a few more modules since then and the issue pops up almost everywhere. It's especially obvious in aircraft which have pilot body modeled, so you can roughly see where the pilot's head is supposed to be, and the VR head center point DOES NOT MATCH it. I think this is a very major issue for VR users in many aircraft. Yep, try it in the clipped wing spit... see above SYSTEM SPECS: Hardware Intel Corei7-12700KF @ 5.1/5.3p & 3.8e GHz, 64Gb RAM, 4090 FE, Dell S2716DG, Virpil T50CM3 Throttle, WinWIng Orion 2 & F-16EX + MFG Crosswinds V2, Varjo Aero SOFTWARE: Microsoft Windows 11, VoiceAttack & VAICOM PRO Link to comment Share on other sites More sharing options...
Recommended Posts