Jump to content

Reworked Cockpit Views with proper Neck


PeterP

Recommended Posts

Interesting topic, but I must admit, I don't understand the point here? TrackIR is setup through its software, at least that is where I am accustom to setting up the curves etc,,, how does the DCS Controls interface come into play? Does that not conflict with the custom setup already achieved in the TrackIR software?

Windows 10 Pro - 64 Bit / GIGABYTE 3866MHz GA-Z170X-Gaming 7 MOBO / Intel i7-6700K 4.0GHz Processor (OC to 4.Eight) / G.SKILL TridentZ Series 32GB DDR4 3200 Ram / Samsung 850 EVO 500GB SATA III SSD / EVGA 2080 Ti FTW3 Hybrid/ Onboard Audio card / Creative Inspire 5.1 Surround Speakers /LG-Ultragear 38" IPS LED Ultrawide HD Monitor / Track IR4 / Saitek Pro Flight Combat Pedals / Virpil HOTAS

 

Link to comment
Share on other sites

I think that some setups with multiple monitors and different resolutions just need extra tweaking. I have a triple monitor setup, and used to tweak this stuff for years.. Not so much anymore..

Intel I9-10850K (OC @ 5.0ghz) │ Asus Maximus XII Hero │ G.Skill Ripjaws 64GB (4x16GB) DDR4 3200 │ Thermaltake Water 360mm

Gigabyte RTX 3080 Gaming OC 10gb │ 2TB M.2 EVO Pro; 1T M.2 EVO; Sandisk SSD Drives │ 3x Acer 28" │ 1x 28" Touchscreen
- ҉ - Blackshark Cockpit Trainer - ҉ -    Thread   | Download
Link to comment
Share on other sites

Its weird because if you setup TrackIR though its software, you wind up with all these curves, but then when you open up DCS options/Axis and click on any of the TrackIR Axis, they are all linear,,, so I don't get it,, maybe I don't want to know LOL

Windows 10 Pro - 64 Bit / GIGABYTE 3866MHz GA-Z170X-Gaming 7 MOBO / Intel i7-6700K 4.0GHz Processor (OC to 4.Eight) / G.SKILL TridentZ Series 32GB DDR4 3200 Ram / Samsung 850 EVO 500GB SATA III SSD / EVGA 2080 Ti FTW3 Hybrid/ Onboard Audio card / Creative Inspire 5.1 Surround Speakers /LG-Ultragear 38" IPS LED Ultrawide HD Monitor / Track IR4 / Saitek Pro Flight Combat Pedals / Virpil HOTAS

 

Link to comment
Share on other sites

I think that some setups with multiple monitors and different resolutions just need extra tweaking. I have a triple monitor setup, and used to tweak this stuff for years.. Not so much anymore..

 

Yes it's difficult especially since 1.5 / 2.0. There is some kind of conflict between the map, the GUI and click points in triple screen.

klem

56 RAF 'Firebirds'

ASUS ROG Strix Z390-F mobo, i7 8086A @ 5.0 GHz with Corsair H115i watercooling, Gigabyte 2080Ti GAMING OC 11Gb GPU , 32Gb DDR4 RAM, 500Gb and 256Gb SSD SATA III 6Gb/s + 2TB , Pimax 8k Plus VR, TM Warthog Throttle, TM F18 Grip on Virpil WarBRD base, Windows 10 Home 64bit

Link to comment
Share on other sites

  • 4 weeks later...

JSGME Proper Neck toggle

 

This is a great Mod but it doesn't work in my Mi-8.

In my Mi-8 Seats 2 and 3 are thrown way back behind the cabin.

Huey works fine though. EDIT Ermmm no it doesn't, copilot still not working ...

 

I came up with this:

I've rigged a separate install of JSGME up in the

C:\Users\"My_Name"\Saved Games\DCS

folder.

It then plonks the two Proper Neck files into Config/View.

Lets me use PN for most aircraft and pull it out easily for the Mi-8 or anything else that doesn't work with it.

 

Had to be a separate JSGME install because my DCS installs are on another drive.

Makes it very easy to switch Proper Neck on and off.

Lets me use PN for most aircraft and pull it out easily for the Mi-8 or anything else that doesn't work with it.


Edited by Kozmyk

