"Receiving" screen then nothing

[postreal 10]

Yep two physical processors. It´s not a server computer, its a workstation computer. I do 3d as my work so this is actually my work computer. So how can i limit to one processor? with -cpulimit=1 ? I know about the memory, going to buy more soon..

EDIT: I tried -cpucount=1 / -cpucount=2 / -cpucount=4 / -cpucount=8 ..without any results..it works best with cpucount on 4, but i still get the same AI crash. Maybe my comp is just too bad for this game, gotta go back to Joint Operations : Typhoon Rising :) I love this endless tweaking, maybe they could include a tweakers quide in the retail pack?

Edited February 6, 2010 by postreal

[postreal 10]

Anybody..please. I´m thinking to return my game...My computer specifications should be good enough? (look above).

[postreal 10]

Hi everyone,

Just wanted to tell that I got my problem solved. I was wrong :) It was not about the game, drivers or my computer. I borrowed another gtx275 from my friend and it seems that the one I had was fubar. Everything works now :) Although I do get some (not many) random crashes to desktop, but I can always get back to game.

Thanks!

[sprayer_faust 0]

I think I have found a solution to this problem (flashing receiving screen, memory leak...).

After a month my arma2 multiplayer hunger was back. I went playing some warfare, hoping the receiving screen problem would magically disappear... Wrong. So with nothing to do, I decided to fiddle with the nvidia controll panel and changed some things. But here is the main suspect:

Threaded optimization

Description:

Allows applications to take advantage of multiple CPUs.

Typical usage scenarios:

- Most newer applications should benefit from the Auto-select or On settings

- This setting should be turned off for most older applications

It sounds right to have it turned on or at least on auto for arma2, since it utilizes multiple threads. That's what kept me from turning it off (I had it on auto). I have finally turned it off after I was inspired by another thread on this forum:

http://forums.bistudio.com/showthread.php?t=97154&highlight=threaded+optimization - my performance was also unaffected. I even raised the settings from normal to high (except the postprocessing effects).

The game never crashed ever since - which actually means in two days time, but the testing was both extensive and intensive. :D Before the change the game would have definetly crashed with this amount of gameplay.

So at least in my case the driver was to blame, not the game. I will of course report back if it happens again.