Baldawg

should've downloaded this a long time ago!!!!!! Your app is the only thing that got the Asset pack to download. Command prompt had no effect. To bad its not an integrated feature to DCS :thumbup::thumbup::thumbup::thumbup::joystick:

The more efficient code isnt working for me.....it says no such module exists. then immediately opens the autoupdate.log in notepad

not seeing asset pack ticket in place on DCS support logs included. including here as well. Load time for NTTR on any instant action a10c mission is 10 minutes running on SSD that is only half full. dcs.txt

I still had the beta version installed so i tried it out and it seems that i cant re produce the crash in that version. ill be testing it today on the Su25t as im trying to learn it for a squadron mission coming up. ill keep you posted. edit: i did noticed today in the beta version that the shakval doesnt remember its location on the preferred monitor. whenever i relaunch DCS it goes back to the main display. possibly already fixed with the 2.7.0 release but ill test that as well.

TEWS is working fine. Ive had a few crashes with the 2.7.0 version. checking event viewer reveals a .net framework crash. shortly after a kernelbase.dll for uMFCD then a DCS.exe crash. Im also experiencing some strange issues when i turn my head in game (using track ir) the mfcds go wonky and the rwr and clock have a green effect over it. ill conjure a picture so you can see what i mean. I can give you logs and such as well if needed. Is there any vast difference between the beta and this new version?

I'd gladly pay a nominal fee for your efforts sir! Your app has rekindled my love for my pit and the a10c. The addition of the TEWS is fantastic and came along a lot faster than I could anticipate. Good show! Keep'me coming.

Awesome, can't wait!

:thumbup::thumbup::thumbup: So are these teaser pics for us to look at? Will this require a small update?

labor of love/hate ]I've been adding on to this monster for over two years. The panels are made from pegboard which is great for spacing out toggle switches. I had it laying around and its an optimal thickness and the holes also make mounting easier. My signature describes what I'm using for everything to work but the pic is the latest version with some additions i haven't added to the sig yet.

thanks for the replies....i remapped the offending to my saitek switch panel for now until i can rewire the switches i want to the DSD switchboards i recently purchased. i figured the desktop aviator was the problem child in this playground i got going on here. Heres a pic of the Universal pit ive been piecing together for a few years now...

