Learn how to increase speed of CS4!!!
mod
so, CS4 is clunky... we all know it. especially flash. a guy in my class figured out how to speed it up, so anyone that doesnt know this trick, enjoy...
-open the program of your choice that you find clunky
-press ctrl + alt + delete
-go to task manager
-find the program in the processes list
-right click the program and go to set affinity...
-uncheck half of the processors
thats it... it will speed it up. it also speeds up movies and flash games through the internet if you do it to your browser window.
at school, it usually has 16 processors checked, so i uncheck 8 of them. at home, it runs faster, but i only have 4 processors.
lemme know if this helps any of you
-open the program of your choice that you find clunky
-press ctrl + alt + delete
-go to task manager
-find the program in the processes list
-right click the program and go to set affinity...
-uncheck half of the processors
thats it... it will speed it up. it also speeds up movies and flash games through the internet if you do it to your browser window.
at school, it usually has 16 processors checked, so i uncheck 8 of them. at home, it runs faster, but i only have 4 processors.
lemme know if this helps any of you
Replies
There is also a tool to unregister and thereby unload certain plugins to speed up the loading time. (can't find it atm. but there should be a thread somewhere). Other tricks:
And the best trick I discovered so far:
- revert back to PS CS2
The Processor Affinity setting controls which CPUs the process will be allowed to execute on.
But isnt the whole point of multicore to have have all this happen automatically behind the scenes? So confusing!
Good thing to bring this up Slipsius!
some programs are build to utilize multi-cores, but not as many as some computers have, so it ends up slowing it down. its a quick fix, and doesnt screw anything up with everything else. if anything, it takes the load off for other things, like multi-tasking Poly count in the background
I use set affinity when I'm rendering with mental ray in 3ds max, I have a quad core here so unticking one processor lets me do other things smoothly while max renders away. Otherwise I can barely browse the internet.
I also found out that if images take a while to open it might be a conflict with the network printer, try setting your default printer to "Microsoft XPS Document Writer" or remove all printer connections if you never print anything.
That and if you have any mapped network drives, I've noticed that too. It will kill you're program if you try to open or save anything.
Once again, you are the man! Having every image--even tiny ones--take a loooong time to open recently started plaguing me in CS3 and nothing I (and our competent but overworked IT staff) tried could fix it. Thanks for this!
Anyone:
I just got a new Intuos4 Medium. I've been using an older Cintiq 18, but wanted something that is portable and has tilt sensitivity. The Int4 is great for the most part, but the eraser and tilt sensitivity do not work (XP 32, CS3). I installed the drivers that came with the Int4, but no luck. It also doesn't seem to have as good a pressure sensitivity as the Cintiq 18, on which the eraser does work and pressure sensitivity is good.
I've had the eraser occasionally stop working on the Cintiq 18, but either a PS restart or a Wacom Tablet Service stop and restart fixes it. No luck with the Int4.
I tested the Int4 with CS2, but no luck. I then tested it on one of our classroom machines (XP32 CS4). It works great, and the pressure sensitivity is better, so it is not the Int4 hardware. I suppose I could try CS4 on the home rig, but I'm trying to avoid it.
I've tried various combos of settings in the Wacom Tablet Properties on the home rig for the Int4, but still no luck. I tried making the PS prefs Read Only, and other suggestions from the many Polycount threads devoted to tablet issues. I even looked at the Wacom_Tablet.dat file to see if I could spot something, but nothing stood out (not surpising, I'm an art guy). Any help would be appreciated.
If there is anyone around still rendering stuff on a single core CPU a trick with similar results is lowering the priority of the rendering process. This will more or less only let the rendering run when the CPU would otherwise be idle.