jDoom Question
Victor
Just installed jDoom with KickStart 2.09 (no models) on my Win98SE desktop
with DirectX 8.1. It's maxed out at 256K RAM with an AMD-K6 processor with a
Rage II+ video card maxed out at 4M. Well, it runs all the original Doom
programs great...
(BTW, my business computer is a 576M P3/650 laptop, but I do not install
games on it because it interferes with work.)
Direct3D won't initialize, so I selected OpenGL. I got an glBSP error so I
added the -allowsoftware command option.
I turned off my antivirus.
jDoom runs as slow as a herd of turtles stampeding through peanut butter.
Do I need glBSP? Do I need to set options?
Any suggestions?????
Grieve
"Victor" <Victo...@hotmail.com> schrieb im Newsbeitrag
news:fo-dncjtmoA...@comcast.com...
I encountered the same back in 2001 when I used an AMD 500 and a Voodoo2
(umm, a Righteous Orchid 2 with the same 3DFX chipset as the Voodoo2 card,
to be more precise :)). JDoom ( which was very basic back then ) ran fine in
Direct3D, but in OpenGL it would only run with the -allowsoftware option,
and then with 1 frame per second, or rather with 1 frame in 3 seconds.
You would get a slideshow even on much faster computers when a program is
using OpenGL commands that are not available on your graphics card and have
to be emulated with software. That means you get no hardware acceleration
for these operations. The cpu will always be too slow for such things, even
much faster ones than yours.
glBSP is only the nodebuilding utility that is used by JDoom, it is running
automatically per default and builds gl-compatible (more precise) nodetables
for the maps you are playing. These are internal game data and have nothing
to do with the OpenGL implemented on your system. JDoom would also play
levels with no gl nodes built, it only would show more rendering errors
(holes in walls, slime trails ... ). glBSP is the utility to build these gl
nodes and it should be launched automatically by your JDoom frontend when
you start a level.
I guess the only thing to try is to uninstall your graphic card drivers and
look for better and newer ones.
Maybe this is a possibility to get JDoom to run. But I think not.
Your graphics card is outdated, you need a better and faster one one. Even
the Voodoo2 compatible card I used back then had 16 MB memory.
The best thing is to buy a cheap GeForce2. This one will rock for all Doom
ports and even much bigger games.
Raymond Martineau
wrote:
>I am a major Doom fanatic.
>
>Just installed jDoom with KickStart 2.09 (no models) on my Win98SE desktop
>with DirectX 8.1. It's maxed out at 256K RAM with an AMD-K6 processor with a
>Rage II+ video card maxed out at 4M. Well, it runs all the original Doom
>programs great...
Rage II+ sounds like a very old video card that might not support the
necessary features - you might have to upgrade your video card (or perhaps
your computer.) However, the readme does state it meets the minimum
requirements - most likely the slow rendering is caused byattempting to use
special effects.
>(BTW, my business computer is a 576M P3/650 laptop, but I do not install
>games on it because it interferes with work.)
>
>Direct3D won't initialize, so I selected OpenGL. I got an glBSP error so I
>added the -allowsoftware command option.
The first thing I would check would be the driver - specifically how the
latest and previous drivers change the situation. Another poster said the
reasons at why OpenGL wasn't working - you can read his post for more
information.
Victor
"Grieve" <nos...@nospam.com> wrote in message
news:41ef88dc$0$27058$91ce...@newsreader01.highway.telekom.at...
>
:
> Your graphics card is outdated, you need a better and faster one one. Even
> the Voodoo2 compatible card I used back then had 16 MB memory.
>
> The best thing is to buy a cheap GeForce2. This one will rock for all Doom
> ports and even much bigger games.
I'd like to upgrade my video card, and I appreciate the recommendation. I
don't want a video card that will already tax my computer - I want a video
card that will add real hardware acceleration to my video (not a card that
"requires a Pentium 800" or whatever, which seems to defeat the purpose).
Is a GeForce2 a PCI card that will do that for me?
Victor
Grieve
Ow, you are looking for a PCI card ? GeForce cards for PCI were produced
once as far as I know, but they are no longer. Ebay would be the right thing
to look for it.
Stephen Howe
> with DirectX 8.1. It's maxed out at 256K RAM with an AMD-K6 processor with
> a
> Rage II+ video card maxed out at 4M. Well, it runs all the original Doom
> programs great...
>
> (BTW, my business computer is a 576M P3/650 laptop, but I do not install
> games on it because it interferes with work.)
>
What is the _exact words_ it complains about?
What version of Direct3D are you running on your computer (find DXDIAG.EXE
on your computer and run that to tell).
If it is not the latest you should consider upgrading (particularly if it
has a minor version number of 0 - not usually Microsofts best efforts)
>, so I selected OpenGL. I got an glBSP error...
That is strange. The Doomsday engine now does it is own node building., it
not longer uses glBSP (I complained about the numerous bugs I found with
Hexen, Heretic WADs)
Again, do you have latest OpenGL driver for your card?
SH
Victor
"Stephen Howe" <sjhoweATdialDOTpipexDOTcom> wrote in message
news:41f127f3$0$18116$cc9e...@news.dial.pipex.com...
> > Just installed jDoom with KickStart 2.09 (no models) on my Win98SE
desktop
> > with DirectX 8.1. It's maxed out at 256K RAM with an AMD-K6 processor
with
> > a
> > Rage II+ video card maxed out at 4M. Well, it runs all the original Doom
> > programs great...
> >
> > (BTW, my business computer is a 576M P3/650 laptop, but I do not install
> > games on it because it interferes with work.)
> >
> > Direct3D won't initialize...
>
> What is the _exact words_ it complains about?
> What version of Direct3D are you running on your computer (find DXDIAG.EXE
> on your computer and run that to tell).
> If it is not the latest you should consider upgrading (particularly if it
> has a minor version number of 0 - not usually Microsofts best efforts)
I've looked hard into it, and the issue seems to be that my graphics card
just doesn't fully support Direct3D.
>
> >, so I selected OpenGL. I got an glBSP error...
>
> That is strange. The Doomsday engine now does it is own node building., it
> not longer uses glBSP (I complained about the numerous bugs I found with
> Hexen, Heretic WADs)
>
> Again, do you have latest OpenGL driver for your card?
Probably not.
However, I can run ZDOOM effortlessly - so that is now my DOOM port of
choice.
Sir Robin
wrote:
>glBSP is only the nodebuilding utility that is used by JDoom, it is running
>automatically per default and builds gl-compatible (more precise) nodetables
>for the maps you are playing. These are internal game data and have nothing
>to do with the OpenGL implemented on your system. JDoom would also play
>levels with no gl nodes built, it only would show more rendering errors
>(holes in walls, slime trails ... ). glBSP is the utility to build these gl
>nodes and it should be launched automatically by your JDoom frontend when
>you start a level.
Btw, am I right about JDooM not needing to use glbsp at all nowdays? I
think I read such thing.
***/--- Sir Robin (aka Jani Saksa) Bi-Sex and proud of it! ---\***
**/ email: s...@robsku.NO-SPAM.cjb.net <*> Reg. Linux user #290577 \**
*| Me, Drugs, DooM, Photos, Writings... http://robsku.cjb.net/ |*
**\--- GSM/SMS: +358 41 580 1715 ---/**
Stephen Howe
> just doesn't fully support Direct3D.
I don't really believe that. Direct3D is a fairly fluid standard. If ATI
know that a particular card of theirs does not support a particular feature
(or the feature is buggy), the driver will tell Direct3D and any game on
making a Direct3D inquiry as to what the card supports in terms of features
will get a negative on that particular feature.
>> >, so I selected OpenGL. I got an glBSP error...
To me, this is symptomatic that you are not running with the latest drivers.
If you were, you would probably find that both Direct3D & OpenGL work.
1. Now the latest DirectX is DirectX 9.0c, are you running that?
2. You say you have "Rage II+ video card maxed out at 4M". But Rage II+ is
the chipset.
What is the name of the card? Is it an All-In-Wonder?
If it is, you can get Version 4.10.2420 here:
http://www.ati.com/support/products/pc/rageii/winme/aiwwinmedrivers.html
3. You could try clicking on Start -> Run, Type DXDIAG and click on Ok, and
if it runs,
click on button "Save all Information..." and save DxDaig, a text file to
the Desktop.
Open the file with Notepad, cursor down to section Display Devices and
copy-and-paste this to next message
On one of my PC's (completely crap card, I admit), mine looks like
You can see that I have DirectX 9.0c installed
>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>
------------------
System Information
------------------
Time of this report: 1/24/2005, 04:37:53
Machine name: WINXP1
Operating System: Windows XP Professional (5.1, Build 2600) Service Pack
2 (2600.xpsp_sp2_rtm.040803-2158)
Language: English (Regional Setting: English)
System Manufacturer: Dell Computer Corporation
System Model: OptiPlex SX270
BIOS: Phoenix ROM BIOS PLUS Version 1.10 A03
Processor: Intel(R) Pentium(R) 4 CPU 3.20GHz
Memory: 1022MB RAM
Page File: 241MB used, 2221MB available
Windows Dir: C:\WINDOWS
DirectX Version: DirectX 9.0c (4.09.0000.0904)
DX Setup Parameters: None
---------------
Display Devices
---------------
Card name: Intel(R) 82865G Graphics Controller
Manufacturer: Intel Corporation
Chip type: Intel(R) 82865G Graphics Controller
DAC type: Internal
Device Key: Enum\PCI\VEN_8086&DEV_2572&SUBSYS_01511028&REV_02
Display Memory: 96.0 MB
Current Mode: 1280 x 1024 (32 bit) (60Hz)
Monitor: Plug and Play Monitor
Monitor Max Res: 1600,1200
Driver Name: ialmrnt5.dll
Driver Version: 6.14.0010.3762 (English)
DDI Version: 9 (or higher)
Driver Attributes: Final Retail
Driver Date/Size: 2/10/2004 11:10:08, 36415 bytes
WHQL Logo'd: n/a
WHQL Date Stamp: n/a
VDD: n/a
Mini VDD: ialmnt5.sys
Mini VDD Date: 2/10/2004 11:17:06, 681469 bytes
Device Identifier: {D7B78E66-6632-11CF-2A7D-5B21A3C2CB35}
Vendor ID: 0x8086
Device ID: 0x2572
SubSys ID: 0x01511028
Revision ID: 0x0002
Revision ID: 0x0002
Video Accel:
Deinterlace Caps: n/a
Registry: OK
DDraw Status: Enabled
D3D Status: Enabled
AGP Status: Not Available
DDraw Test Result: Not run
D3D7 Test Result: Not run
D3D8 Test Result: Not run
D3D9 Test Result: Not run
>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>
Stephen Howe
> think I read such thing.
Greetings :-)
You are 100% right.
In SourceForge you will find bug reports on glBSP, by me, mostly to do with
Heretic & Hexen.
I have also complained about it to SkyJake. I think he has removed it (as
unreliable) and the Doomsday engine is directly doing its own node building
now.
In some senses, it is not glBSP's fault. The authors cleaned up glBSP. But
what was discovered is that original WADS like HEXEN.WAD & HERETIC.WAD and
also classic WADS like REQUIEM, ETERNAL, ICARUS etc are "dirty" WADs where
the maps are not 100% pure. It is slightly embarassing to find that ID
Software/Raven and other classic WAD authors did not make 100% pure maps. In
some cases they take advantage of known bugs the in original Doom engines.
So what can the authors of glBSP do? Alter it, so that node builds inpure
maps?
What is really needed is for someone to go over all the classic WADs and
"clean" them up, so that all Doom map rules are followed (if possible) and
so that all node-builders, like glBSP, will be able to build without issing
any warnings. In other words, don't change the map authors original design
intentions but _do_ conver the map from impure to pure.
Stephen Howe