OS:Win10 Home CPU:i7 3770K 3.5(@4.3GHz) COOLER:ZalmanCNPS10X-PERFORMA MOBO:GigabyteGA-Z77X-UD5H SSD#1:SamsungEVO850Pro 500GB SSD#2:SanDisk240GB HDD:2x Seagate2TB GFX:GigabyteGTX670 WF3 2GB OC1058MHz RAM:16GB 16000MHz DDR3 KEYB'Ds:Corsair K95/MS SidewinderX4 MOUSE:LogitechG700s MON:2x ASUS 24” ROUTER:ASUS RT-N66U DarkKnight INTERWEBS:Fibre152Mbps/12Mbps JOYSTICK:TM T16000m Modded THROTTLE:TM TWCS HEADTRACK:TrackIR5Pro

Link to comment
Share on other sites

Fix for Mi-8

Well, it turns out that it's an easy fix. All of the up to date values are in the game so it's just a matter of copying them.

 

To make the settings working for Mi-8 replace the section in your server.lua file with this:

ViewSettings["Mi-8"] = {
   Cockpit = {
   [1] = {-- player slot 1
       CockpitLocalPoint      = {3.916, -0.11 , 0.0},
       CameraViewAngleLimits  = {20.000000,160.000000},
       CameraAngleRestriction = {false,90.000000,0.400000},
       CameraAngleLimits      = {140.000000,-65.000000,90.000000},
       limits_6DOF            = {x = {-0.200000,0.400000},y ={-0.200000,0.25000},z = {-0.650000,1.0},roll = 90.000000},
   },
   
   [2] = {-- player slot 2
       CockpitLocalPoint      = {3.916, -0.11 , 0.0},
       CameraViewAngleLimits  = {20.000000,160.000000},
       CameraAngleRestriction = {false,90.000000,0.400000},
       CameraAngleLimits      = {140.000000,-65.000000,90.000000},
       limits_6DOF            = {x = {-0.200000,0.350000},y ={-0.200000,0.25000},z = {-0.400000,1.0},roll = 90.000000},
   },
   
   [3] = {-- player slot 3
       CockpitLocalPoint      = {3.916, -0.11 , 0.0},
       CameraViewAngleLimits  = {20.000000,160.000000},
       CameraAngleRestriction = {false,90.000000,0.400000},
       CameraAngleLimits      = {140.000000,-65.000000,90.000000},
       limits_6DOF            = {x = {-0.200000,0.400000},y ={-0.200000,0.30000},z = {-0.400000,0.4},roll = 90.000000},
   },
   
   }, -- Cockpit 
   Chase = {
       LocalPoint      = {-5.700000,1.400000,-3},
       AnglesDefault   = {0,-8.000000},
   }, -- Chase 
   Arcade = {
       LocalPoint      = {-20.000000,5.000000,0.000000},
       AnglesDefault   = {0.000000,-8.000000},
   }, -- Arcade 
}

I can't promise but if I find some time next week maybe I'll make an updated version of the file as the one originally posted one seams quite outdated.

For the moment I've just got Mi-8 and can't get my hands out of it :joystick:. It's my first hell so I'm extremely excited and gravely terrified when flying it - well at least trying to :)

 

EDIT: Sorry for the issue but the fix above should be using the "Mi-8MT" rather than "Mi-8" for the view settings. Also it is not applying the global configuration. Please check for an updated version in my next post.


Edited by firmek
The fix contains a bug
  • Like 1

F/A-18, F-16, F-14, M-2000C, A-10C, AV-8B, AJS-37 Viggen, F-5E-3, F-86F, MiG-21bis, MiG-15bis, L-39 Albatros, C-101 Aviojet, P-51D, Spitfire LF Mk. IX, Bf 109 4-K, UH-1H, Mi-8, Ka-50, NTTR, Normandy, Persian Gulf... and not enough time to fully enjoy it all

Link to comment
Share on other sites

Fix for Mi-8

Well, it turns out that it's an easy fix. All of the up to date values are in the game so it's just a matter of copying them.

 

To make the settings working for Mi-8 replace the section in your server.lua file with this:


I can't promise but if I find some time next week maybe I'll make an updated version of the file as the one originally posted one seams quite outdated.

For the moment I've just got Mi-8 and can't get my hands out of it :joystick:. It's my first hell so I'm extremely excited and gravely terrified when flying it - well at least trying to :)

