This is incredible

[karx11erx]

http://stackoverflow.com/questions/7128 ... pen-source



nuff sed.

[pokeman7452]

Go ask in the D2X-XL forum.

He did...

[karx11erx]

So what?

[pokeman7452]

So why tell him to do something he already did?

[Sirius]

Uh... wow. Correct me if I'm mistaken, but isn't stack overflow used to answer programming questions? Like, "why does this compiler error occur and what kinds of bugs in my code should I look for"?

Chances of getting a meaningful resolution out of that avenue seem pretty close to zero. Maybe if someone else saw a similar problem in their own code (has to be a 3D game engine, which makes the pool very small!) and fixed it, but that's a pretty forlorn hope...

[karx11erx]

Exactly my thoughts.

[Aus-RED-5]

You know... after seeing that video he posted.

A LONG time ago.... I had that same problem. However, it was on my old PC - P4 3.4EE, 1Gig memory with EVGA Nvidia 7800 GS 256MB - AGP 8x.
The problem I found to be is this:
The XL install that was on that PC was before v1.14 and I decided to do an update of that install.

I solved that problem by deleting the entire install and by doing a complete re install from the CD. Then re install added features and mandatory files for XL to work properly. Plus it is a MUST that you create a new player profile. The old player profile seems to cause corruptions in it too.

[karx11erx]

Afaik he is using fresh installs and the default player. I cannot reproduce his problem though.

From how it looks I am pretty sure that one of the two threads he has specified D2X-XL to use (via d2x.ini) doesn't work, so half of the visible faces aren't processed.

I have no problem with his bug reports, but what I really don't like is that while guy has no clue what so ever about D2X-XL (and maybe coding in general), he is constantly trying to tell me what is probably wrong with the program where he encounters problems with it.