whartsell

Sorry to take so long to reply. The arduino firmware source code for EOS is available and you could adapt it to run on a Teensy if need be. The purpose of EOS is to not to have to use powerful (expensive) boards like Teensy,arduino,etc. the purpos of EOS will be based on simple ATMega based board that runs arduino bootloader and has specific features you would need for implementing your own panels. an EOS board is an arduino based design but an arduino board is not required (except as a bus controller if needed). For example you can buy all the parts to build a single EOS board for less than $20 dolars. this includes functionallity for 16 outputs/16 inputs 6 analog inputs and a few extra pins to do anything extra you need. You can customize these via firmware for more inputs/outputs rotary encoders etc. A single Bus Controller (arduino Leonardo) can control about 12 EOS boards via RS485 (imagine RS232 in a daisy chain) Eventually there will be EOS compatible boards for sale as well as the schematics and such.

I have been using Helios exclusively as well as Gadroc's EOS hardware/firmware. There are still some rough edges to take care of but so far it works great. Right now i build my own boards by hand but EOS compatible boards will be available in the near future ;)

If your going to be installing mods you should really checkout JSGME. It makes installing and removing mods so much easier

I have experienced something similar to this and the root cause was the plug on the stick grip was not properly seated to the connector on the base where it threads in. What i saw in windows was that the stick was detected but no axis or buttons were there. In TARGET the stick was also not detected nor in any game Try re-seating the stick grip to the base by taking it off and putting it back on

That is only the case with extreme overclocks..I run 4.6Ghz just fine with hyperthreading on (i have some sims that actually use it) on an I7-3770K

If you want a very precise but inexpensive stick check out the Thrustmaster T16000 Its less than 50 bucks and very precise. The buttons on it are average but it makes up for it with its precision. Talk to the aerobatic guys and you will see that alot of them use this stick (with a saitek throttle). If/when you outgrow it you will also have a great "backup" stick

Just saw the post and you beat me to it :)

is the control lock engaged? wonder if its bugged and the controls are still "working" kinda

I have a 3770K 8GB ram and SSD with two monitors running a total res 1920x2160. Going from a 6970 with 2gb vram to a 770GTX with 4gb ram doubled my low fps from in the low 20s to the mid-upper 40s with no settings change. My average (light object) fps went from 50s to the 90s. That was with no fps limit. I do limit the fps at 31 to remove any jitter in frame rate. this was not a scientific test. I have had my 770 for over a month and am very happy with it. It also made a nice difference in FSX as well ( i run that limited at 33) I wasnt concerned about max fps per say but am extremely happy with its consistency

After your EGI is aligned (CDU will have Nav ready flashing) select EGI on the NMSP on the lower part of the instrument panel ( the control stick blocks the view of the panel). Then you should see the TVV.

Saitek fit just fine. I'm using the combat pedals with dime bugs plans

Psyrixx...just a small issue (Im being anal retentive). In the description on the first post the UH-1H is not listed as a Player Controlled aircraft. You might want to add that as people might not read any further to realize it is actually included in the mission

Remember that the A-10s nosewheel is NOT on the centerline of the Aircraft. Its offset due to the GAU-8A

actually they make water cooled shirts and stuff for auto racing. My neighbor's 10yr old son has one for the TX summers when its over 100 degrees and he's sitting in the car in all his gear waiting for the lineup. Yea its crazy ...a 10 year old racing "mini" (Bandolero class) stock cars.

Vodka is standard ;)

TARGET advanced scrip programming is really the way to go VS the GUI. IMHO the GUI is useless and I have never used it. TARGET is basically ANSI C so if you know C syntax (not C++) all you need to learn is the TARGET framework. You can even do crazy stuff like load DLLs and execute external binaries from TARGET but I haven't tried it.

you can do this with TARGET straight from page 48 in the manual... In the DCS Flaming Cliffs 2 software, you cannot create your own chaff and flare program. T.A.R.G.E.T gives you the possibility of generating keystroke outputs. This is how we will create our custom chaff and flare program. We want to release 4 chaffs and 4 flares 400 milliseconds apart, and we will repeat this program every 4 seconds. We also want the ability to have this program looping automatically. We will use the Joystick HAT4 to manage the chaff and flares.  H4U will launch the program and loop it until I release the button.  H4D will launch the program to loop until I order a stop.  H4P will stop the Program. The interesting point here is that we will use the same program twice. So, rather than write it twice, we will create a function that contains our keystrokes. This way, we will only have to call up the function in H4U and H4D. For the program, we will use a CHAIN with delays to manage the keystroke outputs. The big difference here is that we will not associate this CHAIN with any MapKey. We will create a function called: Chaff_Flare_Program_1 Chaff_Flare_program_1 = CHAIN( PULSE+INS,D(400), PULSE+INS,D(400), PULSE+INS,D(400), PULSE+INS,D(400), PULSE+DEL,D(400), PULSE+DEL,D(400), PULSE+DEL,D(400), PULSE+DEL); Now that the program is ready, we need to associate it with our buttons. We want the function to loop, so we will use REXEC. The program uses 2800 milliseconds, then we want a break of 4 seconds (4000 milliseconds): we must REXECute our function every 4000+2800 = 6800 milliseconds. For H4U: MapKey(&Joystick, H4U, REXEC(0, 6800, "ActKey(KEYON+Chaff_Flare_program_1);")); For H4D: MapKey(&Joystick, H4D, REXEC(1, 6800, "ActKey(KEYON+Chaff_Flare_program_1);", RNOSTOP)); And to stop the automatic loop: MapKey(&Joystick, H4P, EXEC("StopAutoRepeat(0);")); Now, all we have to do is to declare our Function before the int main (): int Chaff_Flare_program_1; //we declare our new function You could even do some cool stuff like switch which program is run depending on position of unused switches...there is an autopilot example of this in the manual the mimicks the A-10C style autopilot modes/buttons for FC2(3). I have used both of these examples to make my own functions and they work great

Yeah I'm not shooting for a fresh from depot level finish

What paint did you use?

You could also use VAC and just use voice control. That's how I handle all keyboard related stuff in my pit. Don't want a keyboard in it.

Film have you ever been here They have a few airworthy Hinds and a MiG-23 that is undergoing certification for airshows. Located in Lancaster TX

It's not cheap but checkout Komodo

What stick do you fly with? Flim sells the hardware for a stick extension for the Warthog Hotas. I sell a curved shaft for his hardware. Together the Huey handles much better. Review of the extension here

Me too...will be getting one soon