Duke3D port
Duke3D port
http://jonof.edgenetwork.org/buildport/duke3d/
I stumbled into this, just tried it and give it a big thumbs up! Played at 1024x768, it felt very much like the original. No errors, great config menu (use his setup utility).
I stumbled into this, just tried it and give it a big thumbs up! Played at 1024x768, it felt very much like the original. No errors, great config menu (use his setup utility).
That's it then, I extracted this port into its own folder and just added duke3d.grp, then answered "yes" when it asked about creating a .con file.Enjay wrote:I also found that if I had a duke.cfg setup by a different program, it wouldn't register my changes unless I deleted the config and set up a new one with the new setup program.
Re: Duke3D port
Thanks for the link. It's great that many DooM/ZDooM fans are also DN 3D fans.Biff wrote:http://jonof.edgenetwork.org/buildport/duke3d/
I stumbled into this, just tried it and give it a big thumbs up!
Oh, very well. Here it is. The status bar acts funny, and I think there was some other problem, but it should run. You will need to either set your controls in the console, or run it once and then edit the ini. The key to open the console is backslash (\) instead of `, because Duke already uses that for quick kick.Biff wrote:Or, Randy gives us a taste of his version....
- Attachments
-
- duke3d.cab
- My port of Duke Nukem 3D. Needs fmod.dll.
- (316.38 KiB) Downloaded 252 times
Hmmm, well for me the game starts with the game window positioned off the screen. I can right click the status bar button and maximise the window though.
It doesn't seem to be saving any form of ini or cfg that I can find.
The status bar comes and goes as you said it might, but it does run. I'll not go into a long list of bugs because I'm sure you don't want to start suppporting this (at least not yet).
For information, on a UK keyboard, when people normally say use the ~ (tilde) key to open the console (not that you did), the key that actually opens the console (the one just below the Esc key) does not have a ~ character on it. The key that does have the ~ character is beside the Enter key (shift for ~ and non shifted for #). Anyway, the reason I mention it is because the \ key did not open the console for me, but the ~# key (beside enter) did.
It doesn't seem to be saving any form of ini or cfg that I can find.
The status bar comes and goes as you said it might, but it does run. I'll not go into a long list of bugs because I'm sure you don't want to start suppporting this (at least not yet).
For information, on a UK keyboard, when people normally say use the ~ (tilde) key to open the console (not that you did), the key that actually opens the console (the one just below the Esc key) does not have a ~ character on it. The key that does have the ~ character is beside the Enter key (shift for ~ and non shifted for #). Anyway, the reason I mention it is because the \ key did not open the console for me, but the ~# key (beside enter) did.