cj43g3r

@Fireman1979 I believe there are training missions included with the mod. You can use the mission editor to browse the contents under <Saved Games>\DCS\mods\aircraft\JAS39\Missions You can also download Rudel-Chw's missions and copy them to that folder https://www.digitalcombatsimulator.com/en/files/3324687/

https://www.digitalcombatsimulator.com/en/files/3344319/ Here's a mission based on the C-130 Hercules aircraft carrier trials on Oct 10, 1963. You will be attempting takeoffs and landings at various weights. Takeoffs will be without catapult assist. Landings will be without a tailhook. You should map controls (perhaps airbrakes controls) for "Throttles Beta Reverse" and "Throttles Flight to Beta Full Reverse". Or you can pretend to be the stunt pilot for JAG Season 9 Episode 5 "Touchdown". For simplicity, the Forrestal is headed due north at flank speed to give you a headwind. Records indicated 40knot winds that day. You can use the mission editor to change the direction or disable the winds under the weather options. The readme.txt includes the instructions to make the Anubis C-130 mod aircraft carrier capable. It also includes instructions to fix the CJS SuperHornet compatibility issue with recent DCS 2.9 Have fun!

@MAXsenna I apologize if I offended you. That was not my intention. You provided information to help others with head tracking. I'm just trying to doing the same. Additional configuration examples will help since I'm sure there's many cases that the ones you and I provided do not cover. i believe you may be overly sensitive to the term "realistic". As an analogy, I tend to fly with "full" labels and use the controls to zoom in and zoom out. Is it realistic? No. Do I get a better gaming experience? Absolutely. It also seems that DCS has already implemented a "misc" option "head movement by g-forces in cockpit" that is disabled by default.

@MAXsenna The title says Head Tracking Help, so I believe this applies. When I was researching head tracking for DCS, I didn't even know this forum existed. And I only recently found out about this thread involving head tracking. I couldn't find any opentrack mapping templates. So I researched various medical websites, NIST, and took measurements of many cockpit videos freeze frames to come up with the numbers i provided. You can match up the numbers with the axis of the various mappings. It will help new opentrack users to understand what they mean. I used a linear mapping since it's easier to control. There is also a deadband when looking straight ahead to avoid jitter from micromovements. I would also recommend using any of the opentrack filters to reduce jitter when moving. If you are flying warbirds instead of jets, it would be applicable to have linear curves for the X, Y, and Z axis. These are just recommendations after all and the user can adjust them to personal preferences.

@SharpeXB Then why don't you post more realistic opentrack mappings ? At 9G's it's not the straps but the G's holding your head against the headrest. I see lots YouTube DCS videos where the pilot's head tracking is easily moving in all 6 degrees despite pulling high G's. And current head tracking software doesn't use DCS telemetry to scale the mappings.

@SharpeXB Notice how the pilot's straps are very loose that they're constantly falling off. You don't want to do that if you don't want neck/back issues. But to each their own... An average human head is around 11 lbs. At 7.5G's, 82.5lbs. At 9G's, 99lbs. I think you get my point. And I know I'm replying to a 4 year old thread because there are DCS users that still use head tracking. I see a lot of YouTube videos using head tracking unrealistically with 180deg yaw or pitch.

Wanted to mention that opentrack has built in Kinect Face support for Kinect V2. But only if you can get it at a reasonable price from a reputable seller. I originally used AITrack v0.6.5 which worked well with a PS3 Eye but is sensitive to differences in ambient lighting conditions (backlighting in particular and works best with overhead lighting) and required adjustment in gain and exposure at different times of day. Its a good low cost solution and I did not want to wear a hat/headset for an extended session. AI Track v0.7.0 and later uses a different face model and attempts to optimize performance by reducing the detection rectangle surrounding the face. This is ok when sitting at a desk but not at a distance. I am using it on a sofa approximately 2 meters away from a tv and this causes detection problems. I was intending to use kinect to do IR face tracking without wearing any clips. But Kinect Face does video face tracking with auto gain/sensitivity which works without any adjustment. From a completely dark room only lit by the tv to a brightly lit sunny room. The caveat is the Kinect V2 is a discontinued product and you should only consider it if you can get one at a reasonable price from a reputable seller. I bought my Kinect V2 for $15 and its power adapter for $25 and have been using it for around 2 years. Since the Kinect is much larger than a webcam, you will need to mount an above tv shelf to support it.

I would also highly recommend opentrack with built in Kinect Face support for Kinect V2. But only if you can find one at a reasonable price from a reputable seller.

I would recommend the following opentrack mapping curves based on the following for added realism: you are strapped tightly into the ejection seat for high G maneuvers so there will be little to no X, Y, Z axis movement typical camera on top of display can detect approximately +/-30deg face yaw and +/-30deg face pitch as input a human neck can do approximately +/-20deg roll a human neck can do approximately +/-75deg pitch with 5 degrees added for vertical eye movement. But you may be able to look +90deg in an inclined seat. And may require -90deg for cockpit controls. a human neck can do approximately +/-90deg yaw, but with some torso rotation and horizontal eye movement can reach approximately +/-160deg Y and Z mappings are the same as X null null nullnull

