Thirdup

Pulled onto my street after work just in time to see the UPS truck turning in from the other end. Perfect timing. The box was much smaller than I expected (my old CH-FFX and Pro Throttle from years back arrived in a container large enough to ship an entire computer system). Everything was neatly packed (small ps, pedals, throttle and stick each in a separate cardboard holder). The pedals are most impressive. Larger than CH gear but smaller than my old TM Elites (and *much* lighter than the Elites). They have a very sturdy feel to them. The rubber footing locked them down to my hardwood floor like they were bolted (which I actually had to do with my old Elites). They have some aggressive-looking little carpet hooks that retract and would obviously hold them well in place if needed. Rudder travel is extremely smooth with a easy-to-reach tension knob in the center (even maxed, they don't require near as much force as the Elites did). Toe brake travel is nice and deep. Gotta give the pedals a 10/10 right off the bat. Next came the throttle. About the same footprint as my Saitek X45 throttle, it also has a radial travel (unlike CH's straight forward/back movement). Ample controls on the thumb side are all within reach. The grip (an A-10 replica) is not as comfortable as the Saitek. It's a bit squared/box-like. It splits into two for multi-engine/prop/throttle configurations. The eight buttons on the front of the base have tri-colored LEDs (red/amber/green/off). There is a sheet of printable labels that can be inserted under the clear caps. I'm going to give the throttle a 7/10 until I figure out how to get the LEDs functioning with a mod that I've located. The stick is really sweet. My old CHFFX was a monster (both size and weight). The G940 is much smaller (again about the same footprint as the Saitek X45 stick). The grip is is narrow and not as tall as the CHFFX (which was a bit too tall for my hand). All the buttons are within tight reach. The upper hat is a mini-mouse and appears to be very sensitive. There are three trim wheels at the front of the base. The stick itself gets a 10/10. I had already installed the latest software from Logitech, so it was just a matter of plugging everything in. Rudders and throttle cables simply plug into the back of the stick. Power supply feeds the FF motors. USB to the PC powers the LEDs on the throttle. The controls all appeared under Windows7 64 without issue (shown as three separate controllers). Calibration was a breeze. Force effects can be adjusted to taste (or disabled). Each button provides a force sample (tug, roll, shake, vibrate, etc). The motors are much quieter than the circa 90's CH-FFX of the MSFFB. So far the force effects themselves get a 8/10 (and that may improve as I learn more about dialing it all in). The Logitech software allows you to program everything to your heart's desire. You can save each profile, associate it with a game, and launch a selected game from within the Logitech program. I fired up ArmA2 and went to options. The G940 was present three times (stick/throttle/rudder). I cleared all the default settings in options>controls and plugged in my own. Started the mission editor with an A-10 and away I went. Much to my surprise, ArmA2 does in fact support the basic force feedback flight effects (although any effect from weapons firing appears to be absent, I'll have to look into that). Control is fluid and *very* precise (I've never flown with a stick this precise, actually). I can't wait to get some flight time logged with it. At first glance I'm giving it a 8.75/10 overall. I've missed force feedback for far too long....

That's one of Richiespeed13's videos. He's a forum member (and official "pied piper" of ArmA2 thanks to his videos). Send him a PM and ask about the mission (Richiespeed13). He's a great guy and I bet he'll point you in the right direction.

http://forums.bistudio.com/showthread.php?t=98650

Try just pasting in the part of the YouTube link after the "=" (in you case "rw-FocEP3Fo") and they placing the forum YouTube tags on either side

I use Creative Fatal1ty HS1000 headset and surround works great.

Complied pbo and launched on dedicated server. Helo and crew present. Call Medevac present and functioning All radio text appears to be functioning *No audio (nine-line, etc) Abort option present until smoke Abort functioning and medevac resetting Smoke functioning *Smoke duplicated if call/abort/recall Helo arrived and team disembarked *Helo still warping/teleporting between 5 and ~50 feet *Cannot board helo RTB radio call present and functioning Helo RTBs *Cannot test reinsert (cannot board warping helo) Did not test with second player, yet. Looks like you're getting very close to all "working as intended". Issues: No radio sound fx Helo hover/warp Might want to look into a way to delete smoke shell from inventory if aborted

As with most threads like this: More options = GOOD for more play styles Trying to force everyone else to play the way I feel is more realistic = BAD I don't have a horse in this particular race, but anytime someone suggests removing features from everyone in the name of realism it's something I'm opposed to it. Optionally (as a server rule), sure I'd support changes like this. More options is always a good thing. If you really want total realism, keep a loaded 45 next to the monitor. When you get shot in-game, you'll know what must be done. Just don't expect everyone else to share your level of enthusiasm. ;)

OK, this was why I didn't have the call_action for atillery. Equiped the PRC radio pack and it appeared. I searched the ACE2 thread, the ACE2 wiki, and Google and never once could I find any mention of exactly how to call atrillery in ACE2. The closest I found was some obscure 10-month-old ACE dev post on a possilbe interfaces they might use when released. /sigh I don't play ACE much. If I did I guess I'd learn these things. But not being able to find answers to this sort of thing is why I don't play ACE much. Thanks Mr. Charles. edit: btw has anyone tried to call in flares in Domi2 w/ACE2? I get the radio traffic from arti but the salvos never appear.

