DescentBB

First suggestion, see if you can get ahold of Sekmu (i'll try to track down his email for you) and get into the D1x source as well, so D1x can be improved.

Biggest problems other then a lot of people having trouble running D1x/D2x correctly (main problem, don't have it, others will have to talk about their problems), is joystick support. While both games do eventually work correctly with joysticks such as the 3DPro and PrePro & PrePro2, it takes a LOT of work to try and get these to work properly.

Also, compared to the DOS executables of D1x that don't work with Win2k & XP correctly, both applications have TERRIBLE joystick sensetivity settings and keyboard ramping. Sliding left and right on keys is somewhat OK, still really slow. Turning left and right / looking up and down on the joystick and using the hat on the joystick to slide up and down are a big turnoff.

I'm not really sure what causes this, I imagine all that would need to be done is increase the current sensetivity rate when its at its highest setting because the highest setting just isn't cutting it. There are other things, such as D2x not being able to correctly recognize the axis settings for a joystick to utilize the twist function. We ended up having to make pre-defined joystick .plr files with the correct axis settings already configured using a HEX editor (THX again Jeff! ) and releasing it as a patch on PlanetDescent. This problem should have been identified and fixed early on IMO because the majority of online Descent players have used or do use a joystick.

There are more things that I'm sure I've forgotten at the moment. I was about to go to bed when I saw this. Hopefully this might be a start though. There are plenty of other people here on the DBB who have had other problems that need equal attention. Such as joysticks not being detected period or the application not running at all (which could be a hardware issue). Let the fun begin

Note that D2X completely supports D1 missions. I've seen weird things with some textures when the D1 PIG file is in the D2X directory though.

i had allways 2 problems with any d2x versions, the joystick settings and the sound lagging behind the action, that kept me from using d2x.

for the joystick-settings... hmmm well i am probably on thin ice here but is it really that difficult to read a few analog axis and buttons from direct input and pass it over to d2? who needs the old method of polling the gameport anyway this days?

DigiJo wrote:i had allways 2 problems with any d2x versions, the joystick settings and the sound lagging behind the action, that kept me from using d2x.

for the joystick-settings... hmmm well i am probably on thin ice here but is it really that difficult to read a few analog axis and buttons from direct input and pass it over to d2? who needs the old method of polling the gameport anyway this days?

And becides that, I havnt had a gameport joystick in years, all my precision pros are USB. (it is a royal pain to get em working in D1x or D2x).

My 3Dpro is a standard gameport joy, so I'd like that to be fixed. D2x should also have good support for USB joysticks as well.

The lagging sound issue was fixed a while ago. D2x needed the latest sdl.dll file (Simple DirectMedia Layer) placed in the D2 directory to correctly process the sound. For Those of you having this issue.. http://missions.dyndns.org/downloads/SD ... -win32.zip

might be saner in the long run to exise SDL from the win32 version, and use DX.

especially for controllers.

I believe that was on Valin's agenda for Descent.NET, and IINM TB is planning on reworking D2X with DirectX.

DCrazy wrote:I believe that was on Valin's agenda for Descent.NET, and IINM TB is planning on reworking D2X with DirectX.

I hope you aren't referring to me by that.

I have fixed the crash in the joystick config when assigning handle axis to a control. There is a bug in in joystick_read_raw_axis() from arch/sdl/joy.c:

for (i = 0; i <= JOY_NUM_AXES; i++) axis = Joystick.axes.value;

i is running to far due to the "<=" comparison. It should be "<".

I have managed to create an MSVC project for D2X and build a working D2X executable. It's way smaller than the official one and even has it's first bug fix.

??
Using the D2x source from here?

Lets try to stick to having ONE core project of fixes for D1 and D2 so that when its all said and done there aren't 20587037503 D1Xs and D2Xs with different types of fixes in each different one.

Set the standard. If someone wants to integrate DX coding to help improve D1x and D2x run better in a win32 environment then they should work WITH Diedel or Diedel with them to make sure that everything gels together.

On another note, Diedel, did you get my DBB instant message with Sekmu's email? Hopefully we can get you setup with the D1x source so you can continue the excellent work Sekmu did on improving D1.

There's a lot of D1X code already in D2X.

And last I looked, icculus.org has been working with D2X for awhile. Though I don't know exactly what they're doing right now, if anything. The only problem I currently have with D2X is that I get random crashes in custom SP missions.

Joystick is fully working in my d2x_w32.exe now!

If anybody cares:

The function reading the axis input should have returned a bit field denoting which axis had been moved, but it always returned 0. So the following code never knew the joystick handle had been moved. So simple.

Check my descent site (click on D2X/Windows in the side menu).

holy crap. it actually works..

now what about sound?

can't charge fusion, and the ab sounds like it's pulsing.

Ferno wrote:can't charge fusion, and the ab sounds like it's pulsing.

no one uses fusion anyway....

Yeah, limiting input rate has brought some problems. D2X is ferkin bad programming, heck.

Still want the code I used to enable music? It is a pretty bad implementation, but I'm sure you could improve on it .

Yes, I'd like to have it.

Diedel: Check your mail . Sorry it took so long to get it to you, but I was without power for a couple of days, so I had no Internet access during that time .

The next version of D2X-W32 is available. It can handle repair centers (similar to fuel centers, but replenish shields), which can be added to a mine with DLE-XP.

Next thing I will look into is colored light. If I get this to work, I will try to add new segment types "under water" and "under lava" with bluish and reddish lighting.

Diedel wrote:Update: A new version of D2X-W32 is available, that will display cloaked walls properly (all other versions always paint them black, regardless of their cloak value).

Downloaded it and ran it.
Odd--it isn't fixed. They still render as black.
The level I took the two screenshots from can be found here. The level is called "PTMC City" (pcity.hog/mn2) in the level list.

Yes, my fix was buggy. I have a working version now. I will upload a version where it works this evening (I am on GMT+1).

Oooooh yeah - I got colored segments for underwater and under lava effects ...

I think adding in support for DETLEF32 servers for mission autodownload would be handy. If you need something to do with D2X .

I don't have access to Detlef support source code, and I don't have much time to do big changes to D2X. All I am doing is tinkering around a bit with it.

Are all of these D2X/W32-only features (underwater/underlava lighting etc) backwards-compatible with regular .rl2 files? Like, if I make a D2 level with D2X/W32-specific features, like the shield regenerator cube for example, can that same level be played on regular D2 without the D2X/W32 features? That would be awesome for something like the Descent 2 Revivals.

If not, can you change the file extensions for D2X/W32-only levels to something like .rlx, that way levels with cube types not supported by regular D2 don't crash people's games when they try to load the level?

Repair centers are compatible with all D2-Versions. Water and lava cubes are not necessarily, as I had to introduce new segment type identifiers for it. My changes for D2X-W32 are being integrated into the main D2X development branch, so D2X might be able to cope with them to. I had however D2X w/o some (very minor) modifications for water and lava cubes CTD (because one of the functions check the segment type and end the program when an unknown segment type is encountered). I will try standard D2 with a level and tell you what it does.