D2X-XL Bug Reports - MS Windows
Moderators: Grendel, Aus-RED-5
HELP!!
I downloaded D2X 1.5.123 the other day... and several things are messed up.
- Whenever I use Shift+F1 or Shift+F2 to cycle my cockpit monitor views, I lose the ability to change my weapons manually. The only changing that will occur is via autoselect, which I usually have disabled.
- The mouse controls seem too \"fluid\" if you will; I stop moving the mouse and the ship coasts a bit farher into the turn. It almost feels like trying to fly with a joystick, which I *despise* (I'm horrible with a js, so sue me) And now that I think about it, it might not be simply the mouse controls but everything in the game. It's TOO smooth; its lost some of the original feel and my gameplay is suffering because of it.
- The briefings stutter. The robot movie \"pauses\", a character of the description appears, a character beep goes off, the movie plays a frame, and it repeats. Very, very, annoying. Definitely broken; it used to work fine. I'm running in 1152x864 if that matters.
- The game crashes if I attempt to specify any commandline parameters--HOWEVER--this *might* be my machine. I havent noticed it with any other programs, and D1X still works fine this way--I reinstalled Visual studio recently and im constantly getting debug errors and crashes where i didn't used to... so this one might be a false alarm. The top 3, however, WERE ok before i updated D2X-XL.
I downloaded D2X 1.5.123 the other day... and several things are messed up.
- Whenever I use Shift+F1 or Shift+F2 to cycle my cockpit monitor views, I lose the ability to change my weapons manually. The only changing that will occur is via autoselect, which I usually have disabled.
- The mouse controls seem too \"fluid\" if you will; I stop moving the mouse and the ship coasts a bit farher into the turn. It almost feels like trying to fly with a joystick, which I *despise* (I'm horrible with a js, so sue me) And now that I think about it, it might not be simply the mouse controls but everything in the game. It's TOO smooth; its lost some of the original feel and my gameplay is suffering because of it.
- The briefings stutter. The robot movie \"pauses\", a character of the description appears, a character beep goes off, the movie plays a frame, and it repeats. Very, very, annoying. Definitely broken; it used to work fine. I'm running in 1152x864 if that matters.
- The game crashes if I attempt to specify any commandline parameters--HOWEVER--this *might* be my machine. I havent noticed it with any other programs, and D1X still works fine this way--I reinstalled Visual studio recently and im constantly getting debug errors and crashes where i didn't used to... so this one might be a false alarm. The top 3, however, WERE ok before i updated D2X-XL.
Re:
Thanks. =)Diedel wrote:A tracker allows for up to 80 entries, so I have expanded the game selection menu appropriately.
Ah. I was wondering what was causing that. =)D3Phoenix wrote:- Whenever I use Shift+F1 or Shift+F2 to cycle my cockpit monitor views, I lose the ability to change my weapons manually. The only changing that will occur is via autoselect, which I usually have disabled.
Did you play D2 back in the DOS days? Does it feel different from standard D2 or just different from D3?D3Phoenix wrote:- The mouse controls seem too "fluid" if you will; I stop moving the mouse and the ship coasts a bit farher into the turn. It almost feels like trying to fly with a joystick, which I *despise* (I'm horrible with a js, so sue me) And now that I think about it, it might not be simply the mouse controls but everything in the game. It's TOO smooth; its lost some of the original feel and my gameplay is suffering because of it.
Let me rephrase that... smooth as in I keep gliding too far. Yes, all of the descents you do not stop instantly due to inertia. Common sense. But for some reason with the last update the ship continues gliding for rediculous amounts... about the width of a normal sized cube. when im turning and stop the mouse movement, i usually rotate about an extra 20 degrees or so. It's wierdness... I've tried adjusting sensitivity and keyboard ramping controls to no avail. The \"fluid physics\" option seems to have SOME effect, but not much. I'll try recreating my pilot profile. That has fixed controller issues in the past; perhaps this is related to the Shift+F1/F2 problem. I'll check back in later.
Ok, remade profile and it fixed the mouse issue for some reason; I think that profile had been around since D2X-W32 and I han't updated D2X-XL in a long time, so that could explain it to some degree.
I still lose the ability to change weapons (1 thru 0).
Here are details...
-Glitch occurs after I use Shift+F1 or Shift+F2 to rotate into the first RADAR view mode. I do not lose functionality on rear view, which comes up first. OR AFTER I ENTER AUTOMAMP. Didn't notice that at first.
-I can still rotate weapons with Z or X, my \"Cycle weapon\" keys for primaries and secondaries, respectively -- but I still prefer the numerical selection.
-Advancing to the next level or a secret level does not correct the problem.
-Quitting to the main menu does not resolve the issue.
-What DOES resolve the problem is COMPLETELY exiting D2X-XL. Relaunching the EXE will allow me to agian cycle my weapons, PROVIDED THAT RADAR view was NOT enabled when I closed it out. If radar view was enabled, then it comes up by default again. I must turn off radar view, exit the game, and restart it in order to get my weapons controls back.
-Resolution changes have no effect.
-Disabling the cool new menus ( Waaa... ) solved the briefing issue as you said it would, but it had no effect on the Shift+F1/F2 situation.
Sooo.... Automap has finally cracked and gone insane... It just couldn't take all the changes to the main game and got jealous and decided to start eating controls every chance it gets. Maybe you should give it textures... ... a little something to boost its self-esteem, lol.
MY HYPOTHESIS:
Something is broken with the code in Automap that watches the buttons for marker selections. OR in the code that loads the automap.
Whatever it is, its broken on my end, and apparently other people have troubles with it too. (Suncho) In the interim I'm making notes on my forehead to make sure to back up D2X-XL before updating it from now on, lol -- just in case. Hopefully this can be fixed with the next update, suff always is...
I find it amazing that you keep up the motivation to work on this huge of a project. *round of applause for Diedel*
I still lose the ability to change weapons (1 thru 0).
Here are details...
-Glitch occurs after I use Shift+F1 or Shift+F2 to rotate into the first RADAR view mode. I do not lose functionality on rear view, which comes up first. OR AFTER I ENTER AUTOMAMP. Didn't notice that at first.
-I can still rotate weapons with Z or X, my \"Cycle weapon\" keys for primaries and secondaries, respectively -- but I still prefer the numerical selection.
-Advancing to the next level or a secret level does not correct the problem.
-Quitting to the main menu does not resolve the issue.
-What DOES resolve the problem is COMPLETELY exiting D2X-XL. Relaunching the EXE will allow me to agian cycle my weapons, PROVIDED THAT RADAR view was NOT enabled when I closed it out. If radar view was enabled, then it comes up by default again. I must turn off radar view, exit the game, and restart it in order to get my weapons controls back.
-Resolution changes have no effect.
-Disabling the cool new menus ( Waaa... ) solved the briefing issue as you said it would, but it had no effect on the Shift+F1/F2 situation.
Sooo.... Automap has finally cracked and gone insane... It just couldn't take all the changes to the main game and got jealous and decided to start eating controls every chance it gets. Maybe you should give it textures... ... a little something to boost its self-esteem, lol.
MY HYPOTHESIS:
Something is broken with the code in Automap that watches the buttons for marker selections. OR in the code that loads the automap.
Whatever it is, its broken on my end, and apparently other people have troubles with it too. (Suncho) In the interim I'm making notes on my forehead to make sure to back up D2X-XL before updating it from now on, lol -- just in case. Hopefully this can be fixed with the next update, suff always is...
I find it amazing that you keep up the motivation to work on this huge of a project. *round of applause for Diedel*
Re:
I rebooted my computer, and now setting the gl_reticle back to 0 doesn't affect AA anymore (why this happened, I don't know). Still, I get the same funny AA effect I mentioned above.Diedel wrote:afaik AA in D2X-XL depends on the driver settings. D2X-XL does nothing here. I need to check how gl_reticle can affect this. It shouldn't at all. gl_reticle only enables drawing the reticle using OpenGL line functions instead of using the bitmapped reticles that come with D2.
This is quite strange, since any level of AA I adjust (either in in-game settings or Display Properties) works fine in other games I played (Half-Life 1 or 2, Unreal/Unreal Tournament, Doom III, Serious Sam 2, Doomsday, etc), but has little or no effect for D2X-XL.
@Neumaennl: same bug I'm seeing. If you have GDB installed you can use the workaround I posted to get through the reactor room without crashes. At least it's not just me.
@Phoenix, Diedel: I also noticed this, but thought it was a Litestep issue, not a Descent one. Nice to know it's fixed.
@Diedel: Savegames.
[Edit]
Upgraded to .126. Observations:
- exiting the mine music now plays (thank you)
- mine exit textures are still wrong (they're now a sort of dense white-grey hatchwork?) but much less jarringly so; it's plausibly a mine exit now
- fan in level 1 plays correct sound now
- briefing music plays
- however, the intro still has the fan going in the background, and the inter-mission briefings the grinding squeaking noise
- purple spawnwebs in D1 still cause SIGFPE; faulting address is now 0x0041e818 rather than 0x0041de68
@Phoenix, Diedel: I also noticed this, but thought it was a Litestep issue, not a Descent one. Nice to know it's fixed.
@Diedel: Savegames.
[Edit]
Upgraded to .126. Observations:
- exiting the mine music now plays (thank you)
- mine exit textures are still wrong (they're now a sort of dense white-grey hatchwork?) but much less jarringly so; it's plausibly a mine exit now
- fan in level 1 plays correct sound now
- briefing music plays
- however, the intro still has the fan going in the background, and the inter-mission briefings the grinding squeaking noise
- purple spawnwebs in D1 still cause SIGFPE; faulting address is now 0x0041e818 rather than 0x0041de68
- Aus-RED-5
- DBB Friend
- Posts: 1604
- Joined: Fri Apr 23, 2004 7:27 am
- Location: Adelaide, South Australia
- Contact:
Re:
On page 49. This has been reported already.devourer wrote:found a bug in the D1 missions: when entering the reactor room in level 4 in D1, the game crashes and exits to windows. it occures since one of the latest upgrades, 1.5.222 i guess
Thanks though. Its good to know that you're not the only one running into this bug.Neumaennl wrote:I downloaded v1.5.124 (although it says 1.5.123 when I start the game) and everytime I enter the reactor room of D1 Level 4 the game crashes. Savegame
and the outer texture of the exit tunnel on every D1 Level is garbled - it shows the PTMC logo
I'm sure Diedel is looking into this prob.
Re:
Litestep is an alternative shell for Windows...kind of like KDE/Gnome for LinuxDiedel wrote:What is Litestep?
Re:
fine...ya want one?Diedel wrote:Dang - you scared me! I thought "oh no, not another bug report!"
Thx for the info.
Steps to reproduce:
1) At main menu, click on Single Player Game
2) click on either starting a D1 or D2 game
3) when it asks you to input the level you want to start at, hit ESC to get back to the main menu
4) When you enter the Single Player Game menu again, there is now a listbox with the clickable contents '[...]' in it. When you click it, you can now continue on to selecting the game you want to play
Other than that and that cube lighting problem I mentioned earlier, that's about it
@Kirby: I noticed this once, but it seemed sporadic to me; didn't pay that much attention.
@Diedel -- don't worry about the mouse 'super-glide' thing; I think i just had a screwed up player profile. I don't update D2X-XL often, and this last version was a couple months old. I redid my player profile, replaced the dlls, and some other stuff... something fixed it... not sure what, but it wasnt a prob. With D2X-XL.
@Diedel -- don't worry about the mouse 'super-glide' thing; I think i just had a screwed up player profile. I don't update D2X-XL often, and this last version was a couple months old. I redid my player profile, replaced the dlls, and some other stuff... something fixed it... not sure what, but it wasnt a prob. With D2X-XL.
@Diedel,Kirby: LiteStep can also be used in parallel with explorer.exe, as opposed to instead of it - that's how I'm using it. Windows desktop, start menu, and taskbar, but with Litestep providing hotkeys, multiple desktops, and the system monitor.
I was worried that LS might be grabbing keystrokes meant for D2X (which has happened before with older versions of LS), but as it turns out that's not the case.
I was worried that LS might be grabbing keystrokes meant for D2X (which has happened before with older versions of LS), but as it turns out that's not the case.
Re:
I'm getting this one too. Version 1.5.128.Kirby wrote:Something strange with the sound in D1 Level 1...
The room where the Red key is stored....I keep on hearing the "cloak on" SFX, even when no robots are in sight. This does not happen in any other part of the level...just that one room :/
Also in version 1.5.128:
#1: When I select to play a movie from the main menu, the music never starts playing again after the movie finishes.
#2: When I select to play a movie from the main menu, the mouse cursor remains visible on top of the movie.
EDIT: Also in version 1.5.128...
#3: The "show movie subtitles" toggle in the rendering options menu always stays the same as the "high movie quality" toggle. If I uncheck it and "high movie quality" is checked, it becomes checked again when I open the menu.
EDIT: Also in version 1.5.128...
#4: The texture on the mine shaft when I escaped the mine appears to be a sky texture (purple with stars).
#5: After I beat level 1, during the level 2 briefing screen, I hear a robot sounds repeating over the music. I pressed escape to skip the post-game screen.
#6: The movies don't really look very good at 2048x1536 resolution. What about changing the resolution to 640x480 when playing back movies? (this might be more of a suggestion)
EDIT: Version 1.5.128
#7: When I exit the mine in D1 level 1, the screen turns black instead of showing me the explosions from a first person perspective. The full rendering doesn't reappear until it switches to the third-person camera.
#8: If I start a D1 game, exit out, then start a D2 game, the Door texture in D2 appears as a blown-out switch:
EDIT: Also 1.5.128
#9: In Descent 1, when I type "frametime" to display my framerate, it calls me a cheater and takes all my shields and energy.
#10: When I record a demo, the playback is kind of jittery.
Looks like I'm not hallucinating. I destroyed a Fox, then two another Fox spawned. I destroyed a Lou, then a Bulk Destroyer spawned.
BTW these things happens in Terrafrost Catacombs (level 16).
Edit: and another: if I kill a mini-boss (the one looks like the system 1 boss, but smaller and orange), three Smelters spawned...
BTW these things happens in Terrafrost Catacombs (level 16).
Edit: and another: if I kill a mini-boss (the one looks like the system 1 boss, but smaller and orange), three Smelters spawned...
I don't trust your computer and your data anymore. I want this confirmed by another player. Please don't take it personally.
Btw, you can use DLE-XP's robot tool to check whether a certain robot in a certain level could actually spawn other robots.
Suncho,
most things fixed in v1.5.129. You can also press Alt+R to toggle frame rate display. Jittery demo playback is there as long as I can remember - don't ask me where it comes from.
Btw, you can use DLE-XP's robot tool to check whether a certain robot in a certain level could actually spawn other robots.
Suncho,
most things fixed in v1.5.129. You can also press Alt+R to toggle frame rate display. Jittery demo playback is there as long as I can remember - don't ask me where it comes from.
Re:
I'm not using any cheats.Suncho wrote:Escorter, do you have a 100% reproducible case that's easy to get to possibly using cheats? If so, I can go test it myself.