Stewmanji

This sounds absolutely fantastic. Well done! I can't wait to check it out and I'm excited to see that you posted this in the recent Hoggit post regarding crowd-sourcing keybinds (ED Forums version of the post). The final step would be to see if we could get JoyPro to read these custom keybinds.

This is a fantastic idea!! Kudos for all of your work so far and hopefully others contribute their work as well. Thanks for sharing this with the community!

Thank you for posting this. I'm having this problem as well. I've owned the Viggen for 6 months so I'm not sure if this is the result of a recent patch/update or what the root cause may have been. I tried uninstalling and reinstalling the module but that has not solved the problem. @Tonk99Can you be more specific about what dll was corrupt so that I can uninstall it and repair DCS in the same way? Thanks! Update: After deleting and reinstalling the module a few times, I finally got it to work. Very strange. At one point, the module just disappeared from the tab at the bottom of the main menu entirely...as if it didn't even exist in the game at all. Hopefully it will be a non-issue moving forward.

I just want to chime in to give a huge thank you to Razbam for this color option. This is an absolute game changer for me in terms of visibility on the EHSD/Data pages. Thanks Razbam!

Thanks for the suggestions. However, I've tested both routes and have not been able to pass the integrity test with other option. I'd be curious if anyone has had success passing the integrity test with either of the suggested solutions in the last few weeks. While these solutions worked earlier this summer, that appears to no longer be the case. From what I'm seeing, any attempt to modify the viewporthandling.lua file in Scripts\Aircrafts\_Common\Cockpit\ folder causes issues. Edit (10/12/2020): Just tried the kneeboard mod fmedges suggested once again...it works great and the Menu option is fantastic...but it does NOT pass integrity check.

Bumping this issue as it's a huge problem for those of us with multi-monitor setups. ED, please address this and remove integrity checks from kneeboard-associated file changes. This has a huge negative impact for those of us who exclusively fly in multiplayer.

I'm also experiencing this problem. I can successfully bind the landing gear to the lights on the PZ55. However, if I choose to leave the gear as the "N" light and bind another status to "L" or "R"...say arresting hook lever for example...the light no longer functions correctly. I've reconfigured the light several times, switching between gear and other cockpit switches, and only the gear handle appears to function correctly. Curious if anyone else has noticed this problem and/or has a possible solution. Thanks!

Thanks for the positive feedback Warlord. These flight panels have been a wonderful addition to my DCS setup so I'm happy to contribute to this community in my own, very small way. Sincerely apologize for that problem Ysiad. I updated the templates and forgot to update the links. Won't make that mistake again! Here are the updated links: PDF Template PPT Template To get around this problem, I've also created a link to the folder where I'll keep these files in the future: DCS Flight Panels Templates As I create additional aircraft panels, I'll add them to the folder (along with their binding files). Please feel free to edit them as you wish! Here is the current draft of the F/A-18C and AV-8B:

Hey everyone, I've seen a few templates floating around for the Switch Panel (PZ55) that allow you to create your own custom panel cover for labeling purposes. However, I had trouble getting any of them to fit correctly and several required installing new software. So, I created a simple version in PDF and PPT formats that make things a bit easier. When you go to print, just make sure that your printer doesn't default to resizing the image for whatever reason. Hope this is helpful to a few folks! PDF Template PPT Template

I'd be happy to be proven wrong, but I believe it's a limitation of DCS that makes the ability to dynamically change profiles when changing views impossible (i.e. changing exported displays when switching between the pilot and RIO seat). My understanding is that when you click "fly" DCS is processing that monitor setup file and locking things in place. Hence, whatever you have asked to be rendered is essentially "locked in." Thus, there is no way to simply activate or deactivate viewports while in flight. 1.6 definitely did a lot, but I think what you're asking for would require ED to fundamentally change how viewport exporting works. The only way I could properly envision what you're looking to do would be to utilize two monitors...one for the pilot's view and and one for the RIO. Then you would export all the relevant viewports. That's far from ideal but I can't think of another option off the top of my head. If you haven't already, I would encourage you to bring this up in Capt Zeen's discord. There is an F-14 channel there where you could ask this question and others might have a more detailed understanding of the limitations (or a possible alternate solution).

In case anyone else comes here with this issue, a user on the Github page found the solution: Ok, so I found out the parameter is case sensitive. Under the stream deck article in the wiki it is presented as "-nostreamdeck", but under the command line parameters article it is "-NoStreamDeck". Looks like the documentation just needs to be updated/corrected.

Adding my support for this issue. This would be a huge quality of life improvement for many of us. Please give this strong consideration ED. This change would do more for my in-game performance than any other graphical change/fix on the schedule right now. Great suggestion Ammo!

Looking good Togg! Love that Jester icon. Thanks for sharing these for the community and for hosting it all on Github.

The current state of the F-18's exports are that you can either have them look good in your export or they can look good on your primary monitor. I don't know if it's possible to have them both look good. I've opted to make the export look better. To do that, you can edit your RWR_ALR67_intit.lua file. If you're using the standalone version of the game, it can be found here: C:\Program Files\Eagle Dynamics\DCS World Open Beta\Mods\aircraft\FA-18C\Cockpit\scripts\TEWS\indicator\RWR_ALR67_init.lua Edit the ShaderLineDefaultThickness and Fuzziness values as such (or edit them to a level you find more preferable): Remember though, it's a trade-off: your export will look better but your in-game RWR on the main cockpit won't be visible.