Carrier spawning seems be resolved by DCS 2.9.14.8394 for compatibility with: dofile(current_mod_path .. '/Weapons/Loadouts/jas39_a-darter.lua') dofile(current_mod_path .. '/Weapons/Loadouts/jas39_mar-1.lua') but still requires: --dofile(current_mod_path .. '/Weapons/Loadouts/jas39_dws39_arm.lua') --dofile(current_mod_path .. '/Weapons/Loadouts/jas39_dws39_tv.lua')

Carrier spawning seems be resolved by DCS 2.9.14.8394

Seems to be resolved by DCS 2.9.14.8394

RAFALE PACK EVOLUTION II 2.8.7 2023. you will need to create a case1 mission in the mission editor: 2025-03-26 03:07:09.118 INFO APP (Main): MissionSpawn:spawnShips 2 2025-03-26 03:07:09.119 ERROR woShip (Main): Failed to create ship: Descriptor not found weapons.shells.M61_20_HE_gr 2025-03-26 03:07:09.160 INFO APP (Main): MissionSpawn:initScript

For DCS 2.9.14.8222, the following JAS39C loadouts has conflicts with the A-4e-c, F/A-18C, T-45 not spawning carriers. It's resolved by commenting out those loadouts with only those mods: --dofile(current_mod_path .. '/Weapons/Loadouts/jas39_a-darter.lua') --dofile(current_mod_path .. '/Weapons/Loadouts/jas39_mar-1.lua') --dofile(current_mod_path .. '/Weapons/Loadouts/jas39_dws39_arm.lua') --dofile(current_mod_path .. '/Weapons/Loadouts/jas39_dws39_tv.lua') But I also see other mods now causing the same symptom A-4e-c, F/A-18C, T-45, UH-60L not spawning carriers: MiG-31K and MiG-31BM RAFALE PACK EVOLUTION II 2.8.7 2023 VSN mods The A-4e-c, T-45 and UH-60L all have exceptions in scripts function copyFile where iniFile = nil, caused by scandir not finding any mission file. It does not seem to be the cause of the carrier spawning issue since these exceptions also occur in the case of successful carrier spawning. The carrier spawning issue seems to be related to M61_20_HE_gr and M2_12_7_T. Perhaps a missing core resource ? 2025-03-25 23:27:23.287 INFO APP (Main): MissionSpawn:spawnShips 2 2025-03-25 23:27:23.295 ERROR woShip (Main): Failed to create ship: Descriptor not found weapons.shells.M61_20_HE_gr 2025-03-25 23:27:23.303 ERROR woShip (Main): Failed to create ship: Descriptor not found weapons.shells.M2_12_7_T 2025-03-25 23:27:23.358 WARNING LOG (10036): 1 duplicate message(s) skipped. Seems this can be easily reproduced with only the VSN F-4 mod installed using it's case1 mission: VSN_F4 v2.8.2.102 standalon case1 succeeds spawning aircraft carriers. VSN_F4 standalone V2.9.5.206 case1 fails to spawn aircraft carriers. 2025-03-26 02:14:05.992 INFO APP (Main): MissionSpawn:spawnShips 2 2025-03-26 02:14:05.996 ERROR woShip (Main): Failed to create ship: Descriptor not found weapons.shells.M61_20_HE_gr 2025-03-26 02:14:06.200 INFO APP (Main): MissionSpawn:initScript

For DCS 2.9.14.8222, the following JAS39C loadouts has conflicts with the A-4e-c, F/A-18C, T-45 not spawning carriers. It's resolved by commenting out those loadouts with only those mods: --dofile(current_mod_path .. '/Weapons/Loadouts/jas39_a-darter.lua') --dofile(current_mod_path .. '/Weapons/Loadouts/jas39_mar-1.lua') --dofile(current_mod_path .. '/Weapons/Loadouts/jas39_dws39_arm.lua') --dofile(current_mod_path .. '/Weapons/Loadouts/jas39_dws39_tv.lua') But I also see other mods now causing the same symptom A-4e-c, F/A-18C, T-45, UH-60L not spawning carriers: MiG-31K and MiG-31BM RAFALE PACK EVOLUTION II 2.8.7 2023 Seems like all VSN mods The A-4e-c, T-45 and UH-60L all have exceptions in scripts function copyFile where iniFile = nil, caused by scandir not finding any mission file. It does not seem to be the cause of the carrier spawning issue since these exceptions also occur in the case of successful carrier spawning. The carrier spawning issue seems to be related to M61_20_HE_gr and M2_12_7_T. Perhaps a missing core resource ? 2025-03-25 23:27:23.287 INFO APP (Main): MissionSpawn:spawnShips 2 2025-03-25 23:27:23.295 ERROR woShip (Main): Failed to create ship: Descriptor not found weapons.shells.M61_20_HE_gr 2025-03-25 23:27:23.303 ERROR woShip (Main): Failed to create ship: Descriptor not found weapons.shells.M2_12_7_T 2025-03-25 23:27:23.358 WARNING LOG (10036): 1 duplicate message(s) skipped. Seems this can be easily reproduced with only the VSN F-4 mod installed using it's case1 mission: VSN_F4 standalone V2.9.5.206 case1 fails to spawn aircraft carriers. VSN_F4 v2.8.2.102 standalon case1 succeeds spawning aircraft carriers.