Nice job.

Worked for me on the Mi-8

I tried the same logic on the Huey... it almost worked but the co-pilot view was a bit to the right. I must have missed something.:unsure:

OS:Win10 Home CPU:i7 3770K 3.5(@4.3GHz) COOLER:ZalmanCNPS10X-PERFORMA MOBO:GigabyteGA-Z77X-UD5H SSD#1:SamsungEVO850Pro 500GB SSD#2:SanDisk240GB HDD:2x Seagate2TB GFX:GigabyteGTX670 WF3 2GB OC1058MHz RAM:16GB 16000MHz DDR3 KEYB'Ds:Corsair K95/MS SidewinderX4 MOUSE:LogitechG700s MON:2x ASUS 24” ROUTER:ASUS RT-N66U DarkKnight INTERWEBS:Fibre152Mbps/12Mbps JOYSTICK:TM T16000m Modded THROTTLE:TM TWCS HEADTRACK:TrackIR5Pro

Link to comment
Share on other sites

  • 2 weeks later...

Update for 1.5.3

 

I've made an updated version of the file for 1.5.3.

It's more of an user configuration as all of the values and functionality are already in game. The issue is however that each of the aircrafts uses its own settings and for this reason they are not consistent. For instance it happens that some aircrafts have the shoulder size is set to 0.

Using this configuration makes all of the airplanes sharing the same FOV, neck and eye offset dimensions as also limitations for the head turn angles.

 

Modules included in the configuration:

A-10A, A-10C, F-15C, Hawk, Ka-50, MiG-29, P-51D, TF-51D, Su-25, Su-25T, Su-27, Su-33, Mi-8MT, C-101EB

 

Modules NOT included in the file. For those DCS will use the default values:

Huey, M-2000C, BF-109K, FW-190D, others...

 

I don't have them so I could not find necessary values. At the same time the procedure is really simple so everyone can do it on his own:

 

1. Locate the default "views.lua" file for the module for example

DCS install folder\Mods\aircraft\Mi-8MTV2\Views.lua

 

There are several locations which I think depend on the type of the module:

- DCS install folder\CoreMods\aircraft\module name\views.lua

- DCS install folder\Mods\aircraft\module name\views.lua

- DCS install folder\CoreMods\WWII Units\Views.lua (may contain the settings for all WW2 aircrafts apart of P-51 but again. Someone owning those modules will have to check it).

 

2. Copy the "ViewSettings" section

3. Check the SnapViews.lua file for the proper name of the module - for instance "Mi-8MT". Index the ViewSettings -> ViewSettings["Mi-8MT"]

4. Make sure that the "Cockpit" uses the "default_fighter_player" function

5. Remove all entries except the "CokpitLocalPoint" and "limits_6DOF".

 

Example, settings from the original views.lua for Mi-8:

