Furret

Just gave it a quick try in a 5v5 ai battle, impressive. The find cover mechanics really makes combat more engaging.

21/12/13 Short game in the editor using the Alive framework: http://pastebin.com/U1E8QZzi i7 920 @ 3.7ghz (HT off), 6gb 1800mhz, gtx 670 Hope its of some use to you

I'd start looking to see if the mission you're playing on multiplayer has been updated. Might be worth contacting the developer/reading the missions thread to see if others have this problem. Does it happen on all servers? Does it only happen on a particular mission?

5% as he's alt-tabbed out of the game.

Does it happen in single player or multiplayer? or both? does it happen in the editor?

You said no antivirus, are you 100% sure? ESET advanted memory scanner runs even when the rest of it is turned off.

I believe the issue is due to threading not being aggressive enough, something only the engine team can work on. From what I can tell the main process is utilising the other cores by using helper threads to offload work from the main process, it seems that the main process may be starved of work due to having to wait for other tasks on other threads to be completed or perhaps not sharing the workload out to its helper threads as much as it should/could. This is why I believe having a CPU with efficient processing(sandy/ivy/haswell etc) is better to have than one with more cores, that primary process uses all it can. My multithreading experience is low, so I may be completely wrong. It would be nice to see members of the engine team open up about this topic in more detail.

Really hope this is sarcasm.

I believe the dev version available has lots of debugging enabled which lowers fps significantly.

Before people start spending time helping you out, have you read the other threads on this sub-forum? there's lots of people with the same exact problem, low fps. Can you give us a run-down of what you've tried?

Has anyone created interesting missions with Alive yet? I'm interested in seeing what people have done with it. (Besides the 3 sample missions on the homepage)

Would you describe yourself as an ideas guy, OP?

Its very easy to try it out, and might be easier than waiting for an answer from someone in your situation. I would assume it would have an a small positive effect as its making changes to how things are stored in memory.

I thought all devs were away for the Christmas holidays.

I would strongly disagree with the above post, adding dlls is not a good thing to start doing. The problem seems to be graphics card related, perhaps try: Uninstall graphics drivers and restart Use a tool like driver sweeper to completely remove all remnants of the driver Install new drivers fresh from the website. edit: googling "nvwgf2um.dll" provides some interesting reading.

Could you create a mission in the editor that shows the problem? ideally it should be 100% repeatable.

If nothing has changed I would start to consider the possibility of hardware failure. A full memtest86+ run etc

Try downloading the directx redistributible and running it. http://www.microsoft.com/en-gb/download/details.aspx?id=35 Does it crash in the editor or in a specific mission? Are you playing multiplayer?

Make sure shadows are not on Low, this forces them to the CPU instead of the GPU. Lower the viewdistance? over 3k is going to be bad. 331.93 drivers vs 331.82, any difference? Has your bios been reset to default, thus reducing your cpu to a low multiplier? or the ram timings have been set to lowest level. Heat throttling, is your graphics card/CPU overheating and lowering its performance to prevent damage? I'm assuming this is all being tested in single player, no one gets fps higher than 30 in multiplayer, that's an entirely seperate issue with the game.

Try using a tool called GPU-Z to see if your graphics card is being used when your machine is idle. If it is, it could be a bitcoin mining program causing your crashes. If it isnt, watch the temperatures as you play the game, if it goes over 80c, you've got a heat problem.

If you're using ESET anti virus try disabling the advanced memory scanner.

Now you're dealing with a separate, multiplayer issue. Check the multiplayer sub-forum, dwarden is asking for help testing a new MP server executable.

You're dealing with thread starvation, every object in a 12k range of you needs to be processed before anything else can occur, lower the range and you'll have less of a problem.

12k View distance and you expect decent FPS? seriously? Come on man, be reasonable.

There are literally dozens of threads that discus this very thing. Its a long standing issue with the engine that arma is based on.