Sprool

Downloaded the 'fixed' deployment campaign for the KA-50 but running the 1st mission - familiarisation, if i follow the spoken instructions i end up way off course and never get to complete the mission, if i just use nav to go to the preprogrammed waypoints it takes me on different headings to the instructions and mission never completes. Any suggestions?

Thanks - will give that a try! Just need to edit it to check 4 rotaries in a loop

Try this: https://forums.eagle.ru/showthread.php?t=251377

Found it! https://forums.eagle.ru/showthread.php?t=251377

Thx Flappie, while this reports 7 pages of people having same problem, the thread I saw had someone with a really good solution editing the default.lua and it solved it.

This just sends out 2 signals as keypresses instead of one to DCS, in effect getting the knob to rotate 2 click instead of one. Fine for some knobs like cockpit illumination, instrument brightness, etc, but then knobs like hornet radio channel select will miss out every other channel.

From Longuich: "..so what an encoder does is add or subtract (usually) 4 from what its current values is. Hence the equation to see whether you're turning it clockwise or counterclockwise. if I'm reading it all correctly you just get a 1 or 0 for the left and right pins on the encoders. there's no way to make those values more.. unless you tell the script to press "turn left" or "turn right" twice. if (result == DIR_CCW) { Joystick.button(rotaries.ccwchar, 1); delay(50); Joystick.button(rotaries.ccwchar, 0); }; if (result == DIR_CW) { Joystick.button(rotaries.cwchar, 1); delay(50); Joystick.button(rotaries.cwchar, 0); }; this here turns the joystick button press on and or off. I'm missing the part where all joystickbutton states are sent to the computer. could you try and see what happens if you change the code to: if (result == DIR_CCW) { Joystick.button(rotaries.ccwchar, 1); delay(50); Joystick.button(rotaries.ccwchar, 0); Joystick.button(rotaries.ccwchar, 1); delay(50); Joystick.button(rotaries.ccwchar, 0); }; if (result == DIR_CW) { Joystick.button(rotaries.cwchar, 1); delay(50); Joystick.button(rotaries.cwchar, 0); Joystick.button(rotaries.cwchar, 1); delay(50); Joystick.button(rotaries.cwchar, 0); };

Sometimes I'm playing DCS without the headphones and head tracker running - after a minute or two the PC suddenly realises trackIR is not active and stutters briefly; There was a post here a few months back that had an edit for one of the config files to solve this stutter. It worked really well, but I lost it during a re-install. Does this ring a bell with anyone? It just pauses a second or two when flying and realising trackIR may not be running/connected.

Sometimes I'm playing DCS without the headphones and head tracker running - after a minute or two the PC suddenly realises trackIR is not active and stutters briefly; There was a post here a few months back that had an edit for one of the config files to solve this stutter. It worked really well, but I lost it during a re-install. Does this ring a bell with anyone? It just pauses a second or two when flying and realising trackIR may not be running/connected.

Suntsag has a few tutorial videos on his channel about setting up AI jtacs in a mission https://www.youtube.com/channel/UCnMdglLzp7KBkLiaNiq9N-Q/videos

do you mean pre-planned target co-ordinates? FLIR is for targets of opportunity. Loadout can be selected in the airbase via comms menu - ground crew - rearm/refuel

That would be pretty low down on my priority list, I'd rather they sorted the bugs in the models we can fly first before updating some AI cosmetics.

Totally disagree with mosqui! Something satisfying about saving money and crafting something yourself and getting it tuned sweetly. Just takes some tweaking. For me it was the pointtracker calibration and relative translation settings in opentrack that sorted everything. My 3 LEDs are on the left of my head, so when I turn head right, the LEDs effeectively move closer to the camera, and further when I turn head left. the relative translation compensates for this effect.

Everything and a lot more is explained in this thread: https://forums.eagle.ru/showthread.php?t=89226

Fair enough, its now also a minor revenue stream for cap, not just a flight sim video game

I noticed the lua files were different for the middle east animals (which show up in game) and the cows/boar/chickens which dont. Cow-a.lua: mount_vfs_model_path (current_mod_path.."/Shapes/") mount_vfs_texture_path (current_mod_path.."/Textures/") Camel.lua: mount_vfs_model_path (current_mod_path.."/Shapes/") mount_vfs_texture_path (current_mod_path.."/Textures/animals.zip") But even if I edit the luas for cows & chickens, they dont appear in-game?

Dropbox download ask for password ? Found this https://www.dropbox.com/s/9q49z5j53ag15io/DCS_Animals_Mod_V1.5.zip?dl=0&file_subpath=%2FDCS_Animals_Mod_V1.5 but DCS says its not authorised and wont run it. Maybe its an OVGME thing. I installed manually into my saved games / mods and it shows up, but no cows or chickens appear - I get most of the other animals. But I want cows and chickens!

my trim works as normal too, no change. Ive always had to trim rudder and cyclic as separate items though.

In the Supercarrier manual it says the LSO position (LAlt+F9) has a separate PLAT window you can move and interact with (Alt+C), the LSO Main Screen Window, wiht the grey PLAT Camera view below it. I just get the 2 small green screens on the physical LSO workstation. It says the view can be scrolled up and down with the mouse wheel - mine does nothing. It says window can be opened and closed by clicking top left? Is this still work-in-progress? It shows a grey plat camera view I have never seen in game. Am I missing s/thing? How do I bring this view up and interact with it? Or is it all still WIP?

fields a bit too crisp and stripey for me, mountain looks fabulous!

thanks - better solution!

Glad to have helped a little.

The problem may be that the Lua code only sees buttons/switches as on or off, and you want one switch to be seen as A, off or B. I would post a request in LeCuvier's toggle switch thread and see if he can suggest a workround for you. https://forums.eagle.ru/showthread.php?t=89226&page=81

--{ down = SMS_commands.MasterArmSw, cockpit_device_id = devices.SMS, value_down = 1.0, name = _('Master Arm Switch - ARM'), category = {_('Instrument Panel'), _('Master Arm Panel')}}, --{ down = SMS_commands.MasterArmSw, cockpit_device_id = devices.SMS, value_down = 0.0, name = _('Master Arm Switch - SAFE'), category = {_('Instrument Panel'), _('Master Arm Panel')}} {down = SMS_commands.MasterArmSw, up = SMS_commands.MasterArmSw, cockpit_device_id = devices.SMS, value_down = 1.0, value_up = 0.0, name = _('Master Arm Switch 2-Pos ARM/SAFE'), category = {_('Instrument Panel'), _('Master Arm Panel')}}, put 2 dashes in front iof the 2 lines you posted to tell the lua code to ignore the command (it treats it as a comment so you can undo later if needed) then add the third line. Then go into settings controls in DCS menu and find the new entry for the F-18 master arm switch - "master arm - 2 pos - arm/safe." Then just designate a keypress or switch to assign to it. Thanks to LeCuvier for his brains on these toggle switch codes! LeCuvier's single line sort of combines the 2 original lines into one command. All its doing is telling the game to look for one keypress to arm, and pressing the key down flags it as 1 = armed, then it looks for a second keypress to toggle the safe state and assigns zero to it. LeCuviers edit combines both in that the if the switch is down = armed (value = 1) and if the switch is up = safe (0)

Yes- thanks for the help :)