Does it always take forever for 1.7 games to load?
Anonym:
Update: With everything finally seeming to work, I sat down for a nice, long night of simming tonight.
The lag was awful. The lag is made far worse by the fact that the game clock moves as if there were no lag, so you basically can't accomplish anything, as a simple social like "flatter" can take a sim-hour. "Chat" could take four sim-hours or something.
If it were my computer's specs, it would have been that way before 1.7.9, and it wasn't. Or, as is possible, the needed specs to run it decently went up quite a bit with the new patch.
Arrrgh!
uknortherner:
I've noticed my game getting increasingly laggy over the last few days. I thought it may be a rogue mod but now I have the feeling it's crappy EA code. My PC is hardly high-specced, but it ran the game fine before the latest patch.
I wanted to try and decompress all my mods to see if that made an improvement as I have a feeling that the new EA fucktardery code isn't playing nice with compressed files, but there's no way of doing it as a batch process (and I'm sure as hell not manually typing out those stupid "548975378yd79f8gyw98gfys89hyg78s9.package" filenames over 200 times in DOS). Crappy store crap.
Ioria:
Quote from: uknortherner on 2009 December 09, 15:21:06
I have a feeling that the new EA fucktardery code isn't playing nice with compressed files
I have that feeling too.
As I said in my previous post, I never had trouble with compressed files before the patch.
Now that I have them decompressed (a good 252 MB of joy), my game loads very fast and runs smoothly without (!!) all the bugs I was so angry at.
Buzzler:
Quote from: J. M. Pescado on 2009 December 08, 17:59:43
Whether or not the values are treated as signed or unsigned, also cannot be changed after the program is made. Since a program compiled and intended to run on Win32 must adhere to the minimum compatible behavior, this limitation is thus applied to all Win32 programs: Given that a fiery explosion will result on a Win32 system, the one the program is meant to RUN on, should this limit be ignored, the program is thus so limited and cannot use more than 2 GBs of RAMs: If it tried, the game would run seemingly okay on some systems and explode horribly on others. So it can't do that anywhere.
Well, that's what the LAA-flag is for. Windows is able to provide 4GB of virtual address space to an application, but the application must explicitly declare that it's able to handle it.
Devs probably leave the low-level memory management to the compiler in most cases, so it's simply a question whether the compiler supports LAA. Lots of games at least won't explode if the LAA-flag is set, although admittedly there's usually no benefit from doing so either.
Anonym:
Quote from: Ioria on 2009 December 09, 20:41:15
Quote from: uknortherner on 2009 December 09, 15:21:06
I have a feeling that the new EA fucktardery code isn't playing nice with compressed files
I have that feeling too.
As I said in my previous post, I never had trouble with compressed files before the patch.
Now that I have them decompressed (a good 252 MB of joy), my game loads very fast and runs smoothly without (!!) all the bugs I was so angry at.
I pray to Pescado to make a batch uncompressor.
I didn't compressorize my CC, but I'm sure much of it came compressed.
Navigation
[0] Message Index
[#] Next page
[*] Previous page