Jump to content

toggle switches input questions


kombatkarl
 Share

Recommended Posts

Newbie pit builder, and new to the forum. Been playing a10c for a few months now and want to increase my immersion with a panel with some commonly used switches. Ive gone thru Tigershark's great tutorial/build of his panel and have a general idea of what im in for. My main question is regarding the implementation of toggle switches...by default a toggle connected to a controller would reult in a continuous "button pressed" input. It seems that dcs can handle this but i feel like too many continuous inputs from a bunch of "on" toggles might cause problems. True? Ive looked into pulse generators, but that seems like it would generate a momentary inputs each time the toggle is thrown, ie "button 1" is pressed whenever the switch is turned onn or off, therefore turning on whatever that swich input is bound to, even if youre trying to tturn it off.

 

Im just fishing for info...i know you guys have solved this, but im having trouble wrapping my head around a solution.

 

This is from my phone, sorry about typing errors.

Link to comment
Share on other sites

Hi Kombatkarl, and welcome to the forum.

You will have to modify the .lua file associated with the card you will use to interface your switches. I have a GP WIZ 40 and it works great.

 

Have a look at this post :

http://forums.eagle.ru/showpost.php?p=1559307&postcount=10

 

Good luck

Asus P8Z68 Deluxe, Intel Core i7-2600K (3.4 GHz), Corsair Vengeance 2x4096 Mo DDR3 1866 MHz, SSD 120 Go Vertex 2, EVGA GeForce GTX 970 FTW ACX 2.0 4Go (04G-P4-2978-KR), TM HOTAS Warthog #03797 (MB replaced), Saitek Combat Pro Rudder, TrackIR 5, TM Cougar MFDs with Lilliput 8" UM 80

Link to comment
Share on other sites

You could also think of using an Arduino. Most people find them a lot more complicated than a joystick controller but they do seem to be cheaper. I use them in my pit and for a while I was using a program called Link2FS_Keys fromhttp://www.jimspage.co.nz/arduino_keys_beta.htm (scroll down to version 4). It allows toggle switches to be used and outputs key presses. It can handle combinations and is very simple to set up because it requires no .lua file modifications as it runs completely seperate from DCS.

Link to comment
Share on other sites

