Raisuli Posted Saturday at 07:58 PM Posted Saturday at 07:58 PM Not sure if anyone else has had this problem, but I have 8 panels that use teensy controllers (Arduino with more pins/options) and in most cases 4ish MCP 20317 16 port I2C chips to further increase the number of digital ports (switch positions). That works great, I get tons of options, but... Once in a while Windows will re-assign the UUID to those USB devices, and that changes the role the controller plays in DCS, among other things. Generally I can figure out which panel is assigned to which UUID and by changing file names I get my mapped controls back; something like the F-18 can take over a hour to map out so this is good, but that means changing the name of up to 8 files in every aircraft that has mapped controls. That incentivizes me not to map controls in most of the every aircraft I have for DCS, leaving only the small handful I fly regularly. Seems like a waste. So, my solution was to write a Power Shell script that will take a text file and recursively go though all the aircraft in ~/config/input and change the names of all the Teensy based USB devices so all I have to do is get the input file sorted so the script knows which controller should have what name under the new UUIDs If anyone is interested I can post the script; not sure if this is a common problem or a teensy thing. 2
Recommended Posts