skypickle

Could you elaborate on where the listen command would be placed? Somewhere in the default.lua of an aircraft input joystick file?

I looked at benches on tech powerup. At 4k the 7950 is only a hair better than the 13900k and less than 10% better than the 5800x3d. Who plays dcs at 1080p?

This github is JavaScript that allows voice communication with chatGPT https://github.com/C-Nedelcu/talk-to-chatgpt i would like to turn it into a lua file that i can activate with a button on my throttle

binding 'right wing down' to a button and using it in sim gives right wing up. likewise left aileron trim is backwards as well. In the attached track, watch the trim hat on the stick and observe the aircraft's roll. In this case, I have bound the 'Right wing down' to a left motion of the hat. In the cockpit, the hat moves left but the aircraft rolls right. f53trim.trk

Benchmarks looking at the 5800x3d showed massive gains in msfs and dcs over non x3d parts and were on par with a 13900k. Too bad very few reviewers look at flight sims

what size amps are people using?

i assume this is total L2 so the per core L2 is the same across all chips?

What would you expect a North Korean infiltrator to say? AI should be viewed with the same suspicion we apply to our worst enemies. Trust but verify.

which doc? the manual??

The F5E has a special options menu that allows different joystick behaviors. I have been using the Displaced Neutral (FFB) as it puts the neutral pointof the stick about 3/4 forward (meaning for for neutral flight and zero trim, the stick is forward). I would like to move this neutral point back towards center. I found lua file that uses this: C:\Eagle Dynamics\DCS World OpenBeta\Mods\aircraft\F-5E\Options\optionsDb.lua local DbOption = require('Options.DbOption') local i18n = require('i18n') local oms = require('optionsModsScripts') local _ = i18n.ptranslate return { aiHelper = DbOption.new():setValue(false):checkbox(), SightCamera = DbOption.new():setValue(0):combo({DbOption.Item(_('OFF')):Value(0), DbOption.Item(_('ONLY FOR TRACKS')):Value(1), DbOption.Item(_('ON')):Value(2),}), JoystickMode = DbOption.new():setValue(0):combo({DbOption.Item(_('LINEAR')):Value(0), DbOption.Item(_('NONLINEAR')):Value(1), DbOption.Item(_('DISPLACED NEUTRAL (FFB)')):Value(2),}), CPLocalList = oms.getCPLocalList("Cockpit_F-5E"), } How can I modify this position? Displaced Neutral (FFB) seems to get assigned 'value(2)' but nowhere in the lua files for the F5E can I find where value(2) is assigned. Does anyone have any insight in how to change the neutral point of the joystick for the F5E?

What everyone doesnt understand is that Ed and razbam are intentionally taunting us. We should recognize this and start revealing how much money we spend on planes from IL2. before long ed will come up with the idea of micro transactions (put your name on the plane for extra money?)and limited editions. (Only 1000 copies of an F35 will b sold) They will then spawn a secondary market where people can buy and sell their own planes (with ed taking a healthy commission from each transaction) finally they will offer support groups in their forum to address addiction.

try deleting everything except this line from your export.lua dofile(lfs.writedir()..[[Scripts\DCS-ExportScript\ExportScript.lua]])

For example, the Su17 https://www.digitalcombatsimulator.com/en/files/3316288/ is a flyable mod based on the SU25T. Although the controls have keybinds for the kneeboard, it never appears. Is there a lua file that needs tweaking?

correcting the registry entry to point to the DCS install on the C drive does not prevent KB from reassigning the install on the D drive as the DCS folder. weird.

I thought you said you used a magura lever. Isnt that hydraulic?

clever design. It seems that damping requires the lever to be held? If it's a hydraulic system, how could you get lever compression to RELEASE the damping mech?

@Admiral Sarn Is that with you in the cockpit of airframe? It wont populate unless you are. It also wont populate with a non ED mod (unless you use a trick to fool DCS)

