Install Steam
login
|
language
简体中文 (Simplified Chinese)
繁體中文 (Traditional Chinese)
日本語 (Japanese)
한국어 (Korean)
ไทย (Thai)
Български (Bulgarian)
Čeština (Czech)
Dansk (Danish)
Deutsch (German)
Español - España (Spanish - Spain)
Español - Latinoamérica (Spanish - Latin America)
Ελληνικά (Greek)
Français (French)
Italiano (Italian)
Bahasa Indonesia (Indonesian)
Magyar (Hungarian)
Nederlands (Dutch)
Norsk (Norwegian)
Polski (Polish)
Português (Portuguese - Portugal)
Português - Brasil (Portuguese - Brazil)
Română (Romanian)
Русский (Russian)
Suomi (Finnish)
Svenska (Swedish)
Türkçe (Turkish)
Tiếng Việt (Vietnamese)
Українська (Ukrainian)
Report a translation problem
I'm sorry, but what the heck are you talking about?
All I know is that Duke runs at full speed no matter what he's doing.
You can slow down by holding SHIFT though.
Cores (or CPUs) are the physical elements of your computer that execute code. Usually, each core has all necessary elements to perform computations, register files, interrupt lines etc.
Most operating systems represent applications as processes. This means that the application has its own address space, where the OS makes sure that this view and its content are isolated from other applications.
A process consists of one or more threads, which carry out the real work of an application by executing machine code on a CPU. The operating system determines, which thread executes on which CPU (by using clever heuristics to improve load balance, energy consumption etc.). If your application consists only of a single thread, then your whole multi-CPU-system won't help you much as it will still only use one CPU for your application. (However, overall performance may still improve as the OS will run other applications on the other CPUs so they don't intermingle with the first one).
What the heck are you talking about? what does Call of Duty have to do with this thread?
I know what hardware is. I just don't think that having a multi-core cpu slows DN3D down.
In the early days of FPSs, your character normally walked, and you had to hold SHIFT to run. Then later FPSs added the auto-run feature which was toggled by pressing CAPSLOCK, and auto-run always defaulted to off. Duke Nukem 3D was one such game which defaulted auto-run to off.
Back when shooting enemies in the head was no different from shooting him in the finger and auto-aim targeted your enemy's center as long as he was within a certain conical area of your central point of view, I played without a mouse and configured my keyboard so that I could efficiently aim up/down, duck, jump, jetpack, run, turn 180 degrees, switch weapons, secondary attack (the mighty foot), operate doors/switches, etc. and I did quite well against players who just used the now-standard WASD + mouse setup. I preferred to ignore auto-run and hold SHIFT when running then let go when I needed to slow down so that I could easily steer precisely (kind of like operating a gas pedal in an automobile, I suppose).
????WTF???? R U talking about? Using ONLY a single core on ANY duel/quad core CPU made in the last five years would SMOKE the hardware this game was orginally designed on and for . Hell, the vanilla X-Box 360 version is flawless, my cell phone has more power than that POS-BoX. :]
Also on topic as Jian Hou Zi stated it could be a simple thing such as auto run turned off and also as he stated game made back in those days walking was the defualt speed but they all came with a button you could use to run as well. You could always pick up some steroids to help you run even more faster if it bothers you that much :)