pdmarsh

Great news, alonpet! Thanks for the update. Paul

Hi alonpet, In order to display the barometric pressure setting, you will have use the formula below. Here are the steps: On the PZ70/Multi Panel tab within DCSFP; Left click display button where you want data to appear, e.g. "Upper LCD Data"; In the dialog box that appears, check the box for "Use formula for final output"; In the formula box, copy and past the following code: (ALT_PRESSURE0 + ALT_PRESSURE1*10 + ALT_PRESSURE2*100 + ALT_PRESSURE3*1000)*0.000152590219 Click "OK"; Barometric pressure should now appear on the Multi Panel display. Let us know if you have any trouble. Thanks, Paul P.S. -- For anyone else seeing this, the above applies only to the A-10C. Other modules might deal with barometric pressure readouts differently.

Hi alonpet, Here are some written instructions that I hope will help. I'll have to look into displaying barometric pressure. It appears to be broken down into four seperate control functions for each of the four digits in the number. This will probably require a user formula. Put Heading Data on Multi Panel Display On the PZ70/Multi Panel tab within DCSFP; Left click display button where you want data to appear, e.g. "Lower LCD Data"; In the dialog box that appears, and in the "Type aircraft control search words:" field, type "HDG_DEG"; From the list that appears, double-click on "HDG_DEG"; "HDG_DEG" should now appear in the "Control ID" field; Click "OK" Set Up Knob to Control Heading Bug On the PZ70/Multi Panel tab within DCSFP; Right click on "LCD Knob (+/-) DEC" field; Left click on "Edit DCS-BIOS Control"; In the dialog box that appears, click on "New"; In the dialog box that appears, and in the "Type aircraft control search words:" field, type "HSI_HDG_KNOB"; From the list that appears, double-click on "HSI_HDG_KNOB"; "HSI_HDG_KNOB" should now appear in the "Control ID" field; In the "Enter value sent to DCS-BIOS:" field, enter -1500; Click "OK"; If desired, enter something in the "Description" field; Click "OK" Repeat the above using the Knob INC field and enter 1500 for the step value. Again, "-1500" and "1500" can be changed to whatever value works best for you.

Hi alonpet, With regard to heading, and in the case of the A-10C, a formula has already been embedded in the code. Simply use the Control ID "HDG_DEG" in whichever display you want it to show. For course, you would use "HSI_CRS." I have found HDG_DEG to be off a few degrees relative to the virtual gauge, probably magnetic vs. true. You can put in a simple formula to correct this. As an example: "HDG_DEG + 3" or "HDG_DEG - 4" (whatever is needed) In order to use the knob to control the heading bug, please see the attached image. Use the Control ID "HSI_HDG_KNOB." Then, in the "Enter value sent to DCS-BIOS" field put -1500 for decrease or 1500 for increase. You can make that variable step number higher or lower to adjust the speed of moving the bug relative to amount of dial turn. I also use the trim wheel the same way to set the course. In this case, use the Control ID "HSI_CRS_KNOB." I hope this helps. Paul

New Module Profiles for DCS-BIOS Since it is unclear when there might be an official update of DCS-BIOS, we want to make some new profiles available to the DCS-BIOS user community. These have been developed in support of DCSFlightpanels, but could be of use to others as well. New Profiles Spitfire LF Mk. IX AJS-37 Viggen SA342M Gazelle SA342L Gazelle SA342 Mistral Gazelle In order to use these profiles, simply extract the attached zip file into your DCS Scripts folder: C:\Users\xxx\Saved Games\DCS\Scripts Allow all folders to merge and supporting files to be overwritten. As always, backup your original DCS-BIOS folder before making these changes. I hope these profiles will prove useful. Sincerely, Paul DCS-BIOS.zip

Thanks Hawkeye60. You reminded to me to post the idea behind adding the device (added above). Paul

OK, ArturDCS did some testing and it appears that this device could be configured to use DCS-BIOS controls as well as act as a keyboard emulator through DCSFlightpanels. If we find that there is interest, we'll look into adding it to the panel linup in DCSFP. https://www.logitechg.com/en-us/product/farm-simulator-side-panel Thanks, Paul P.S. -- With this re-post, I forgot to note the idea behind this, as mentioned by Hawkeye60 below. At least, the Gazelle and Viggen have secondary left side joysticks for controlling cameras, cursors, etc. Depending on your existing main joystick or HOTAS, this could be useful in other modules as well, such as the A-10C to control the targeting pod and/or Maverick aim point. Plus, you can never have enough buttons and switches to configure!

Deleting post on secondary control stick for now. Would have to do testing to see if DCS-BIOS controls would work through the device.

Hi BlackLibrary, Unfortunately, this won't be possible. Only newer modules with clickable cockpits can be set up with DCS-BIOS profiles, which are needed for this kind of functionality. With the FC3 planes you will be limited to keyboard emulation, I'm afraid. Paul

