[d1x/d2x 0.60 beta 2 - Windows] Game won't launch
#1
I've followed install instructions. Both D1 and D2 have necessary GOG files copied over. My GOG versions launch in DOSBOX and work fine.

Windows 10 x64 bit
Nvidia GTX 1080

There is nothing in stderr.txt nor stdout.txt. Launching from a command line, there is no output. It just never really launches. Turning on options for -debug -verbose and even -safelog do nothing.

Neither d1x-rebirth.exe nor d2x-rebirth.exe will launch. Compatibility options in Windows 10 don't help either.

Threads here:

https://forum.dxx-rebirth.com/archive/in...d-877.html

and here:

https://www.mtbs3d.com/phpbb/viewtopic.php?f=3&t=14979

Suggest you may need a replacement opengl32.dll file in the folder, but neither work. And I have a device with working OpenGL (Nvidia GTX 1080 with the latest drivers)

But even the NoGL versions (d1x-rebirth-nogl) won't launch, so it doesn't appear to have to do with OpenGL.

This is what appears in the Windows Event Viewer:

Faulting application name: d1x-rebirth.exe, version: 0.0.0.0, time stamp: 0x5ad29161
Faulting module name: ntdll.dll, version: 10.0.17754.1, time stamp: 0xcee84e63
Exception code: 0xc0000005
Fault offset: 0x0004f1e5
Faulting process id: 0xa794
Faulting application start time: 0x01d44e2b8914dff8
Faulting application path: D:\Games\D1X-Rebirth\d1x-rebirth.exe
Faulting module path: C:\WINDOWS\SYSTEM32\ntdll.dll
Report Id: f8874862-b2e4-4eab-a92b-6240c46a87fe
Faulting package full name: 
Faulting package-relative application ID:
Reply
#2
d1x-rebirth_v0.58.1-win however launches just fine.
Reply
#3
Thank you for providing the Windows Event Viewer data. As I read that, it is blaming a system library (ntdll.dll) for an invalid memory access. Unfortunately, there is nothing I can do about it with the information provided. Such crashes in ntdll.dll are usually an indication of memory corruption elsewhere, which only became fatal when ntdll.dll tried to use the corrupted memory. Unless you can trace the memory corruption to its source, I cannot fix the source (and the source may not even be under my control, if it comes from some other library on your system, such as your graphics driver). At this point, all I can offer is that other people have run the game without this problem, from that build. Presumably, some of them are on Windows 10.

Have you ever run that build successfully on any Window 10 machine? If so, how do the systems differ? Can you reboot into a different version of Windows and test whether the game runs there?

[This response cross-posted to issue you opened on Github. There's no need to post so many places. I read them all.]
Reply
#4
I'll try on another Windows 10 machine, but I was looking to get started with Descent (never played it before).

0.60 beta 2 was the first version I tried. Then I went back to 0.58 and that one launches just fine.

I've rebooted and tried 0.60 beta 2 again, and still nothing.
Reply
#5
Yes, it's weird that the older one launches fine. There are extensive changes between those builds, but none that I would expect to matter here. I'm not the one who built any of those though. You'd need to ask AFP about 0.60-beta2. I don't recall who built 0.58.1.

I'd suggest also trying a Windows machine that is not Windows 10, as well as try a Windows 10 of a different patch level. As the GOG page says for all their Windows games:
Code:
Please be advised that Windows 10 operating system will receive frequent hardware driver and software updates following its release; this may affect game compatibility
I don't test on Windows 10 at all.
Reply
#6
Hi,

Both the v0.60 04/14/18 and the v0.60 BETA 2 do not work anymore for me.

Tested on 2 different computers, both running Windows 10 v1809. Both with AMD graphic cards.

Windows Event Manager generates an error in ntdll.dll each time I try to run the game.

v0.58.1 works fine though.

Last time I played Descent was about 2-3 months ago and there it ran just fine.
Reply
#7
When it ran fine for you back then, were you using the same 0.60 betas? AFP hasn't posted new builds in months, so if you're relying on those, the only thing you could have changed is Windows system state. I tried running a recent build in a Windows 10 guest and it worked fine. I don't recall what Windows build it had.
Reply
#8
Yeah it was the same dxx-rebirth installation that ran fine before.

Pretty much the only meaningful things changed since then would be the update of Windows 10 from 1803 to 1809. And AMD graphic driver updates.
Reply
#9
Since it once worked for you, and now does not, that strongly suggests that a change in Windows broke it. Without more information, I cannot determine whether this is a Windows bug provoked by Rebirth or a Rebirth bug provoked by Windows. Rebirth is relatively light on its graphics requirements, so I would expect a core system change to be at fault.

I cannot reproduce the fault in a Windows 10 virtual machine, and have no real hardware running Windows 10, nor any hardware I can convert to Windows 10. I need more information before I can do anything to help you. Working steps to reproduce the crash would be ideal. Failing that, if you can identify specifically what change breaks it, I can try to reason about why the changed version is broken. The distinction between 0.58.1 and 0.60.x is interesting, but not nearly specific enough. There are thousands of commits between those two builds. The build environment itself was also changed in the three years between those builds, so a bad interaction with the build tools is also possible.
Reply
#10
Hi,

so I have tested out Descent1 on a third computer. Now there is no mentioning of ntdll.dll but it still does not work:

OS: Windows 10 Home 1803
Graphics: Intel HD Graphics 2000
v0.58.1: no issues
v0.60 BETA 2: Application Hang on Interplay Logo
v.060 04/14/18: Application Hang on Interplay Logo


Code:
Protokollname: Application
Quelle:        Application Hang
Datum:         18.11.2018 16:51:59
Ereignis-ID:   1002
Aufgabenkategorie:(101)
Ebene:         Fehler
Schlüsselwörter:Klassisch
Benutzer:      Nicht zutreffend
Computer:      xxx
Beschreibung:
Programm d1x-rebirth.exe, Version 0.0.0.0 kann nicht mehr unter Windows ausgeführt werden und wurde beendet. Überprüfen Sie den Problemverlauf in der Systemsteuerung "Sicherheit und Wartung", um nach weiteren Informationen zum Problem zu suchen.
 Prozess-ID: 2ab8
 Startzeit: 01d47f5690c47102
 Beendigungszeit: 1739
 Anwendungspfad: D:\Descent\d1x-rebirth.exe
 Berichts-ID: 3f196aba-645a-40ed-8714-0554ab428b29
 Vollständiger Name des fehlerhaften Pakets:
 Auf das fehlerhafte Paket bezogene Anwendungs-ID:

Ereignis-XML:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
  <System>
    <Provider Name="Application Hang" />
    <EventID Qualifiers="0">1002</EventID>
    <Level>2</Level>
    <Task>101</Task>
    <Keywords>0x80000000000000</Keywords>
    <TimeCreated SystemTime="2018-11-18T15:51:59.400102900Z" />
    <EventRecordID>16756</EventRecordID>
    <Channel>Application</Channel>
    <Computer>xxx</Computer>
    <Security />
  </System>
  <EventData>
    <Data>d1x-rebirth.exe</Data>
    <Data>0.0.0.0</Data>
    <Data>2ab8</Data>
    <Data>01d47f5690c47102</Data>
    <Data>1739</Data>
    <Data>D:\Descent\d1x-rebirth.exe</Data>
    <Data>3f196aba-645a-40ed-8714-0554ab428b29</Data>
    <Data>
    </Data>
    <Data>
    </Data>
    <Binary>55006E006B006E006F0077006E0000000000</Binary>
  </EventData>
</Event>
Reply


Forum Jump:


Users browsing this thread: 1 Guest(s)