I need hl.exe to run on one core, else i get horrible frame loss. Setting it in task manager isn't persistent (if I quit and start again, it goes back to all cores). THG task assignment manager is all I could find googling, and it doesn't always work
I know this is an old thread, but here's the easy answer that didn't come up. WinXP (and also Vista, I believe) has a utility included called start. This utility can be used to run a program with a specified cpu affinity. the command would look like this:
start /affinity xx myprogram.exe
Use the actual name of the program you want to run, of course, and substitute xx for a hex number representing the affinity you want as follows:
01 - 1st CPU 02 - 2nd CPU 03 - 1st and 2nd CPU 04 - 3rd CPU 05 - 1st and 3rd CPU ... etc
no /affinity parameter for the start command in XP, and also I'm hoping to find a way (program,w hatever) to set affinities just as they launch rather than manually. Thaks though sir, and nice to see you again!
I went back to Processor Lasso, which works alright. I thought it had been causing my computer to freeze, but it happened a couple times without it running. I think it's massive disk IO in my new raid device causing it to freeze (happens with utorrent running @ full network speed and sometimes when transferring files)--not sure why yet.
i'll do more research when i can and let you know if i find anything, i'll probably post it here one the forum because i don't seem to see you online on steam friends very often
and i do miss cs1.6, the server we had, the comunnity we had it was tons of fun, talking about it bring back so much memories
What I'm getting from it, despite them not really talking about this particularly, is that some processors/drivers/versions of xp may have affinity as an option on multicores, but others seem to be missing it.
Meanwhile, here was my batch file attempt. I was SUPER dirty, and literally copy the cmd.exe into the folder of my target program before calling the target .exe with the /C options.
goddamn the more I mess with affinity settings in Process Lasso, the more pissed off I am towards Windows. I was streaming CS (hltv.org has pro players streaming pugs now), and it was taking up ~20% of my cpu, which for just flash streaming is ridiculous (I'm on a Phenom x4 965 be). I tried switching Chrome to one core from all cores, and it dropped to around 8%. Let me repeat that: 20% across four cores vs. 8% on a single one.
In CS using all cores means constant fps drops to 50 or lower, down and up and down and up and down and up, etc., etc., even with all settings at minimum. With everything on max and restricting it to one core I'm at a constant 99fps.
Everything I've tried so far has worked as well or better when restricted to a single core.
I'm curious if Windows 7 is any better, but I had installed it, and I can't run the mouse acceleration fix (dll injection into hl.exe to get direct mouse input passed into CS) along with EAX sound.
Oddly enough, I was poking around last night in my task manager and happened to see the manual option for Affinity. Which pops a list of my cores. And checkboxes. My proc/driver/OS/MoBo combo is capable, but it doesn't seem to be a valid cmd switch.
I'm actually very interested in what the hell might make it show in some people's systems and not in others.
Mine has the option to set it manually from Task Manager. I was hoping for a way to have Windows memorize those choices so I wouldn't have to do it every time. It's fine for something I keep open all the time, but cs for example I do not. Process LAsso has been working out alright. It has some additional features that I'd rather not use (like changing priority when it somewhat arbitrarily decides a process is using too much cpu), but it memorizes affinity choices at least.
Yeah, that was more or less my experience as well. But that means there's a switch somewhere. Registry doesn't feel right. MsConfig doesn't feel right. CMD isn't right, apparently. What's Process LAsso written in? I have a code explorer that works pretty well at dissecting things in VB.Net and C#, so I could at least see what APIs it's calling to set affinity.
It's a fucking computer. If you can set something manually, you damn well better be able to set it automatically. I don't like mysteries inside my devil-box.
Woer i am not sure if it could help but if i remember correctly cs had launch options you could set on steam to fix mouse accelleration with those commands -noforcemspd -noforcemaccel -noforcemparms
there is also other commands for which directx you want to use, set how much memory you want cs to use, disable certain options to gain fps and such it might not fix your problems but it might help who knows