Yes there is! And it says version 2.5. ?!

I realize this is not really an SU25 issue but this mod is based on the SU25 (downloaded it from User Files). It really is just a model that uses the SU25 avionics. But I dont understand why no kneeboard appears when commanded.

I have noticed an interesting bug that might be affecting other users. I have two installs of DCS open beta. One on a D drive and another on a C drive. I specified the correct install on the C drive as well as the saved game folder on the C drive. I made sure to click save after specifying the correct directories in the preferences dialog. But if I open the prefs dialog again, KB lists the DCS folder in the D drive install. I dont know why it thinks the DCS on the D drive is 'mama' and it keeps running home to that one. but it is annoying and has created some degree of confusion for me until i realized this. Also, I read about profiles in the manual. However, I cannot find a settings page where I can specify profiles in KB. I am running KB 1.9.0.0 downbloaded from the official website.

Not to derail this topic, but i think ED has to expose a variable to the user that it presently does not: the center point. Regardless of whether an axis is designated a slider or not, we really do not know how this number is being applied. We think the reading of a ‘slider’ cranked all the way left is zero and the control assignments window may indicate this, but the control in the jet may still be based on a range where the midpoint of the controller is calculated (the center point) and used as zero. And when you check the slider checkbox, it puts the calculated midpoint as the start position. Another example where this is a feature and not a bug is in the special options for the F5E where there is a selection for the pitch axis to be: linear non linear FFB These choices change the center point of the axis so that the plane flies straight and level with different deflections. So when you fly with the FFB setting, the stick has to be pushed forward for level flight. But you as well as dcs recognize the controller is pushed way forward. We never really know where the center point (zero point) of the jet is until we fly it. If we knew the zero point, then i would know where to put the stick ahead of time. Similarly if i knew the zero point of these axes that are misbehaving, the bug would be immediately apparent.

The RWR buttons in the f5E behave oddly. It seems some cycle only when the value '1' is sent. So for example the search button works only when an incremental input (rotary) is used. When '1' is sent, the button in the jet is in a depressed condition. When '0' is sent, the button in the jet is in an up condition. However this button does not toggle on and off with its two states. Rather, The button in the jet is only activated when a 1 is sent when it is in the off state. And it is deactivated when a '1' is sent when it is in the on state. Unfortunately, using a simple button and disabling the the second value does not work because the button in the jet only changes appearrance when it detects a state change from 0 to 1.

