wriley

I think if SAS is turned off it will cause this. There are probably other things on which the autopilot relies.

That is a good looking armament panel, great job snipes.

Nice. I would need the plastic cover for sure to keep from ruining the pages when my wife shot me after seeing the bill for a game manual... :D

I searched and didn't find anything about sessions timeouts. Is there any way to increase the session timeout for this site? I seem to have to login if I don't touch my computer for just a few minutes. Thanks

Some more work on the main panel design. I'm going to use my TM Cougar MFD's which are smaller than the real thing so the proportions look a little off.

Thanks for the reply. I have tried all combinations of settings on my Nvidia GTX 460 with no effect. Is there a more appropriate forum/method for HawgTouch support? I don't want to hijack this thread with my little problem.

First of all, thank you ClearDark for sharing this great program free of charge. I have a problem that I'm hoping you can help with. None of the gauges will show on my system, even using the supplied xml files. It appears to be some kind of z-buffer problem because I can briefly see the gauges when I click on the button for the tab. This is kind of hard to explain but I see a big solid color rectangle where the gauges should be. If I click repeatedly on the button for the gauge tab then I get kind of a shutter effect where the solid rectangle disappears for a split second and the gauges show through. They are working, I can see them moving as they should if I click fast enough. This is on Windows XP x64 edition. Any clues? TIA

+1 This is very confusing.

I think you are on the right track snipes. Looking at the silkscreen on the center PCB for the connector to the PCB on the left I see what looks like a controller port (P0.3) and button numbers (9,10,12). It might be worth checking if what I think are button numbers line up with what the joystick reports. Good luck.

Thanks for the work you put into this Tiger. I was wondering about maintaining state between the sim and your panel for the functions that toggle. Do you always set your panel a certain way before launching A-10?

A forum member asked for the dimensions I used for the AHCP so I'll post them here. Note that these are my own creation and may or may not reflect the actual panel in any way. :) The large holes are 1/2" and the small are 1/4". Adjust for your switches as needed.

Looking great Feed! I can't wait to get to this point with my CNC. :)

This is a great looking setup, thanks for sharing.

@Duckling: These panels are just "mockups" to flesh out my CAD design and test my software. My CNC is nearly complete, lacking only a speed controller to be able to mill plastic effectively (20,000 RPM + plastic = melted mess). The final panels will be fabricated/engraved by CNC to look like the CAD design.

Until I build something better I am using a custom joystick controller with 64 buttons. These buttons are wired to my toggle switches on the panel. I then assigned the buttons to commands as shown in this post. Since that time I have written my own software that reads the buttons, performs logic, and then sends commands via the network directly to the simulator (search this forum for "Export.lua" for discussions about this). If you are not up for writing your own software then you might take a look at products like Helios that are mentioned in this forum. Good luck!

Mockup #2, AHCP

I have started designing the main instrument panel. This will not be an exact replica as I am using the "good enough" principle and the measurements are all guesswork. My Thrustmaster MFDs are on backorder so I will wait until they arrive to start laying out that part of the panel. My software is also working nicely for interfacing. How cool is it to throw a real toggle and have the sim react? :thumbup:

Thanks!

I figured out the fix, just change line 155 c:setpeername(host, port) to this c:setsockname(host, port) and it works like a charm.

Looking good rocketeer!

The wiring is pretty straightforward for simple toggle switches. It will get more complex once I get to the panels with rotaries. There are a lot of great tutorials on the web for wiring controls don't be afraid to dive in and try it yourself. Right now I am just using the built in joystick button mapping but am working on my own software with logic that will interface via network with Export.lua. This will work around the limitations of the built in functions that do not have a set on/off state. For example on this panel the Battery Power function only appears to have a toggle control, you can't set it to off or on. This leads to cases where your physical switch position does not match the simulator state.

My build is starting off very humbly. I have one proof of concept panel built. The panel was designed in Google Sketchup and built using .125" plastic and a laser printed label. Eventually these will be cut using my home built CNC but I am still learning how to use that.

Thank you for sharing your script. I am unable to get any UDP to flow (checking with packet capture). Is there some trick to get the network part to work? Export appears to be enabled because I get logging from Export.lua. TIA.

Wow, thanks rocketeer. I had two toggles hooked up to Master and Gun and working in about 5 minutes (I stole the switch panel off of my C172 pit). This is awesome! Thank you ED for making life easier for pit builders! Here is my lua snippet that uses joystick buttons 41 and 42 from my controller: [260] = { ["combos"] = { [1] = { ["key"] = "JOY_BTN41", ["reformers"] = { }, -- end of ["reformers"] }, -- end of [1] }, -- end of ["combos"] ["name"] = "Master switch ARM/SAFE", ["category"] = "Armament HUD Control Panel", ["down"] = 1373, ["up"] = 1374, }, -- end of [260] [261] = { ["combos"] = { [1] = { ["key"] = "JOY_BTN42", ["reformers"] = { }, -- end of ["reformers"] }, -- end of [1] }, -- end of ["combos"] ["name"] = "GUN/PAC switch ARM/SAFE", ["category"] = "Armament HUD Control Panel", ["down"] = 1376, ["up"] = 1377, }, -- end of [261]

This is outstanding work. Thank you for sharing!