MavericK96

Yeah, you add it in the command line. You want to leave a space between the -mod parameter and the -exThreads one, though. And you don't need the semicolon.

Interesting, thanks for at least letting me know that I'm not alone. :D Hopefully we'll see some use of that new parameter. How did you find out about it?

I also noticed the flickering. I've gotten that in the past but it seems worse in this beta than in 70313.

My Approx. Total Memory says 3817 MB. I'm guessing this is local + non-local VRAM? EDIT: Interesting to note also is that, for the hell of it, I tried turning back on Threaded Optimization, and I saw no difference in the new beta versus having it off (i.e. no v-buffer crashes so far). So maybe they fixed that issue at least so that you don't have to have Threaded Optimization off.

Yeah, I've found the same to be true, it's definitely related to flying over cities/buildings, not just out in the open. And it's obvious something is wrong with the Default setting, but that's why I'm complaining about it, because I want it to be fixed. :cool: It's supposed to detect how much VRAM you have and use it accordingly, so theoretically any amount of VRAM *should* work on this setting. Unfortunately, as it stands, this is not the case, and setting it to High or Very High gives me awful stuttering, stability or not. Obviously this is because High/V. High is not utilizing all of my VRAM, so Default seems the obvious choice. However, stability is an issue as I have said. Interesting, though the only parameter I've been using (other than exThreads) is maxmem=2047, and I've tried with and without that and there's no difference I can see in either performance or stability. I don't use cpuCount because I never saw a difference with that either, and I have HT turned off. Never heard of this "fullproc" one, though. And I don't have any of my config files write protected. Here is what it detects for Local and non-Local memory: localVRAM=1054539776; nonlocalVRAM=2147483647; Which seems about right, since I have 1 GB VRAM. Not sure about non-Local, or how it obtains that value. My page file is set at a minimum of 6 GB, maximum of 9 GB. Yeah, you were the one that told me about setting Threaded Optimization off in the nVidia control panel. That more or less solved the "v-buffer creation error" I was getting, but this seems to be a different animal altogether. I agree that High is more stable but at the same time it comes with a steep performance cost in terms of stutter for me. Also, performance seems to decrease over time while LOD thrashing seems to increase over time with High/V. High. until it gets to a point of being unplayable. The whole thing seems like a memory leak somewhere. ---------- Post added at 04:39 PM ---------- Previous post was at 04:22 PM ---------- Did some flybys over Chernogorsk as per usual, and I still get the "Receiving..." issue with exThreads=0 (no exThreads param used). With exThreads=3, I get "Out of Memory" crashes. I can't win with this game, lol. :(

AFAIK 3D TVs/monitors still need glasses to see in 3D.

Well, this is interesting. I just played online for probably about 20 minutes, flew a heli over to the coast north of Chernogorsk and went on foot for maybe 50 meters, and then the game crashed with this message: In the .RPT file I get this repeated over and over (look familiar?): Memory store: Failed mapping, already mapped 8988 KB, error 8 Virtual free 25456640 B, page free 4294967295 B, physical free 2680565760 B Memory store: Failed mapping, already mapped 8992 KB, error 8 Virtual free 25456640 B, page free 4294967295 B, physical free 2680565760 B Memory store: Failed mapping, already mapped 8996 KB, error 8 Virtual free 25456640 B, page free 4294967295 B, physical free 2680565760 B Memory store: Failed mapping, already mapped 9000 KB, error 8 Virtual free 25456640 B, page free 4294967295 B, physical free 2680565760 B File read error: addons\ca.pbo,ERROR_NOACCESS Error 3e6 reading file 'addons\ca.pbo' ErrorMessage: Invalid access to memory location. This is with Video Memory on Default, exThreads=0.

Yeah, I think the self-shadowing on objects is what improved, as there used to be some z-fighting with those, and it seems better now. Distance object z-fighting seems about the same from what I can tell from flying around for a bit. Also, stutter definitely seems worse in this version, but not terrible. Also, I haven't yet gotten the black screen "Receiving..." issue even with about 10 minutes of flying around Chernogorsk and surrounding cities. Obviously more test time is needed (online is where I get the problem the most and it affects gameplay the most, and I haven't tested it in MP yet) but if it was a trade-off to have a little more stutter versus no "Receiving..." screen, I'll take it. :cool:

If you're referring to my post, yes. Check out the two different benches for 70644, one is exThreads=0 and one is exThreads=3 (I didn't test eXthreads=1 because it was by far the worst performance for me in 70313)

Initial testing: Stutter seems a little worse in this release, but overall framerate is on par with 70313. Minimum FPS went down in this by about 2-5 FPS as you can see from the results from the _FPS_6 test below. Avg Avg Low High Low 70313 exT=0 37 26 52 13 70313 exT=3 37 26 52 10 70644 exT=0 36 26 50 9 70644 exT=3 36 26 52 8

I was just wondering the same thing actually.

Yep, it's up. Downloading now. :cool:

How do you get email notifications of new betas? Also, if the z-fighting is fixed, SWEET! Though it says it's regarding shadows, so it might not be entirely fixed.