I get what your saying. Too much draw from numerous toggles can cause stability issues on you rig i.e. BSOD. You just need to fabricate a switchboard that pulses for open or close event on the circuit. Toggles to switch to pc. Put you a fuse or breaker (I'm planning on putting fuses to each push button cluster in a panel and every toggle to help troubleshoot and put the fuze panel below the horizon indicator like the a-10c) on the switch and voila. Half the fun is making the stuff and putting it all together. The guys at radio shack know not to ask me if I need help finding anything. I can draw up a schematic for an example if you wish. Would now but I'm lying in bed fixing to sleep and no point if you get what I'm saying. :)

 

 

Btw that's assuming you doing a direct input method like a custom game controller.


Edited by Sn0w_Lynx
Spelling

[sIGPIC][/sIGPIC]

 

Rig: :joystick: :pilotfly:

AMD FX8350 8 core @ Stock Clock

G. Skill X Series 32GB (4x 8GB) @ 2200Mhz OC

GTX 1070 8GB

Corsair H110 Liquid Cooler

 

Link to comment
Share on other sites

Link2FS_Keys unlike Sn0w_Lynx's method uses an indirect input method in which something must go between the hardware and DCS World this is where Link2FS comes in.

With Link2FS_Keys you do not need to fabricate any circuit board with capacitors or something to produce pulses. The code that you load onto the Arduino only outputs changes, which through the software, are just set to send key presses. You can use different ones on press and others on release. This way DCS World is not overwhelmed by continuous commands being sent at it as it only receives changes in switch state, just the same as using a keyboard or mouse to control switches.

Link to comment
Share on other sites

  • 2 weeks later...

This continuous input would be a concern if you were using a keyboard for example. Anyone who has based their panel on the guts of a keyboard would be in trouble. But as most of the interface boards are treated like a game controller and conform with DirectX in Windows it isn't really a concern.

 

You might to looking to solve a problem that really isn't one.

 

And I'm not sure you're conclusion about pulse generators is correct. DCS would handle it exactly like it does now. You can bind both the off state and the on state to separate button presses so whether the button press is continuous or momentary, DCS doesn't have to care.

[sIGPIC][/sIGPIC]

 

Creator of:

 

F-18C VFA-195 "Dambusters" 1998 CAG Livery

https://forums.eagle.ru/showthread.php?t=213788

 

F-18C VFA-195 "Dambusters" July 2001 CAG Livery

https://forums.eagle.ru/showthread.php?t=215950

 

Pilot avatars for DCS Logbook

https://forums.eagle.ru/showthread.php?t=221160

 

How to make a DCS A-10C Panel

http://forums.eagle.ru/showthread.php?t=65998

Link to comment
Share on other sites

BaD CrC , Congratulations on a job very well done, what a terrific pit.

Regards

 

DL available skins here:

https://www.digitalcombatsimulator.com/en/files/?CREATED_BY=Strut

 

 

Pictures of my Skins here: https://imgur.com/a/bOQyQqW

 

[sIGPIC][/sIGPIC]

Win10 64bit, Intel® Core i7-5820K CPU OC @ 4.50GHz x6, X99A GAMING PRO CARBON, MSI RTX 2080 TI GAMING X TRIO 11Gb, 32GB DDR4 RAM, SSD 960 EVO250GB, SSD 850 EVO 500GB, JetSeat, MFG Crosswind Pedals, VPC Mongoose T-50, TMWH, DSD ButtonBox, Pimax 5k XR/BE

 

 

Link to comment
Share on other sites

Thanks guys for your kind comments,

 

I realized my pit construction thread is a bit old now (I started it with BS1) and may have been missed by many newcommers. Most of the questions I can read in the Home Cockpit topic on this forum have been solved by the "pioneers :smartass: " with BS1 since 2009. Maybe I should up from time to time this thread: http://forums.eagle.ru/showthread.php?t=41358

 

S1000268.JPG

 

 

SSAM_1632.JPG


Edited by BaD CrC
Link to comment
Share on other sites

  • 2 weeks later...

I use Helios in conjunction with GroovyGameGear boards and had never had a problem like your describing. Check out my thread on the panels I made;

http://forums.eagle.ru/showthread.php?t=94457&highlight=panel

 

Also check out my vids on how to setup Helios;

http://forums.eagle.ru/showthread.php?t=97100&highlight=Introduction+Helios

i7-8700k 3.07mhz|32GB DDR4 G.SKILL Ripjaws V Series 3200|ASUS ROG STRIX GeForce RTX 2080 8G GDDR6|Corsair 750D|Corsair H-100i|Corsair AX750|AOC Agon AG241QX 24"|Hanspree HT231DPBU|TM Cougar MFDs| Buddyfox UFC|Thrust master Warthog HOTAS(Modified spring/Slew control)|Saitek Combat Pedals|Logitech Marble Trackball|CorsairK70|TrackIR5|Custom Panels

http://goo.gl/vCWXRd

Desktop Simpit Thread

http://goo.gl/uNaNN1

Helios Tutorials

http://goo.gl/Sw1Uo6

Helios Profile

http://goo.gl/RM8BLP

Link to comment
Share on other sites

Some ppl like to do things themselves but I am just using Helios it's great & is recommended.

 

I have never heard of pushing too many buttons for too long causing a BSOD. I assure you that compared to running a external HDD through USB it does not rate much.

 

This is all just my opinion though.

Link to comment
Share on other sites

 Share

  • Recently Browsing   0 members

    • No registered users viewing this page.
×
×
  • Create New...