So forget the deadmau5 connection for a moment – it seems about time Windows got its own mature touch app for general purpose applications. Most apps focus on individual apps (like Ableton Live or Apple Logic), and most are still iOS-only. TouchOSC is still plodding along but hasn’t changed much since its debut. Lemur, the app based on the hardware that started the whole genre, hasn’t seen active development in a long time. The time seems ripe for a new controller – well, once live shows start again. It’s like a Windows successor to Lemur, with some powerful features, developed by one of the developers behind TouchDesigner. (A better explanation might be needed).Deadmau5 is releasing the app he’s torture-tested in his live shows, OSC/PILOT. To get the layout from your computer to a tablet one way is to download TouchOSC to your computer and import the layout to TouchOSC running on your computer, map it as a server and then connect to it from your tablet.If you can send but not receive check that the ipadress for whatever is running TouchOSC is set in the config file.In the config file the send port should be the same as the TouchOSC receive port and the config file receive port should be the same as the TouchOSC send port.Check that you are using the DCS BIOS fork not the original.Open an issue in the Issues section and let's get it fixed. Using the TouchOSC Editor on your computer, you can create your own layouts. The applications don't have to be launched in any specific order, but the first run can be a bit funky. You might also try restarting both TouchOSC and TouchDCS. If not, there might be an issue with your DCS-BIOS setup verify that's working property first. If it doesn't, check the console to see if your aircraft has been identified. Load up a mission and test your layout - when you press the sync button in the layout, the sync light should light up. Now when you run TouchDCS, you should be good to go. Make sure to change your configuration path under osc -> configLocations to wherever you end up putting your *.json osc configuration files. You can find out more about creating layouts and adding existing layouts here. The default config has multiple paths depending on the version you're using - but if you have multiple versions of DCS-BIOS or DCS installed, you may need to pick just one in your config file. If you are on the release version of DCS and you are using the FlightPanels fork of DCS-BIOS, modify dcsBios -> configLocations to %userprofile%/Saved Games/DCS/Scripts/DCS-BIOS/doc/json/. The default configuration is set up for Open Beta. If your network configuration is different (e.g., DCS-BIOS is running elsewhere on the network and exporting to a non-default IP/port combination), you'll need to edit the settings under dcsBios -> endpoint to match your network configuration. Unless you have an abnormal configuration, you shouldn't have to do anything here. Just make sure they match in your config.json. Your default settings in TouchOSC will probably have the ports as 8000/9000 - that's fine. You'll also need to add the IP address of the machine running TouchDCS to TouchOSC. Open up the config.json file that TouchDCS created, and edit the settings under osc -> endpoint to match the settings you see in TouchOSC -> Settings -> OSC. TouchDCS sends and receives commands from your device with TouchOSC installed. Open this up, we're going to edit itĬonfigure TouchDCS to talk to your device TouchDCS will create a default config file for you, config.json, in the same folder as the TouchDCS exe.after granting all these permissions, you'll likely have to relaunch in order to actually be able to use your device with TouchDCS.you may see another dialog requesting network permissions.Don't worry, TouchDCS is guaranteed to be 99.9% virus free!
0 Comments
Leave a Reply. |