Slashdot Mirror
Duke3d in Linux
Obiwan Kenobi writes "So it took four days, but Duke3d now runs in Linux, courtesy of Icculus.org. Ironically, a win32 port has yet to be released. Features include full sound support, hi-res video modes (aka VESA modes for those familiar with DOS), saved games, full screen or windowed viewing, and even the BUILD editor works (to a degree). No mouse, demos, or networking just yet, but the basic gameplay is there and now that the BUILD engine has been ported a win32 version is soon on the horizon."
Time to kick ass and chew bubble gum!
Posting useless rant since 2003.
Basic gameplay is there, but the fun stuff doesn't work...
What doesn't work/known bugs:
* Windows port doesn't exist yet, but is probably just a matter of getting it to compile (the engine itself is already ported).
* Networking/modem/multiplayer at all.
* Resampling of audio is broken, so sometimes duke sounds weird.
* Mouse/joystick input isn't working yet.
* Demos are broken (they are broken in the initial source release, too).
* Probably other stuff. Do NOT consider this stable and complete yet!
"Some things have to be believed to be seen." - Ralph Hodgson
Having two computers on-hand rules too. Now if I could just find the game files...
Interesting case for buying games instead of warez'ing them. In 5 years when the game source is GPL'd, the box with all of the game data will be sitting on your shelf.
Right, now lets start getting this ported to every system on earth. Duke3d for Dreamcast, PalmOS, and JavaVM everyone!
...but is a Mac OS X port feasible? I know Duke3D used to run on OS9, so whatever mac-specific code it needs is extant. Was that released along with all the x86 stuff?
- CVS to check out the code.
- SDL Libraries for graphics and sound.
- An original Duke Nukem CD to get the configuration files and game data
- A DOS box or DOS emulator to install said CD
- Make and other compile tools to put it all together
I'm missing items 3 and 4. Anybody have a working binary they can put up for download?Unless you have a copy of the CDROM Duke Nuken: Atomic Edition, you can't use this. The shareware version doesn't work.
:(
This leaves me pretty much out in the cold..
"Ironically, a win32 port has yet to be released."
Ironically, Duke3d has been running on win32 operative systems since the beginning. The tweaks to get the it working has been around about as long.
Oh, I can't help quoting you because everything that you said rings true
hehehehe double reference jokes are funny.
Ignore the "p2p is theft" trolls, they're just uninformed
Ironically, a win32 port has yet to be released.
They're probably too busy playing games released this decade.
These guys are usually actually willing to give great support with odd problems. In general I have received MUCH better support from the OSS community, then what i get for paying $150/hr to a brain-less M$ support tech. Why would they provide support for a product that they know isn't done or even beta ready, has tons of known problems and after all, has been in development for 4 days? I think this is very reasonable. And when was the last time YOU talked to the actual coder of a piece of software at M$ or other commercial software company? In the OSS community, if you really have a bug or weirdness, they are usually more then willing to exchange emails with you directly. AND this is FREE. What are you complaining about?
Reinard
General Kenobi, years ago you served my father in the Browser Wars. Now he begs you to help him in his struggle against the Duke of Nukem. I regret that I am unable to present my father's request to you in person, but my isp connection has fallen under attack and I'm afraid my mission to bring Duke to Linux has failed. I have placed information vital to the survival of the code into the memory systems of this x86 unit. My father will know how to retrieve it. You must see this boxen safely delivered to the free people running free software. This is our most desperate hour. Help me, ObiWan Kenobi, you're my only hope.
Don't you love the support you get with Linux software?
Yes I do, how dare they! I paid good money for that game and I expect it to work perfectly! Dammit they should be at my beck and call!
Sheesh, 4 days with the source and it should already use the Geforce4 features and look better than Ut2003! what are these aresholes doing? I demand they support me now! I demand they do what I want!
Hmmm, I am SURE that microsoft will gladly give me free support on all their products.
This sarcasim brought to you by the letter O.
Do not look at laser with remaining good eye.
Hey, I *was* a so-called "brainless" MS Support Tech. And let me tell you. We had some of the brightest people I've ever worked with at that place. It was the best group of people I ever worked with. Any problems with NT or Exchange you could POSSIBLY have and we'd be able to fix them.
And it's not $150/hr. It's $250/incident. Unlimited callbacks and time about the incident. It's not bad considering the caliber of support people we had over there.
It could be different now, I don't know. But it couldn't be too different. Maybe you got unlucky with a new tech.
Not defending MS here, and I agree that I can find solutions to most problems with OSS/GNU/Free software quick online. But don't just throw out this kind of junk because it's popular opinion.
- It's not the Macs I hate. It's Digg users. -
a Win32 port HAS been released. Check this thread on the 3drealms forum. It supports all versions of duke (except the shareware), and you don't need to install it, you just need the .grp file and the .cons that were released with the source.
Username taken, please choose another one.
...right?
The win32 port here was released several hours before the linux port.
Username taken, please choose another one.
/syle
IF YOU HAVE PROBLEMS:
Tough luck. Do NOT contact us with bug reports at this time. Do NOT contact us if you can't get it to build. Do NOT contact us for copies of the game.
People are already grousing about this and saying it's a fault of open source. But the thing is, they probably have a list of their own planned updates/fixes, and accepting a slew of bug-reports from every linux-newbie who wants to run duke3d would just be distracting from (the above) more important things. I expect they'll accept feedback once we're past the current beta-type stage of coding.
I wonder about some of the original duke3d bugs too. Nothing worse than just about fragging somebody in deathmatch only to get munched by a closing door...
let me be the first to say "huh?"
Notice that icculus weren't the ones that posted this to slashdot (or any other major news site). They finished the first stage of the port, got the DOS game to run on Linux using SDL (which the game was not written in) and then were cool enough to allow us to try it out.
Isn't the whole point of releasing the source so that people can dabble with it? It's not like they're releasing Duke3d Retail, they took four days to make a port of it to linux (and they're even trying to port it to windows too if you read their page).
I'm pretty much 100% certain that a Duke3d linux port that they took four days to work on which isn't perfect yet won't turn people off to the linux desktop.
Maybe you should be happy that someone with the talent to port it to linux (and windows) is working on it at all.
remove -Werror... you know that if you quit complaining and hack a little, it goes a long way.
remember the authors' notes that there is no support for this game *unless you contribute code*
SIGERR: laziness exceeds quota
I won't dispute the anti-MS tone here.
However, you seemed to be at the other end of the spectrum. Singing the praises of MSFT support will likely get you snorts and giggles from most MSFT developers.
The fact is, anybody who pushes the limits of the system (as we did) is going to run into trouble. And as you said in an earlier post, you guys (MSFT support) don't have access to the source. You basically have what the developers have. In that case, which I have to imagine happens quite a bit, support is useless, no matter how "bright" the people reading the scripts are.
And ya know what, I will sing some praises here. I find bugs in Resin that I can't track down, and I post a message to the developers, and it's fixed. You just don't get that kind of interaction with MSFT. And maybe I've gone off on a tangent here (okay, I have), but that's what's really lacking with MSFT. A pipeline to the developers.