DescentBB

After the message says "Prepare for Descent" in D2X-W32, it quits. what should I do?

Does it do that with every level?

Diedel wrote:Does it do that with every level?

Yes...

Are there any files with extension ".256" in your Descent folder?

yes, why?

Nope. Them missing would've been an explanation for your problems. Get the D2X version I had uploaded to my Descent site an hour ago or so and try it - maybe it works for you. Unfortunately I cannot reproduce your problem.

Do you have the SDL 1.2.7 set installed in your D2 dir?

This is a sound thing and the kinda crash you're getting smacks of a sound crash.

Sorry, I dont have 1.2.7 on my d2 directory, thanks for the tip

Let me know if installing SDL 1.2.7 helped. If you cannot find it, I can upload the binaries to my Descent site.

it didn't work

Actually the proper SDL DLL is included in my D2X-W32 zip file. I'm afraid I cannot help you then. I just cannot reproduce that bug.

SDL 1.2.8 works with your build too (no reason why not though)

where you getting 1.2.8?

Lastest stable release

http://www.libsdl.org/download-1.2.php

thanks

Dark Falcon wrote:thanks

X2!!!!

You're welcome

Dark Falcon wrote:thanks

I take it the latest dsl helped/fixed your problem?

Garak wrote:You're welcome

Dark Falcon wrote:thanks

I take it the latest dsl helped/fixed your problem?

It gave me an error.

*sweat drop*

Which error?

I will d/l SDL 1.2.8 and incorporate and link it with D2X-W32.

Edit: New version of D2X-W32 compiled and linked with SDL 1.2.8 is online. New SDL DLL is included in the zip file.

Diedel,
Does d2x-w32 write any kind of crash info to a file like stderr or anything? Or is that something the old d2x versions did?

I'm just curious.

Afaik not. The debug version might do that, but only for trapped exceptions (i.e. problems the programmers have foreseen and created some code to test for them and report them if they occur - usually with some assert macro calling a warning or error message. In such a case, you will see a message box on-screen though).

If there is a bug that causes a real crash (i.e. an unhandled exception of some kind), there will be no error logging.

The same is true for problems in the SDL. I e.g. had found at one time that the SDL would spuriously fail to properly initialize the OpenGL subsystem. All the proper arguments were passed to the proper functions, but the OpenGL driver returned an error for some reason I could not figure, resulting in D2X not starting.

The most promising thing would be to set up a development environment on a PC having problems with D2X and debugging it there.

Well, I guess this was about 5 times more than you wanted to know.

Heheh... this is another reason why open-source is so useful.

Except it does rely on the person experiencing the bug to be able to track it down and fix it, and most of them can't...

all true

/damn double post

Dark Falcon wrote:

Garak wrote:You're welcome

Dark Falcon wrote:thanks

I take it the latest dsl helped/fixed your problem?

It gave me an error.

*sweat drop*

Dude, you realize that none of us can read your mind...right? We've got to know what the actual error message is, what hardware you're using, and what you've done to your system. Contrary to popular belief, we cannot pop out of your phone jack and push the magic button that solves all your computer problems.

I think he believes a magic pokemon will fly out of his alss and solve all his problems. It's no wonder he'd believe we can too

You almost made me spill my coffee. That was funny.

Maybe I should create an error message reading "*sweat drop*" ...

Diedel wrote:Maybe I should create an error message reading "*sweat drop*" ...

Tack on an ID10T error while you're at it.

Things are getting increasingly rough here ... which, so I'm afraid, will again inevitably lead to the kind of ... "discussion" ... that made me shun this forum for quite a while.

Please don't ruin this thread.

@Dark_Falcon,

please tell what error message you were given.

it gave me this:

Which doesn't tell us anything. Next time it crashes, click on the link that would show what file it had a problem with.

Diedel: I see sarcasm isn't your strong suit.

What about this one:

That technical information link would probably be of some use too.

*sigh*, is this it?:

copy the text and paste it, so we can see it all

It won't let me copy and paste the text.

MD-2389 wrote:Which doesn't tell us anything. Next time it crashes, click on the link that would show what file it had a problem with.

Diedel: I see sarcasm isn't your strong suit.

I'm not exactly sure that *you* know what sarcasm is. I found your remark a little bit on the rude side.

@Dark_Falcon,

oopsy. I am afraid I cannot help you. This is a "hard" program crash, not D2X running into some assertion, displaying an error message and quitting halfway decently. If however I am wrong and there *is* such a message, please write it down on some piece of paper and quote it here. The probability that I can help you in that case is very high.

You do not happen to live in Germany, do you?

Diedel wrote:

MD-2389 wrote:Which doesn't tell us anything. Next time it crashes, click on the link that would show what file it had a problem with.

Diedel: I see sarcasm isn't your strong suit.

I'm not exactly sure that *you* know what sarcasm is. I found your remark a little bit on the rude side.

@Dark_Falcon,

oopsy. I am afraid I cannot help you. This is a "hard" program crash, not D2X running into some assertion, displaying an error message and quitting halfway decently. If however I am wrong and there *is* such a message, please write it down on some piece of paper and quote it here. The probability that I can help you in that case is very high.

You do not happen to live in Germany, do you?

I'm from America.

Okay, I give up!

Have you tried using the 2.6 version of D2X?