Guess Who

Thanks again for the update. Downloding now ...

I like those little twists in the storyline. Just awesome! :D

Well, thanx for squashing! :D Looking forward to the new version.

Yep, running 1.9. Doesn't work in 1.8 either. Backpack was a custom version inherited from the KSK packs. I did a little test mission with vanilla BAF soldiers though; just put down a group of Rifleman (Backpack) in Desert and removeMagazines of all of them. No one grabs a mag out of his backpack. Using CBA version 0.7.6.160. Thanx for looking into it.

Hi Rob, lovin' this mod, it's actually hard to play without it. While you're testing the next version, can you please have a look at the rearming from BIS backpacks? My experience from last weekend's sessions is, that they don't arm from their own backpacks nor from the backpacks of their team mates. My team guys prefer to grab an AK from OPFOR while having 4 mags for their own rifle in their own backpacks; they don't touch it even in safe mode! You have to drop a backpack for them to recognize it as a crate. Thanx for continiously developping this. It's one of those must have mods.

Well, actually he ain't telling you that. If you actually read his post, you would know ... Options is all we ask. And really, what is so bad about that? Care to explain?

Personal opinion, yes? Well, I beg to differ: everything has to be optional. And don't start with endless crosshair yes/no discussions. Again. BIs is trying to make this instance of the series a little more accessible and that's the way to go. So options are everything that matters!

I don't think it's related. But a bug is already reported at CIT. See http://dev-heaven.net/issues/12143. The problem it didn't get fixed yet maybe because it's kind of a "content fix". Those get lower priority, obviously. Kju even provided the fix on the CIT, just have a look at the ticket.

There's a small config bug in the configs for the Glock and for the Colt (ranges not defined) so that AI uses pistols instead of rifles at longer ranges. Try to give him an M9 for instance and repeat the test. Since I made myself a little bugfix config, I never ran into this bug again. Thanx to .kju for pointing that one out!

I know his site and his articles. And DB has been around here sometimes. But what you see over there is not the topic of this thread! We were discussing the possiblities of adding purchasable infantry of different factions in BIS Warfare. And there's definately no solution to this problem at this moment.

Back for report: played warfare for one hour strait in build 80955 before it crashed. Didn't see any artifact. So I consider it clean. i7/920 with 6 GB -Win7 x64 - AMD 5870 with driver version 10.4 (the last one worth the hazzle to install) ------------ Just tested with build 81201, same mission. Flashing started at 7 minutes after start. Several times within 30 seconds. Seems it is between 80955 and 81201 then. ------------ Edit #2: With build 82448 it still flashes, but rarely. I saw it once in half an hour and only for one frame.

I just downloaded build 80955; gonna install and playtest it now. 79600 is the build I played the most since patch 1.59 and I never saw that artifact in that build. The version showing it the most, is definetely 82604. I just finished a 5 hour warfare mission in Takistan and it happened every other minute, sometimes multiple instances in a short time span. I will report back soon.

Yep, happens in 3rd person and in "tactical" view also.

No, unfortunately it's not. OA doesn't recognize this parameter, or maybe not now. Just wanted to say: we can still hope! :D

Nope, seems impossible with the actual incarnation of Warfare. You can only recruit troops of one faction. My workaround: a small replacement config for the troops I want to play making them the same faction. There may be scripted workarounds as well.

First things first: please excuse the following wall of text. Did a test run yesterday but didn't have the time to test for stability on the long run; so this is for performance only. First: malloc=4 doesn't work on my system. Arma crashes instantly when loading the menu scene on Desert. My system: i7 920 at stock speed (2.66 Ghz) / Intel X58 mainboard 6 GB triple channel 1600 Kingston memory 5870/1GB GPU at stock speed Samsung SSD 120 GB Win7 x64 w/SP1 Arma running on mostly very high settings except for HDR and AA on NORMAL and post processing on LOW at 1920x1200. Frame rate, memory usage and other parameters monitored with ATI Tray Tools. Test mission (CPU and MEM heavy): BIs Warfare, personal edit, full scale on Takistan; fixed starting loation west of Loy Manara. Recruiting 3 guys, calling in helo transportation, helo transfer to north eastern strongpoint of Chardarahkt, jogging down to the city center and finally jogging through the town back west to the western most strongpoint. ALICE, SILVIE and Ambient animals activated. Observations: - After mission start and around the base there is not much of a difference between the three options. Frames start at 50 going down to low 20s when activity starts. Only difference is in memory usage: option 0 and 1 start with lower than 600 MB, option 2 starts with over 900 MB and option 3 at 750. - On the helo transfer passing Loy Manara and Chardarahkt there is a significant drop down in fps to the low 20s in all options except for option 3. With #3 fps stayed in the 30s. Same happens when I got near the town of Chardarahkt, when the civvis in the town are activated (city center is on the eastern outskirts, not in the town!). - While jogging back west through the town, frame rate drops to the mid 20s in the center an raises again up to mid 30s when leaving town at the west side for all options but #2. Best and most stable frame rate here with option 3. Memory usage for option 0 and 1 was still below 1GB while option 3 was slightly above. With option 2 the memory usage raised above 1.2 GB already in the town; when mem usage got to 1.2 GB the frame rate dropped below 20 to 15 and stayed below 20 for the rest of the test, even when leaving the town. Conclusion: The winner is "-malloc=3". Over all best performance, smoothest gameplay and less terrain streaming influence on performance than the others. Imagine me totally surprised that this would have so much influence on performance. Well, after all I'm not a programmer ... I will take a stability test on the weekend for sure. Normally Warfare crashes for me after 3 to 4 hours of continuous gameplay. After all these years I can even smell it comming! :D

No, not the kind with multiple factions. But I seem to remember to get it to work with one faction as a replacement for the original faction built into the mission. Well, I tried a lot of things and sometimes you get lost in that "trial and error" part, you know. I'm currently at work, so no access to ArmA at the moment. I will try to replicate the situation on the coming weekend and report the results back here. Keep the research going ...

Well, as I said before, I never got this to work either. For instance, I tried to make two factions (like US and GER) to work in Warfare. I assume, you put that modified "Config_Factions" into your misions's structure and added it to the "Config_Common" so it gets loaded for the mission? When I tried to put "BIS_GER" as a faction into the Config_Factions as a "replacement" for the US faction like: BIS_WF_Common SetVariable ["WestFactions",["BIS_GER"]]; it kinda works. Just never did, when I tried to get more than one faction into one side of the mission. I would love to get this to work.

Have a look at "Config_Factions". It's inside the \Common\Configs ... folder. I was actually never able to get this to work. Please report back.

ninja'd...

Na ... I'm not BIS. Just bored at work. And yes, you guys needed a hint. :D

This was posted on OFPEC today: So ... what's going on here?