Making it a server-side option for admins to turn on/off.

I don't see a problem with making it a server-side setting (on/off). I personally can't say that I find it "killing everything" about the game. I think that will largely depend on the type of play. My squad plays coop against AI. I've never gotten in the habit of using the spacebar and see no reason to ever use it (I like having to use my eyes). And I could care less if my squadmates use it. So to me, it's a non-issue. But as I said, I could see where it would be a good server-side control for those admins who want more reality. So my vote would be for a selection not offered in your poll. I certainly don't want BI to remove the feature (I'm certain some people depend on it to play). I seem to recall that disabling spacebar is an ACE2 feature. Like I said, I never use it so I wouldn't know.

OK. I LOL'ed

Here's a REALLY good way to actually view how/when/where/and for how long the AI sees a player. http://forums.bistudio.com/showpost.php?p=1525272

Let me check it. ---------- Post added at 03:09 PM ---------- Previous post was at 02:44 PM ---------- Neg. The "Abort Medevac" is present but not fucntioning on the dedicated server. Confirmed with three passes. I'm headed out for a bit but will check back in when I return.

All radio chatter (voices) are present. Both to-and-from helo. The only text I see is my character transmitting "Smoke Grenade Out" at marking LZ. Also getting notice when corpsman joins team ("Four follow one"). Did another pass to test: Helo and crew present. Call Medevac present and functioning Abort option present until smoke Smoke functioning Helo arrived and team disembarked Can board helo *Again, no radio call to RTB available. Stuck at that point. *also noticed that the coprsman/crew can get stuck trying to cross under hovering helo. Corpsman would not re-board when ordered. I *think* this is related to the hover/holding patern itself.

Tested in editor and all appears to function as intended. Compiled .pbo and placed on dedicated server. First Pass: Helo and crew present. Call Medevac present and functioning Abort option present until smoke Smoke functioning Helo arrived and team disembarked *Helo kept teleporting between 5 and ~50 feet *No option to board or abort. Stuck at that point (my guess is that it just glitched in the hover and was out of range to get the boarding option. We've seen this before in early testing.) Second Pass: Appeared to function normally. Boarded helo. *No radio call to RTB available. Stuck at that point. Third Pass: Appeared to function normally. Boarded helo. *No radio call to RTB available. Again, stuck. I'll have another go at it during lunch. * Did NOT test with another player yet

Same here. Looked thru the code and don't see where it's disabled anywhere obvious.

Is artillery disabled in the ACE version? I'm not seeing any call action menu (on any of the slots).

Sure thing. Link it.

According to Fortan's documentaion, yes.

Sure it's possible and it's been done. Fortran's F-117 for ArmA2 is "stealth" (unless the gear are down). http://forums.bistudio.com/showthread.php?t=83459

Thanks for all the hard work, Xeno. Hope your wife fully recovers quickly.

It's still under development. The module itself currently does not work in MP. I'm sure Goliath will work on it some more when he gets the time.

Yep. SWO-YWsyYpA

I came to gaming from flight sims. Plus I've used force feedback rigs before. I still give the G940 very high scores with regards to flight sims. I currently fly IL-2, Blackshark, FSX, and of course in ArmA2. It's a nice HOTAS rig even given the price (when you factor in the FFX and the pedals). My only minor complaint is the lack of detents in the rotories. I'd like to try out the X-65. To be clear, it's not a "force feedback" rig but rather "force sensing" (meaning it has no moving parts and measures the forces asseted onto it). It would take some getting used to but I imagine it's very well suited for modern aviation sims. I also like Saitek throttles. But metal sticks seem to cause me a bit more fatigue after several hours (I flew with a TM Cougar for a few weeks). TM's Warthog will be out soon. If you're shopping for a new HOTAS, you may want to wait on the reviews for that bad-boy. Of course, it will be metal, expensive (ie: Cougar), and like the Saitek it won't include rudder pedals nor be force feedback. http://www.thrustmaster.com/ ---------- Post added at 06:52 PM ---------- Previous post was at 06:46 PM ---------- btw: here's an interesting little overview of some of the current HOTAS rigs. It deals mostly with the software side. http://www.simhq.com/_technology2/technology_094a.html

I'll test a few things this afternoon and tonight. I'm not using analog. When it first came out I wasn't really happy with it (I've heard that it was "sort of" fixed in 1.05, but I've not even tried it since then). I'll tinker with it a bit and see. Keeping in mind that flight models do have some variance, I don't spend much time flying the LOACH. I'm mostly in the Apache these days but yes, I can hold a sustained hover at just about any alt. ---------- Post added at 01:17 PM ---------- Previous post was at 01:15 PM ---------- Ah, good to see you sorted it out. Yeah, I've avoided the analog in ArmA2 (although I'd love to use it if it worked properly).