Spitfire2170 Posted May 1, 2013 Posted May 1, 2013 After this patch, it seems they did away with CameraViewAngleLimits in config/view. I used this to put the zoom FOV's to a manageable setting for my triple screen. Now with this new patch I am sitting in a fishbowl and cant see jack. At middle zoom I can see maybe 2 gauges and max zoom a single digit. It is crazy now. Somebody please figure a way to fix this. I tried inserting the old camerviewanglelimits in with an extra [uH-1H] line, but it didn't work. Help!! [sIGPIC][/sIGPIC] ---------------------------------------------------------------------- Intel DZ77GA70K Extreme Board | Intel Core i5-3570K Ivy Bridge 4.6GHz | EVGA GeForce GTX670 FTW Edition | Corsair Hydro Series H60 Corsair Enthusiast Series 750W | Corsair Vengeance 8GB 1600 | Corsair Obsidian Series 550D | Triple Acer 27" 2ms 5760x1080 Thrustmaster HOTAS Warthog | Cyborg M.M.O.7 | Razor BlackWidow Ultimate | TrackIR 4
RedRain Posted May 1, 2013 Posted May 1, 2013 After this patch, it seems they did away with CameraViewAngleLimits in config/view. I used this to put the zoom FOV's to a manageable setting for my triple screen. Now with this new patch I am sitting in a fishbowl and cant see jack. At middle zoom I can see maybe 2 gauges and max zoom a single digit. It is crazy now. Somebody please figure a way to fix this. I tried inserting the old camerviewanglelimits in with an extra [uH-1H] line, but it didn't work. Help!![/quote Same, chin on dashboard ?
TOYKILLA Posted May 1, 2013 Posted May 1, 2013 oh man,that Suck!!! I use Triple Screen too.... [sIGPIC][/sIGPIC] Thrustmaster Warthog SLM - F/A-18 , MFG Crosswind V2 , Cougar MFD`s , HP Reverb , PointCtrl , i9@5,1Ghz/2080Ti, :joystick: DIY 2DOF Motionsimulator with 4Ch Simshaker :joystick: https://www.facebook.com/micsmotionsimulator
Kuky Posted May 1, 2013 Posted May 1, 2013 Camera view angle limits sets the Min and Max limit... it does not set your default FoV... if you however set your Min and Max FoV value to same value your FoV will be fixed... or if you want to be able to increase/decrase FoV while in game (with mouse scroll axis) you can set FoV you want in SnapViewsDefault.lua (and this was always the case) and it works just fine No longer active in DCS...
LNR212 Posted May 1, 2013 Posted May 1, 2013 Hey Kuky, where do i have to set those Min and Max FoV? Can't find it... Cause im having a problem with the x_trans. im not able to set a proper distance to my Cockpit/Dashboard. Maybe its because the min/max isnt set up properly after update?
9.JG27 DavidRed Posted May 1, 2013 Posted May 1, 2013 i had the same problem, note with a single screen though...so i dont know if the following is of help. first i went into my game directory: C:\Program Files\Eagle Dynamics\DCS World\Config\View and adjusted the view.lua file(line 13) to UseDefaultSnapViews = false ...and saved it. then i opened the SnapViews.lua file in my saved games folder: C:\Users\David\Saved Games\DCS\Config\View in this file you will find all flyable aircraft and all possible views for it.i searched for the "default view" line of the module i wanted to change.the first line in this section changes the FOV apparantly: viewAngle = 90.000000,--FOV(my adjusted P51 FOV) i also changed the following line in the same section: y_trans = 0.200000 which makes my pilot a little bit taller....i have the impression, that with 124, my pilot shrinked to a midget by default, and i was somehow barely able to look outside of my pit.... hope this helps...oh of course after adjusting the file, dont forget to save it :) PS: maybe this is of help as well: http://en.wiki.eagle.ru/wiki/Snap_views
JetBLASTER Posted May 1, 2013 Posted May 1, 2013 Me too [sIGPIC][/sIGPIC] Intel® Core™ i7-6850 CPU@3.60GHz @4.068 Asus ROG STRIX X99 GAMING ATX Motherboard 64 bit operation System- RAM 32.0 GB Gigabyte GeForce GTX 1080 WindForce OC 8GB - Disk Drives KINGSTON SVP200S37A 1tb/WDC WD 10EZEX-00ZF5A0 - Samsung ssd 1tb 840 series. - 3 Samsung 27"SyncMaster 3D Game monitors - Windows 8.1 Pro - TM Hotas Warthog-Trackir5 pro-Saitek Rudder Pedals-Cougar MFD.
LNR212 Posted May 1, 2013 Posted May 1, 2013 i tried true/false but no luck... i can change y-trans, vangle, viewangle... but NOT x_trans :mad: WHY??? im going slightly mad!!!
Kuky Posted May 1, 2013 Posted May 1, 2013 For example, to change FoV for Su-27 cockpit you edit: (and same for other aircraft - each in their own section) ...Config/View/SnapViewsDefault.lua SnapViews["Su-27"] = { [1] = {-- player slot 1 [1] = { viewAngle = 71.824692,--FOV hAngle = 0.000000, vAngle = -32.458889, x_trans = 0.000000, y_trans = 0.000000, z_trans = 0.000000, rollAngle = 0.000000, }, [2] = { viewAngle = 33.361835,--FOV hAngle = 41.045925, vAngle = -40.805656, x_trans = 0.000000, y_trans = 0.000000, z_trans = 0.000000, rollAngle = 0.000000, }, [3] = { viewAngle = 30.427544,--FOV hAngle = 0.000000, vAngle = -41.808968, x_trans = 0.000000, y_trans = 0.000000, z_trans = 0.000000, rollAngle = 0.000000, }, [4] = { viewAngle = 34.392349,--FOV hAngle = -32.597401, vAngle = -35.293747, x_trans = 0.000000, y_trans = 0.000000, z_trans = 0.000000, rollAngle = 0.000000, }, [5] = { viewAngle = 87.468338,--FOV hAngle = 129.012665, vAngle = 14.547977, x_trans = 0.000000, y_trans = 0.000000, z_trans = 0.000000, rollAngle = 0.000000, }, [6] = { viewAngle = 43.977936,--FOV hAngle = 0.000000, vAngle = -4.951577, x_trans = 0.000000, y_trans = 0.000000, z_trans = 0.000000, rollAngle = 0.000000, }, [7] = { viewAngle = 87.468338,--FOV hAngle = -129.012665, vAngle = 14.491872, x_trans = 0.000000, y_trans = 0.000000, z_trans = 0.000000, rollAngle = 0.000000, }, [8] = { viewAngle = 87.468338,--FOV hAngle = 82.862923, vAngle = -9.500000, x_trans = 0.000000, y_trans = 0.000000, z_trans = 0.000000, rollAngle = 0.000000, }, [9] = { viewAngle = 87.468338,--FOV hAngle = 0.000000, vAngle = 38.979362, x_trans = 0.000000, y_trans = 0.000000, z_trans = 0.000000, rollAngle = 0.000000, }, [10] = { viewAngle = 87.468338,--FOV hAngle = -82.461266, vAngle = -12.843998, x_trans = 0.000000, y_trans = 0.000000, z_trans = 0.000000, rollAngle = 0.000000, }, [11] = {--look at left mirror viewAngle = 68.786629,--FOV hAngle = 15.618313, vAngle = 7.522498, x_trans = 0.000000, y_trans = 0.000000, z_trans = 0.000000, rollAngle = 0.000000, }, [12] = {--look at right mirror viewAngle = 69.165199,--FOV hAngle = -15.683434, vAngle = 8.549150, x_trans = 0.000000, y_trans = 0.000000, z_trans = 0.000000, rollAngle = 0.000000, }, [13] = {--default view viewAngle = 87.468338,--FOV <-- you set your desired FoV here in ° (degrees) hAngle = 0.000000, vAngle = -9.500000, x_trans = 0.113927, y_trans = -0.004946, z_trans = 0.000000, rollAngle = 0.000000, }, }, ps: you edit section [13] only ...Config/View/Server.lua ViewSettings["Su-27"] = { Cockpit = { [1] = {-- player slot 1 CockpitLocalPoint = {7.959000,1.419000,0.000000}, CameraViewAngleLimits = {20.000000,120.000000}, <-- FoV Min & Max limits in ° (degrees) CameraAngleRestriction = {false,60.000000,0.400000}, CameraAngleLimits = {140.000000,-75.000000,90.000000}, EyePoint = {0.050000,0.100000,0.000000}, limits_6DOF = {x = {-0.050000,0.450000},y ={-0.200000,0.200000},z = {-0.220000,0.220000},roll = 90.000000}, }, }, -- Cockpit Chase = { LocalPoint = {4.259000,3.819000,0.000000}, AnglesDefault = {180.000000,-8.000000}, }, -- Chase Arcade = { LocalPoint = {-12.041000,6.419000,0.000000}, AnglesDefault = {0.000000,-8.000000}, }, -- Arcade } 1 No longer active in DCS...
LNR212 Posted May 1, 2013 Posted May 1, 2013 You saved my Holiday today, Kuky! Thanks for the hint with server.lua...
Scarecrow Posted May 1, 2013 Posted May 1, 2013 Thank you, this one had me scratching my head also. Why the change though?
eFirehawk Posted May 1, 2013 Posted May 1, 2013 Can somebody post a stock v.1.2.4 Server.lua file here please? I had mine replaced with a backup from v.1.2.3 but it seems that the files changed significantly since mine doesn't have any of those paramenters. :helpsmilie: Pentium II 233Mhz | 16MB RAM | 14.4kb Modem | 1.44MB Floppy Disk Drive | Windows 3.1 with TM Warthog & TrackIR 5
Kuky Posted May 1, 2013 Posted May 1, 2013 ^^^ you can just delete the file... then force DCS Repair from start menu, that will restore the deleted file No longer active in DCS...
LNR212 Posted May 1, 2013 Posted May 1, 2013 here you go... same issue here. file is from a friend, i made the same mistake :music_whistling:View.rar 1
eFirehawk Posted May 1, 2013 Posted May 1, 2013 Thank you lnr212 and Kuky, now I've been able to get everything fixed :) Pentium II 233Mhz | 16MB RAM | 14.4kb Modem | 1.44MB Floppy Disk Drive | Windows 3.1 with TM Warthog & TrackIR 5
Boris Posted May 1, 2013 Posted May 1, 2013 For some reason changing the FOV in section 13 does nothing for me. Everything looks exactly the same. TrackIR seemingly always centers on exactly the same position no matter what I do. I did fix an issue where the Su-25T cockpit view centered too low below the HUD however. I changed the vAngle from -18.382137 to -8.382137... so at least some of my changes worked. Why not the FOV??? PC Specs / Hardware: MSI z370 Gaming Plus Mainboard, Intel 8700k @ 5GHz, MSI Sea Hawk 2080 Ti @ 2100MHz, 32GB 3200 MHz DDR4 RAM Displays: Philips BDM4065UC 60Hz 4K UHD Screen, Pimax 8KX Controllers / Peripherals: VPC MongoosT-50, Thrustmaster Warthog HOTAS, modded MS FFB2/CH Combatstick, MFG Crosswind Pedals, Gametrix JetSeat OS: Windows 10 Home Creator's Update
gonvise Posted May 1, 2013 Posted May 1, 2013 For some reason changing the FOV in section 13 does nothing for me. Everything looks exactly the same. TrackIR seemingly always centers on exactly the same position no matter what I do. I did fix an issue where the Su-25T cockpit view centered too low below the HUD however. I changed the vAngle from -18.382137 to -8.382137... so at least some of my changes worked. Why not the FOV??? +1, but only with trackir in all new 6DOF cockpits.
LNR212 Posted May 1, 2013 Posted May 1, 2013 (edited) Do you guys have set a new FoV in the server.lua? The min/max is the viewangle which you can zoom in/out and in the defaultview.lua you set your desired FoV (zoomlevel) Im not at my rig right now, but try to change your FoV in the server.lua to a bigger one. E.g. {20.00000,155.00000} And in the defaultview.lua set FoV to 120... now you should be able to move fwd and aft. Maybe this helps... :thumbup: Edit: today i had to setup new all keystrokes and buttons from P-51. Since the Update TrackIR wasnt working in the Mustang. After redoing all commands, trackIR worked fine again - dont know why or what this was... Edited May 1, 2013 by LNR212
gonvise Posted May 1, 2013 Posted May 1, 2013 Do you guys have set a new FoV in the server.lua? The min/max is the viewangle which you can zoom in/out and in the defaultview.lua you set your desired FoV (zoomlevel) Im not at my rig right now, but try to change your FoV in the server.lua to a bigger one. E.g. {20.00000,155.00000} And in the defaultview.lua set FoV to 120... now you should be able to move fwd and aft. Maybe this helps... :thumbup: Edit: today i had to setup new all keystrokes and buttons from P-51. Since the Update TrackIR wasnt working in the Mustang. After redoing all commands, trackIR worked fine again - dont know why or what this was... But I'm able to move fwd and aft if I not connect the trackir... in the moment I put the trackir in my head, the FOV is fixed and the zoom keys doesn't work. Only in new 1.2.4 6DOF, in F15C works fine. Thanks.
-Ice Posted May 2, 2013 Posted May 2, 2013 A few problems: 1. I use TIR, and changing the viewAngle from default 87 to 90 to 100 to 110, I've not noticed any change. I still have the forward canopy rails (the one in front) on either side of the screen. I'd like to "move my head back" a bit more and get more of the cockpit in view. 2. I've seemed to have messed up my HUD. In the SU-27, all I can see are my current airspeed and altitude, the desired airspeed and altitude are "hidden" behind the HUD glass and I need to move my head to see either one. 3. There is no way to zoom in/out of cockpit view with TIR and mouse wheel, but I can zoom in/out with the mouse wheel when in out-of-cockpit view. Any help appreciated! - Ice
plexi Posted May 2, 2013 Posted May 2, 2013 I found that going into to the Axis settings brougth up the TrackIR settings i changed that and it works much better. But then i have 2 Screens not 3 and only 1 displays Cockpit. Maybe that might be worth having a look at, it might help.
Boris Posted May 2, 2013 Posted May 2, 2013 I found that going into to the Axis settings brougth up the TrackIR settings i changed that and it works much better. But then i have 2 Screens not 3 and only 1 displays Cockpit. Maybe that might be worth having a look at, it might help. What exactly did you change? Here's what I found out... It seems the old cockpits have a different TrackIR axis assignment than the newer 6DOF ones. The older cockpits have the TrackIR Z-axis assigned to "Zoom View" while the newer cockpits have the Z-axis assigned to "camera forward/backward". I changed the z-axis from "zoom view" to "camera forward/back" for the Su-25T and so far so good... the cockpit now centers on the new FOV from the snapviewsdefault.lua. However I HATE this setting. Why? Because now moving my head forward tends to zoom in everything but the HUD. Furthermore This fix isn't suited to the Su-25T, as the nose graphic is broken when moving the head forward. I'm now probably going to change the Z-Axis in the new 6DOF cockpit aircraft too, as at least then I can zoom in on the HUD. The problem still remains, why can't the default zoom position then be changed? Or can it? PC Specs / Hardware: MSI z370 Gaming Plus Mainboard, Intel 8700k @ 5GHz, MSI Sea Hawk 2080 Ti @ 2100MHz, 32GB 3200 MHz DDR4 RAM Displays: Philips BDM4065UC 60Hz 4K UHD Screen, Pimax 8KX Controllers / Peripherals: VPC MongoosT-50, Thrustmaster Warthog HOTAS, modded MS FFB2/CH Combatstick, MFG Crosswind Pedals, Gametrix JetSeat OS: Windows 10 Home Creator's Update
Boris Posted May 2, 2013 Posted May 2, 2013 Ok, I just found out it's in fact realistic that the HUD doesn't get bigger, no matter how closely you look at it in an actual aircraft. Apparently it's focussed to infinity. So I guess I'll have to rethink this. I did like zooming into the HUD though to get a clearer picture. PC Specs / Hardware: MSI z370 Gaming Plus Mainboard, Intel 8700k @ 5GHz, MSI Sea Hawk 2080 Ti @ 2100MHz, 32GB 3200 MHz DDR4 RAM Displays: Philips BDM4065UC 60Hz 4K UHD Screen, Pimax 8KX Controllers / Peripherals: VPC MongoosT-50, Thrustmaster Warthog HOTAS, modded MS FFB2/CH Combatstick, MFG Crosswind Pedals, Gametrix JetSeat OS: Windows 10 Home Creator's Update
Spitfire2170 Posted May 2, 2013 Author Posted May 2, 2013 I failed to mention, I control zoom with the slider on my warthog throttle, not with track IR. But changing the slider axis limits in the options fixed it for me, mostly. [sIGPIC][/sIGPIC] ---------------------------------------------------------------------- Intel DZ77GA70K Extreme Board | Intel Core i5-3570K Ivy Bridge 4.6GHz | EVGA GeForce GTX670 FTW Edition | Corsair Hydro Series H60 Corsair Enthusiast Series 750W | Corsair Vengeance 8GB 1600 | Corsair Obsidian Series 550D | Triple Acer 27" 2ms 5760x1080 Thrustmaster HOTAS Warthog | Cyborg M.M.O.7 | Razor BlackWidow Ultimate | TrackIR 4
Recommended Posts