After taking repeated beatings with this mission, it's time to ask for a little direction. Thanks, Paul

As mentioned above, here is an example of how to manually modify your *.bindings file to use the new Multi Panel configuration options. In this case, I am mapping existing commands to the "ALT" dial setting. PanelType=PZ70MultiPanel PanelInstanceID=\\?\hid#vid_06a3&pid_0d06#7&39001d8f&0&0000#{4d1e55b2-f16f-11cf-88cb-001111000030} BeginPanel [i]MultiPanelKnob{1FLAPS_LEVER_UP}\o/OSKeyPress{HalfSecond,LCONTROL + VK_S}[/i] MultiPanelKnob[b][color="Red"]{ALT}\o/[/color][/b]{1FLAPS_LEVER_UP}\o/OSKeyPress{HalfSecond,LCONTROL + VK_S} [i]MultiPanelKnob{1FLAPS_LEVER_DOWN}\o/OSKeyPress{HalfSecond,VK_S}[/i] MultiPanelKnob[b][color="red"]{ALT}\o/[/color][/b]{1FLAPS_LEVER_DOWN}\o/OSKeyPress{HalfSecond,VK_S} EndPanel The original command line is in italics and the added code is in bold & red in the new command line. Of course, the old command lines have to be deleted. All of the dial setting commands are these: {ALT}\o/ {VS}\o/ {IAS}\o/ {HDG}\o/ {CRS}\o/ Hope this helps. Paul

We are running into a bit of a problem integrating this module into DCSFlightpanels with regard to the FR22 radio. While we can get the knobs on the Logitech Radio Panel to change frequencies on the virtual radio, we can't read back the frequency numbers themselves for display on the Radio Panel. We probably need the equivalent of this code from the Ka-50 module, as an example: R800Revolve1 = CreateGauge() R800Revolve1.arg_number = 424 R800Revolve1.input = {0.0, 1.0} R800Revolve1.output = {0.0, 1.0} R800Revolve1.controller = controllers.R800Revolve1 If anyone from Heatblur, or someone familiar with the code, can provide such output data for the FR22 radio frequency indicators, that would be great. Thanks, Paul

If you have a particularly complex configuration of the Multipanel and don't want to remap everything from scratch, you can manually alter the *.bindings file and assign those mappings to whichever dial position you wish, e.g. ALT, VS, etc. I'll post an example later, but I just wanted to provide this information and stop anyone from rebuilding their Multipanel configuration, unless you want to, of course. Please note that only the Multipanel is affected by this update. All other panel configurations will still work in this updated version of DCSFlightpanels. Thanks, Paul

Just waiting on the next release of DCS-BIOS. Hopefully, that will be soon. Paul

Thanks for the heads-up. I had a feeling this was the case. It's a shame, really. I can see that a great deal of work went into writing and maintaining this mission. If it does get updated, we'll look forward to flying it. Paul

Thank you Chicki. We're always looking for missions for our little group of flyers. Paul

Is this mission no longer available? I can't find working link for it. If it has been taken down, any plans to resurrect it? Thanks, Paul

I found the fast erect button in the cockpit (on the left side of main ADI, not on the bottom as indicated in the manual) and it works in the cockpit. However, I can't find the argument number for this control. If anyone happens to know that, please post it and I'll add this control to the DCS-BIOS profile. Thanks, Paul

Thanks! Now that I know what it is, I'll see if I can get it working in the profile. Paul

I was hoping this would be included in the recent release of DCS-BIOS, but it didn't make it. I had some trouble with uploading my files to GitHub. That's all sorted out, so hopefully there will be another release of DCS-BIOS soon. Otherwise, this profile is ready to go. I'll look forward to any feedback once it goes live. Thanks, Paul

Thanks, but it's my pleasure. We should see a new release of DCS-BIOS very soon with these profiles. Paul

Thank you, Ian. When a hobby starts to feel like a job, it's time to pull away. You did the right thing, but we're glad to have you back. Sincerely, Paul

DCS-BIOS profiles for the SA342L, SA342M and SA342Mistral Gazelle are complete and have been posted for the next release of DCS-BIOS. Paul

That's correct. The Radio Panel is the only one that gets preprogrammed for individual modules. Actually, only two gauges were made for the A-10C. While they look fantastic and work great while they function, one or both lock up fairly soon and, if running multiple FIPs, all eventually lock up. We did try to get some support from Logitech on this, but they are quite busy with other projects and DCS is just not a priority for them. Still, they say they monitor this forum, so maybe we'll get some suggestions from them at some point. Paul

FIP support was never formally launched, but first attempts showed up in some releases. It's unstable in that the FIPs eventually freeze. It has been extremely difficult to sort this out. Unless ArturDCS has an epiphany, it seems unlikely that we'll get the FIPs functional. P.S.--I can't tell you how many hours ArturDCS spent trying to get the FIPs to work reliably. He was truly hoping to add this capability to DCSFlightpanels.