Have you seen a bug in D1X-R or D2X-R just give me a small message.
An exact description of the bug would be very helpful.
In case it's a graphical glitch a screenshot could be handy.

Thank you
zico

Getting kind of screen \"flashes\" when picking up powerups.

Again:

An exact description of the bug would be very helpful.
In case it's a graphical glitch a screenshot could be handy.

The original Descent does palette flashes when you pick up a powerup...

Yeah, i guess that \"white fading\" while picking up powerups reminds me strongly to the original DOS Version of the game

On D2 missions with custom MIDIs, the custom music isn't played, but instead the original D2 MIDIs are played. Not sure if it's a bug or just not a feature yet :/

MIDI is not working on Linux. Is this a bug or just not implemented (yet)?

MIDI works on Linux for D1X-R and D2X-R from v0.40.

D2X should play MIDI on AWE (using awsfxload) and MPU401 (using timidity) compatible cards.
The binary of D1X is compiled for AWE support.
To change this to MPU401, grab the source, change WANT_AWE to WANT_MPU in defines.mak and compile again.

I've already thought about to implement new formats to play. OGG will be supportet definetly in a later version.
For MP3 I need to look out because of some license stuff.

well if mp3 is too much of a hassle, don't worry about it and use the .ape format (also opensource).

I'll keep that in mind

Joystick handling needs to be fixed. By default, it refuses to read the throttle or twist on my Logitech Extreme 3D Pro. It reads the hat switch backwards as well (I have the up direction on the hat set to move down in my profile, yet I move up instead. Same goes for the other directions.) Also, when I leave the options menu in-game DXX refuses to read the X and Y axis at all. Even in the options menu. Does the same thing when I complete a level. Also, it crashes when reading a profile created from the previous released version of DXX upon loading a mission post briefing.

_________________
"One spelling mistake can destroy your life. A Husband sent this to his wife : "I'm having a wonderful time. Wish you were her." - @RobinWilliams

The Joystick problem is known. It seems that D1X doesn't currently like Gameport Joysticks. I'll go for more tests in the next weeks. I wish joystick manufacturers would create a standard for these devices... can't be so complicated, works with mouses, too.

The problem with the pilot data you mentioned is also known. As described on the website and in the readme you need to reset resolutions and your controls when updasting from an older version to v0.40.

d1x143_oglmw.exe has no trouble with my stick. In the DXX version, my stick works great when I first make a Pilot... until I try to configure anything. Then I loose it completely. And unfortunately, the 1.43 pilots can't be ported in of course.

My stick is a USB. Siatek Cyborg 3D Gold.

The stick I mentioned is USB as well.

_________________
"One spelling mistake can destroy your life. A Husband sent this to his wife : "I'm having a wonderful time. Wish you were her." - @RobinWilliams

According to the joystick problems. I started a \"collect\"-thread in the DXX-Forums.
It would really help me if you could post information as described there at this place. Y'know I'm not a professional and \"unfortunately I never expected these problems. So any information could come in handy.

Thank you

you can always nick the xl joystick code.

It wouldn't be a problem to get the XL code into D2X-Rebirth. But the D1X Joystick code is a lot different.
So I need to know more precisely information - especially about how your sticks perform in d2x-rebirth.

d1x doesn't like gameport jsticks? thta's wierd, because it works great w/ my 3dpro that's on a gameport.

it's just that d2x gets a little confused when you mix a gameport and usb stick together.

It might be just the way USB interfaces with D1x. I know squat about code and that kinda stuff, but I can test.

The results of that what I currently know are as follows:

D1X makes trouble with random sticks. I suppose many will be caused when selecting other sticks than the normal while the game joystick selection.
D2X only problems seems to be combinations with gameport and USB joysticks while two or more USB sticks together work great.

If it is possible without rewriting the half code i will fix the gameport/usb bug in d2x code and put that code completly to d1x. So everyone should be happy.

Good luck. You'll be amazed how much I have changed. If you don't yet know what a side effect is, you will probably learn it when doing that.

I haven't said that I will implement your code.
But I often do learn from it.
But don't be afraid. I will not \"steal\" anything. As it looks I will solve this joystick stuff on my own if i get the chance to see what's not correct with it.

I don't think Diedel is worried about you using his code. He released it GPL for a reason. As long as you give credit where credit is due, I don't think he'll give you any grief.

_________________
"One spelling mistake can destroy your life. A Husband sent this to his wife : "I'm having a wonderful time. Wish you were her." - @RobinWilliams

zico,

I just pointed out that it might be harder to port it to your version than you might think. Changing some things in D2X-XL required to change a lot of stuff across the entire program.

When using D2X-Rebirth...

1. When saving a game, the screen blanks and a small view of the current position is shown (briefly in the upper left-hand screen corner and then the program compeltely crashes (no error messages). Re-entering the game, the saved game is there and can be used.

2. Overall speed of the Pyro seems a little slower...

this is normal.

Ooookay... Why would that be normal?

Okay a little overview what has been fixed in v0.42, regarding the bugs posted here:

>Getting kind of screen \"flashes\" when picking up powerups.<
Not anymore. The brightness now only affects the game window.

Me and Fernii have worked a bit on the D2X joystick code and it seems making no trouble anymore. It's not implemented in the current release yet but there is a link:
http://dxx-rebirth.de/download/dxx/user ... maxhat.exe
If there are more Joystick problems with D1X or D2x please report it as exact as possible so i will be able to find a fast solution. Best place for such bigger reports would be mail or the DXX forum. It has a whole Bug section.

Crash after Briefings:
This should ONLY happen if you use a pilot from a pre-0.40 version. It's always recommended to create new pilots and configs (delete the old ones) if you upgrade from an older version. If you don't want to do so you could TRY to reset your complete controls config and set a valid resolution in the options menu. This should do the trick.

Pyro moves slower:
Well, compared to D2X-XL the Pyro should move, or better said turn slower. D2X-XL uses keyboard ramping and some other movement improvements i guess while Rebirth uses the \"old\" DOS movement. This could be the difference.

There are no 'movement improvements' in D2X-XL, apart from limiting the input device polling frequency to 40 fps to have equal conditions for all players and to make the mouse work properly. Keyboard ramping slows down the acceleration, but doesn't affect end speed. D2X-XL has been checked with the original D2-Win95. Movement and turn speeds are the same. The only problem was a too high pitch speed (nose up/down), which I have fixed a while ago.

Normal ship behaviour.

It handles the same way as it does in the DOS version.