2008-11-23, 01:59 AM
(This post was last modified: 2008-11-23, 02:12 AM by KajitiSouls.)
Alt+tab is actually one method to nuke the infamous Zakum Vista glitch. So it graphics changing during the battle and getting SP1.
As for setting graphics to low, this is to have a much lower load time when fetching the map images from the map.wz files, and it also takes up less memory in the system so you can do other shyts with less l4g. In theory anyways. The reason it doesn't affect the monsters and characters themselves is because the high amount of detail is necessary so you can actually act on what you see. Otherwise it'd be a lot like looking at blobs doing indistinguishable motions which wouldn't really make sense unless you've seen it hundreds of times.
Actually harrisonized's method of having people gradually attack is a correct method in helping people cope with CPU stress. No matter what you do in pre-Zakum summoning, you'll never be able to load the "monster-is-hit" images or all of the other fancy crap associated with it (unless everyone bothers to smack around Bains). Take for example a Paladin's holy ACB attack on a monster. When that attack hits monsters, you'll see lots of shininess on the monsters where you hit them. It's very noticeable, and it looks a lot like a shining star with a large aura. This image will never appear otherwise.
If you've played Counter-Strike or most of the other games by Valve, you'll probably have noticed a phase where the computer is "pre-caching resources". This is a step that reduces l4g in the game caused by loading graphic images and such into its RAM. Once graphics and images are called from the file or w/e from the hard drive into the RAM, the computer can re-use and recall those images with little to no delay, thus allowing for a smooth experience with graphical applications.
As for setting graphics to low, this is to have a much lower load time when fetching the map images from the map.wz files, and it also takes up less memory in the system so you can do other shyts with less l4g. In theory anyways. The reason it doesn't affect the monsters and characters themselves is because the high amount of detail is necessary so you can actually act on what you see. Otherwise it'd be a lot like looking at blobs doing indistinguishable motions which wouldn't really make sense unless you've seen it hundreds of times.
XTOTHEL Wrote:The 10 second rule is to give all the players time to load zakum's sprites, allowing their PC to catch up. It doesn't have anything to do with not having everyone start at the same time.
You're idea of starting one after another is completely wack. For example if party 1 starts at second 1, party 2 start at second 2 and so on, until party 6, at which point all the parties would be attacking at the same time.
Actually harrisonized's method of having people gradually attack is a correct method in helping people cope with CPU stress. No matter what you do in pre-Zakum summoning, you'll never be able to load the "monster-is-hit" images or all of the other fancy crap associated with it (unless everyone bothers to smack around Bains). Take for example a Paladin's holy ACB attack on a monster. When that attack hits monsters, you'll see lots of shininess on the monsters where you hit them. It's very noticeable, and it looks a lot like a shining star with a large aura. This image will never appear otherwise.
If you've played Counter-Strike or most of the other games by Valve, you'll probably have noticed a phase where the computer is "pre-caching resources". This is a step that reduces l4g in the game caused by loading graphic images and such into its RAM. Once graphics and images are called from the file or w/e from the hard drive into the RAM, the computer can re-use and recall those images with little to no delay, thus allowing for a smooth experience with graphical applications.