There are a lot of instances of that. For example just for the Apache C:\Eagle Dynamics\DCS World OpenBeta\Mods\aircraft\AH-64D\Cockpit\Scripts\AI\PrestonAI_indicator_noVR.lua (1 hit) Line 4: purposes = {render_purpose.HUD_ONLY_VIEW, C:\Eagle Dynamics\DCS World OpenBeta\Mods\aircraft\AH-64D\Cockpit\Scripts\AI\PrestonAI_indicator_VR.lua (1 hit) Line 4: purposes = {render_purpose.GENERAL_AFTER_POSTEFFECTS, render_purpose.HUD_ONLY_VIEW_AFTER_POSTEFFECTS, render_purpose.AUXILLARY_SIGHT} C:\Eagle Dynamics\DCS World OpenBeta\Mods\aircraft\AH-64D\Cockpit\Scripts\Cameras\MAP\MAP_CAM_init.lua (1 hit) Line 10: --purposes = {render_purpose.GENERAL, render_purpose.HUD_ONLY_VIEW} C:\Eagle Dynamics\DCS World OpenBeta\Mods\aircraft\AH-64D\Cockpit\Scripts\Cameras\PNVS\PNVS_CAM_init.lua (1 hit) Line 9: --purposes = {render_purpose.GENERAL, render_purpose.HUD_ONLY_VIEW} C:\Eagle Dynamics\DCS World OpenBeta\Mods\aircraft\AH-64D\Cockpit\Scripts\Cameras\TADS\TADS_CAM_init.lua (1 hit) Line 9: --purposes = {render_purpose.GENERAL, render_purpose.HUD_ONLY_VIEW} C:\Eagle Dynamics\DCS World OpenBeta\Mods\aircraft\AH-64D\Cockpit\Scripts\ControlsIndicator\ControlsIndicator.lua (1 hit) Line 4: purposes = {render_purpose.SCREENSPACE_INSIDE_COCKPIT,render_purpose.HUD_ONLY_VIEW} C:\Eagle Dynamics\DCS World OpenBeta\Mods\aircraft\AH-64D\Cockpit\Scripts\Displays\BRU\BRU_cpg_init.lua (1 hit) Line 18: purposes = render_purpose.SCREENSPACE_INSIDE_COCKPIT --{render_purpose.GENERAL, render_purpose.HUD_ONLY_VIEW} C:\Eagle Dynamics\DCS World OpenBeta\Mods\aircraft\AH-64D\Cockpit\Scripts\Displays\BRU\BRU_plt_init.lua (1 hit) Line 18: purposes = render_purpose.SCREENSPACE_INSIDE_COCKPIT --{render_purpose.GENERAL, render_purpose.HUD_ONLY_VIEW} C:\Eagle Dynamics\DCS World OpenBeta\Mods\aircraft\AH-64D\Cockpit\Scripts\Displays\HMD\indicator\HMD_init.lua (1 hit) Line 27: purposes = { render_purpose.GENERAL, render_purpose.HUD_ONLY_VIEW } C:\Eagle Dynamics\DCS World OpenBeta\Mods\aircraft\AH-64D\Cockpit\Scripts\Displays\MFD\indicator\LCD\MFD_LCD.lua (1 hit) Line 6: purposes = { render_purpose.GENERAL, render_purpose.HUD_ONLY_VIEW } C:\Eagle Dynamics\DCS World OpenBeta\Mods\aircraft\AH-64D\Cockpit\Scripts\Displays\MFD\indicator\MFD_init.lua (1 hit) Line 17: --purposes = {render_purpose.GENERAL, render_purpose.HUD_ONLY_VIEW} so for example in the file C:\Eagle Dynamics\DCS World OpenBeta\Mods\aircraft\AH-64D\Cockpit\Scripts\Displays\MFD\indicator\LCD\mfd.lua I commented out line 4 giving dofile(LockOn_Options.common_script_path.."devices_defs.lua") dofile(LockOn_Options.common_script_path.."ViewportHandling.lua") indicator_type = indicator_types.COMMON --purposes = { render_purpose.GENERAL, render_purpose.HUD_ONLY_VIEW } pages = {{1}} init_pageID = 1 function declareMFD(left) local viewport = make_viewport(1,left) dedicated_viewport = viewport dedicated_viewport_arcade = viewport if left then page_subsets = {LockOn_Options.script_path.."Displays/MFD/indicator/LCD/page_plt_left.lua"} try_find_assigned_viewport("LEFT_MFCD") else try_find_assigned_viewport("RIGHT_MFCD") page_subsets = {LockOn_Options.script_path.."Displays/MFD/indicator/LCD/page_plt_right.lua"} end end And it works! Now if I go to HUD only view I can use the mfd panels on my desktop and not be blinded by the ones in game Thank you.

Same here. I tried to add axis control for TDC by modifying the default.lua file in the joystick folder here (C:\Eagle Dynamics\DCS World OpenBeta\Mods\aircraft\F-5E\Input\F-5E\joystick) with {action = iCommandPlaneSelecterHorizontalAbs, name = _('HOTAS Slew Horizontal')}, {action = iCommandPlaneSelecterVerticalAbs , name = _('HOTAS Slew Vertical')}, but that does not work. Any clues/suggestions would be appreciated.

Yes they should respond. Is this on an instant mission?