DudleyAz

Outstanding! I look forward to your Helios profiles almost as much as the sim itself!

I would love to find a source for Hall effect sensors to replace the pots in my old Cougar! I just tried doing it with a Honeywell HRS100WAB090 and I couldn't get the thing to register any output. I have reached out to Honeywell about it but haven't heard back yet. Anyone have any sources or ideas? I really don't want to try building my own with a Hall sensor and some magnets, I would rather just have a drop in Hall pot... Anyone? :)

In the current DCS World it would be the AH-64D. If they would get a bit more detailed at low level and incorporate more of an infantry vibe - aka ARMA 3ish, then hands down it would be the MH-6!

Deacon, You are doing a great job, especially when you consider it's your first pit. I wish my first one would have turned out that well! I reference to your question about which physical switches to put into the pit, I would recommend having all of the ones you would use in flight. Ones that are only used during start up - shut down - ground operations are easily done via Helios. This should cut down on the number of physical switches you need to contend with. In my current pit I went the other direction and put in about 70% of the switches needed to fly any one of several aircraft/sims. Now I have a BUNCH of switches, which required a BUNCH of wiring, and I don't use most of them very often, if at all. Being that you have the panel space, you can always add a switch or two later if you find that it would be more handy to have it as a real switch.At least that's my experience anyway. Keep up the good work! Dud http://cnadeau.webs.com/simpitasitsitstoday.htm

I just took the plunge and spent the better part of a day overclocking the pc that runs my simpit. The only problem is I'm not seeing any improvement in my frame rates. :mad: I've had the PC for a couple of years, and took an initial try at overclocking when I first built it, but didn't have much luck so I've been running it stock. I've been wanting to get some higher frame rates in DCS A-10C, so I found this excellent walkthrough online about overclocking by Miahallen, and I was successful with the overclock, but I'm not seeing any impact in the sim. 34fps before AND after the OC. I don't get it?? With everything else being the same, seeing a 30%+ OC to the CPU, a 10% OC to memory, and a 10% OC to the GPU, you would think I would see at least a few frames higher performance wouldn't you? :helpsmilie: So I have a few specific questions: 1. Could there be another bottleneck somewhere in the system that would be keeping the frame rates down? If so, how do I address it? 2. On the overclocked video cards: I noticed that the Catalyst Control Center Overdrive Panel (where I did the overclocking) says that "The GPU clock settings will only be effective when the GPU is running in high performance mode". I am assuming that this kicks in automatically when the GPU is under load because testing using GPUz does report back that it operates at the overclock settings during the testing. Is there a way to manually set the GPU to use the OC settings all the time just to be sure? So here are the specs and details of what I've got and what I've done. All input is welcome, not just for me but for anyone else who may struggle with system performance issues (almost sounds like an ad for those little blue pills huh? ). Thanks, Dud PC Mobo: Gigabyte GA-EX58-UD3R CPU: Intel Core i7 920 Bloomfield 2.66 Ghz - overclocked now to 3.6Ghz CPU Cooler: Xigmatek Dark Knight S1283v Memory: 12Gb (3x4Gb) of G Skill DDR3-1333 PC3-10666 (7-7-7-21 1.5v) overclocked to 1440 PSU: Rosewill RX-950 950watt GPU1: XFX/Radeon HD 5830 1Gb overclocked to 900Mhz core & 1300Mhz memory driving 3x Benq E2400HD displays, each at 1920x1080 for 5760x1080 triple screen GPU2: ATI/Radeon HD 4800 1Gb overclocked to 950Mhz core & 1350Mhz memory driving an HP L2105tm touch screen at 1920x1080 Sound: Soundblaster XFI SB0880 HD: 2ea Western Digital Caviar WD6400AAK 640Gb OS: Win7 Pro 64bit SP1 Build 7601 Sim Settings DCS A-10C (34 fps using Quick Start-Easy-Spring mission as benchmark) Same results before and after OC All patches and updates are current Textures: low Scenes: low Civ Traffic: off Water: low Visibility Range: med Heat blur: off Shadows: low Resolution: 5760x1080 Aspect Ratio: 5.3333 Res of Cockpit Displays: 1024 MSAA: 2x HDR: off Clutter/bushes: 0m Trees visibility: 5021m Preload radius: 63011m Disable Aero Interface: unchecked Tree Shadows: unchecked Vsync: unchecked Full Screen: unchecked Cockpit Shadows: unchecked TSAA: unchecked Sorry for the length of the post, but I always see everyone asking for details to troubleshoot issues like this.

