Duke Nukem 3D: Megaton Edition

Duke Nukem 3D: Megaton Edition

View Stats:
Fused Mar 20, 2013 @ 3:04pm
Duke runs so slowly
IDK if that's a glitch or if there will be other changes, as well.
< >
Showing 1-15 of 17 comments
Elazul Mar 20, 2013 @ 4:26pm 
I would think it entirely possible that since when the game was designed there were no multi-core processors it can only utilize a single core. So that fancy processor you have may not work as well with this game. Of course I may be entirely wrong in which case someone please correct me.
SirYiffsaLot Mar 20, 2013 @ 4:44pm 
Originally posted by Elazul:
I would think it entirely possible that since when the game was designed there were no multi-core processors it can only utilize a single core. So that fancy processor you have may not work as well with this game. Of course I may be entirely wrong in which case someone please correct me.


I'm sorry, but what the heck are you talking about?
Tsundere Kanojo Mar 20, 2013 @ 4:45pm 
Probably just a glitch for you.

All I know is that Duke runs at full speed no matter what he's doing.

You can slow down by holding SHIFT though.
dunadan Mar 20, 2013 @ 4:48pm 
COD kiddies trying to make everything stupid and dumbed down already.
Elazul Mar 20, 2013 @ 5:07pm 
Originally posted by HardPumpkin:
Originally posted by Elazul:
I would think it entirely possible that since when the game was designed there were no multi-core processors it can only utilize a single core. So that fancy processor you have may not work as well with this game. Of course I may be entirely wrong in which case someone please correct me.


I'm sorry, but what the heck are you talking about?

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).
SirYiffsaLot Mar 20, 2013 @ 5:08pm 
Originally posted by dunadan:
COD kiddies trying to make everything stupid and dumbed down already.


What the heck are you talking about? what does Call of Duty have to do with this thread?
SirYiffsaLot Mar 20, 2013 @ 5:09pm 
Originally posted by Elazul:
Originally posted by HardPumpkin:


I'm sorry, but what the heck are you talking about?

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).

I know what hardware is. I just don't think that having a multi-core cpu slows DN3D down.
JessHawk Mar 20, 2013 @ 5:14pm 
Originally posted by Elazul:
Originally posted by HardPumpkin:


I'm sorry, but what the heck are you talking about?

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).
Dude he's talking about movement speed not fps XD
Jian Hou Zi Mar 28, 2013 @ 2:29pm 
I haven't played this version yet, so I don't know what the default configuration is, but it could be that auto-run is simply turned off.

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).
Muleke_Trairao Mar 29, 2013 @ 9:57am 
yeah i feel that too, i think he runs faster in the classic version
Monsterfritteuse Mar 29, 2013 @ 4:57pm 
agreed, he is slower, but i think it's looking better and the game keeps playable, so doesn't matter to me :)
JIMI Apr 1, 2013 @ 5:26pm 



Originally posted by Elazul:
I would think it entirely possible that since when the game was designed there were no multi-core processors it can only utilize a single core. So that fancy processor you have may not work as well with this game. Of course I may be entirely wrong in which case someone please correct me.

????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. :]
JIMI Apr 1, 2013 @ 5:39pm 
Just purchased the game. Been watching it since it's release. I like the support by the Dev's, and the ease of running e-duke, HD packs w/o having to d/l stuff and write .bat files.Been there, done that,,, a long time ago lol,,
LarryTheCrab Apr 2, 2013 @ 6:34am 
Originally posted by dunadan:
COD kiddies trying to make everything stupid and dumbed down already.
Agreed

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 :)
Jian Hou Zi Apr 2, 2013 @ 8:27am 
Another thing that occurs to me, some versions of DN3D I've played have the multiple-keypress issue on post-XP operating systems (a problem we never had in good old DOS), whereby if you hold SHIFT and press forward, the new keypress causes SHIFT to be ignored, kind of like if you were to hold A in a word processor until the letter is automatically repeated, but then you press B, which interrupts the As and inserts a B. In such cases, the annoying work-around is to press forward then press SHIFT. I haven't played this release of DN3D yet, but it is possible it is afflicted similarly.
< >
Showing 1-15 of 17 comments
Per page: 1530 50

Date Posted: Mar 20, 2013 @ 3:04pm
Posts: 17