xoomigo

Dear PHMAC, Marcos and DCS-COINS users, I have just discovered an easier and more efficient way to get the Hornet's UFC Display (or any aircraft's text display) value updated - without the need for global events and values. You can do the following at the page button level: Expand "Change title to" --> "${value:mgdc_fa-18c_hornet_st_ufc_option_cueing_1}${value:mgdc_fa-18c_hornet_st_ufc_option_display_1}". It should be evident by now that I am also new to Touch Portal/DCS - still learning and discovering new stuff along the way. Also a heads-up - a DCS-COINS enhancement is being planned to convert Max65535 and Max65000 parameter values (typical for gauge reading, throttle position engine RPM and etc.) into the more human-friendly percentage format (0-100). Will update here when it's available.

Did you try parameters mgdc_fa-18c_hornet_st_ufc_option_display_# (1 to 5) and mgdc_fa-18c_hornet_st_ufc_option_cueing_# (1 to 5)? I think PHMAC already did what you are trying to do. If so, please check out the discussion in the previous page (page 2) where he showed parts of his setup. Otherwise please elaborate what/how you are thinking to achieve.

If you are referring to fuel level indicators, looks like a no. I don't find such DCS-BIOS parameters for the Hornet.

Yes, sure. You can download it from https://www.digitalcombatsimulator.com/en/files/3319504/

Hi PHMAC, No, you got it right! I was inadvertently leading you off track - bad habit of copy-and-paste without thinking. Very glad that you have a effective workaround to get your desired outcome. Cheers!

Hi PHMAC, I think you should be able to get the same results for "ufc_option_cueing_1" with the same method for "ufc_option_display_1". 1. Create a "Value" for it eg. "UFCCueing1". 2. Create a "Event" eg. "F/A-18C UFC Cueing 1 Change" with "When the plugin fa18c_hornet_cueing_1 does not change to <empty>" and action as "Set value with id Option Cueing 1 to "mgdc_fa-18c_hornet_st_ufc_option_cueing_1. 3. On your TP page "On Event", add "When the value UFCCueing_1 does not change to <empty>" with the action change title to "${value:mgdc_fa-18c_hornet_st_ufc_option_cueing_1}${value:mgdc_fa-18c_hornet_st_ufc_option_display_1} ". Cheers!

Hi PHMAC, If you are still wiling to spend a little more time to try to fix it... I just thought of this approach. You can try using the TP "Values" and "Events" feature. From "Events", you can setup a trigger for a "does not change" to an empty value condition (basically in a inverse manner where event will trigger if parameter value received is not empty). And the action will populate a pre-defined TP local value (eg. UFCDisp1) with that of the aircraft parameter. And then you set your UFC page "On Event" to trigger on does not change to empty value. Let me know how it goes. Cheers!

Hi PHMAC, I thought over again the issue you have and I can see clearer where the problem is. For simplicity and to avoid heavy performance hit, DCS-COINS's design is for a single-direction signal from DCS --> DCS-BIOS --> DCS-COINS --> TP. In short, TP can only listen/wait for events to be served from DCS-COINS. Therefore, your "On Event" settings should not work as it trying to request for parameter updates from DCS-COINS - as such function does not exist. Your first UFC button push probably got the values from an earlier TP cache of the parameters concerned. It's a long shot with my initial suggestion but it may work - if the page "On Event" "When fa-18c_hornet Function Selector Pushbutton, ILS is ON" is triggered after TP received related update for "mgdc_fa-18c_hornet_st_ufc_option_cueing_1" and "mgdc_fa-18c_hornet_st_ufc_option_display_1". To increase this probability, put a "Wait for Timer" for perhaps 500ms to 1 second before the "Change title to" to the parameter value action. A limitation with current TP version is the absence of "not" operator in conditional matching. If it can do the following, it would be ideal. Not sure whether it's in TP's future road map. When fa-18c_hornet_st_ufc_option_display_1 is not empty Change title to $(value:fa-18c_hornet_st_ufc_option_display_1) Other more troublesome approach is to map out all possible values for the parameter concerned - which requires mapping them within DCS-COINS and listing it in TP. When fa-18c_hornet_st_ufc_option_display_1 is CHNL Change title to $(value:fa-18c_hornet_st_ufc_option_display_1) When fa-18c_hornet_st_ufc_option_display_1 is XXXX Change title to $(value:fa-18c_hornet_st_ufc_option_display_1) When fa-18c_hornet_st_ufc_option_display_1 is YYYY Change title to $(value:fa-18c_hornet_st_ufc_option_display_1) If someone can provide a complete list, I may be able to map them for use in TP in the above manner. Cheers!

