whartsell

the source code is available here: https://code.google.com/p/hogkeys/source/browse?repo=iris&name=0.1.0.11+Release

thanks for the kind words..Its my pleasure to do things like this. If you have any comments on anything you would like to see changed lemme know. Did this software solve your Textures on HIGH problem?

Gremlin I have released the screen exported utility. I have named it Iris and it is located on my project page. https://code.google.com/p/hogkeys/ feel free to add it to your hosting page as well. Im not completly happy with the UI so I will entertain all suggestions and comments about any changes. If you have any questions let me know Iris Screen Exporter.pdf

Gremlin, I havent had the same problem with the Textures on HIGH causing any problems. I got an alpha release of the pic server program ready but just need to document it. The UI is not pretty as im not a ui guy but functional...once i get the features documented ill post it on my project site and give you a link so you can host it on your site as well. should have the docs ready tomorrow

Gremlin, I have been working on your screen exporter utility. I have it mostly re-factored and will have it ready for initial release either Friday or Monday.

Gremlin, I checked out your sample screen server code here at work and it appears to work great. Ill prolly do some tweaking this weekend or next week to make it a little more user friendly and share the results. If that is fine with you.

should just be a 10:1 reduction gear and you would be good to go

Im the one who is working on the pokeys integration. If there is much interest i could "accelerate" my plans on integrating with arduino based hardware. FYI you can breadboard up an Arduino compatible system for about $8 USD. I havent played with servos/steppers yet but do have the hardware laying around. I planed on getting to it when my cockpit is ready to use them. My plans call for common hardware broken up into functionality e.g. one for inputs one for outputs, one for servos,etc. I chose this ideology as it appears to be cheaper in the long run than using one microcontroller per panel. My HogKeys software should be able to transition over to arduino with little changes. All I need to do is add support for multiple devices and add a driver library to take my softwares model and convert it to something the arduino will understand and vice versa. That of course means I would have to spend some time writing firmware for the arduino. Again if there is much interest and if you know what your requirements are PM me.

These gauges look great. The only thing missing is the 10's needle on the temp and the 1s needle on the Rpm. I use those all the time to make sure the engines are in sync on TO and cruise

I diddnt notice that they made a short pedal. Wish they had a picture of that. By dealbreaker I mean that if im spending that kind of money there should be no compromises in what i want.

it also appears that the second set uses a gameport and not usb. At least thats what the article states but it is really old. Gameport is a deal breaker for me. I cant stand the looks of the first set. If they would change the pedals to look more like a commercial or combat jet i would be very happy

Hogkeys V1.2.0 is out includes support for up to 7 analog inputs. I plan on adding some extra hardware to allow up to 56 analog inputs in the near future. At this point im going to focus on bug fixes ,tidying up code, and documentation. then will most likely come enhanced analog input support and rotary encoders. That would cover all the basic features Then on to servos, multiple pokeys cards,and maybe arduino based hardware support

It's not difficult, it's just very flexible. The target GUI will do what most people need. The script editor will do the rest. It can even execute code based on conditions

I am VERY Interested in this :thumbup::thumbup::thumbup:

I would start with the Target UI. If you really want to unlock the power of the scripting language the script editor is the way to go. The GUI is very limited in what it can do. The WH advanced scripting is basically a subset of ANSI C so you could go through some basic c tutorials really just covering syntax and basic features then learn all the API calls they have in their library and you would be good to go. If you do not have any programming experience i would STRONGLY recomend you start with just the GUI

IMHO since they are still in "add features" phase you are likely to see more bugs for a while until they are feature complete. Once feature complete they will most likely turn most/all attention to fixing bugs. Typically in the current phase only major bugs and "low hanging fruit" will be addressed. This is drawn in my 13 years exp in software development. This is also why it's still a beta. If bugs bother you don't touch it until its near a release candidate.

Cold air is denser than warm air. So all thing being equal the ac will have more lift. Other factors to take into account are humidity, pressure, and weight. This is a short list

I experienced that as well

Military channel just had a show about 73 easting a few weaks ago...was interesting Especially the poor bradly unit that parked right next to a dugin t-72

Here are my profiles. the Mig29 profile will work for the su27/33 I havent had time to document them but if you open up the tmc files you will find your way These are to be loaded via the script editor..not the TARGET gui. as they make use of advanced features e.g short vs long hold. Also the different autopilot modes are using the ap switches on the warthog. for example PATH = follow waypoints, alt = altitude hold etc also the alt hold will be either barometric or radar depending on the position of the warthog rdr alt power switch. The idle detents will shut down the engines. the engine operating switches will start the engines as well. Profiles.zip

I have a 25t as well. Not as refined but ill doc and post that as well

I dont know if this is answered anywhere else but im interested in this question as well

I have created some target profiles for the the F-15,Mig29/Su-27/33. They were created using the advanced scripting editor and have support for TS3 and VAT. If your interested lemme know and i will document them and upload

in short the update wont be available till 2030-2100ish UTC also the updater only checks once a day...you can manually run it from the start menu to force a check see...http://forums.eagle.ru/showthread.php?p=1685448#post1685448

CCIP with CR it a perfectly valid procedure with CBUs. for one in CCIP-CR you don't need to be in a constant dive and two you can in allot of cases get ordinance on target faster as you don't have to designate anything just put the pipper on target and press-hold from there. no spi or targeting required ...just the good ole mk1 eyeball if you are using unguided CBUs as the poster mentioned, dropping them from high alt via ccrp can cause accuracy problems