Invictus84

Does the new DDI show up in Windows Game Controllers? If so, I had the same problem but eventually SimAppPro recognized the device. Why? No idea. How many controllers do you have connected to your gaming PC? I have experienced problems relating to having too many controllers being connected to a Win11 PC (I never experienced these issues on Win10).

Interesting discussion - need to try this myself. On a side note - you all might want to consider looking at the aircraft module files for DCS ExportScript and/or DCS-BIOS. They have the most of the DCS ID numbers you need to do this stuff. https://github.com/asherao/DCS-ExportScripts https://github.com/DCS-Skunkworks/dcs-bios I've attached the DCS-ExportScript and DCS-BIOS JF-17 scripts as examples of the data you can pull from their scripts. There are also several tools you can use to pull this data from DCS aircraft modules: https://github.com/asherao/dcs-unclickabledata-extract https://github.com/charlestytler/dcs-clickabledata-extract JF-17.lua JF-17.lua

Check PM

I hope someone finds this useful. You can find the model on Thingiverse by clicking here or via the attached zip file. The cover screws on to the FSSB R3 and should provide protection from dust, bumps and (to a lesser extent) spills. I assume it will also work with the new FSSB R3 MK II ULTRA as well, but I have no way to test that statement so YMMV. I admit it isn't fancy but is relatively easy to print and gets the job done. Took me about 30-40 minutes to design it on TinkerCAD, but feel free to modify the model for your needs. Add a logo on top, or a cup holder, or whatever...feel free to go wild with it!. The ring STL can be printed as well to slide on to the cover, and is useful for covering any potential gaps at the bottom of the cover as well as make it look more interesting. The ring should slide on to the cover and be fairly snug, so there is no need to use glue to keep it in place. NOTE: I recommend printing the cover itself with the top of the model down on the print bed. This will allow you to print it without the need for supports. I used eSun PLA+ filament for mine. My copy was printed in Cura using Standard Quality - 0.2mm with 20% infill. FSSB Cover.zip

It is possible to get many of these working if you just juggle the order around. The following is the contents of my Export.lua file. Everything works fine, even Tacview (when I choose to uncomment / enable it). dofile(lfs.writedir()..[[Scripts\DCS-ExportScript\ExportScript.lua]]) dofile(lfs.writedir()..[[Scripts\DCS-BIOS\BIOS.lua]]) local wwtlfs=require('lfs') dofile(wwtlfs.writedir()..'Scripts/wwt/wwtExport.lua') -- load the DCS ExportScript for Helios dofile(lfs.writedir()..[[Scripts\HeliosExport16.lua]]) local SimShakerlfs=require('lfs'); dofile(SimShakerlfs.writedir()..'Scripts/SimShaker.lua') dofile(lfs.writedir()..[[Scripts\SimShaker-export-core\ExportCore.lua]]) pcall(function() local dcsSr=require('lfs');dofile(dcsSr.writedir()..[[Mods\Services\DCS-SRS\Scripts\DCS-SimpleRadioStandalone.lua]]); end,nil); -- local Tacviewlfs=require('lfs');dofile(Tacviewlfs.writedir()..'Scripts/TacviewGameExport.lua') local telemffblfs=require('lfs');dofile(telemffblfs.writedir()..'Scripts/TelemFFB.lua') FYI - I do not see significant drop in performance with this even when playing multiplayer, but I have a pretty beefy PC (i7-13700KF, RTX4080, 3 1TB Samsung 980 Pro SSDs & 96GB of RAM). Hope this helps.

It is one day. I have other things to do, so no big deal for me.

Mig-19P profile and customized export script based on the one on Bailey's GitHub site with some added stuff I ported over from the DCS BIOS script for the Farmer. Fair warning...it's not a work of art...but it works for me. I hope one of you finds it useful as well. Enjoy! NOTE: I also uploaded the profile to User Files -> Device Profiles: https://www.digitalcombatsimulator.com/en/files/3336052/ Mig-19P Streamdeck Profile.zip

Photos taken on Dec. 8th, 2023. MiG-17 located at the Valiant Air Command Warbird Collection in Titusville, Florida. https://www.valiantaircommand.com/ Also have a MiG-21 and lots of other Cold War planes (F-104, F-105, F-8, etc.)

PM sent.

I am no expert, but I have one of the first generation Samsung 49" monitors which are 1080p (resolution 3840x1080) and used to run things on a GTX1070 using a 10th gen i7 card and things ran fine as long as I adjusted my graphics and expectations i.e. I did not expect to be able to run every setting on high (I eventually upgraded my whole system to do so). Keep in mind some of the new 49" monitors run 1440p resolution (5120x1440), so that will also hit your performance if you go that route. I'm planning on replacing my current monitor with the Samsung G9 1000R 49" monitor later this year (love the higher curve and have the system to support higher resolutions).

