Steam telepítése
belépés
|
nyelv
简体中文 (egyszerűsített kínai)
繁體中文 (hagyományos kínai)
日本語 (japán)
한국어 (koreai)
ไทย (thai)
Български (bolgár)
Čeština (cseh)
Dansk (dán)
Deutsch (német)
English (angol)
Español - España (spanyolországi spanyol)
Español - Latinoamérica (latin-amerikai spanyol)
Ελληνικά (görög)
Français (francia)
Italiano (olasz)
Bahasa Indonesia (indonéz)
Nederlands (holland)
Norsk (norvég)
Polski (lengyel)
Português (portugáliai portugál)
Português - Brasil (brazíliai portugál)
Română (román)
Русский (orosz)
Suomi (finn)
Svenska (svéd)
Türkçe (török)
Tiếng Việt (vietnámi)
Українська (ukrán)
Fordítási probléma jelentése
Thanks for the courteous and logical reply :)
That being said (or rather, re: what I've previously said), I *AM* glad though that the Steam version just might get some more Dukers out there. If EDuke32 (or JFDuke) will connect to the Steam version (possibly IP to IP, or using a third-party server browser such as "Yang"), I'm surely looking forward to kick y'alls butts in DukeMatch <grin>...
...or possibly some nice AI butt kicking co-op :)
Gawd, the days I wasted back in the day, modem-to-modem :)
Folks,
In the meantime:
http://steamcommunity.com/sharedfiles/filedetails/?id=133143095
...and then,
YANG - Yet Another Netplay Guider[yang-online.com] (for use with EDuke32) :)
Yeah, my first PC was a 486 DX-2 80 MHz with first 4 and later 8 mb of RAM. It ran Duke3D quite ok with the 8 mb RAM. But after buying my 2nd PC (Pentium 133 with 16 mb RAM) I could finally play Duke3D the way it was designed to be.
486 CPU's of higher clockrates could run Duke3D quite ok, but you needed the DX version. The SX didn't have a math co processor, that's why they were much slower.
You do need cache though, Duke3D will tend to cause hiccups without cache.
Also, a PCI or VLB video card (such as an ATI Mach64, S3 Trio64v, etc) will prove to be very useful.