ViewSettings = {
   Cockpit = {
   [1] = {-- player slot 1
       CockpitLocalPoint      = {3.916, -0.11 , 0.0},
       CameraViewAngleLimits  = {40.000000,140.000000},
       CameraAngleRestriction = {false,90.000000,0.400000},
       CameraAngleLimits      = {150.000000,-65.000000,90.000000},
       EyePoint               = {0.080000,0.100000,0.000000},
       limits_6DOF            = {x = {-0.200000,0.400000},y ={-0.200000,0.25000},z = {-0.650000,1.0},roll = 90.000000},
       ShoulderSize            = 0.25,
   },
...

And modified in the Server.lua:

ViewSettings["Mi-8MT"] = {
   Cockpit = {
   -- player slot 1
   [1] = default_fighter_player({
       CockpitLocalPoint      = {3.916, -0.11 , 0.0},
       --CameraAngleRestriction = {false,90.000000,0.400000},
       --CameraAngleLimits      = {150.000000,-65.000000,90.000000},
       limits_6DOF            = {x = {-0.200000,0.400000},y ={-0.200000,0.25000},z = {-0.650000,1.0},roll = 90.000000}}),
...

One point that I've noticed is that increasing the values for maximum head turning angles may result in being able to see the pilot body without head when looking back... which can be a bit disturbing :huh: Being able to turn head more is needed for planes but not so much for choppers (since you'll just see a wall behind you). For this reason I've only commented the values. If the CameraAngleLimits is uncommented for a specific aircraft it will override the global setting.

 

Note that the initial head position in the cockpit is also determined by your custom snap views.

 

Please leave a comment in case of any issues. I've tested the file with a number of planes in 1.5.3 but to be honest not with all of them. I also don't have 2.0/NTTR so I can't guarantee that it will work with it.

Server.lua


Edited by firmek
Attached updated version of the file

F/A-18, F-16, F-14, M-2000C, A-10C, AV-8B, AJS-37 Viggen, F-5E-3, F-86F, MiG-21bis, MiG-15bis, L-39 Albatros, C-101 Aviojet, P-51D, Spitfire LF Mk. IX, Bf 109 4-K, UH-1H, Mi-8, Ka-50, NTTR, Normandy, Persian Gulf... and not enough time to fully enjoy it all

Link to comment
Share on other sites

You can see pilot body and see it has no head (because there it should be the camera unobstructed like the cockpit is removed from external 3d model when view is in F1 and you see the high quality 3D cockpit) if you lean forward enough and then look back.

 

An alternative to solving all problems is to abandon altogether this old mod and build one from scratch that will contain the folder structure necessary and all the view.lua files of the new modules and then modify all files accordingly and with their own sintax etc. Server.lua should be kept only for FC3 and old modules.

 

Imho is this complication that it's kept and propagated by this mod that makes user "believe" that this mod does some sort of magic when it simply doesn't. Imho is simply obsolete.

[sIGPIC][/sIGPIC]

I5 4670k, 32GB, GTX 1070, Thrustmaster TFRP, G940 Throttle extremely modded with Bodnar 0836X and Bu0836A,

Warthog Joystick with F-18 grip, Oculus Rift S - Almost all is made from gifts from friends, the most expensive parts at least

Link to comment
Share on other sites

...

An alternative to solving all problems is to abandon altogether this old mod and build one from scratch that will contain the folder structure necessary and all the view.lua files of the new modules and then modify all files accordingly and with their own sintax etc. Server.lua should be kept only for FC3 and old modules

 

Imho is this complication that it's kept and propagated by this mod that makes user "believe" that this mod does some sort of magic when it simply doesn't. Imho is simply obsolete.

 

@Zealu I don’t want to be provocative here, but could you elaborate more on this point. I just would like to understand better the point as I'm not so long on the forums. If I get a better perspective on the issues I might be able to spend more time on making a better version of this mod.

 

Considering the "mod" I share the same view that it's not fair to call it a mod. It does not add any new functionality to the sim, all of the head movement algorithms are already there.

The fact is however that all of the modules are configured individually with different values for neck/eye position. This has some advantages but at the same time introduces an issue of inconsistent head movement experience when jumping from one airplane to another.

From this perspective this "mod" does his work giving users the same, consistent head movement across airplanes.

 

Having a single server.lua file or modifying each of the individual view.lua would have the same result, being just a different way of how the "mod" is implemented. There is a maintenance problem as when new modules are released they need to be added but the same issue would be with modifying all individual view.lua files. Unless it would be possible to come out with a generic update algorithm which may be too optimistic expectation as none can guarantee that new modules will have the same structure of view.lua files.


Edited by firmek
Typos

F/A-18, F-16, F-14, M-2000C, A-10C, AV-8B, AJS-37 Viggen, F-5E-3, F-86F, MiG-21bis, MiG-15bis, L-39 Albatros, C-101 Aviojet, P-51D, Spitfire LF Mk. IX, Bf 109 4-K, UH-1H, Mi-8, Ka-50, NTTR, Normandy, Persian Gulf... and not enough time to fully enjoy it all

Link to comment
Share on other sites

@Zealu I don’t want to be provocative here, but could you elaborate more on this point. I just would like to understand better the point as I'm not so long on the forums. If I get a better perspective on the issues I might be able to spend more time on making a better version of this mod.

 

Considering the "mod" I share the same view that it's not fair to call it a mod. It does not add any new functionality to the sim, all of the head movement algorithms are already there.

The fact is however that all of the modules are configured individually with different values for neck/eye position. This has some advantages but at the same time introduces an issue of inconsistent head movement experience when jumping from one airplane to another.

From this perspective this "mod" does his work giving users the same, consistent head movement across airplanes.

 

Having a single server.lua file or modifying each of the individual view.lua would have the same result, being just a different way of how the "mod" is implemented. There is a maintenance problem as when new modules are released they need to be added but the same issue would be with modifying all individual view.lua files. Unless it would be possible to come out with a generic update algorithm which may be too optimistic expectation as none can guarantee that new modules will have the same structure of view.lua files.

 

Excellent reply bro. I see where you are going here. Not provocative at all, merely factual :)

Windows 7 64 Home Premium, i5 3570K (3.4 @ 4.4GHz), Asus P8Z77-V LX, 16GB dual channel 1600 ram, EVGA Nvidia GTX980ti, 240 GB OCZ SSD, 3 TB Raptor, Thrustmaster Warthog Hotas and Throttle, Saitek Pro Combat Rudder pedals.

Link to comment
Share on other sites

No problem... I don't feel provoked or anything. I am all for discussing things and changing my views (lol) if necessary.

 

I don't know exactly where should I elaborate. I see all kinds of problems people have that are not related at all with the mod or are not solvable at all by modifying anything about these files. Like the missing head. This leads me to believe that most users of this mod just don't understand what it does but are somehow "mesmerized" by a sort of placebo effect that the changes within this mod do and just want more "magic" to change the unchangeable.

 

My opinion is you can't have same settings for all cockpits... I wish it was possible but it is not. I also wanted for example a single FOV angle but it turned out using the same angle in some planes was awful. So I have FOV ranging from 95 to 105. Probably when VR will be mainstream we all use 180 or 200 and be done with it but for now... it is very dependent on monitor screen size/resolution, view distance, headtracking usage, user preference.

 

That is why that syntax simplification " "default_fighter_player" function " for me instead of a simplification is actually a wall that most of the user smack into. It is suppose to make the text smaller and thus easier to understand but in fact it complicates the "meaning" in such way that most of users abandon "discovery" and rely on such old mods like this one instead of discovering their own preferences by understanding the simple things each line do.

[sIGPIC][/sIGPIC]

I5 4670k, 32GB, GTX 1070, Thrustmaster TFRP, G940 Throttle extremely modded with Bodnar 0836X and Bu0836A,

Warthog Joystick with F-18 grip, Oculus Rift S - Almost all is made from gifts from friends, the most expensive parts at least

Link to comment
Share on other sites

  • 3 months later...

Anyone got this working with 2.0?

 

And a slightly offtopic question, is it possible to temporarily disable trackir while flying in such way that you can use snapviews or mouse to look around in the cockpit? Pausing or stopping tracking just forces the view to stay still.

Fighting for peace is like screwing for virginity.

Link to comment
Share on other sites

I don't have 2.0 but attached is the version working with 1.5.4 - with few more airplanes than the last one I did.

Server.lua

F/A-18, F-16, F-14, M-2000C, A-10C, AV-8B, AJS-37 Viggen, F-5E-3, F-86F, MiG-21bis, MiG-15bis, L-39 Albatros, C-101 Aviojet, P-51D, Spitfire LF Mk. IX, Bf 109 4-K, UH-1H, Mi-8, Ka-50, NTTR, Normandy, Persian Gulf... and not enough time to fully enjoy it all

Link to comment
Share on other sites

I can.

 

Anyone got this working with 2.0?

 

And a slightly offtopic question, is it possible to temporarily disable trackir while flying in such way that you can use snapviews or mouse to look around in the cockpit? Pausing or stopping tracking just forces the view to stay still.

 

When I hit the TrackIR "pause", then I can use the arrow keys on my keyboard to look around the cockpit. I've found that I cannot keep my head steady enough with the TrackIR to be able to operate some of the switches and knobs, so I simply hit "TrackIR Pause" and use those arrow keys to take me where I want to go and the view stays steady until I move it again with the keys. Once I've got done what I want, I then go back to TrackIR active by cancelling the "pause" button.

Intel i5-4690K Devil's Canyon, GForce TitanX, ASUS Z-97A MB, 16GB GDDR3 GSkill mem, Samsung SSD X3,Track IR, TM Warthog, MFG Crosswind pedals, Acer XB280HK monitor,GAMETRIX KW-908 JETSEAT

Link to comment
Share on other sites

I don't have 2.0 but attached is the version working with 1.5.4 - with few more airplanes than the last one I did.

Would you be able to put it as JSGME compatible in the OP

 

Sent from my SM-G900W8 using Tapatalk

Know and use all the capabilities in your airplane. If you don't, sooner or later, some guy who does use them all will kick your ass.

 

— Dave 'Preacher' Pace, USN.

Link to comment
Share on other sites

Sorry but I'm not using JSGME (though maybe I can try to make a version for it). Nevertheless, the file should be stored in user files (Config/View folder if I remember correctly) - not in DCS directory (updates don't override it).

 

109/190?

I don't have those planes so they're not included (lack of values, no possibility to test). You can try to use the instruction from this post to add them - should be fairly simple.


Edited by firmek
fixed link

F/A-18, F-16, F-14, M-2000C, A-10C, AV-8B, AJS-37 Viggen, F-5E-3, F-86F, MiG-21bis, MiG-15bis, L-39 Albatros, C-101 Aviojet, P-51D, Spitfire LF Mk. IX, Bf 109 4-K, UH-1H, Mi-8, Ka-50, NTTR, Normandy, Persian Gulf... and not enough time to fully enjoy it all

Link to comment
Share on other sites

I use a Macro in my x55 profile editor to turn on Snapviews so I can click around. I just have to make an Advanced Command and check the Macro checkbox so that it processes all of the commands(keys) whether I hold the button long enough or not.

 

I use Snapviews on a hat, so I only use 4 views. Numpad 1,2,3 and 8; for Left, Center, and Right panels and then HUD Zoom.

 

The command for the left panel is:

RCtrl + Numpad0, then Numpad1

 

I put a .03 sec delay between the push down and release of RCtrl + Numpad0, and Numpad1. And also between the two key presses. (I figured out this timing by trial and error.)

 

Once in Snapview I can click on switches. To turn off Snapview you press RCtrl + Numpad0 again. So, when I just press the hat again, it sends those keys and snapview is turned off, and the rest of the command is ignored since snapview is off.

 

Works great if you get that timing/delay right.


Edited by Snacko

Intel I9-10850K (OC @ 5.0ghz) │ Asus Maximus XII Hero │ G.Skill Ripjaws 64GB (4x16GB) DDR4 3200 │ Thermaltake Water 360mm

Gigabyte RTX 3080 Gaming OC 10gb │ 2TB M.2 EVO Pro; 1T M.2 EVO; Sandisk SSD Drives │ 3x Acer 28" │ 1x 28" Touchscreen
- ҉ - Blackshark Cockpit Trainer - ҉ -    Thread   | Download
Link to comment
Share on other sites

  • 2 weeks later...

Hi,

 

I just updated to 1.5.4 but the view is all srewed up. Before 1.5.4, I managed to setup a great viewpoint thanks to this properneck mod, but right now, I can't get this mod working.

 

Can anyone please help to get this mod working in 1.5.4? Anyone got the same issue?

 

Best regards,

 

Pierre

Link to comment
Share on other sites

  • 2 weeks later...
same here,

1.5.4 took out peter_p settings...

any one knows how to fix? I'm having neck problems again trying to look around and press buttons in my A10-C cockpit...

 

I used this

http://forums.eagle.ru/showpost.php?p=2822725&postcount=134

to set the TrackIR default lua to the old 1.5.3 settings.

Proper neck has been working fine with these.

Except for the old Huey and Mi-8 troubles of course ;)

OS:Win10 Home CPU:i7 3770K 3.5(@4.3GHz) COOLER:ZalmanCNPS10X-PERFORMA MOBO:GigabyteGA-Z77X-UD5H SSD#1:SamsungEVO850Pro 500GB SSD#2:SanDisk240GB HDD:2x Seagate2TB GFX:GigabyteGTX670 WF3 2GB OC1058MHz RAM:16GB 16000MHz DDR3 KEYB'Ds:Corsair K95/MS SidewinderX4 MOUSE:LogitechG700s MON:2x ASUS 24” ROUTER:ASUS RT-N66U DarkKnight INTERWEBS:Fibre152Mbps/12Mbps JOYSTICK:TM T16000m Modded THROTTLE:TM TWCS HEADTRACK:TrackIR5Pro

Link to comment
Share on other sites

  • Recently Browsing   0 members

    • No registered users viewing this page.
×
×
  • Create New...