wowbagger Posted May 15, 2021 Posted May 15, 2021 (edited) The Train Strafe quick start mission for the Channel map contains a folder called config which itself contains Server, SnapViews, SnapViewsDefault, and View lua files. These get dumped into the Temp folder and override the user's settings, messing up the views. Edited May 19, 2021 by wowbagger no sig
Flappie Posted May 22, 2021 Posted May 22, 2021 (edited) @wowbagger I just can't use my custom views with ANY mission, even the ones I create in the mission editor. Steps to reproduce: Create a mission with any P-47 model as client or player Hit Fly Move the pilot's head with Numpad keys Hit LWin + Numpad1 once Hit RAlt + Numpad0 once Press LWin + Numpad1: the custom span view is displayed. It's working. Yay! Reload the mission. Press LWin + Numpad1: this time, the default snap view number 1 is displayed... Am I doing something wrong? Edited May 22, 2021 by Flappie ---
wowbagger Posted May 22, 2021 Author Posted May 22, 2021 (edited) Check the TEMP folder. If a mission dumped this dumb Config folder in there, it may still be there - in which case the game will read the views from that Config folder instead of your own defined views for all missions. I also had lua files with strange names show up in the TEMP folder which also had view settings inside and which over-rid my own settings. Just clear out the TEMP folder to solve this issue, if that's the cause. I think custom snap-views are buffered until you exit the mission, at which time they actually get saved to your SAVED GAMES folder. Edited May 22, 2021 by wowbagger no sig
Flappie Posted May 22, 2021 Posted May 22, 2021 (edited) This is what I did after reading your post: Recorded my snap view. After exiting the mission, I saw my Snap View lua was changed accordingly. Emptied "Local\Temp\DCS...". Loaded Caucasus "Takeoff" instanct action mission. Once in the cokpit, my custom snap vew doesn't work. I see no "Config" folder in my "Local\Temp\DCS..." folder. [2] = {--LWin + Num1 : Snap View 1 viewAngle = 94.096327,--FOV hAngle = 140.241257, vAngle = -1.880616, x_trans = 0.298479, y_trans = 0.037436, z_trans = -0.203056, rollAngle = 7.745360, cockpit_version = 0, }, Edited May 22, 2021 by Flappie ---
wowbagger Posted May 22, 2021 Author Posted May 22, 2021 (edited) Hmmm... Maybe check those files in the TEMP folder and open any non-zero files to see if they contain view settings. I had it happen with a couple of different missions, in different ways, and one definitely had view settings in a strange and unexpected file from which the game was reading the view settings - I thought it was a lua file but it might have been a ~mis file. Edited May 22, 2021 by wowbagger no sig
wowbagger Posted May 24, 2021 Author Posted May 24, 2021 I just checked that mission, Flappie, and you are correct. This mission doesn't seem to dump anything into the TEMP folder that would override your custom snap-view settings. And, when I fly it, my views work properly. So your problem must be rooted somewhere else. no sig
Flappie Posted May 24, 2021 Posted May 24, 2021 (edited) I solved my "problem": Now this option is enabled, I can try to reproduce your issue. Edited May 24, 2021 by Flappie ---
ED Team BIGNEWY Posted May 25, 2021 ED Team Posted May 25, 2021 reported 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, PIMAX Crystal
Recommended Posts