CoNa Posted January 12, 2008 Share Posted January 12, 2008 As I have a widescreen monitor, I have adjusted the FOV to 1,6 changed to the correct resolution (1680x1050), adjusted view angle (145) Ok, looks nice...but I feel like I'm waaay to close to the sight. I would like to move the seat position a notch or two back. OK, I can lean forward and reset the trackir for the distance, and then sit in the normal position again. But that's not good if I want to reset it during flight. Were do I change this and which parameters do I change to get this right? I have tested the "higher position" mod, but I don't want to get higher, just further back. Some one please? Link to comment Share on other sites More sharing options...
The_GOZR Posted January 12, 2008 Share Posted January 12, 2008 Something like this ? http://www.gozr.net/iocl/viewtopic.php?t=1663 Here my views ( F O V ) at MAX zoomed OUT with Track-IR or manually. if you want to try the file get it H E R E Link to comment Share on other sites More sharing options...
Nate--IRL-- Posted January 12, 2008 Share Posted January 12, 2008 I think he means head position in the cockpit, rather than Just widening the FOV. This ia a particular problem for Widescreen monitors and the Su-25t. Nate Ka-50 AutoPilot/stabilisation system description and operation by IvanK- Essential Reading Link to comment Share on other sites More sharing options...
The_GOZR Posted January 12, 2008 Share Posted January 12, 2008 At first start i think it's in the Eagle Dynamics\Lock On\Config\View\View.cfg and it's in CockpitViewAngleDefault = 105.0; default is 60 for example. You can move your pilot up down but i think you can't move the seat position back. It's with the Fov that you can tweak a bit.. but i'm not completely sure. Link to comment Share on other sites More sharing options...
CoNa Posted January 12, 2008 Author Share Posted January 12, 2008 Correct Nate. But perhaps setting the FOV back a bit would do the trick though. These are however waaaaay to much. I will have a look at the file and see if I can adjustthe to my requirements. Link to comment Share on other sites More sharing options...
The_GOZR Posted January 12, 2008 Share Posted January 12, 2008 less than this and you fly zoomed in.. Link to comment Share on other sites More sharing options...
CoNa Posted January 13, 2008 Author Share Posted January 13, 2008 Tried this, but I dont get any change? Still the same FOV. // If MouseCockpit is not set here then option value is used. // Remove two slashes in the next line and set your custom value: MouseCockpit = 1; MouseExternal = 0; MouseSpeedSlow = 1.0; MouseSpeedNormal = 1.5; MouseSpeedFast = 3.0; KeyboardSpeedSlow = 0.5; KeyboardSpeedNormal = 3.0; KeyboardSpeedFast = 15.0; CockpitViewAngleMin = 20.0; CockpitViewAngleMax = 145.0; // If CockpitViewAngleDefault is not set here then option value is used // Remove two slashes in the next line and set your custom value: CockpitViewAngleDefault = 105.0; ExternalViewAngleMin = 3.0; ExternalViewAngleMax = 170.0; // If ExternalViewAngleDefault is not set here then cockpit value is used // Remove two slashes in the next line and set your custom value: //ExternalViewAngleDefault = 60.0; CameraTerrainRestriction = 1; DisableSnapViewsSaving = 1; UseDefaultSnapViews = 0; ExplosionExpoTime = 1.0; CockpitSnapStepHor = 45.0; CockpitSnapStepVert = 30.0; CockpitNyMove = 1; ChazeCameraNyMove = 1; Link to comment Share on other sites More sharing options...
Ironhand Posted January 13, 2008 Share Posted January 13, 2008 What you need to change is in SnapViews. You can change those other numbers until the cows come home and you won't be happy. The default cockpit view (the one TrackIR uses when you first enter the cockpit) is view 13 (IIRC). You'll need to change it for each aircraft. The nice thing about this, though, is that you can fine tune the view you want. I use the snapviews themselves quite a bit and setting them up for my display took awhile but now I see exactly the instruments I want with each view. I'm at work right now but I'll upload my file this evening for you to try. Rich YouTube Channel: https://www.youtube.com/channel/UCU1...CR6IZ7crfdZxDg _____ Win 10 Pro x64, ASUS Z97 Pro MoBo, Intel i7-4790K, EVGA GTX 970 4GB, HyperX Savage 32GB, Samsung 850 EVO 250 GB SSD, 2x Seagate Hybrid Drive 2TB Raid 0. Link to comment Share on other sites More sharing options...
CoNa Posted January 13, 2008 Author Share Posted January 13, 2008 Thx Ironhand, that would really be appreciated. Which one is it that needs changing? Viewangle? Snap[1][13] = {} Snap[1][13]["viewAngle"] = 87.468338012695 Snap[1][13]["vAngle"] = -9.5 Snap[1][13]["hAngle"] = 0 Looking at the snapviews default.lua there is some information I don't follow. "User-made snap views for all his missions are saved in the Config/View/SnapViews.lua file if the parameter DisableSnapViewsSaving = true in the Config/View/Cockpit.lua file" Do I need to change this somewhere? Because I don't have an cockpit.lua Link to comment Share on other sites More sharing options...
CoNa Posted January 13, 2008 Author Share Posted January 13, 2008 OK, tried to change the different parameters, but still don't get the correct result. Changed : ViewAngle, no difference vAngle, head is looking down towards the instruments (headpitch) hAngle, head is turned from center (Headrotation) Link to comment Share on other sites More sharing options...
Ironhand Posted January 14, 2008 Share Posted January 14, 2008 Tried this, but I dont get any change? Still the same FOV. // If MouseCockpit is not set here then option value is used. // Remove two slashes in the next line and set your custom value: MouseCockpit = 1; MouseExternal = 0; MouseSpeedSlow = 1.0; MouseSpeedNormal = 1.5; MouseSpeedFast = 3.0; KeyboardSpeedSlow = 0.5; KeyboardSpeedNormal = 3.0; KeyboardSpeedFast = 15.0; CockpitViewAngleMin = 20.0; CockpitViewAngleMax = 145.0; // If CockpitViewAngleDefault is not set here then option value is used // Remove two slashes in the next line and set your custom value: CockpitViewAngleDefault = 105.0; .... From the looks of it, you are modifying view.cfg. The_GOZR is talking about changing the numbers in view.lua. But anyway... Here's the modified snapviews.lua file I use: SNAPVIEWS.LUA. For the most part, it's just the standard 4:3 with the 16:9 "wings" to either side. My computer is sufficiently dated that pulling the view back much more causes significant framerate issues. But you are correct in that ViewAngle controls the field of view. In the example you posted: Snap[1][13] = {} Snap[1][13]["viewAngle"] = 87.468338012695 Snap[1][13]["vAngle"] = -9.5 Snap[1][13]["hAngle"] = 0 ::you are altering the default cockpit view for the Su-27. Don't know if you are aware of that. The first set of brackets after the word 'Snap" is the aircraft: 1 = Su-27 2 = Su-33 3 = Su-25 4 = Su-25T 5 = MiG-29 7 = A-10 8 = F-15 So, play with the ["viewAngle"] number (bigger is wider) first in Snap[?][13]=. Then fine tune the default view in terms of up/down with Snap[?][13]["vAngle"]. That is how I got the default views I wanted for each cockpit. And, as I noted earlier, Snap[?][13] is where TrackIR gets its default view when you first enter the cockpit. BTW, I don't think I made any changes to the Su-25's snapviews. Just the Su-25T and that one isn't pulled back much at all. Hope this helps. Rich YouTube Channel: https://www.youtube.com/channel/UCU1...CR6IZ7crfdZxDg _____ Win 10 Pro x64, ASUS Z97 Pro MoBo, Intel i7-4790K, EVGA GTX 970 4GB, HyperX Savage 32GB, Samsung 850 EVO 250 GB SSD, 2x Seagate Hybrid Drive 2TB Raid 0. Link to comment Share on other sites More sharing options...
CoNa Posted January 14, 2008 Author Share Posted January 14, 2008 Hi, tried your snapview.lua file, but It does not make any difference. What am I missing? Link to comment Share on other sites More sharing options...
TekaTeka Posted January 14, 2008 Share Posted January 14, 2008 If you are using TrackIR to zoom, you have to change min and max FOV values. See my very old post. http://forums.eagle.ru/showpost.php?p=42749&postcount=3 You can use LOCFG to modify these. http://forums.eagle.ru/showpost.php?p=378784&postcount=89 TekaTeka from Japan [sIGPIC][/sIGPIC] Visit my site Beyond Visual Range. Link to comment Share on other sites More sharing options...
Ironhand Posted January 14, 2008 Share Posted January 14, 2008 Hi, tried your snapview.lua file, but It does not make any difference. What am I missing? It's not what you're missing. It's what I missed. You are using TrackIR's zoom axis. I don't and, so, never considered that where TrackIR gets it's default settings might change. Follow TekaTeka's link and you should be all set. My apologies for any confusion I caused. Rich YouTube Channel: https://www.youtube.com/channel/UCU1...CR6IZ7crfdZxDg _____ Win 10 Pro x64, ASUS Z97 Pro MoBo, Intel i7-4790K, EVGA GTX 970 4GB, HyperX Savage 32GB, Samsung 850 EVO 250 GB SSD, 2x Seagate Hybrid Drive 2TB Raid 0. Link to comment Share on other sites More sharing options...
CoNa Posted January 14, 2008 Author Share Posted January 14, 2008 No problems, thanks for helping. But I still don't get it. This is what my defaults look like in view.lua -- Camera view angle limits {view angle min, view angle max}. CameraAngleLimits = {} CameraAngleLimits[PlaneIndex.iSu_27] = {160.0, -76.0, 110.0} CameraAngleLimits[PlaneIndex.iSu_33] = {160.0, -79.0, 110.0} CameraAngleLimits[PlaneIndex.iSu_25] = {109.0, -70.0, 105.0} CameraAngleLimits[PlaneIndex.iSu_39] = {116.0, -85.0, 110.0} CameraAngleLimits[PlaneIndex.iMiG_29] = {160.0, -80.0, 110.0} CameraAngleLimits[PlaneIndex.iMiG_29K] = {140.0, -65.0, 90.0} CameraAngleLimits[PlaneIndex.iA_10] = {160.0, -72.0, 110.0} CameraAngleLimits[PlaneIndex.iF_15] = {160.0, -81.0, 110.0} Nothing close to TekaTekas. CameraViewAngleLimits And my only say, CameraAngleLimits -- Camera view angle limits {view angle min, view angle max}. CameraViewAngleLimits = {} CameraViewAngleLimits[PlaneIndex.iSu_27] = {20.0, 120.0} CameraViewAngleLimits[PlaneIndex.iSu_33] = {20.0, 120.0} CameraViewAngleLimits[PlaneIndex.iSu_25] = {20.0, 120.0} CameraViewAngleLimits[PlaneIndex.iSu_39] = {20.0, 120.0} CameraViewAngleLimits[PlaneIndex.iMiG_29] = {20.0, 120.0} CameraViewAngleLimits[PlaneIndex.iMiG_29K] = {20.0, 120.0} CameraViewAngleLimits[PlaneIndex.iA_10] = {20.0, 120.0} CameraViewAngleLimits[PlaneIndex.iF_15] = {20.0, 120.0} Link to comment Share on other sites More sharing options...
Ironhand Posted January 14, 2008 Share Posted January 14, 2008 No problems, thanks for helping. But I still don't get it. This is what my defaults look like in view.lua -- Camera view angle limits {view angle min, view angle max}. CameraAngleLimits = {} CameraAngleLimits[PlaneIndex.iSu_27] = {160.0, -76.0, 110.0} CameraAngleLimits[PlaneIndex.iSu_33] = {160.0, -79.0, 110.0} CameraAngleLimits[PlaneIndex.iSu_25] = {109.0, -70.0, 105.0} CameraAngleLimits[PlaneIndex.iSu_39] = {116.0, -85.0, 110.0} CameraAngleLimits[PlaneIndex.iMiG_29] = {160.0, -80.0, 110.0} CameraAngleLimits[PlaneIndex.iMiG_29K] = {140.0, -65.0, 90.0} CameraAngleLimits[PlaneIndex.iA_10] = {160.0, -72.0, 110.0} CameraAngleLimits[PlaneIndex.iF_15] = {160.0, -81.0, 110.0} ... That looks suspiciously like something from V1.02. Unfortunately I'm at work right now and can't double check. Anyone? Rich YouTube Channel: https://www.youtube.com/channel/UCU1...CR6IZ7crfdZxDg _____ Win 10 Pro x64, ASUS Z97 Pro MoBo, Intel i7-4790K, EVGA GTX 970 4GB, HyperX Savage 32GB, Samsung 850 EVO 250 GB SSD, 2x Seagate Hybrid Drive 2TB Raid 0. Link to comment Share on other sites More sharing options...
CoNa Posted January 14, 2008 Author Share Posted January 14, 2008 Strange, as I have v1.12b installed, and it's working perfect. And some of the changes I have done in the lua's have actually made difference. Link to comment Share on other sites More sharing options...
Sytse Posted January 14, 2008 Share Posted January 14, 2008 The only thing I know about this, is that you have to alter the server.lua file in order to change the head position in on-line games. It depends on the server.lua file of the host. [sIGPIC][/sIGPIC] Virtual Red Arrows homepage Link to comment Share on other sites More sharing options...
Ironhand Posted January 15, 2008 Share Posted January 15, 2008 Strange, as I have v1.12b installed, and it's working perfect. And some of the changes I have done in the lua's have actually made difference. Mmmmm. I looked through the various LOMAC/FC versions on my hard drive and the closest thing I have to what you show in view.lua: -- Camera view angle limits {view angle min, view angle max}. CameraAngleLimits = {} CameraAngleLimits[PlaneIndex.iSu_27] = {160.0, -76.0, 110.0} CameraAngleLimits[PlaneIndex.iSu_33] = {160.0, -79.0, 110.0} CameraAngleLimits[PlaneIndex.iSu_25] = {109.0, -70.0, 105.0} CameraAngleLimits[PlaneIndex.iSu_39] = {116.0, -85.0, 110.0} CameraAngleLimits[PlaneIndex.iMiG_29] = {160.0, -80.0, 110.0} CameraAngleLimits[PlaneIndex.iMiG_29K] = {140.0, -65.0, 90.0} CameraAngleLimits[PlaneIndex.iA_10] = {160.0, -72.0, 110.0} CameraAngleLimits[PlaneIndex.iF_15] = {160.0, -81.0, 110.0} ... comes from the server.lua. The format is the same, although the numbers are different. Don't know what it's doing in view.lua, though, or how it would have gotten there. Rich YouTube Channel: https://www.youtube.com/channel/UCU1...CR6IZ7crfdZxDg _____ Win 10 Pro x64, ASUS Z97 Pro MoBo, Intel i7-4790K, EVGA GTX 970 4GB, HyperX Savage 32GB, Samsung 850 EVO 250 GB SSD, 2x Seagate Hybrid Drive 2TB Raid 0. Link to comment Share on other sites More sharing options...
Recommended Posts