*throws up hands* Nevermind...I've moved on to another collective project. https://www.thingiverse.com/thing:5226353 Full BOM in project description. Enjoy if interested.

Thanks...anyone ID the spring yet? I have all the parts printed and my own plan for the electronics (i.e. FreeJoy and custom shift registers), but without that spring its a no go.

https://www.thingiverse.com/thing:6132978

If memory serves, DAC leans on the same DCS-ExportScript backend that Ikarus and DCS-Interface use. DAC is meant to interface with an old (and no longer supported) hardware solution called Arcaze (DAC stands for DCS Arcaze Connector) which were used to automate MSFS cockpits i.e. same basic concept to using DCS-BIOS and Arduino to automate lights, gauges, etc. etc. Pretty sure Arcaze was produced by a German company but as I stated they are no longer supported or produced. ^ Arcaze modules being used to drive LEDs in a cockpit. Ikarus is a DCS glass cockpit solution similar to Helios which utilizes the DCS-ExportScript backend. The developers dropped support a few years back, but you can still download it off GitHub. It is sad it is no longer supported because in my opinion it is in someways easier to use than Helios. It also doesn't introduce the export script complications that arise when you try to run DCS-Interface and Helios at the same time. I use Ikarus and DCS-Interface in my cockpit and it works fine and has very little impact to FPS/performance. On a side note - the DAC entries in the DCS-ExportScript config.lua file can be used to drive other instances of Ikarus and/or DCS-Interface either running locally on the same machine and/or on different machines. If you are running both on the same machine you need to define different ports for each solution. Here is a snippet of my config.lua file to get an idea how to do it: -- Ikarus a Glass Cockpit Software ExportScript.Config.IkarusExport = true -- false for not use ExportScript.Config.IkarusHost = "127.0.0.1" -- IP for Ikarus ExportScript.Config.IkarusPort = 1725 -- Port Ikarus (1625) ExportScript.Config.IkarusSeparator = ":" -- D.A.C. (DCS Arcaze Connector) NOTE: This is used for DCS-Interface / Streamdeck solution ExportScript.Config.DACExport = true -- true for use ExportScript.Config.DAC = {} -- first hardware ExportScript.Config.DAC[1] = {} ExportScript.Config.DAC[1].Host = "127.0.0.1" -- IP for hardware 1 ExportScript.Config.DAC[1].SendPort = 1625 -- Port for hardware 1 NOTE: port changed to 1625 here and in DCS-Interface ExportScript.Config.DAC[1].Separator = ":" -- second to n hardware --ExportScript.Config.DAC[2] = {} --ExportScript.Config.DAC[2].Host = "192.168.100.2" -- IP for Ikarus instance on second cockpit PC --ExportScript.Config.DAC[2].SendPort = 9092 -- Port for hardware 2 --ExportScript.Config.DAC[2].Separator = ":" -- Ikarus and D.A.C. can data send ExportScript.Config.Listener = true -- false for not use ExportScript.Config.ListenerPort = 26027 -- Listener Port for D.A.C. Just be sure to also change the listener port in DCS-Interface (or Ikarus) to match those in the config.lua. For example, in my config.lua I changed the listener point for the second 127.0.0.1 entry (used for DCS-Interface) to 1625 and changed the port config within the DCS-Interface DCS Comms option dialog: Hope this helps someone.

I saw this setting in Mods\aircraft\MIG-21bis\Cockpit\RADAR\Indicator\definitions.lua object.additive_alpha = true Sadly, changing it does not help with my radar export. Ah well..

I find it does make a difference with FPS, but YMMV.

http://pw-developer.com/soft_dcs_mfd.html

http://pw-developer.com/soft_dcs_mfd.html

It is for me. I slide the seat up slightly to use the stick. To be completely honest, I personally think the "cut out" seats are overrated and not needed...but YMMV based on what's important to you.

MB-339 was crashing my installation. A-4E, T-45 and Su-30 are OK. YMMV!

In my experience it wont work. Only the first listed export script will work....unfortunately.

Same here. Noticed it yesterday but just got around to researching them when I saw this thread. I have an HP Reverb.

Are you running DCS full screen? If so, it is possible the kneeboard is generated but "behind" the DCS screen. I suggest loading Ikarus without DCS running and test to see if the kneeboard shows up on your main display. If so, try running DCS without the Full Screen option. Might work, might not...but worth a try. :dunno:

Respectfully, I have a 144hz monitor and used it with a TrackIR 4 for 2+ years now. I've never had any issues with either in any of the air combat sims I fly (DCS, IL2 Great Battles, IL2 Cliffs of Dover Blitz, Rise of Flight), and my framerates in both are always well over 100fps or even higher.