If you're using CaptZeen's profiles, there are small buttons/icons on the main panel that allow you to "pop up" or "activate" the secondary panels. I've made those switches a little bigger in my own profiles, but here is what they look like on the A-10.

https://forums.eagle.ru/showpost.php?p=4240743&postcount=259

Hey Fakum, I experienced something similar myself when I was playing around with Helios/exports for the first time several months back. I'm afraid I don't really have any advice for you or a quick fix. Due to the situation you described, I opted to simply place my monitors side-by-side in Windows even though I have them stacked one above the other in real life. It just makes things easier when it comes to aligning the monitors in Windows and calculating the x/y coordinates. It took a few days of getting used to moving my mouse right to go "down" to the bottom monitor but after that it was second nature.

Sorry about that! I guess I forgot to hit save on the attachment. Should be there now!

As sobe mentioned, you can definitely do this if you modify a few additional init files to uniquely name exports for specific aircraft. I've attached my own "one monitor config" file to rule them all which includes exports for the following: - A-10 - AV-8B - F-14 - F-16 - F-18 - KA-50 - SA342 I have a separate .lua file for the F-15 as I could never get it to play nicely with this "master" file. To enable this "master" file, I modified the following files for each aircraft: ### F-18 MFD names: C:\Program Files (x86)\Steam\steamapps\common\DCSWorld\Mods\aircraft\FA-18C\Cockpit\Scripts\Multipurpose_Display_Group\MDI_IP1556A\indicator - MDI_left_init.lua - MDI_right_init.lua ### AV-8B MFD names: C:\Program Files (x86)\Steam\steamapps\common\DCSWorld\Mods\aircraft\AV8BNA\Cockpit\MPCD\indicator - MPCD_init.lua ### F-16 MFD Names: C:\Program Files (x86)\Steam\steamapps\common\DCSWorld\Mods\aircraft\F-16C\Cockpit\Scripts\Displays\MFD\indicator\LCD - MFD_left_init.lua - MFD_right_init.lua ### KA-50 For LEFT_MFD (SHKVAL) C:\Program Files (x86)\Steam\steamapps\common\DCSWorld\Mods\aircraft\Ka-50\Cockpit\Scripts\SHKVAL\BAKE - init.lua For RIGHT_MFD (ABRIS) C:\Program Files (x86)\Steam\steamapps\common\DCSWorld\Mods\aircraft\Ka-50\Cockpit\Scripts\ABRIS\BAKE - init.lua Stewmanji monitor config.lua

Glad to hear it worked for both of you! Fusedspine33, if you're referring to the blurriness of the MFDs, you can try the following: In your DCSWorld folder, navigate to "\Mods\aircraft\FA-18C\Cockpit\Scripts\Multipurpose_Display_Group\Common\indicator" and open the "MDG_strokesDefs.lua" file. In that file, I edited the values to read: --stroke_thickness = 0.8 (Original) stroke_thickness = 0.6 --stroke_fuzziness = 0.5 (Original) stroke_fuzziness = 0.3 I just commented out the original values so I would have them there as reference. Hope that helps. If not, feel free to share your exact issue and hopefully we can get you squared away!

Hey Wayne, Glad it worked for you! That one panel is definitely the most challenging across all the aircraft I have exports for so congrats...it's all downhill from here, hahaha! Regarding your profile .lua file, I keep mine in C:\Users\xxxxx\Saved Games\DCS\Config\MonitorSetup. I have the OVgME program installed, but like you, I was never sure how exactly to set it up so I've just continued to run without it. I haven't had any problems with anything being overwritten through numerous DCS updates. That said, I keep all the files I've edited backed up just in case and I'd recommend the same for you.

Glad you're up and running now foid! @hrnet940 @Fusedspine33 I wish I could say there was a one-size-fits-all solution, but in my experience, it really just come down to continual trial-and-error until it works. The trick for me was to slightly change the width of the panel itself. I think the default value from CZ was around 596 or so and I decreased it to 526. Perhaps tweaking the width in addition to the X,Y coordinates will do the trick for you! For reference, these are the values I'm currently using for my panel: F18_IFEI = { x = 154; y = 758; width = 526; height = 203; } NOTE: Adjust the "x" and "y" values accordingly based on how you have that second monitor positioned.

Hey foid, Yes, there is a transparency option in Helios that you might need to watch out for. Open your profile in the Profile Editor. In the profile explorer, double-click on the Monitor that contains your cockpit artwork (in my case, Monitor 3). On the right side you should see the properties window appear for that monitor. What you want to look for is the Section that says "Background." Below that should be a box called "Fill" that you can check/uncheck. Make sure this box is unchecked. This will ensure your Helios panel is transparent when you launch it via the control center. My guess is that it's set to fill right now and is simply covering up all your exports. To be on the safe side, you can also look at the "DASHBOARD panel" as well and make sure it's Fill status is also unchecked. Hope that helps! Let me know if you can't find it for any reason.

Fantastic news! Glad you're back up and running!

Thrilled we could get em4joshua up and running! Another important takeaway, for anyone who has a similar problem in the future, is to ensure you're running DCS in windowed mode (uncheck the "fullscreen" option in the DCS in-game settings).