Guess Who

No, the Warthog doesn't twist.

This. But don't forget a set of rudder pedals. This Warthog comes without pedals.

No, it's really not! Driving ain't fun anymore ...

Not supposedly. There is a statement by Suma and a long and heated discussion in the multiplayer forum. ASR_AI has to init every infntry unit on the map, spawned or pre placed. I don't know enough about scripting to determine init times for that to run. What I do know is that the menu for disabeling the rearm feature which comes with ASR_AI sometimes takes longer than 30 seconds after mission start to show up. I guess only Robalo can clearify that. @ seba: I usually set skills between 1.0 and 0.9 in the options. Works great with ASR_AI.

Seba, your post suggested it would be kind of systematic. I just stated I had not experienced such a thing like "first shot is always a kill/hit". I play a lot and mostly with ASR_AI in SP and if there would be some sort of systematic glitch I think I would have noticed. Yes, init takes a while after mission start. I would suggest to run the test mision with a delay of, let's say, at least 120 seconds. Maybe someone can script in some sort of marker that kicks in when a units init is done, just to be sure that the skills are set before you fire the first shot?

The inherent problem with systems like in Raven Shield is, you cannot aim while you're adjusting your stance. That is/was bad design.

I'd say your problem is more with the time after spawning than with the mod in general. The skill settings are applied after spawning, so dependant of the amount of units you're spawning and the amount of other scripts running at mission start, the skill may kick in a little to late for your test. Do you get the same results when running the test scenario for a couple of minutes before testing the results? I've been using this mod since forever but never experienced first shot first kill events in regular missions that much.

I feel your pain ... :) No, that's actually the stick/collective messing up your fine adjustment. Not that TKOH flight model was easy to fly or hover ... Those "mods" with custom controllers are far beyond my enthusiasm as well. What this stick needs is a coder that ripps that damn' firmware apart and get's rid of that BS of hysteresis. The rest is would be an easy fix. I don't fly at all at the moment. While I'm some sort of sim head since Falcon 3.0 (was that in the eighties or the nineties?) I gave up on the most flight sims, the last one beeing Falcon BMS just recently. Too much hassle to less fun; maybe I'm getting old ... But I will repair the wiring in the throttle and start again with Take On. Apart from being a kind of preparation for ArmA III I do like Take On a lot. It's lots of fun just flying around and practising stuff. Prior to the G940 I used an MS Sidewinger FF 2 for things like ArmA or space sims for more than a decade. But it was getting old and for a helo sim you would want a good collective an pedals. That's why I bought the G940. But the Sidewinder still feels better in Take On ...

Have you read about the reversing bug on the Logitaech forums or at SimHQ? It#s quite prominent in TKOH when you have the virtual hud enabled. You can test it on the ground: When you pull collective and then reverse the motion at any point the gauge won't follow for a moment and then jump quite a distance to catch up with the actual position of the collective. That's why you can't do fine adjustments around a specific point; the collective will not react at all or will jump for quite an amount which leads to over correction. The hysteresis adjustment is supposed to lessen the effect, meaning the amount of pot travel (input value) the firmware needs to give out new values (output value) to the software. The source of evil is the firmware. It was a design decision to suppress spiking of the pots, which leads to the conclusion that Logitech uses sub par hardware on this set ... with the latest firmware they reduced the hysteresis for the stick to marginal (not zero!), which makes sense, because there are no pots on the stick; it's hall sensors. What were they thinking? They stated somewhere on their forums, that there will not be anymore attempts to fix this "bug" which for me and many others equals denial of support. Apart from the infamous reversing bug their are many others. My collective for instance needs a complete rewiring because the thumb pots spike when you move the collective, the mode switch looses it completely or changes it's value when you move the collective and so on. And that's from day 3. But I don't wanna bore you with my problems with this set. Just wanted to state that it's seriously overprized and not very usefull for helo sims because of construction details and questionable handy work. BTW: SimHQ has a large discussion about this. There are also some examples of collective rewiring and other attempts to make things better.

Caught my attention at least :) I fly the same stick. But I use it without any centering spring, totally loose. That way you can do smaller corrections a lot faster and over time you'll learn to "feel" the helo. Anyway make sure you have the latest driver, the latest firmware, and set the hysteresis adjustment to minimum. That's for the stick; the bad news is, there is no way to tone down the hysteresis enough for the collective, which leads to problems with fine adjustments durig landing and hover. That is just bad design by Logitech (the infamous reversing bug) and the reason I wouldn't advice anyone to buy the G940 for Take On.

