🚀 go-pugleaf

Woo awesome - I've been looking forward to a port!

-- 
R. Halkyard, amateur BOFH
rhalkyard@the-free-mail-service-provided-by-Google.com

I don't get it... what's the difference between the regulary d2x and
d2x-w32?

On 19 Nov 2005 02:11:55 -0800, "ReCover" <recover89@gmail.com> wrote:

>I don't get it... what's the difference between the regulary d2x and
>d2x-w32?

D2X-W32 is the Windows version of Descent.  

Raymond Martineau wrote:
> On 19 Nov 2005 02:11:55 -0800, "ReCover" <recover89@gmail.com> wrote:
>
>> I don't get it... what's the difference between the regulary d2x and
>> d2x-w32?
>
> D2X-W32 is the Windows version of Descent.

More specifically, it's for 32 bit windoze

--
Steveski

Read http://www.descent2.de/d2x.html (english) and be enlightened.
D2X-XL (I renamed the project today) has a lot of bug fixes and way
more features than D2X.

To the ppl wondering why you need another port of D2X to Linux:

D2X-XL has fixed all bugs in D2X and added a plethora of new features
to it (that's why I call it 'XL' ;). Read
http://www.descent2.de/d2x.html (english) for details. :)

karx11erx

"karx11erx" <karx11erx@hotmail.com> wrote in message 
news:1132433794.979225.185020@g49g2000cwa.googlegroups.com...
> Read http://www.descent2.de/d2x.html (english) and be enlightened.
> D2X-XL (I renamed the project today) has a lot of bug fixes and way
> more features than D2X.
>

So D2X-W32's functionality is now a part of D2X-XL? 

Hi everybody,

D2X-XL Linux port is done, and a Mac OS X port is in the works and also
almost done. :)

karx11erx

karx11erx wrote:
> Hi everybody,
> 
> D2X-XL Linux port is done, and a Mac OS X port is in the works and also
> almost done. :)
> 
> karx11erx
> 

Very nice!
It worked straight away on my Mandrake 2000LE system:
KDE Desktop
AMD Athlon XP 2800+
SOYO MoBo
1GB RAM
SB Live! 24bit sound card
nVidia Gforce 6200 (7676 drivers)
Saitek Cyborg 3D Gold USB Joystick

Haven't had a chance to put it through it's paces though.

However, I did notice that it did not create a '$HOME/.d2x-xl'.
Was it supposed to? Or, am I supposed to create it?
If I am, do you have a sample file?
I created a $HOME/.d2x-xl' and it will now
save the Fullscreen setting, for instance.

Also, it does not take new joystick axis settings.
That is to say, that under the Options > Controls > Joystick
it will not notice when I move the joystick.
I can re-assign joystick buttons though.
And, the joystick does work in the game with my old
player axis settings.

Thank you very much for a great new Linux port of one
of my all time favorite games!

-- 
Lance DeVooght

You need to create .d2x-xl yourself and put the desired default
settings to be applied at program start in it.

See my Descent site's D2X section ("Switches") for details.

I will look into the joystick issue.

Current version is 1.5.28, btw. (a few bug fixes and portability
related code fixes)

D2X-XL (formerly D2X-W32) is based on D2X 0.2.6. It has fixed virtually
all bugs still contained in D2X (latest version 0.2.6) and contains a
host of new features. D2X-XL is available for MS Windows, Linux and Mac
OS X. See my Descent site for details.

So to speak.

karx11erx wrote:
> You need to create .d2x-xl yourself and put the desired default
> settings to be applied at program start in it.

Ok.

> See my Descent site's D2X section ("Switches") for details.

Yep, that's just the sort of thing I was looking for.
A few questions though.
On you web page you have:
-gl_texmagfilt <f> set GL_TEXTURE_MAG_FILTER (see readme.d1x)
-gl_texminfilt <f> set GL_TEXTURE_MIN_FILTER (see readme.d1x)

There is no mention of these switches in my copy
of readme.d1x (v1.40), nor on the d1x web site's copy.
Do you have a readme.d1x that says something about this?

You recommend:
-gl_alttexmerge ;use new texmerge, usually uses less ram (default)

But, this is said to be faster. I have 1GB of RAM. Should I use this?
-gl_stdtexmerge ;use old texmerge, uses more ram, but _might_ be a bit
	       ;faster

You recommend:
-gl_reticle 0 ;use OGL reticle 0=never 1=above 320x* 2=always

What do you have against an OGL reticle? Just personal preference?

Care to comment on these other OpenGL/dx1 settings?
-gl_intensity4_ok ;text bitmap format for transparent rendering to
		  ;GL_INTENSITY4
-gl_luminance4_alpha4_ok ;text bitmap format for transparent rendering
			 ;to GL_LUMINANCE4_ALPHA4
-gl_rgba2_ok ;text bitmap format for transparent rendering to GL_RGBA2
-gl_readpixels_ok ;tell D2X whether the graphics driver supports reading
		  ;from the frame buffers
-render_quality <n> ;Set render quality from pixelated (0) to fully
		    ;filtered and mipmapped (3)
-hwsurface ;For possibly a large fps increase with Linux.
-hires_textures ;Use high resolution textures


What are the pros and cons of:
-tmap <t> ;select texture mapping method ('c'|'fp'|'i386'|'pent'|'ppro')
	  ;default: 'c'. 'fp' relies heavily on floating point
	  ;performance. 'i386', 'pent', 'ppro' not available in D2X-XL.

Do you plan to support 'pent', 'ppro' in D2X-XL in the future?

> I will look into the joystick issue.

Thank you.

> Current version is 1.5.28, btw. (a few bug fixes and portability
> related code fixes)

