ctytler

There are multiple versions of DCS-BIOS out there. I believe this one is the most actively maintained: https://github.com/DCSFlightpanels/dcs-bios

It should be available in the most recent version of DCS BIOS. If you haven’t updated the files lately re-download and update them in your Scripts/ folder. (If using the DCS-flightpanels fork version)

Unfortunately, that's part of the Streamdeck GUI and I don't have control over it from a plugin. I just have access to the space below the "Title" bar and to the right of the button image. Elgato didn't really intend for users to configure such complicated buttons within their system. So for the next version with DCS-BIOS I plan to transition to doing all configuration in a larger separate window I can open (which, annoyingly, can only be set to one size). There is not a way to keep it open because the way the Streamdeck software works is it intends every button to be its own unique entity. So for the ID Lookup what I do is store the last selected module and last search query and restore that each time it opens. With the new version I have been looking into an "Auto-Open" checkbox that may make this somewhat better, the window will just close and reopen in the same spot each time you select a different button. I will look into if I can add that feature to the existing DCS-ExportScript buttons if its helpful, but will likely not have time until a couple weeks from now.

@Toni Carrera what do you mean when you say load the DCS BIOS program. Is this starting up the "DCS BIOS Hub" executable? Would you be able to confirm that it does not work before opening this and does work after opening? I may have to look into some DCS BIOS startup steps I'm missing. @Chacal_IX could you check if you're able to command A4E-C from the DCS BIOS web interface? (As seen in Mordants March 5th post). When I last tried it, it doesn't seem the A4 was working with DCS BIOS, I think we'll need to reach out to the BIOS maintainers.

Hi Mordants, do any other button commands work for you? The reason I asked was I tested the PLT_FAN one in the Streamdeck and thought it wasn't working at first when looking at the fan, but when looking at the left panel switch itself I would see it move on and off again with a press/release. I'm curious if it's all commands or just one. Thanks

So the issue right now is the Configure window can only be opened once for a button until you deselect then reselect that button. So for now I added a "Beta limitation" message with a v1.1.4, as this will take a bit of refactoring for me to manage the websocket differently so it works correctly. v1.1.4 - Changes: Disabled "Configure" button with Beta limitation message until button unselected and re-focused Fixed the "Disable" checkbox setting not restoring on window reopen

@Mordants I was able to test the PLT_FAN button and it works for me. One thing to note though... with your settings right now it will set the fan to ON while pressed, then OFF when released (You should see the cockpit switch moving with button press if so). Check the box (Disable) for the Release to change this from a momentary to a latched button press. [Right now I only have momentary/held command available, switch is not yet added]. ^ I've been able to recreate this now as well, will look into a fix.

Thanks for the update. I suspect I may have forgotten to handle the new global setting in the DCS-ExportScript buttons. Does the username persist if you go between DCS-BIOS buttons, but reset after opening an old DCS-ExportScript one? EDIT: I just tested this and doesn’t appear to be the case on my end. Would you be able to share the log details when this happens? Also the search term is designed to persist across buttons (so users can fill in details for many buttons of the same category easily) As for the command not working, would you be able to use the DCS-BIOS Control-Reference page (the web browser tool) to see if it performs as expected there?

OK, I think I have resolved the issue. I unfortunately had to remove my "Auto-Open" checkbox -- which I quite liked -- until I can find a better way to implement that, but feel free to download and install the latest (reads Version 1.1.3 on a right-click of menu) from the same link and see if it works

Thanks @automag928 that aligns with my expectations of the current bug I see. The config window that pops up talks to the main Streamdeck application via a websocket. So when the window opens it connects to the websocket and needs to get all the stored information through this. So the sequence goes like this (you can follow along with the log print out above): Send a request to Streamdeck app for Global settings (these are settings that apply to all buttons of the dcs-interface plugin, including dcs_bios_installation_path) Send a request to Streamdeck app for Settings (these are settings unique to each button, generally the IDs to monitor and what to send on press) [HERE is where the bug is occuring and the Websocket closes that I need to figure out why] Config window Receives Global settings response which it uses to fill in stored information (e.g. dcs bios path which replaces the default "username") Config window Receives Settings response which it uses to fill in last stored Command, Title Monitor, State Monitor settings After user inputs path, Send a request to Set Global Settings and store the newly provided DCS Bios path When the dcs bios path updates, Send a request to plugin (this is a background .exe) of "Request Module List" at a DCS Bios path location Config window Receives message with the ModuleList it uses to populate the dropdown selector After getting a module list, Send a request to plugin of "RequestControlReferenceJson" with path of a selected module in ModuleList Config window Receives message with contents of the json file it uses to populate the table data So the websocket connection is closing early, and the window still works it's just not getting any information, and also not able to store any inputted information (since all info needs to be stored in the Streamdeck app itself and not the Config window).