M2k Toggle Debacle Ive been beating my head trying to get a few switches in my pit to work for the Mirage. Namely the Alternator 1 and 2 switches. The particular board im using is a desktop aviator 2235 which pulse generates a signal when the switch is flipped. Unfortunately ive tried to write new code in the default.lua but cannot get it to perform a simple on/off function. For example, i can bind a button to "Alternator 1 OFF" and get the switch in game to go off but cannot use the same to flip the switch on. does anyone have any idea what i could be missing. code ive tried as follows.... {down = 3522, up = 3522, cockpit_device_id = 8, value_down= 1, value_up = 0, name = _('Alternator 1 Toggle'), category = _('Electrical')}, Ive also tried adding a 1 to the up state in the diff.lua for this particular usb device. ["d3522pnilu3522cd8vd0vpnilvu1"] = { ["added"] = { [1] = { ["key"] = "JOY_BTN14", }, }, ["name"] = "Alternator 1 OFF", The battery Toggle performs as desired but the code is an icommand which is easy to add up and down statements to make them perform as needed. Any help would be appreciated.

I built my own out of pvc and plastic garden hose splice kit.

I haven't made a move to get into arduino yet. Everything I'm using in my pit is in my signature. I purchased a book on arduino but haven't gotten around to reading it yet. Not much of a programmer so the idea of trying to implement it even though it's sounds relatively easy isn't something I'm ready to get into quite yet. I did notice in your video there is a few small differences in my CDU as far as the labeling on the buttons and an on/off rotary on the bottom right of the screen. I wasn't to concerned about the on off rotary as it wouldn't apply to the A10 anyway. It does have the same 37 pin dsub connector on the back so as far as the alpha numeric keys, arrow keys and a few others the matrix pin out should apply to mine as well. What arduino board would you use in this case. MEGA perhaps? Thanks for the response and the addition to your thread. Hopefully I'll get motivated to add this to the pit someday soon

CDU I found a cdu just like that on ebay and was wondering how the hell I would get it working without having to build a new board. Is this picture you posted Han your own work?

More than 75% of you guys would rather fly a cargo helicopter full of rubber dog$$$$ outta Hong Kong?

+1 on that airdog!

As the title states I was successful in adding the Variable Sight Selector Unit (VSSU) as an axis by adding the line below in \Mods\aircraft\F-86\Input\F-86F\joystick\default.lua {action = device_commands.Button_23, cockpit_device_id = devices.A4_GUNSIGHT, name = _('Variable Sight Selector Unit - Rocket Depression Angle Selector - CW/Increase'), category = {_('Center Pedestal'), _('A-4 Sight')}}, The issue I am presented with is the reaction of the in game knob compared to the actual potentiometer movement doesn't coincide and has a very narrow field of adjustment close to the center of the axis range of motion. i bound the axis I'm using for the VSSU to the Wing Span axis and it works as it should ruling out a hardware issue. I've tried adjusting curves and x,y saturation to give a smooth transition of movement throughout the full range but cant seem to dial it in. I've looked in the clickabledata.lua to try to compare designed axis' to see if i can get the same results as the Wing Span, Bomb Wind Control, and other axis for example. What these share in code are not common Wing Span: elements["Wing_span_adjustment_knob"] = { class = {class_type.LEV}, hint = _("A-4 Sight Wing Span Adjustment Knob"), device = devices.A4_GUNSIGHT, action = {device_commands.Button_1}, arg = {716}, arg_value = {0.0215}, arg_lim = {{0,1}}, updatable = true, use_OBB = true, gain = {0.1}, cycle = false } Bomb Wind Correction: local Bomb_wind_control = default_axis (_("Bomb-Target Wind Control Knob") , devices.A4_GUNSIGHT, device_commands.Button_14, 727,0.0215, 0.6, false,false,false) Bomb_wind_control.arg_lim = {{-1,1}} elements["Bomb_wind_control"] = Bomb_wind_control Is the lack of the above syntax the cause of the VSSU axis not performing as desired?

i have edited the default.lua in Mods/aircraft/F-5E/Input/F-5E/joystick folder to accommodate the warthog switches for the Flaps lever, Flaps switch (on the throttle), Pitch and yaw damper switches (using the EAC and RDR ALTM switches) and the Missile cage switch (china hat forward) i removed the up statement from the Missile cage so that you dont have to hold it forward whilst trying to dogfight. i have made a few other edits to get toggles switches in my pit to perform as i wish but these listed should help those of you wanting to bind your warthog to a few things for the F-5. default.lua

DIY !!!!

ATIS not working Im having trouble getting the ATIS feature to work in DCS....some things on the configuration arent clear to me so i may be misinterpreting them... 1.) Is a license required for the ATIS feature to work? 2.) Is LotATC required and if so im only able to see it in Open Beta, open alpha doesnt have the option to enable it Any help would be appreciated....my squadron just play tested UniversRadio last night and we are all very impressed with this compared to Aries radio which had strange bugs. Adding the ATIS feature to our mission nights will add the additional icing on the cake. Im sure I speak from all of my squad mates that we would endorse UniversRadio along side your other happy customers. Thanks in advance

I modded my old TM RCS pedals with tow brakes and tied them and the rudder axis pot to a BU0836X card. Being that the rudder pedals had to plug into the TM Cougar to work when I'm using the TM Warthog forced my hand with that project. There is a lot of info online about pots and there is only three wires to connect. Just make sure you know which one is which or you'll send 5V to the wrong pin on the pot and fry it. The attached pics show the mods I've done but not the wiring for the rudder pot but you get the idea. For less than 100$ you can get your pedals operational and maybe learn some new stuff along the way.

I just purchased a second radio panel from pilot mall for about $145.00 after shipping. But it seems amazon and eBay are the greater sources of gouging.

I too have the same issue with the led readout. Every once in a while it comes on but most of the time it doesn't.

Cool mod for this cool mod On a youtube adventure today and stumbled across this mod for the radio and multi panel. a little steep on the price but adds a better set of encoders and a new board that adds the push button on the encoder as the act/stby button. http://www.motivemods.com/mobile/Product.aspx?ProductCode=MM-SA-RP

No problem man....im grateful that you took the time to add the commands in the first place.....just trying to get it to work in my sim pit.