Cezar11

has anyone used the I-pac chips? http://www.ultimarc.com/ipac1.html any feedback would be great.. limitations? 64bit o/s? etc... Thanks

it works fine in x64.. you need a 32bit O/S to program it.. but once that's done... you can take it anywhere... the x-key stuff is way too $$$... i'd build my own first with a couple 32 button usb game controllers..

I plan on using using it sideways on my right side.. I already have a good printout of the CDU keyboard and I plan on cutting out each letter to put on the keys. ( the keys have clear covers that come off so you can put whatever you want on the key ) the way i'm going to mount it, it will be a 6 row by 13 column keyboard.... should be very nice :)

http://www.geeks.com/details.asp?invtid=PKB-078-PB&cat=KYB just got one of these... it's cheap ( $49 ) but has 78 keys that can be programmed with either ascii or key codes .. and you can do macros also ( left ctrl key down, then press "a" ,left ctrl key up then press F5 etc..) I plan on making a cdu interface.. just thought i'd spread the word on this nifty little device.

absolutely... you won't get the "out of the box" functionality.. you'll have to manually remap everything.. I have a cougar and warthog hooked up right now ( I use the thrustmaster pedals.. they are hooked into the cougar ) but you can use any combination of stick and throttle you like.... windows sees all 4 of them..

didn't say it was pretty or efficient.. just a way around the limitation.. besides, vehicles should NOT be able to just happily jaunt through a forest. I understand about code..i'm a network engineer and used to write code myself, so I also understand about thinking outside the box. Obviously, the best answer is get a better engine that allows for these types of things, but that's not always possible or practical. Even if you ringed the forest area with tree shaded buildings just inside the perimeter and left the inside with the "not really there" trees, you would still fix the issue of line of site while allowing pathfinding of foot troops. to me it's a simple thing that you could do with existing tools while other options are being sought.

okay.. I guess I didn't realize just how beta this thing is... i'll be patient and wait :) i'm happy to support DCS

well... since buildings work as they should, why not make the forest simply groups of small buildings that have a tree skin and are arranged in a brick pattern. So it would be impossible for line of site and missiles/ammo to pass strait through without hitting something, but still give infantry pathfinding ability. you could also play with the density by leaving enough room for various sizes of vehicles to pathfind through. vehicles should not be able to pass through forests.. small thin woods, maybe depending on the vehicle... but even tanks can't just dive into thick woods without getting stuck.

I'm new to CA.. but not to DCS.. been flying blackshark since it came out and a-10 since beta. I hopped in CA for my first missions the other day and I may be missing something but do the tanks I command not know how to fire back? i've yet to see it. I have no idea how to actually give targets to anything ( i've RTFM'd to death ) and to top it off... ( this is what really gets me..) is the enemy can magically shoot through trees and forests. I tried to manually take control and flank some tanks on the other side of a forest, damn if there weren't AT-6 missles and HE tank rounds coming out of the trees to hit me. really?? ....if anyone has any documentation on gameplay and how you play.. not just what keys do what i'd be interested to read it. but i'm very frustrated

It's amazing what happens when you read the F'n manual!! LOL Thanks!

What's the deal with the airspeed, vsi and alt tapes on the hud??? I want!!

and skewering the probe while refueling is going to be a fun time....

Now everyone has to get another set of thrustmaster cougar mfd panels. Since the F-18 has 3 mfd's...lucky for me I ordered 2 sets.

Just finished the Warthog book... very very good read.. tells a lot about the ROA-10G ( you'll understand when you read the book ) And this is the A-10A.. how they overcame the lack of all the cool toys is amazing...

i've done it... don't care :) ... i'll reinstall anyway when beta 6 comes out.. so that'll wipe my scores out..

Right arrow + LCtrl = HOTAS TMS Right, just press it.. there is no long version of this button press....this is also assuming that you haven't remapped your keyboard :) Also.. there's no overt indication that you've created a markpoint, keep pressing it looking for some kind of signal and all you'll do is create a boatload of markpoints for the same spot.... ( page 454 in the manual ) here's the default keyboard map http://forums.eagle.ru/showpost.php?p=991796&postcount=2

Here's how I did mine.... materials were right in the basement.. took 20 mins or so to slap together. Nice thing is, my seat ( very comfy IKEA chair ) slides right under the stick and puts it more "in the crotch".. LOL simple plywood bottom.. 2 2x4's attached together and 3/8" plywood on top of that. then simply screw the WH onto that.

Here's mine... simple.. not quite finished. I'm putting together an opencockpit cards set up with the PC's on the left there

Here's how I did it. Had all the materials I needed right there in the basement. Took all of 15 minutes... plywood base.. 2 2x4's screwed to the plywood base then a piece of 3/8 plywood cut using the WH base as a template. Counter-sink the screw holes so the WH can be attached. very very stable and this design allow my chair to scoot up under the stick and put it more "in my crotch" LOL

I ordered the cards today... ( man.. $160 for a master and usb card + shipping ) but we'll see what's going on here :) the nice thing about the OC cards is you don't have to run them on the A-10 pc, so I can use a less than capable pc for that.. ( from what I've seen, the whole LUA thing can be run over the LAN.. please yell if i'm mistaken..) Feed, maybe you and I can support each other in this world, sharing little bits of info we find out from the forums... it's nice not to feel so all alone out here! :)

We're cool.... I do put a little too much emotion into emails and such... breaking rule no. 1 LOL :) It's just frustrating when you do exhaust what you think are the only avenues of information and still can't put it all together in your head.. I zipped up the entire scripts folder and subfolders and going to take them to work tomorrow... see if I can't put something together. I probably just need to order the cards and start building. thanks for your help again.. :)

I kinda resent the assumption that I didn't do any research. I hate asking these kinds of questions on the forums, for the exact reasoning displayed in your post, i'm not trying to be a dink here, but why would I make the magic leap that a-10 uses an incremental counter, when BS was very plain in its device numbering system? Furthermore, why would I make the assumption that I need the dofile statement? I get the clickable data file and all I was missing was the device number. I've searched for the last 2 weeks everyday for hours on this matter before I've asked. All I've been finding is the BS stuff.. which is obviously a little less than 99% similar to a-10 in its availability in the files. I appreciate the help, and I do take a great satisfaction in finding out how to do things myself, I just obviously don't have the time nor the aptitude for reverse engineering these files, however, I don't think that should stop those of us that don't from enjoying the extended functionality that this has to offer...

so.. gonna leave a brother confused on this ?

GIGABYTE GA-EP45-UD3P LGA 775 no problems with WH as of yet... ( fingers crossed.. knock on wood )

not sure I understand what this is.... in the listing there's this.. devices.UFC = { __index = { performClickableAction = function: 357CA260 SetCommand = function: 357CA218 the UFC is more than a single button... so where's the breakout for each button function?