Guess Who

It's more like OS reminding you it has not enough "virtual memory" left. Let Windows determine the size of your pagefile and you're probably good to go. And btw: Welcome to the forums.

Yes, I guess you are right in all accounts. I'm getting old and memory is failing already ... :) The thing that bugs me the most thou is that damn awfull dead zone you have in the y-axis in the old style driving and in both directions in the new way. There is no visual feedback, that's why it fails so hard. If the dead zone would be eliminated it would'nt be that hard. In ArmA I dont't drive to work but mostly under combat conditions. There is no time to focus on not moving your mouse in the y-axis.

If I remember correctly: old style driving since OFP/Arma I was vehicle controls -> (wasd as usual) plus mouse left - drive left (=A) and mouse left - drive right (=D). Introduced in ArmA II, somewhere in the middle between the patches, was the additional key combo you are used to: drive more right/drive more left. The new "freelook UP/DOWN" feature was introduced after the new steering method with that caret thingy with the automatic "look into the turn!" feature for both steering methods, which I think is wrong. Maybe BIS could have left that old style alone and introduced the changes only to the new style. I would not have complained cause that would have been kinda optional. I didn't try beta 94444 yet but up to 94364 my view would go up/down when moving the mouse; and since I use a 5600 dpi mouse it's obvious what is happening: I tend to look everywhere but the road. That's annoying as hell ... :) You should try someday. ---------- Post added at 04:42 PM ---------- Previous post was at 04:37 PM ---------- Nope, that's what you think is the best way of driving. I dont't use third person at all, so no option for me. I was pretty happy with the way it was since ArmA. And that is my opinion.

So it's kinda fixed for the "wrong" crowd and stays for those who use the "standard/old fashioned" method ... :confused:

From your post I would assume that you do the driving different from me. You do use the "more left/more right" settings, don't you? Because in the regular "drive left/right" with mouse configuration I'm used to since ArmA nothing has changed in the last betas at all. And that is the fact I'm complaining about. This should be reverted. BTW: New beta 94444 is out now ...

No, it's far from good to go. It needs an option to be disabled. SoonTM.

Yep. I don't drive anymore, since I don't have 3rd person enabled. I just get drunk and walk across Cherna alot... FPDR

Actually it's a pain to drive _anything_ with that looking up/down _feature_ ...

Rob, after playing warfare for a while, I get heavy lag and the rpt gets spammed with the following script error: Error in expression < { if (!canStand _thisunit) then { if (!isNil (_thisunit getVariable "asr_nolegs> Error position: <isNil (_thisunit getVariable "asr_nolegs> Error Generic error in expression File x\asr_ai\addons\sys_aiskill\fnc_AINet_pf.sqf, line 70 Beta is 94364, but gettin' it also in 94103, version is 1.15.1. Join_loner and Split_legs are disabled. Happens at approximately 1 hour playtime. Is that fixed in the newest test version? Anyway, gonna post this in your bug tracker.

This was a false positive. Performance breakdown was caused by a script goin' nuts after a while; just happened to kick in earlier in the latest beta. I just retested with 94364 and everything is back to normal. Sorry guys ...

I like to confirm massive performance drops in this beta. After playing roughly an hour fps dropped to 50 percent never coming back up again even when restarting ArmA. Mission is Warfare on Chernarus, fps dropped from around 30 to 15 - 13. Additionally there is alot of script lag and scripts start to produce a lot of errors in the rpt. Overall performance is worse in this beta as well by roughly 10 to 20 percent. After rolling back to beta 94103 and reloading the save game the same scene came up with over 30 fps and stayed there.

Maybe you could look for the Warfare Module placed or spawned in a mission? I know Benny's Edition is based on BIS warfare but I don't know how much rewrite he actually did.

Amen! Would be an instant deal for me ...

Well, it kinda does. But that's not the point. The point is, you should welcome every fix the engine gets, no matter what kind of creature triggered that new enthusiasm BIS shows for fixes right now. I'm just tired of the constant whining about DayZ did this and DayZ did that. And the discussion should stops here and now for me; this ain't a smalltalk.

So by your statement DayZ players are not a part of the community? Interesting point of view ...

Well, I can help for a turn. In Warfare there is a fixed squad structure; you normally get 8 squads per side, even ai lead squads. When the squad leader gets killed, the next numerical unit in the squad takes over because there is no rank system. When a squad loses all men but one he will be a squad leader and a loner. That's where disaster strikes. When he joins another squad because of your feature his original squad gets annihilated. You can watch that in the teams menu on the map; the entry for that squad will turn to gibberish. Warfare is designed to spawn a new squad at base whenever an ai squad is wiped out or that, under specific conditions, the remaining members of a squad return to base for reinforcements. The join loner feature just takes that last unit out of the game without it dying and the mission code can't handle the situation, the null squad. So whenever this happens you lose a squad in the game that will not repawn ever. I was thinking about this feature when you first introduced it in v1.14 and thought it could give some "special" results in warfare. I tested it once and then disabled it in the userconfig and everything was ok. That's why I never reported it. It came back to me when I saw xxbbcc's post.

In my experience the "rejoining loner" feature breaks the squad structure in warfare. BIS warfare that is, and I don't know Benny's edition enough. But by disabling that feature everything is back to normal or actually "much better than normal"! Thanks Robalo, this mod is state of the art.

Yep. And it seems fixed as stated on DevHeaven. Thanx a ton, Suma.

It's not so much the motion blur but the depth of field that keeps me from using PP settings beyond "low". I may be old, but my eyesight ain't that bad ... :butbut:

Wow, preemptive fixing! Thanx Suma, I will test and report back. Does anyone know if there is a ticket about this bug at CIT?

So I'm not alone nor paranoid! Thanx for confirming guys.

There is a strange thing since some time thou with AI recognition of enemy positions you wouldn't notice in multiplayer games. Following situation: you save a game in a situation before you get to know an enemy unit that is still a mile away and none of your team AI knows about it yet you continue the games until both groups get closer and end in an egagement where you die you reload the savegame from ten or fifteen minutes before where nobody knew about it each other => and voila, all your team mates and your avatar start calling out enemy contacts a mile away! And in addition the enemy units know exactly where you are. Happening in singleplayer. Seems the knows about isn't reset after a reload. I just can't seem to remember when this has started.

Open the editor, place down a game logic and put the "set..." commands into the init line. You also need to place a player character on the map. Have fun ...

Just delete the beta folder and re-install the beta you want. ---------- Post added at 12:03 PM ---------- Previous post was at 12:02 PM ---------- That's the "smart" way to do it. :)

Looks like home ...