[Game crashes on startup]

23 hours ago, elexis said:

Main Menu -> Tools & Options -> Settings (or was it called Options?). Or copying stuff from default.cfg to user.cfg at wiki/GameDataPaths if you're into that. But mostly try to disable GLSL. If that doesn't already solve it, I'd rather investigate where it crashes.

Um, unfortunately disabling GLSL and/or setting everything to minimum/maximum/custom doesn't help (if sometimes GLSL is causing crashes, why does the tooltip recommend using it?). 0 A. D. seriously do not like that hardware. So I'll have to dive into debugging. Since the PC isn't actually mine but from a friend of mine, I'll have to convince him to install VS13 - this will probably take a few days

the numa.h crash just seems to be the first sign of the underlying problem (game crash at loading a game) - and it has to do with memory size/allocation. I'll probably check if the numa-thing is connected with the strange output in the system_info.txt regarding RAM properties...

On 6.9.2017 at 9:20 PM, elexis said:

You can write a bugreport linking to this topic at https://trac.wildfiregames.com/, but as long as you're the only one affected and noone cares about the performance database, killing bugged useless code  sounds perfectly fine to me.

Yeah, I will do this - but first I want a running 0 A. D. version. Maybe the problem isn't actually caused by this lines but by something in a lower layer (i. e. memory allocation)

Right now I'm really focused on that memory thing without knowing that much about it - but to me it seems to be the most probable reason...

[Game crashes on startup]

Pyrogenesis survived startup now!

I've deleted all three "numa_"-lines (313-315) and 0 A. D. is starting now (first couple of times it crashed while loading fonts and textures, but then it worked). It also created a nice system_info.txt - where I noticed that HWdedect seems to have a problem with DDR4 RAM - i've got only 1 8GB module but it lists four (see appendix).

For testing purposes I've skipped RunHardwareDetection() completely then (by adding a return statement as suggested) and 0 A. D. is behaving completely same. What means that those three lines are causing that error. Now I'm very interested in what this numa_-thing should actually do (starting with the question what numa should mean). Any idea?

 

Unfortunately 0 A. D. still crashes if I try to start a game. It shows the map select menu but as soon as I hit play everything freezes after a second with a half-loaded map loading screen and windows displays it's obligatory "this program has stopped working" message. Sadly no crashlog file gets generated and the mainlog shows 0 errors (last entries are loading messages of simulation scripts).

Thats pobably what you meant with

On 4.9.2017 at 4:57 PM, elexis said:

you might have to test which graphics settings work with your graphics card and driver at worst

Where can I change that (I guess its some kind of textfile)?

Thanks,

Luke

system_info.txt

[Game crashes on startup]

21 hours ago, elexis said:

So you could try to delete this one line from the stacktrace that induces the crash (i.e source/ps/GameSetup/HWDetect.cpp 313)

 

Did so, recompiled everything and - it still crashes. Now at the next line in HWDetect (which has become line 313 since I deleted the orignal one). I've appended the crashlog.

BTW: you may update the wiki links for downloading VS 2013. The second link is totally broken and the first one points to the VS17 site. You may consider inserting this link: http://download.microsoft.com/download/7/2/E/72E0F986-D247-4289-B9DC-C4FB07374894/wdexpress_full.exe  (taken from here)

I'll probably try disabling the hardware detection completely, but at least to me this doesn't sound like a real solution

 

crashlog.txt

[Game crashes on startup]

Wow! Thanks for your fast response! I haven't thought that I would get an reply that fast.

12 hours ago, elexis said:

Can you try previous versions of 0AD and see if that breaks too?

I'd test for r 19876. If that crashes too, could try Alpha 21 release (see Changelogs for the revision IDs).

Tested r19876 and r18915 (Release of Alpha 21), both crashed as well - but quite differently to the actual version

Both old versions created slightly differrent log outputs (not counting different adresses), see attachments...

(Now you've got the machine name :D)

 

Anything else I should test / upload??

crashlog_r18915.txt

crashlog_r19876.txt

[Game crashes on startup]

First of all: I'm new to this forum so I am probably posting things in the wrong forum or whatever. Apologize for any mistake

Originally I wanted to create a ticket on trac, but unfortunately I never recieved a trac account activation email so I am not able to do so...

 

Concerning my orignial problem: 0 A. D., Release 22 and the (currently) newest svn version 20096 crashes on startup. It displays a black screen and then a window of the error handler. I appended the generated crashlog of the svn version, the Release 22 crash is almost identical (can upload this as well if needed). The "interesting log" file is empty and the "mainlog" file shows just the configuration settings (maybe this is intended?).

I guess the error is caused by faulty hardware detection, but I am no expert.

You may be interested in my hardware (created with dxdiag):

Spoiler

------------------
System Information
------------------
      Time of this report: 9/2/2017, 12:12:21
             Machine name: //Should not be interesting ...
               Machine Id: //Should not be interesting ...
         Operating System: Windows 10 Home 64-bit (10.0, Build 15063) (15063.rs2_release.170317-1834)
                 Language: German (Regional Setting: German)
      System Manufacturer: System manufacturer
             System Model: System Product Name
                     BIOS: BIOS Date: 03/20/17 11:22:44 Ver: 05.0000C
                Processor: AMD Ryzen 5 1600 Six-Core Processor             (12 CPUs), ~3.2GHz
                   Memory: 8192MB RAM
      Available OS Memory: 8120MB RAM
                Page File: 2903MB used, 7711MB available
              Windows Dir: C:\Windows
          DirectX Version: DirectX 12
      DX Setup Parameters: Not found
         User DPI Setting: Using System DPI
       System DPI Setting: 96 DPI (100 percent)
          DWM DPI Scaling: Disabled
                 Miracast: Available, with HDCP
Microsoft Graphics Hybrid: Not Supported
           DxDiag Version: 10.00.15063.0000 64bit Unicode

Hope you may help

crashlog.txt