charliefoxtwo / touchdcs Goto Github PK

SRS has a really cool one-click installer that will put everything in the right place and even append a line to your Exports.lua if necessary. It would be cool to do something like this for TouchDCS.

The readme offers pretty weak support for new users. The Wiki can be used to document exactly how a new user should get started, and the next steps they might take.

Hi,

first, I want to say “good job”. You had a great idea and I love what we can do with touchosc and dcs.

I would also like to bump the issue mentionned here #4 (comment)

Now that the mosquito has been released, I downloaded the newest dcs-bios but touchdcs says that it cannot see the “mosquito”, and I believe it is because of the issue above.

Or maybe I am missing something?! Has anyone been able to make it work?

from the different config files I read from dcs-bios, the naming is different (from file: https://github.com/DCSFlightpanels/dcs-bios/blob/master/Scripts/DCS-BIOS/lib/Mosquito.lua ):
BIOS.protocol.beginModule("Mosquito", 0x7000)
BIOS.protocol.setExportModuleAircrafts({"MosquitoFBMkVI"})

TouchOSC uses zeroconf for a lot of setup. It would be nice if we could use it as well in order to simplify adding new devices.

It looks like the key TouchOSC uses is _osc._udp.local

Right now all configuration is loaded from config.json. This is great, except when a user modifies their config file and later attempts to update to the latest version of TouchDCS which might have different default configuration set. It results in an awkward attempt to merge json configuration files which is sure to end in disaster.

If we can either split this into two separate config files or, more likely, just move the default configuration into code rather than config.json, it will put us in a position where we don't need to worry about an update overwriting a user's config settings (especially when things like osc devices are saved in that file as well).

Hey, I was wondering if it was possible to send keyboard input through touchdcs?

I would love to have a page on TouchOSC with F1-F10, ESC, and a combination of keys (eg: CTRL+L, RIGHT SHIFT+RIGHT CTRL+L).

It would be nice if the application could check for updates on startup, and prompt the user to update if a new version is available.

This section should not be present in the default configuration. Additionally, it is being written with casing issues causing commands for aliased aircraft to not work. This section should not be saved to the default configuration.

I am having trouble adding more devices to the config.json. My programing skills are 0, sorry. How could I add a second device here? I tried various things but always results in crashing and errors.

"osc": {
    "devices": [
      {
        "ipAddress": "192.168.3.78",
        "sendPort": 9000,
        "receivePort": 8000
      }
	      ]

Thank you, awesome software :D already creating my second template and I love it.

It would be nice to have TouchDCS autorun through Export.lua like other DCS addons do. I'm not sure what this entails, but SRS has done this with a C# application so it must be doable.

This will help with debugging issues others may have down the line.

I can post more detailed logs later, time permitting, but in lieu of that:
The console app raises an exception when starting up, about a duplicate key being added.
Dropping into a debugger it looks like it happens when the Mirage F-1 is discovered.
I ran a tweaked codebase that skips that aircraft and the exception is avoided.

2.7.16 adds the Mirage F-1.

The previous DCS-BIOS release (2.7.14) does not exhibit the problem.

Some aircraft have multiple models which output different ACFT_NAME values in dcs-bios, but use the same json file (e.g. A-10C and A-10C_2 both use a-10c.json. We'll need a way to associate multiple aircraft with the same dcs-bios json file.

Aircraft that have multiple models: A-10C, C-101CC, F-14B (soon?), all FC3 aircraft, P-47D, P-51D, SA-342M, Spitfire LF Mk IX.

This list does not include modded aircraft, or aircraft that share config files with mods (F/A-18C and UH-1H). The easiest way I've found to check is to look at the lua files in dcs-bios and check for a line like BIOS.protocol.setExportModuleAircrafts({"A-10C", "A-10C_2"}). If there are multiple exports specified, then we'll need to account for that.

I think we can add this to the config.json file. This will allow people to add their own mods fairly quickly for testing too, and update their config if we're behind on a patch. From there, we can build an alias dictionary in BiosOscTranslator and reference that when determining the active aircraft or active json file to consider.

Each C# project should have its own readme outlining what its purpose is, and the top level readme should also cover this at a high level. This will make it easier for new contributors to get up to speed.