MemphisBelle Posted March 28 Posted March 28 Hello, since a couple of updates back, I´ve noticed an issue with the VR recenter view function. The center view positions the view slightly offset to the left and no more straight in the middle. I´ve recorded a Video about it and added a miz. file and screenshots for review. Does someone else noticing this? I have that issue with the Hornet only, all the others are good. VR-Center_Test_Hornet.trk BlackSharkDen | BSD Discord | DCS Tutorial Collection
Solution MAXsenna Posted March 28 Solution Posted March 28 I don't use VR so this might be a goose chase. Could you by chance have saved a Snapviews setting? At least in 2D with TrackIR, you must stop the tracking, or what you observe will happen.You can see if this remedy fixes it. Open the Snapviews.lua in Notepad++ and delete the whole F/A-18C section. You will of course lose all Snapviews settings for the F/A-18C though, while I think you got nothing to lose besides wasting two minutes trying. Cheers! Sent from my SM-A536B using Tapatalk 1 1
MemphisBelle Posted March 28 Author Posted March 28 33 minutes ago, MAXsenna said: I don't use VR so this might be a goose chase. Could you by chance have saved a Snapviews setting? At least in 2D with TrackIR, you must stop the tracking, or what you observe will happen. You can see if this remedy fixes it. Open the Snapviews.lua in Notepad++ and delete the whole F/A-18C section. You will of course lose all Snapviews settings for the F/A-18C though, while I think you got nothing to lose besides wasting two minutes trying. Cheers! Sent from my SM-A536B using Tapatalk I'll give it a shot, even though I doubt that this is the reason since I'm using no snapview button, but an actual VR center view function from the UI Layer List. But I'll come back and let you know if it has helped anyways. Thx. 1 BlackSharkDen | BSD Discord | DCS Tutorial Collection
MAXsenna Posted March 28 Posted March 28 I'll give it a shot, even though I doubt that this is the reason since I'm using no snapview button, but an actual VR center view function from the UI Layer List. But I'll come back and let you know if it has helped anyways. Thx.Yeah, I understand. It's a complete shot in the dark. I'm not even sure if Snapviews work in VR. What I meant is that perhaps at some point RAlt + Num0 was pressed by accident. That saves the Snapview for the current view. And that's usually the default one. Sent from my SM-A536B using Tapatalk
MemphisBelle Posted March 28 Author Posted March 28 (edited) 50 minutes ago, MAXsenna said: Yeah, I understand. It's a complete shot in the dark. I'm not even sure if Snapviews work in VR. What I meant is that perhaps at some point RAlt + Num0 was pressed by accident. That saves the Snapview for the current view. And that's usually the default one. Sent from my SM-A536B using Tapatalk ehhh, you wont believe it...it worked...the VR center view is now corrected after I´ve deleted the Hornet section from the SnapViews.lua. I´m totally blown away, I´ve never expected that. Thus it should actually be valuable enough to be reported as bug, since its caused by fault values, isn´t it? Edited March 28 by MemphisBelle 1 BlackSharkDen | BSD Discord | DCS Tutorial Collection
MAXsenna Posted March 28 Posted March 28 1 hour ago, MemphisBelle said: ehhh, you wont believe it...it worked. Damn! Maybe I should play the lottery today then! 1 hour ago, MemphisBelle said: Thus it should actually be valuable enough to be reported as bug, since its caused by fault values, isn´t it? IIRC, the Snapviews entries are not added in the file unless any of the views have been changed. I'm not saying you did, but I think the chance of you accidentally hitting that key combo when reaching for the keyboard in VR is higher than it beeing a bug no one else has reported. You can test though, just rename the Snapviews.lua and check if it gets populated with incorrect values. If it does, yeah, then it's absolutely a bug! Cheers, and enjoy your weekend!
MemphisBelle Posted March 28 Author Posted March 28 7 hours ago, MAXsenna said: I'm not saying you did, but I think the chance of you accidentally hitting that key combo when reaching for the keyboard in VR is higher than it beeing a bug no one else has reported. Well, I have a button assignrd on my HOTAS, so zero chance to "accidently" hit a key combo. 7 hours ago, MAXsenna said: You can test though, just rename the Snapviews.lua and check if it gets populated with incorrect values. If it does, yeah, then it's absolutely a bug! Cheers, and enjoy your weekend! yeah, thats what I want to test. And if it returns, then I know for sure. Thx for your help and Input, have a nice weekend yourself too. 1 BlackSharkDen | BSD Discord | DCS Tutorial Collection
jaylw314 Posted March 30 Posted March 30 On 3/28/2025 at 5:12 AM, MemphisBelle said: ehhh, you wont believe it...it worked...the VR center view is now corrected after I´ve deleted the Hornet section from the SnapViews.lua. I´m totally blown away, I´ve never expected that. Thus it should actually be valuable enough to be reported as bug, since its caused by fault values, isn´t it? FYI, the "Save Cockpit Angles" function (usually default RAlt+Num0) saves all the snapviews, but that also includes your default head position in VR for each individual module. If you ever need or want to adjust your default position in VR for any one module, just use the Cockpit Camera controls (usually default RAlt+numpad) to tweak it the way you like, press "Save Cockpit Angles", then every time you press VR recenter, you should be there moving forwards.
MAXsenna Posted March 30 Posted March 30 FYI, the "Save Cockpit Angles" function (usually default RAlt+Num0) saves all the snapviews, but that also includes your default head position in VR for each individual module. If you ever need or want to adjust your default position in VR for any one module, just use the Cockpit Camera controls (usually default RAlt+numpad) to tweak it the way you like, press "Save Cockpit Angles", then every time you press VR recenter, you should be there moving forwards.I'm pretty sure RAlt + Num0 was pressed by accident. Sent from my SM-A536B using Tapatalk
Recommended Posts