Just did some benchmarking tests with High instead of Default. It's objectively much, MUCH worse in terms of stutter. In the _FPS_6 benchmark I was getting 10-13 FPS minimum with Default, but with High the minimum drops to 1 FPS. Subjectively, the stutter is a lot worse too, and extremely noticeable. I'd really like to stick with Default and I hope the devs can fix the "Receiving..." issue.

I've heard that V. High is 512 MB and Default is 1 GB+. But who knows, really? I use Default because with Very High I get awful stuttering and performance degrades over time. I haven't tried in the latest betas yet, but maybe I will give it a shot. In any case, the game shouldn't black out or crash or otherwise regardless of what video memory setting you choose. If anything it should just stutter/lag more from the constant memory swapping that would occur if you set it to more than you have.

Update on the "Receiving..." screen issue: After playing for a very short time (~15 minutes maybe) in MP, flying an A-10 over Elektro-whatever I got the issue again, causing me to crash into the ocean. Upon opening the .RPT file, I found this: [b]Forced memory flush (5595136 system memory surface creation failed) Cannot create system memory surface DXT5,2048x2048 (size 5595136 B), Error 8007000e[/b] Virtual memory total 2047 MB (2147352576 B) Virtual memory free 89 MB (94339072 B) Physical memory free 3047 MB (3195904000 B) Page file free 7349 MB (7706042368 B) Process working set 1505 MB (1578307584 B) Process page file used 1623 MB (1702588416 B) Runtime reserved 732 MB (767557632 B) Runtime committed 721 MB (756424704 B) Longest free VM region: 4767744 B, busy 2070159360 B, free 77258752 B Small mapped regions: 12, size 53248 B VID: alloc 984142204, limit 1237799808, free: local 1045323776, nonlocal 2147483647, DX9 4002414592, virt. 94339072 The first two lines (in bold) of this are new from the other instances of this issue, whereas the rest of the error seems the same.

If that's what you're referring to, I made a ticket for it at the CIT. Vote it up if you have this problem and post your .RPT and dumps please. :) http://dev-heaven.net/issues/10716

I've tried the new beta with maxmem=2047 and no maxmem parameter, and I haven't noticed a difference in either performance or stability.

Playing in 70313 with exThreads=0, doing lone flybys over Chernagorsk, I will sometimes get a black screen coming up and then "Receiving..." for 5-10 seconds, and then the game will resume. In the RPT these incidences show up like this: Error during v-buffer creation: error 8876017c Virtual memory total 2047 MB (2147352576 B) Virtual memory free 135 MB (142221312 B) Physical memory free 2822 MB (2959839232 B) Page file free 7518 MB (7884079104 B) Process working set 1419 MB (1488642048 B) Process page file used 1584 MB (1661440000 B) Runtime reserved 458 MB (480247808 B) Runtime committed 430 MB (451518464 B) Longest free VM region: 6291456 B, busy 2022240256 B, free 125177856 B Small mapped regions: 12, size 57344 B VID: alloc 985210316, limit 1237799808, free: local 1045323776, nonlocal 2147483647, DX9 4002414592, virt. 142221312 Looks like our old friend "v-buffer creation error" rearing its ugly head to some extent. However, the game did not crash, even after two of these occurances. Needless to say, if it were an MP game and you were in an aircraft, the amount of time that the screen blacks out would invariably cause you to crash into the ground. In SP, where I was testing, the game paused itself. EDIT: Just got this three times in MP while flying an A-10 over a relatively small town. The third time caused me to crash into the ground. Extremely frustrating and game-breaking issue. :mad: I've created a CIT issue ticket here: http://dev-heaven.net/issues/10716

So I used sbsmac's FPS Analysis Tool (nice work on that, by the way), and here's what I got, running the City Run benchmark mission included with the tool. Please keep the images <100kb. FPS Analysis: http://i263.photobucket.com/albums/ii140/AFireEternal/ArmA2FPS.jpg Notes: Interestingly, exThreads=1 had more "pulling" stutter (where FPS drops low, 5-10 FPS), and exThreads=3 had a lot more "hard" stutter (where FPS drops to zero for a short time). Overall I think the best option for me is still exThreads=0. exThreads=3 does definitely have faster LOD transitions (still delayed somewhat, but better than 1.05) but the hard stutters are pretty annoying. FPS in general looks to be better with exThreads=0 as well.

True. :) And thanks for the reply/info. I wish I had 12 GB of RAM to mess about with. :cool:

I get the same issue, and I typically have at least 4 GB free out of 6 GB. Someone reported something similar and I posted about it in the Community Tracker, you should do the same. :cool:

The GTX295 is a faster card, but I've heard several people on here having issues with getting the dual-GPU setup of that card working right. Probably would go for the 5870 if I were you.

Couple of questions for you: 1) Does the maxmem=2047 actually make a quantifiable difference? Like do you have any benchmarks/screencaps to back it up? 2) What size RAMDrive do you use, and what .pbos do you have on it? I'm not saying you're wrong at all. I just want some more info on these two things to help my game run better as well. :cool:

But there is already a 32-bit version. All they would have to do is develop a 64-bit executable/support files and release that as well. If anything it would increase sales, IMO.