skypickle

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?

Which lua file defines the hud only view? Can I modify it so it only removes mfds?

Also I can use display properties to boost brightness of each monitor-that allows keeping on screen mfds at less than blinding brightness.

your pic of the widescreen does not show much of the cockpit

@MadKreator how do you get DCS to cut off the bottom of the image?

I find that simply turning up the brightness of the in game mfds via the knobs/switches achieves almost the same thing-readable exported mfds, blinding in game mfds. But I’ve seen some people’s screens where the bottom third of the screen image has been amputated. How do they do that?

where is this mission available?

so how does one set this up for the G2? is there a zone of 'in focus' that can be set?

I am trying to refine some of the effects simshaker produces by adding to the simshaker.lua file. I have inspected the mainpanel_init.lua but cannot find some necessary variables. For example for the Apache, simshaker.lua has elseif obj.Name == "AH-64D_BLK_II" then dataTable.rpm = string.format("%.0f~%.0f", LoGetEngineInfo().RPM.left, LoGetEngineInfo().RPM.right) dataTable.panelShake = string.format( "%.2f~%.2f~%.2f~%.2f~%.2f", MainPanel:get_argument_value(820), MainPanel:get_argument_value(821), MainPanel:get_argument_value(822), MainPanel:get_argument_value(823), MainPanel:get_argument_value(824) ) the mainpanel_init.lua also has CanopyDamages.arg_number = 905 pilotDoor.arg_number= 795 Can I just add: local CanopyDamages= MainPanel:get_argument_value(905) local pilotDoor= MainPanel:get_argument_value(795) ? How can I make DCS export variables for hellfire launches, gun firing, rockets, or certain flight conditions like VRS, retreating blade stall? The KA-50 section of the simshaker.lua file has this dataTable.cannonShells = string.format("%s~%.3f", dataTable.cannonShells, GunTrigger) Since I dont have that module I dont know what's in its mainpanel_init.lua but I guess I would find a variable for guntrigger which has the ID 615? How do I find this for the Apache? I tried inspecting the Huey mainpanel_init.lua but that was not helpful.

Thank you for a wonderful set of missions. One small problem tho- I cannot get into CCRP mode reliably. After a few drops the button for CCRP mode (the letter O) doesnt do anything. Is this a known bug?

I am making a profile for the L39 (call me silly for wanting to fly this module). I would like to make two momentary display buttons for the RSBN-5S that by the right elbow so I can better read it (rather than twisting my head to see the little dials). As well as a rotary to control each. This is what I am talking about. They are labeled landing and navigation. The relevant entries in the ctytler lookup are: The nav channel selector works but the landing channel did not. The DCS exports lua for the L39 had interesting discrepancies. [191] = "%.3f", -- RSBN Navigation Channel Selector Knob (Axis) {0.0, 1.0} in 0.025 Steps [192] = "%1d", -- RSBN Landing Channel Selector Knob (Axis) {0.0, 1.0} in 0.025 Steps Changing the [192] line to be "%.3f" now allows the rotary to properly advance the numbers. How do I suggest this improvement to the github? I have never done a pull request and the whole git thing is not my cup of tea? Well, I spent an hour reading about git so I created a pull request to this repo: https://github.com/asherao/DCS-ExportScripts Who is Asherao and is he/she still maintaining the repo? or is there another?

enlighten me. What is the breakdown of the the layoffs?

Microsoft’s 10000 person layoff was their vr division. After the hololens was a disappointment to the military (overheating in 30’?) MS took their toy and went home. so now they will play the chinese tactic, wait for someone else to fix it, reverse engineer the the device and clone it. Meanwhile WMR code will languish. (No game maker will prob continue to develop Wmr code) So openXR to the rescue. And there are three ways dcs can talk to headsets 1) steamVR (aka openVR- please can we killthat word as it is not open) for headsets that use steamvr 2) open composite 3) open which one does simply double clicking on the dcs executable use? what are the modified shortcuts for using 1,2, or 3? what are frametimes/fps for these three choices on an amd/intel system and or nvidia/amd gpu?