Hey Grub, there are three or four (map-) preplaced H's on that airstrip. They don't appear in the map view in the editor. They are west of those buildings where you placed your helos ...

I strongly disagree. Preorder as a prerequisite would exclude a lot of people who want to help but don't buy online. Different idea: BIS will need a bug tracker for alpha and beta tests. Just like CIT at dev-heaven. What ever the bug tracker will be, make it the obstacle to get access to the test builds (just like Kju suggested), make the people register/go through the bug tracker. No one who is willing to help will be excluded that way.

Very nice Idea. Thanx for sharing Wolffy.

I'd say it is everything but subtle when it "kicks" in ... just try to make a hard turn and you'll notice.

I tested the new driving today, and I think the look up/look down has to go. Even without TrackIR I don't have control over the car. Additonally I would prefer if the "look into the turn" feature would be more continious and didn't jump in so suddenly. Feels like a dead zone and I don't like dead zones at all ... :) SMAA looks pretty good at PPAA_Level = 2 doesn't have any performance hit on my rig. So thanx for this.

Hey, come on guys, I like polished products as much as any one else. I did never state otherwise. But ArmA get's better over time, we all know that, and I actually believe I'm not alone. And I would miss something if it was different. What I really wanted to convey is, that I'm confident that ArmA III will be the best iteration of the RV engine to date because of the circumstances of it's development. Every little bit of improvement that is done in the beta program and the coming full patches will more or less directly lead to it. So it really doesn't matter much if it is postponed for six or twelve month. BIS get's more time for "polishing" and we all have the chance to assist and influence the outcome. Where else would you have that opportunity?

As written earlier, Manhattan didn't have any showstopper for me. Version 1.0.1 wa actually worse. And who the hell would give a dime for german game magazines. They have proven time and again that they are cheap. I'm with Sickboy here. Ice, you should know you can't make software bugfree; that would be a paradoxon. And most other developers wouldn't even consider 899 of the 900 bugs you mention as bugs; even less they would consider to fix. I know you're complaining about the skill/precision feature. The decision to remove the possiblilty to tweak it was a little short sighted. But there are still ways around it. Maybe I am just more confident because I am used to tweak little things to my liking since OFP. That works all the time, especially in ArmA. It's just not for everyone, just like ArmA.

I totally agree with that statement. Not that I thought ArmA II so buggy at all at release date, cause I played the whole campaign thru with that version and had not much problems at all. The major difference between Arma II / OA release I see in the beta program that started post OA release. ArmA is just going to be really great, playable, performant and feature rich. And all of those improvements will without a doubt transfer to Arma III. And BIS is listening to the community; they've proven it time and again. And they won't stop making ArmA:OA better just now. Conclusion: ArmA III will be released when it is ready and it will be awesome. Be it Q4/2012 or Q2/2013. Doesn't really matter ...

Yeah it's very nice now. And all the lag is gone. I still miss the navigation path at the bottom of a thread/subforum. Would be nice to have those back ... :)

@ Ten Bensons If you get problems with the vanilla install because of the uninstaller (it sometimes deletes original pbos in the vanilla install) try to reapply the 1.60 full patch first and retest before you re-install the whole game ... That should normally get rid of most problems. ---------- Post added at 06:49 PM ---------- Previous post was at 06:45 PM ---------- Jedra, did you try to set collective to the right throttle and thrust to the left? With different orientation of the axis? Have to fix my throttle wiring before I can test that setup ... Edit: Oops, I guess that's TKOH ... :confused:

Don't ever "uninstall" the beta. The uninstaller is messy ... just delete the "beta" folder in "\Arma2\expansion\" like any other mod.

The new colors are much better. You're definitly getting there ... :) Another thing: the additional windows (like "posting rules" etc.) as well as the all new separated "sticky posts" windows don't stick when you close them. Coming back from a thread shows them all open again.

There is this tiny little HOME button which looks like a black house top left ... :)

The new style is kind of okish. What is bugging me most is the new forum is laggy. I miss the smoothness of the old vB 3.8 version. And the navigation at the bottom of the thread is missing; means a lot of scrolling. Edit: Seems, when I click the "Compatibility Button" on IE9's adress line, the forum gets a little faster/smoother. Maybe vB4 is a little too old for IE9? :butbut:

The Stryker has Commander/Gunner on turret, driver and commander both have TV only with the hatch closed and both have Day-TV, NV and FLIR on their optics. So both can "see thru bushes". ;)