GoodGuy
Posts: 1506
Joined: 5/17/2006 From: Cologne, Germany Status: offline
|
quote:
ORIGINAL: 06 Maestro quote:
ORIGINAL: GoodGuy On the other hand, the fixes in the "performance and stability" sector (in patch 1.3) amount to ~34 fixes only, a few dealing with memory leaks, but most dealing with rendering optimizations (doh) and mouse interaction. Looking at the 1.4 fixes in that sector - and thinking about how unstable 1.3 is - makes me laugh actually: ~26 major fixes, mainly some 5 optimizations ranging from some framerate fix, fixing freezes, ATI shader fixes, and solving maprendering issues, plus 10 crashes when certain countries surrendered had been tracked down. Most of the CTDs I got (and I got a shyteload) happened when I selected a game speed faster than normal game speed and it didn't involve a country just surrendered. Again, many of these problems were not consistent. Perhaps I have avoided many of these issues because I seldom run it at full speed. I do know that high speed play makes the game less stable-from personnel experience. However, as I see no point in running the game at that speed, it certainly does not break the game for me. I hate to quote myself, but I said that "most of the CTDs I got (and I got a shyteload) happened when I selected a game speed faster than normal game speed". I don't see why a user shouldn't run the game at say 2x speed, as that's pretty much the only way to skip the (very) boring parts (peaceful periods, or where you've issued all orders). Also, I set production/research to what I'd call "semi-auto" at times (so that the AI does not waste IC, but that it can't tinker with the content of the respective queues). I even know people who enable the player AI, in order to let a Korps defend England after they have invaded the "isle", in order to take care of the actual battles on the continent themselfs, for example. If you know how to use the auto-features in a way that they don't sabotage your policies/production/research/gameplay, then there is really no NEED to sit and watch (for "hours") how 10 stacked player units are taking a region defended by one AI milita unit. But until patch 1.4, the game speed feature was one of the major sources responsible for the CTDs, well along with the numerous memory leaks. Since they could track down some memory leaks and freezes, it plays a lot better with 1.4 now, but now I've got British partisans showing up in Poland, along with some British divisions popping up at in Russian territory, defending the frontline. I usually don't use it, but I just tested the player AI (defend/attack routines on Army/Supreme HQ level etc.) with 1.4, and I gotta say it does not relocate as many units as before, quite some are stuck in the middle of Germany or France, even though the Supreme HQ estimates the size of the opposing enemy force to be smaller than the size of the subordinated force. So, Paradox does look a bit like one of those companies who track down and kill one bug, but add another bug in the process (well unintentionally I guess, but it doesn't matter). Now that's not new, some company called Microsoft excels in that field. It's hard to avoid Microsoft (OS monopoly), but I'll avoid Paradox and its products in the future, no doubt. I don't feel like paying for a paradox BETA product again in the near future, sorry.
< Message edited by GoodGuy -- 4/1/2010 11:01:31 AM >
_____________________________
"Aw Nuts" General Anthony McAuliffe December 22nd, 1944 Bastogne --- "I've always felt that the AA (Alied Assault engine) had the potential to be [....] big." Tim Stone 8th of August, 2006
|