A quick update. I spent some time yesterday going through and trying all of the combinations of checking/unchecking the "Disable Aero Theme" and "Full Screen" options. I was having the same problems across the board... until I went back to the original state of having both of them unchecked. All of a sudden everything worked perfectly! :thumbup: This is how I had started out the day and it was not working correctly. So the only thing I can think is that somehow, somewhere there was an entry in a lua file that was conflicting, and after going through all of the checking and unchecking those two options, it finally registered?? Anyway, it seems the problem is resolved, and I was able to successfully complete three flights with working VAC, exported MFDs, and no Windows 'bonking' in the background... life is good! :pilotfly: Now if only I could get my copy of DCS AH-64D to install correctly.. oh wait... that's just a dream... maybe one day! Thanks to all you replied and gave me input. Dud

Okay gang, I need some help please! Since installing DCS World and the accompanying A-10 patch I have been experiencing an odd issue. It seems that while in game all key commands are being registered by the game AND by the Windows desktop simultaneously? My first clue that this was happening was when I pressed some keys I would hear the Win 7 input error 'boink'. Most, but not all of the commands still work in the game, but they are also being recognized by Windows and if it has an existing Windows function, they are executing commands there as well, which are causing issues because it is shutting off some apps I have running in the background like VAC, or occastionally jumping me all the way back to the desktop. I can resolve the issue by running in 'full screen' mode, but then my exports to Helios for my MFD's don't work anymore. I had none of these issues when running A-10 prior to the DCS World updates. All of my other things are working fine like my triple screen .lua, my keyboard mapping .lua, etc, and I can tell that the keystrokes are being sent, it's just that it is also registering out of game. I have reached the end of my knowledge and ability, so any help would be greatly appreciated. In game I am using: TM Warthog stock, VAC for voice control of AI Wingman, etc, Helios for touch screen control, Track IR5, Win 7 Pro 64 with all updates, Eyefinity triple screen plus a 4th screen (touch screen). Thanks, Dud P.S. I am also posting this on the SimHQ forums. (shotgun approach)

Problem solved. I'm still not sure exactly what the problem was though. Over a period of two days I started getting more and more previously working commands failing, and then I all of a sudden the game wouldn't load at all. So, based on Widowmakers advice (Thanks bud!), I completely deleted the entire Warthog file out of the Saved Games folder, and reloaded the game. Everything booted right up no problems. The down side is that I had to completely rebuild my keyboard profile, because if I copied back in a backup copy of the old one, I started seeing problems again. Thankfully, I had written down all of the key commands, and everything is good to go, including the seat arming switch! I think that somewhere along the way way back when I had corrupted one of the .lua files and it just took a while to show up. Thanks to all who helped out! Dud

Thanks Tulsa... I was able to successfully bind both the left and right switches via Helios. However, the mappings through the options/control page in the program itself still aren't working correctly. So that means I can't tie them into a physical switch via my Hagstrom. I guess my next step if I don't get anymore ideas is to try and map all other controls and then see what actually adjusts the switch settings... just lots of trial and error...

Tried it this weekend... same result. Maybe DCS has them mismapped in the Options screen??