Hi PHMAC, Thanks for the feedback and compliments. It has been pretty quiet - except for two others, I was wondering whether anyone else got it to work... I am guessing that it could be a case of DCS-BIOS triggering a load of noisy events from that point which had overwhelmed your Wifi connection or TP app on your iPhone - causing the desired events to be missed. To check is to run "DCS-COINS -v" in verbose mode in Command Prompt - before loading DCS. Once the aircraft is running, you will see a stream of events being listed in the Command Prompt as they are received by DCS-COINS, and re-routed to TP. After you hit the ILS button, pause DCS and check to confirm that the st_ufc_option_display_1 event is triggered as below. Once confirmed that the value is updated as expected, the next thing I would recommend you to do is to eliminate the other unneeded noisy events (eg. commondata_st_ias_eu or commondata_st_ias_us, or both). You can do this by following the steps outlined under TIP#3 in the download page. For parameters with "commondata" string, they are located in your extract folder acdb\CommonData.pp. The others would be in the FA-18C_hornet.pp file. Coincidentally, I have just uploaded the package with the latest DCS-BIOS files and had potentially noisy parameters disabled by default. To update DCS-BIOS files, you will need to first delete the DCS-BIOS folder in %HOMEDRIVE%%HOMEPATH%\Saved Games\DCS\Scripts or %HOMEDRIVE%%HOMEPATH%\Saved Games\DCS.Openbeta\Scripts (depending on where it got installed earlier). Alternatively, rename it to something else (eg. DCS-BIOS.old). This is to enable the "Install DCS-BIOS" button in the Setup program. So, you may want to do the DCS-BIOS update first and test whether it's resolved - before doing the earlier approach of identifying and eliminating the unneeded noisy events to lighten the TP load for your iPhone. This is optional of course. Cheers!

Okay. Latest DCS-COINS.Setup.exe now has option "Set DCS Script Folder" (top-right) in the event it cannot detect the folder concerned. You can download it from the same link. Let me know how it goes.

Hi Marcos, I thought you were one of the first few who had downloaded and posted comments in the download page. Regarding your error, no one else has reported this. The setup is expecting your user script folder to be in either %HOMEDRIVE%%HOMEPATH%\Saved Games\DCS\Scripts or %HOMEDRIVE%%HOMEPATH%\Saved Games\DCS.Openbeta\Scripts. Where's yours? It's where the file Export.lua is located. I will need to add some logic to allow user to specify the folder concerned. Let me know. Cheers!

Just found the elevator trim wheel. Need to lift the pilot's left armrest to reveal it.

Certainly. Will have you in mind if the need arises. Anyway, it's now available: https://www.digitalcombatsimulator.com/en/files/3319022/ Note that I have only tested it on own my machine. I may need to fine-tune the installer program for others.

Hi Machiavel, A heads-up for you. I have uploaded the zipped installation package for DCS-COINS (acronym for COckpit Indicator and States) to the official DCS website. It is now pending review and clearance by the admin/moderator before you can see it listed on the Downloads-->User files section. I will update again when it's released. Stay tuned.

Just my 2 cents... It seems to me your issue came about after you ran the DCS Updater utility to switch from Stable to Beta version - most probably impacting your plugin .lua files and the associated configuration files. See whether you have the plugin folders and .lua files in "C:\Users\YOUR_USER_NAME\Saved Games\DCS\Scripts" (typical for DCS stable user folder). If they are there, there's still hope. You will probably see "C:\Users\YOUR_USER_NAME\Saved Games\DCS.OpenBeta\Scripts" for your "newly converted" open beta installation.

From Google Translate (for the benefit of others and myself who do not read French), here's what Machiavel posted above: "Hello, can you tell me where I could find the plugin to try it out because I have already made my pages for several planes (which I can share with you if you wish too, mirage2000, f18 for good, and which work perfectly) but now I would like to know how the plugin works so that it can retrieve the information directly from DCS. Thanks in advance." Hi Machiavel, Hope you can understand my reply here. I will be glad to share it with you and anyone who's interested. The TP plugin that I have put together is based on DCS-BIOS (which supports a long list of official and non-official DCS aircraft modules) and uses a library (dcs-bios-api-master) developed by Ranma-3 (hope I got his DCS forum sign-in name correct). I have also created an installer with option to install my collection of DCS-BIOS files if needed. However, I have yet to find a place to host the files since I wasn't sure whether anyone else was interested in the "poor man's" version of the more popular Stream Deck. Give me a few days and I will get back to you here. Cheers!

Change of plan - discovered existing code libraries, which will save me a lot of time and effort and also support a more complete list of DCS aircraft. Will rework the plugin to base on DCS BIOS after all.

Rider81 asked about TP getting updates from DCS, and I thought about sharing my work if there's sufficient interests. I had been working on a TP plugin feeding on data from Helios export script (found it easier to use than DCS BIOS) for the Hornet and was successful in getting instant updates on switch positions (eg. Flaps, Master Arm, A/A, A/G, LDG/Taxi Lights, and etc.), alarms/indicators (Master Caution, Battery SW, and etc.) and detecting when the aircraft is online. These are visible to TP as events where buttons can be setup to react to. However at the moment, I have yet to look into why it had caused CaptZeen's profiles to stop working on start-up. I want to use it together with TP as there are a few switches that I need to reach at directly without an intermediate step of having to open/close a panel or having to turn/aim my head too much.

It's already available in Steam. You need to search for "DCS: Mosquito".

On Steam, it says "Coming 16 September" with "This game will unlock in approximately 4 weeks". Special promotion offer ends on the said date.

Was your DCS on Steam running fine before? I would suggest that you uninstall DCS from Steam, reboot your PC, and then install it again via Steam.

For me: 1. Carrier ops (with Supercarrier, of course!) 2. Bigger payload/Longer range 3. Easier to land - more forgiving to a newbie like me.

Try checking C:\Users\<your username>/Saved Games\DCS\Logs.

Could it be just a case of a faulty PSU? In my case, the moment the GPU starts to draw more power, the PC just reboots. I had it replaced with a new one - with supposedly better quality capacitors and it had been working well ever since. It appears to me that GPU prices are starting to drop and new inventory is hanging around longer. If it continues to do so, I may get an upgrade end of the year.