Ok. I will grab that one.
I was using 1.5.27.

Sorry for all the questions at once.
I'm just so excited about this new port!

-- 
Lance DeVooght

"karx11erx" <karx11erx@hotmail.com> wrote in message 
news:1133447493.447942.161260@f14g2000cwb.googlegroups.com...
> So to speak.
>

I'm having a problem with D2X-XL. Ever since about version 1.5.30, the 
screen goes blank if I try to change the cockpit's view windows (Shift+F1 or 
Shift+F2).  It stays blank too, even if I exit and restart the game. (via 
new game, game save, it makes no difference). The only way I can restore the 
screen is if I reinstall the whole game.  The version I had before that 
worked fine (v1.5.27). Any help is appreciated, I would like to run the 
latest version.

System
WinXP Pro, SP2
Intel D865PERL mobo
Intel 3 GHz P4
1 GB PC3200 RAM (2x512)
ATI AIW 9600 Pro graphics card
200 GB WesternDigital ATA100 HD
Thrustmaster Firestorm Dual Analog 2 gamepad

joystick problem fixed.

-tmap option is obsolete (I mean, "pentium pro" optimizations ... these
days are long gone. ;)

Current versions 

Win: 1.5.41, Linux: 1.5.41, OS X: 1.5.40

"Tim" <ixnay@ontheamspay.com> wrote in message
news:G5adnWIEaenoawreRVn-jA@comcast.com...
>
>
> I'm having a problem with D2X-XL. Ever since about version 1.5.30, the
> screen goes blank if I try to change the cockpit's view windows (Shift+F1
> or Shift+F2).  It stays blank too, even if I exit and restart the game.
> (via new game, game save, it makes no difference). The only way I can
> restore the screen is if I reinstall the whole game.

Just an update - I discovered that if I save a copy of my pilot "PLR" file, 
before I attempt to cycle the cockpit windows, I can restore the blank 
screen by replacing the plr file with the backup. I don't have to reinstall 
the whole game. However, I still can't cycle the cockpit windows without the 
whole screen going blank again.

This problem is probably due to a bug that caused screen resolution to
be changed when viewing the automap, both in fullscreen or in a cockpit
window. That bug had been fixed already, reappeared, and now squashed
again.

Pls make sure to check my web site and the D2X history and to get the
most recent version before posting bug reports. :)

"karx11erx" <karx11erx@hotmail.com> wrote in message
news:1134169681.848021.85800@o13g2000cwo.googlegroups.com...
> This problem is probably due to a bug that caused screen resolution to
> be changed when viewing the automap, both in fullscreen or in a cockpit
> window. That bug had been fixed already, reappeared, and now squashed
> again.
>

Thanks for your reply. I posted this issue when version 1.5.40 was released 
and that's the one I tested before posting my message.  I have since 
downloaded the latest version (1.5.44) and the problem is fixed, however, 
the screen resolution setting isn't staying set.  It keeps reverting to 
640x480 whenever I relaunch the game (I had it set for 1280x1024). I am 
using the latest graphics card drivers.

> Pls make sure to check my web site and the D2X history and to get the
> most recent version before posting bug reports. :)
>

I always do :)  Regardless, I'm only posting an issue I'm having, I don't 
presume anything is a bug until its verified.

Tim
--
System
WinXP Pro, SP2
Intel D865PERL mobo
Intel 3 GHz P4
1 GB PC3200 RAM (2x512)
ATI AIW 9600 Pro graphics card
200 GB WesternDigital ATA100 HD
Thrustmaster Firestorm Dual Analog 2 gamepad

"Tim" <ixnay@ontheamspay.com> wrote in message 
news:3-udnVX6CIW_pAfeRVn-gQ@comcast.com...
>
> Thanks for your reply. I posted this issue when version 1.5.40 was 
> released and that's the one I tested before posting my message.  I have 
> since downloaded the latest version (1.5.44) and the problem is fixed, 
> however, the screen resolution setting isn't staying set.  It keeps 
> reverting to 640x480 whenever I relaunch the game (I had it set for 
> 1280x1024). I am using the latest graphics card drivers.
>

I realize that your web site notes a potential problem with ATI cards 
changing resolutions, I only mention it because the screen resolution 
settings used to stay set when I used D2X-XL v1.5.27. 

I bet you have enabled screen resolution override in the d2x-xl ini
file ('-640x480').

"karx11erx" <karx11erx@hotmail.com> wrote in message 
news:1134223768.472483.163160@g47g2000cwa.googlegroups.com...
>I bet you have enabled screen resolution override in the d2x-xl ini
> file ('-640x480').
>

Such an entry exists but I didn't enable anything, nor have I found any 
documentation about it. Has this entry been added since version 1.5.27? 

"Tim" <ixnay@ontheamspay.com> wrote in message 
news:5dednYj8_KXwgQbenZ2dnUVZ_sudnZ2d@giganews.com...
>
> "karx11erx" <karx11erx@hotmail.com> wrote in message 
> news:1134223768.472483.163160@g47g2000cwa.googlegroups.com...
>>I bet you have enabled screen resolution override in the d2x-xl ini
>> file ('-640x480').
>>
>

Thanks, btw.  After commenting this line out the game is now flawless, it 
has never run better. 

I didn't mean to blame you for enabling it. It was merely a hint. Glad
you're happy now. :)

"karx11erx" <karx11erx@hotmail.com> wrote in message
news:1134342071.204337.260480@g47g2000cwa.googlegroups.com...
>I didn't mean to blame you for enabling it. It was merely a hint. Glad
> you're happy now. :)
>

Thanks, I'm glad it works well now :)