Okay gang, I need a little help please. I've spent the past several hours trying to figure this one out and haven't had any luck. I have been setting up my first batch of switches in my pit to work with A-10. I have had great success except for the last two items... the Seat Arming command and the commands for actually turning on the MFD's. As I did with all of the other switches/commands, I went into the options screen in A-10 and assigned those items unique key commands. As I always do, after setting a new command in Options, I load a ramp start mission and see if it works. This is where it gets interesting. The command string I have set to arm the seat is actually turning the RIGHT MFD from off to Night illumination. The command string for setting the RIGHT MFD to Day illumination is changing the LEFT MFD to Day illumination. The command for turning the RIGHT MFD off does nothing. Same goes for all of the commands for turning on/off the LEFT MFD, and nothing seems to work for adjusting the seat arming handle. This is seen when using the commands directly from the keyboard or via the Hagstrom KEUSB108 I use to control my cockpit switches (the KEUSB108 is AWESOME btw!). All of these items still work on screen in the clickable cockpit using the mouse, but the key commands are jacked up.. and only for these items. I have everything else working just fine via key commands. I started with these command strings: Seat Arming: E+RCTL R MFD Day: M+RCTL+RALT+RWIN R MFD Night: M+RALT+RSHF R MFD Off: M+RCTL+RALT I thought maybe the command strings were two complicated for some reason, so I found some very simple ones available and tried using those for key commands with the exact same results: Seat Arming: O R MFD Day: R+RSHF R MFD Night: Y R MFD Off: E Any thoughts? Anyone have these items working via key commands? I refuse to let the computer win the fight... Thanks, Dud

An iPad app would be perfect! But until then, I'll just install it on the desktop and only use ME. Thanks for the input! Dud

I am lucky enough to have a home cockpit to fly in. :joystick: While it is awsome for 'yanking and banking', it isn't the best for long periods of normal mouse/keyboard type work, like spending hours in the mission editor developing custom missions. Is there any way to install just the mission editor on my second PC.. which is on the other side of the house... without violating the '1 license per PC' agreement? I have thought about installing the open beta version on my desktop and using the ME from that, but have there been a bunch of upgrades to the ME now that we are on .09 that would make this impractical? Any input is greatly appreciated. Dud

w7 pro 64bit

:helpsmilie: I am in desperate need of some help. I am trying to fly BS with my Cougar HOTAS joystick/throttle, and CH Pro Pedals. It seems that regardless of what I do in the Options panel, the game is reading all of my input devices axis and is inputing them to the three primary axis regardless of how I set it up in the options page, collective up/dn, cyclic fwd/bk, cyclic l/r. Let me elaborate: :joystick: Cougar joystick is assigned to cyclic l/r (axis x) and cyclic f/b (axis y) Cougar throttle is assigned to collective u/d (axis z) CH Pro pedals are assigned to rudder l/r (axis z) The problem is, if I move the rudder pedals, in the game it is effecting the collective, not the rudder. If I move the Cougar throttle, it tries to move the collective, but it stutters and stammers because it is also seeing the rudder pedal input (the pedals self center, so it keeps conflicting the inputs. The same happens for the x/y on the pedals (toe brakes normally). It is effecting the cyclic l/r and fwd/bk. Even if I clear the CH products assignment, if I touch the pedals in the game, I get collective z axis input, and there seems to be no way to get rudder input from anything. Regardless of device or assingment, all devices on my computer with an x/y/z axis ability, whether mapped/assigned or not, effect the two cyclic and collective axis. I do not have this problem in any other sim using these same controls. This happens irregardless of which controls are plugged in to the pc. (if I unplug the ch products, and map the hat switch x axis on my Saitek pc dash (p-8000) to rudder, it still effects cyclic l/r). I have rebooted the pc several times, along with recalibrating all of the various controllers. I have also noted that irregardless of which way I map the Cougar throttle (regular or inverted), it still wants to apply the axis the same way, similar to airplane mode. I normally fly helos reversed, where max collective is all the way 'back', which would normally be idle in an airplane. I think this is related to the problem, but not sure how. HELP! Dudley :mad:

Outstanding checklist SDeath! Just saved me hours of building one myself. Now if I could just get the ground crew to bring me coffee..... :)