Thanks @Mordants! So I tried a lot of steps to recreate this issue and even did a clean Windows installation on my laptop, and finally found a way to reproduce the issue on my end. I have a Streamdeck setting set that outputs logging information, and when I disabled that, my plugin stops working and matches the log Mordants shared. I don't know the problem yet, but I should be able to track it down on my end now that I can reproduce it. Will report back here when I find out more.

I haven't been able to recreate the failure, but I've uploaded a newer build that has debug logging for all of the communications that query for and populate the DCS-BIOS json data. This should work for any install location, and just needs to find a directory that has the json files inside it somewhere, so either DCS-BIOS version should work. (The DCS Install path is only relevant for DCS-ExportScript buttons, there's no need for the DCS-BIOS buttons to know where DCS itself is installed) I would appreciate if one of you could install the new build (at the same link location) and share what you see in the log output. Here is a video of the steps I do when installing and the log it outputs on my machine: 2022-03-02 22-38-42.mp4 Log file contents at C:\Users\ctytler\AppData\Roaming\Elgato\StreamDeck\logs\com.ctytler.dcs0.log 22:38:45.084 Successfully connected to Simulator Interface UDP port 22:38:45.084 Successfully connected to Simulator Interface UDP port 22:38:50.150 Send message: {"event":"getGlobalSettings","context":"004AB4C83BCC0737A25DB483075189CF"} 22:38:50.150 Send message: {"event":"getSettings","context":"004AB4C83BCC0737A25DB483075189CF"} 22:38:50.151 Received message (didReceiveGlobalSettings) 22:38:50.151 Received message (didReceiveSettings) 22:38:50.155 Send message: {"event":"setSettings","context":"004AB4C83BCC0737A25DB483075189CF","payload":{"send_identifier":"","send_address":"","press_value":"1","release_value":"0","disable_release_check":false,"string_monitor_identifier":"","dcs_id_string_monitor":"","string_monitor_address":0,"string_monitor_mask":0,"string_monitor_shift":0,"string_monitor_max_length":0,"string_monitor_vertical_spacing":"0","string_monitor_passthrough_check":true,"string_monitor_mapping":"","compare_monitor_identifier":"","dcs_id_compare_monitor":"","compare_monitor_address":0,"compare_monitor_mask":0,"compare_monitor_shift":0,"compare_monitor_max_length":0,"dcs_id_compare_condition":"GREATER_THAN","dcs_id_comparison_value":"0"}} 22:38:50.155 Send message to plugin: {"action":"com.ctytler.dcs.dcs-bios","event":"sendToPlugin","context":"004AB4C83BCC0737A25DB483075189CF","payload":{"event":"SettingsUpdate","settings":{"send_identifier":"","send_address":"","press_value":"1","release_value":"0","disable_release_check":false,"string_monitor_identifier":"","dcs_id_string_monitor":"","string_monitor_address":0,"string_monitor_mask":0,"string_monitor_shift":0,"string_monitor_max_length":0,"string_monitor_vertical_spacing":"0","string_monitor_passthrough_check":true,"string_monitor_mapping":"","compare_monitor_identifier":"","dcs_id_compare_monitor":"","compare_monitor_address":0,"compare_monitor_mask":0,"compare_monitor_shift":0,"compare_monitor_max_length":0,"dcs_id_compare_condition":"GREATER_THAN","dcs_id_comparison_value":"0"}}} 22:38:58.842 Send message: {"event":"setGlobalSettings","context":"004AB4C83BCC0737A25DB483075189CF","payload":{"autoOpenConfigureWindow":false,"ip_address":"","listener_port":"","send_port":"","last_search_query":"","last_selected_module":"","dcs_install_path":"","dcs_bios_install_path":"C:\\Users\\ctytler\\Saved Games\\DCS.openbeta\\Scripts\\DCS-BIOS"}} 22:38:58.842 Send message to plugin: {"action":"com.ctytler.dcs.dcs-bios","event":"sendToPlugin","context":"004AB4C83BCC0737A25DB483075189CF","payload":{"event":"requestModuleList","path":"C:\\Users\\ctytler\\Saved Games\\DCS.openbeta\\Scripts\\DCS-BIOS"}} 22:38:58.843 Successfully found json modules at: C:\Users\ctytler\Saved Games\DCS.openbeta\Scripts\DCS-BIOS 22:38:58.843 Received message (sendToPropertyInspector) 22:38:58.843 - ModuleList 22:38:58.846 Send message to plugin: {"action":"com.ctytler.dcs.dcs-bios","event":"sendToPlugin","context":"004AB4C83BCC0737A25DB483075189CF","payload":{"event":"requestControlReferenceJson","filename":"C:\\Users\\ctytler\\Saved Games\\DCS.openbeta\\Scripts\\DCS-BIOS\\doc\\json\\A-10C.json"}} 22:38:58.882 Successfully read in json file from: C:\Users\ctytler\Saved Games\DCS.openbeta\Scripts\DCS-BIOS\doc\json\A-10C.json 22:38:58.885 Received message (sendToPropertyInspector) 22:38:58.885 - JsonFile

@Toni Carrera Moving question from https://forums.eagle.ru/topic/230609-new-streamdeck-plugin/?do=findComment&comment=4891698 to this thread. The table is populated by reading in contents of the DCS-BIOS json files within the specified directory, so DCS does not need to be running to get it setup. "Saved Games" has a space in it and works, so I wouldn't see an issue with spaces specifically, but it will fail if quotes are added. Could you try the following: Try without surrounding quotes if you haven't already, copy-paste your path into a windows explorer and check that it is a valid path (no misspellings) Check if there are indeed ".json" files in that path, I would expect them at, for example, "...\DCS-BIOS\doc\json\A-10C.json" You can also in Windows Explorer go to %APPDATA%\Elgato\StreamDeck\logs and the latest log file com.ctytler.dcs.0.log should show something like: 18:09:18.031 Successfully connected to Simulator Interface UDP port 18:21:52.267 Get list of json modules failed at: E:\..just for privacy....\Personal-Systems\System-Profiles\TC-I7-ASUS\Saved Games\DCS\Scripts\DCS-BIOS

Hi All, sorry I haven't been as responsive on this thread lately, but I have pushed up a beta test version of DCS-BIOS compatibility. It still supports your existing DCS-ExportScript buttons if you'd like to try it out and share feedback I've started a new thread for that topic here: For now I plan to keep supporting DCS-ExportScript since there's a lot of functionality people have worked into the export scripts here, but I'd like to see if the DCS-BIOS functionality can mature to accomplish everything as a full replacement at some point. Right now it just has core functionality to do the basics.

I have created an early beta build of the Streamdeck Plugin with DCS BIOS support. You can download and install it from here: https://github.com/enertial/streamdeck-dcs-interface/blob/master/Release/com.ctytler.dcs.streamDeckPlugin First time setup: After downloading and installing the plugin, Create a DCS-BIOS Button Click "Configure" button Click on "Setup" in top right of the "Configure" window and specify path to DCS BIOS installation and click Update. If successful, a table of Control References should populate as seen below. If you don't have DCS BIOS installed there is a link to follow in the Setup window New Feature: This has one new button option: "DCS-BIOS Button" and uses a new User Interface for that button only. There is some limited functionality right now and be warned that newer versions of the DCS-BIOS button may need you to re-create settings until the beta testing period is over. I have kept compatibility with DCS-ExportScript and the plugin can run with both backends at the same time if desired. Please share any comments, suggestions, or bug reports in this thread or submit an Issue on Github. Thanks!

I've been working on the DCS-BIOS backend addition, and tested out that it's working with the A-4E. For some reason exports from the game work well, but input commands to the game for the A-4 aren't working for me. Standard modules like the A-10C work great though, and even slightly faster than DCS-ExportScript for text displays. Anyways here's a preview video. I'm still working on the user interface, but I can try share an early version of the plugin to download so people can play around with if they really want A-4 or other DCS-BIOS capability. @rem27 @bones1014 dcs-bios-a-4e.mp4

@maddog726 check the order of the “dofile” lines in your Export.lua file. The DCS-ExportScript needs to be first before Helios I believe (or try playing around with different orders or enabling/disabling scripts). Sometimes different export scripts don’t interact well together. Also the dcs.log file in Saved Games can be helpful if one of the export scripts is failing.

Re: WinWing and DCS-ExportScript I'm aware that these don't play nice with each other. I had tried digging in a bit in the past, but had not any luck in finding the issue (with Winwing scripts or some other scripts that also have conflicts). It's also unfortunate that the "Fix Lua" button just deletes everything else in the file when I last tried it. I have been working on integrating DCS-BIOS as a backend replacement over the last couple months. And I believe this works alongside Winwing scripts, but I should re-verify that. So from my perspective, I'll keep pursuing integration there as a more complete fix. However I have been learning the React/Typescript languages along the way to create a better UI since it needed to change anyways (BIOS has more complicated concepts for input/output which is why I didn't originally pursue it, but it seems to be the best maintained option now). So that is taking a lot of time and effort to build up, but should make it scalable to more features going forward. Progress is being tracked here: https://github.com/charlestytler/streamdeck-dcs-interface/issues/41, and I can try get an alpha version uploaded in a few weeks so you can at least get core UFC functionality working (although with a perhaps clunky configuration process).

Hey SvenNeu, looking at the F-14B.lua export file, it looks like all functions are running in the "ProcessIkarusDCSConfigHighImportance" function: https://github.com/asherao/DCS-ExportScripts/blob/master/Scripts/DCS-ExportScript/ExportsModules/F-14B.lua#L2096-L2111 You may want to move those to the "ProcessIkarusDCSConfigLowImportance" function and see if that cuts down on some of the bandwidth. There are a LOT of id's being exported from the module file, you might also want to experiment with deleting some of the exports. I would suggest doing an initial test of deleting all export id's except the one you care about and see if the switch button is reponsive with that setting -- if so, you can go back and do a more selective pruning of export id's.

Hi Scoobie, I believe it is a superfluous "1", just following the style of the other "%X.Xf" formats. It is valid lua code, as it is just saying an integer decimal that must have at least 1 space. You can try modifying an export script and I believe it should still work. See lua doc (which is pretty sparse on details), but lua just uses the C language printf format, so more detailed description can be found here.

@jonsky7 The SDA version of this project is no longer being maintained. Another user has started a fork of this project (including Mi24 support) here: https://github.com/asherao/DCS-ExportScripts See discussion here: EDIT: The link is only for continued maintenance of the export scripts, Ikarus profiles will still have to be created manually.

Hey @Bailey that’d be great. I can also update the StreamDeck plugin instructions to point to your fork of the repo if that’s ok. Would be nice to collect community updates in a single place.

I've made the "ID Lookup" script I use in the plugin as a standalone script if you'd like to just extract all the values as a CSV file. See tool here: https://github.com/charlestytler/dcs-clickabledata-extract To find the name DCS uses for the module internally run a Mosquito mission, then afterwards look at the file Saved Games\DCS.openbeta\Logs\Export.log. This should have a "module not found" error and list the module name. You'll want to make a copy of the "Empty-DCS.lua" file in the Saved Games\DCS.openbeta\Scripts\DCS-ExportScript\ExportsModules\ folder and name it to the exact spelling of how the Mosquito shows up in that Export.log above. Now if you restart the mission you should see something like "File <mosquito_lua_file> loaded" You can then use the contents of the CSV to fill in the ExportScript.ConfigArguments = {} section, following the example of other modules. If you just default everything to [ID]="%.1f", that should publish decimal values for all clickable data in the cockpit (you can change these to "%1d" for integers if they show odd rounding errors, or decimal isn't need). That gets you the state of all clickable items (like switches/dials). If you need to get lamp data, see this documentation for some ways to figure them out: https://github.com/charlestytler/streamdeck-dcs-interface/blob/master/Sources/com.ctytler.dcs.sdPlugin/helpDocs/helpContents.md#manually-determining-clickabledata-attributes EDIT: Also please share here or DCS User Files if anyone makes one I've been slowly working on integration of the plugin with DCS-BIOS as an alternative to DCS-ExportScript since it's no longer being maintained. But it likely won't be available in the next month as my actual job is taking all my time lately.

Hi, I'm the developer of the Streamdeck DCS plugin. I looked into this a bit. The IDs are the way the plugin interfaces with DCS so if you can look them up in the lua as mentioned in the joystick inputs file and manually enter them they'll work. For the convenience "ID Lookup" table I generate in the plugin, I populate this by running the "Cockpit/Scripts/clickable_data.lua" file from the module. This means it only populates "clickable" items in the cockpit. Looking in the F/A-18C one they have some of the HOTAS device commands commented out (they maybe get in the way of other switches): -- HOTAS STICK elements["pnt_475"] = limit_button(_("Weapon Release Button"), devices.HOTAS, hotas_commands.STICK_WEAPON_RELEASE, 475) --elements["pnt_476_1"] = limit_button( _('Sensor Control Switch, Fwd'), devices.HOTAS, hotas_commands.STICK_SENSOR_CONTROL_FWD, 476, {0.0,0.2}, 0.2) --elements["pnt_476_2"] = limit_button( _('Sensor Control Switch, Aft'), devices.HOTAS, hotas_commands.STICK_SENSOR_CONTROL_AFT, 476, {0.0,0.4}, 0.4) --elements["pnt_476_3"] = limit_button( _('Sensor Control Switch, Left'), devices.HOTAS, hotas_commands.STICK_SENSOR_CONTROL_LEFT, 476, {0.0,0.1}, 0.1) --elements["pnt_476_4"] = limit_button( _('Sensor Control Switch, Right'), devices.HOTAS, hotas_commands.STICK_SENSOR_CONTROL_RIGHT, 476, {0.0,0.3}, 0.3) elements["pnt_477"] = limit_button(_('RECCE Event Mark Switch'), devices.HOTAS, hotas_commands.STICK_RECCE_EVENT_MARK, 477) --elements["pnt_478_1"] = limit_button(_('Trimmer Switch, PUSH(DESCEND)'), devices.HOTAS, hotas_commands.STICK_TRIMMER_UP, 478, {0.0,0.2}, 0.2) --elements["pnt_478_2"] = limit_button(_('Trimmer Switch, PULL(CLIMB)'), devices.HOTAS, hotas_commands.STICK_TRIMMER_DOWN, 478, {0.0,0.4}, 0.4) --elements["pnt_478_3"] = limit_button(_('Trimmer Switch, LEFT WING DOWN'), devices.HOTAS, hotas_commands.STICK_TRIMMER_LEFT, 478, {0.0,0.1}, 0.1) --elements["pnt_478_4"] = limit_button(_('Trimmer Switch, RIGHT WING DOWN'), devices.HOTAS, hotas_commands.STICK_TRIMMER_RIGHT, 478, {0.0,0.3}, 0.3) --elements["pnt_479_1"] = limit_button(_('Gun Trigger, FIRST DETENT)'), devices.HOTAS, hotas_commands.STICK_TRIGGER_1ST_DETENT, 479, {0.0,0.5}, 0.5) --elements["pnt_479_2"] = limit_button(_('Gun Trigger, SECOND DETENT (Press to shoot)'), devices.HOTAS, hotas_commands.STICK_TRIGGER_2ND_DETENT, 479, {0.0,1.0}, 1) elements["pnt_482"] = limit_button(_('Autopilot/Nosewheel Steering Disengage (Paddle) Switch'), devices.HOTAS, hotas_commands.STICK_PADDLE, 482) --elements["pnt_481_1"] = limit_button(_('Select Sparrow'), devices.HOTAS, hotas_commands.STICK_WEAPON_SELECT_FWD, 481, {0.0,0.2}, 0.2) --elements["pnt_481_2"] = limit_button(_('Select Gun'), devices.HOTAS, hotas_commands.STICK_WEAPON_SELECT_AFT, 481, {0.0,0.4}, 0.4) --elements["pnt_481_3"] = limit_button(_('Select AMRAAM'), devices.HOTAS, hotas_commands.STICK_WEAPON_SELECT_IN, 481, {0.0,0.3}, 0.3) --elements["pnt_481_4"] = limit_button(_('Select Sidewinder'), devices.HOTAS, hotas_commands.STICK_WEAPON_SELECT_DOWN, 481, {0.0,0.1}, 0.1) elements["pnt_480"] = limit_button(_('Undesignate/Nose Wheel Steer Switch'), devices.HOTAS, hotas_commands.STICK_UNDESIGNATE, 480) -- HOTAS THROTTLE --elements["pnt_486_1"] = limit_button(_('COMM Switch, COMM 1'), devices.HOTAS, hotas_commands.THROTTLE_COMMS_COMM1, 486, {0.0,0.2}, 0.2) --elements["pnt_486_2"] = limit_button(_('COMM Switch, COMM 2'), devices.HOTAS, hotas_commands.THROTTLE_COMMS_COMM2, 486, {0.0,0.4}, 0.4) --elements["pnt_486_3"] = limit_button(_('COMM Switch, MIDS A'), devices.HOTAS, hotas_commands.THROTTLE_COMMS_MIDS_A, 486, {0.0,0.3}, 0.3) --elements["pnt_486_4"] = limit_button(_('COMM Switch, MIDS B'), devices.HOTAS, hotas_commands.THROTTLE_COMMS_MIDS_B, 486, {0.0,0.1}, 0.1) --elements["pnt_487"] = limit_button(_('Cage/Uncage Button'), devices.HOTAS, hotas_commands.THROTTLE_CAGE, 487) --elements["pnt_488"] = springloaded_3_pos_tumb(_('Dispense Switch, CHAFF/OFF/FLARE'), devices.HOTAS, hotas_commands.THROTTLE_DISPENSE_FWD, hotas_commands.THROTTLE_DISPENSE_AFT, 313) --elements["pnt_488_1"] = limit_button(_('Dispense Switch, Forward(CHAFF)/Center(OFF)'), devices.HOTAS, hotas_commands.THROTTLE_DISPENSE_FWD, 488) --elements["pnt_488_2"] = limit_button(_('Dispense Switch, Aft(FLARE)/Center(OFF)'), devices.HOTAS, hotas_commands.THROTTLE_DISPENSE_AFT, 488, {-1.0,0.0}, -1.0) --elements["pnt_489"] = default_3_position_tumb(_('Speed Brake Switch, EXTEND/OFF/RETRACT'), devices.HOTAS, hotas_commands.THROTTLE_SPEED_BRAKE, 489, false, anim_speed_default, false) --elements["pnt_489"].side = {} --elements["pnt_490_1"] = limit_button(_('Throttle Designator Controller, Up'), devices.HOTAS, hotas_commands.THROTTLE_DESIGNATOR_CONTROLLER_UP, 490, {0.0,0.2}, 0.2) --elements["pnt_490_2"] = limit_button(_('Throttle Designator Controller, Down'), devices.HOTAS, hotas_commands.THROTTLE_DESIGNATOR_CONTROLLER_DOWN, 490, {0.0,0.4}, 0.4) --elements["pnt_490_3"] = limit_button(_('Throttle Designator Controller, Left'), devices.HOTAS, hotas_commands.THROTTLE_DESIGNATOR_CONTROLLER_LEFT, 490, {0.0,0.3}, 0.3) --elements["pnt_490_4"] = limit_button(_('Throttle Designator Controller, Right'), devices.HOTAS, hotas_commands.THROTTLE_DESIGNATOR_CONTROLLER_RIGHT, 490, {0.0,0.1}, 0.1) --elements["pnt_491"] = limit_button(_('ATC Engage/Disengage Switch'), devices.HOTAS, hotas_commands.THROTTLE_ATC, 491) --elements["pnt_492"] = limit_button(_('RAID/FLIR FOV Select Button'), devices.HOTAS, hotas_commands.THROTTLE_RAID_FOV, 492) --elements["pnt_493"] = default_axis_limited(_('Radar Elevation Control, Up'), devices.HOTAS, hotas_commands.THROTTLE_ELEVATION_CONTROL_UP, 493, 0.0, 0.1, false, false, {0, 1}) elements["pnt_494"] = default_2_position_tumb(_("Exterior Lights Switch, ON/OFF"), devices.HOTAS, hotas_commands.THROTTLE_EXTERIOR_LIGHTS, 494) Perhaps I can look at parsing in the joystick default.lua files as well.

The StreamDeck plugin will work fine if you move DCS install directory. The only place it uses that is in the ID Lookup Window for populating the table data for modules, and in that same window is a place where you can update the install path and click Update.