45 replies to this topic

[Michael Abt]

Since patch 1.4.52 the 64bit client doesn't run any more on my system.

http://mwomercs.com/...31#entry4961631
http://mwomercs.com/...4-dx10-crashes/

The problem was never fixed, only workaround is the 32bit client. Fortunately Tarl Cabot found a workound around their "solution" forcing to load the 64bit version, or i wouldn't be able to play any more.

Edited by Michael Abt, 17 March 2016 - 10:34 AM.

[Tarl Cabot]

Krivvan, on 17 March 2016 - 05:31 AM, said:

Theoretically it's not that bad of an idea to force 64 bit, it should be outright better as long as you're on a 64 bit system. Weird that people are experiencing worse performance with it.

It may be related to system specs. Generally mine is OC 4.5ghz with at least user.cfg FPS limiter set to 70 or 80 for a more consistent FPS The yo-yo effect of hitting 150fps then dropping down to 50/60fps does not work for me.

I set my system back to no-OC settings, i5-3570k 3.4ghz HD 7950 8megs ram

Ran through the same gauntlet using the training ground in V-Bog map. (saw similar results in live drops but with deeper drops in FPS)
Med setting w/AA Off / Vsync off

DX11 (will try dx9 later)
32bit
FPS - 95fps (targeting/killing catapult) to 120fps (climbing steps to small plateau to kill commando)
CPU - 60-65% usage
GPU - 35-40% usage

64bit
FPS - 115fps (targeting/killing catapult) to 145fps (climbing steps to small plateau to kill commando)
CPU - 65-70% usage
GPU - 45-50% usage

Things to remember..

Turbo boost (majority motherboards/cpu use it)- temporary poor man's OC. Enabled by default - when it is activated it applies more power to fewer cores. This draws more power and generates more heat to individual cpu cores. One can end up with a yo-yo effect of normal speed, oc speed then below normal speed (to give time for individual cores to cool down).

Dust build up - when was the last time heatsinks were cleaned out? Just saying, cause almost beat my nephew, after 8 months he had not cleared out the dust on his CPU heatsink but he had kept general dust build up cleared up in rest of system. Took off CPU fan/heatsink assembly, approx 1/16 in of dust/matter on heatsink where fan blows into. His temps went from 75c when playing games back down to 50c. Had the rest of his housemates clearing their systems after that. I made them do the work while I oversaw them.

For the others that it would not work at all, I would say (after assisting a few) is that some do not have the certain 64bit components installed, such as Microsoft's Visual C++ 2010(64bit).

There may be other reasons but they need to be done on a one-by-one basis cause there is rarely a one stop, fix-it for all approach.

Edited by Tarl Cabot, 17 March 2016 - 12:49 PM.

[D V Devnull]

Tarl Cabot, on 17 March 2016 - 12:42 PM, said:

There may be other reasons but they need to be done on a one-by-one basis cause there is rarely a one stop, fix-it for all approach.

That's why PGI should never have taken away the '32-bit Switch'... Trying to force people to use a certain client based on system specs is some of the worst developer failures and awful PR that I've ever seen. Here's to hope that they take their brains out of the tar pit soon, before we end up seeing some rather 'mentally insane' things.

~D. V. "sick of bad situations" Devnull

[M T]

Pretty painful to still see so many issues with 64-bit applications/programs, and to see 99% of the big titles still being released and compiled as 32-bit.

Hats off for PGI to actually deliver us a 64-bit client in the first place.

But seriously though, the first native 64-bit Consumer Desktop processor (Initially AMD) has been released like 15 years ago by now, kind of lolz to see progression and adoption is so slow.. Look at Windows still releasing 32-bit versions.. for what... 20 year old PC's? They barely run new OS'es anymore these days..

But um, I do agree it makes no sense to remove the ability for force 32-bit... Why in the world would you take away features like that without any good reason. Its like taking perfectly fine maps away from the game -.-

Edited by x MT x, 17 March 2016 - 03:17 PM.

[Stunner]

Since the patch yesterday I had my friend remove the "-nopatch". After the patch he can get in fine by using the 32 bit shortcut we put on his desktop. I wonder if they corrected something with this last quick patch.

[Dreammirror]

Thanks Tarl Carbot! Your temp workaround is working for me(for now) though I wish PGI would re-enable force 32 bit back into their game. That was what was causing me problems as well.