Jump to content

0 A.D. 0.0.24b-alpha crashes under Windows 10


Recommended Posts

In VS 2017, I selected 'Release' and 'Win32', but I see that instead of 'Win32' I could also set a new environment for 64bit. Is it possible and does it make sense to build for 64bit?

Link to post
Share on other sites
  • Replies 124
  • Created
  • Last Reply

Top Posters In This Topic

Top Posters In This Topic

Popular Posts

Well it seems that once again Intel had a driver bug :/ and that somehow we fixed it, and they fixed it on their end...

Ah, ok, thanks for your clarification. I will hopefully be able to help identifying the trigger. I will test this on Monday/ Tuesday. Have a good start into the new week.

Hey guys, I just wanted to let you know that I have not given up learning to understand how this all works. It just takes ... I just started from scratch again and will check throughout this week

Posted Images

8 minutes ago, Ceres said:

In VS 2017, I selected 'Release' and 'Win32', but I see that instead of 'Win32' I could also set a new environment for 64bit. Is it possible and does it make sense to build for 64bit?

It's possible and ir could make sense however you're gonna have to rebuild a lot more things than just the game.

  • Thanks 1
Link to post
Share on other sites
Posted (edited)

Ok, I see. Thank you! (still waiting for the 32bit build process to end...)

Now I built Alpha XXV: Y--- from GitHub and will see what I find out with bisect...

Edited by Ceres
Link to post
Share on other sites

I cannot execute 'update-workspaces.sh' when bisecting:

master@HP-PC MINGW64 ~/Documents/0AD/0ad (master)
$ git bisect start --term-old broken --term-new fixed

master@HP-PC MINGW64 ~/Documents/0AD/0ad (master|BISECTING)
$ git bisect fixed master

master@HP-PC MINGW64 ~/Documents/0AD/0ad (master|BISECTING)
$ git bisect broken A24b
Bisecting: 1308 revisions left to test after this (roughly 10 steps)
[ab3f99641ef65f471886987a102adfa8793032f6] Merge 'remotes/trunk'

master@HP-PC MINGW64 ~/Documents/0AD/0ad ((ab3f99641e...)|BISECTING)
$ cd build/workspaces/

master@HP-PC MINGW64 ~/Documents/0AD/0ad/build/workspaces ((ab3f99641e...)|BISECTING)
$ ./update-workspaces.sh
Updating bundled third-party dependencies...

./update-workspaces.sh: line 85: make: command not found
ERROR: FCollada build failed

master@HP-PC MINGW64 ~/Documents/0AD/0ad/build/workspaces ((ab3f99641e...)|BISECTING)

What am I doing wrong?

Link to post
Share on other sites
Posted (edited)

Building does not work either:

1>------ Build started: Project: Collada, Configuration: Release Win32 ------
2>------ Build started: Project: atlas, Configuration: Release Win32 ------
3>------ Build started: Project: engine, Configuration: Release Win32 ------
4>------ Build started: Project: graphics, Configuration: Release Win32 ------
3>precompiled.cpp
3>Unknown compiler version - please run the configure tests and report the results
1>precompiled.cpp
1>c:\users\master\documents\0ad\0ad\libraries\source\fcollada\include\fmath\fmvector3.h(107): warning C4458: declaration of 'x' hides class member

I do not understand why VS now tells me that the compiler version is unknown, when 10 minutes ago (starting from scratch and cloning the latest 0 A.D. version from GitHub), building was fine (and the game also worked).

What does bisect do with regard to the compiler version?

1.png

Edited by Ceres
Link to post
Share on other sites

Oh, great hint! :thumbsup: I was not aware that the binaries are all there. Will try this!

Maybe wraitii could nevertheless give me another hint about bisecting. (yeah, I know that I am slow :blush:)

Link to post
Share on other sites
Posted (edited)

There are 411 steps between 'pyrogenesis_25349.exe' and 'pyrogenesis_24938.exe' (I renamed them like this after DL).

Is it appropriate to halve this and go down from 25349 by 205 to 25144 and then (if it still works) again halve this and go down by 205 to 24939, etc. (roughly)?

PS:

How I can see only auto-built pyrogenesis.exe files in Trac between 24938 and 25356?

Edited by Ceres
Link to post
Share on other sites
21 minutes ago, Ceres said:

Is it appropriate to halve this and go down from 25349 by 205 to 25144 and then (if it still works) again halve this and go down by 205 to 24939, etc. (roughly)?

I suppose yeah as long as it works enough for the game to crash

22 minutes ago, Ceres said:

How I can see only auto-built pyrogenesis.exe files in Trac between 24938 and 25356?

https://trac.wildfiregames.com/log/ps/trunk/binaries/system/pyrogenesis.exe?rev=25356

  • Thanks 1
Link to post
Share on other sites
Posted (edited)

Unfortunately, even the latest autobuilt game crashes on the PC when GLSL is enabled, i.e. simply replacing 'pyrogenesis.exe' does not seem to be a solution to find out which version is the last one that crashes and which is the first one that does not crash anymore. Could it be that some other files are the "culprit", so I have to test them all (i.e. the full set, respectively)?

Edited by Ceres
Link to post
Share on other sites

Is there a way to DL from Trac auto-built archives that include 'system' and 'data'? This would very much help me finding out what the problem was and where it got fixed etc.

Link to post
Share on other sites
22 minutes ago, Ceres said:

Unfortunately, even the latest autobuilt game crashes on the PC when GLSL is enabled, i.e. simply replacing 'pyrogenesis.exe' does not seem to be a solution to find out which version is the last one that crashes and which is the first one that does not crash anymore. Could it be that some other files are the "culprit", so I have to test them all (i.e. the full set, respectively)?

Well that means compiling is a dead end and its one of the files in binaries/data/mods/public/shaders. Or possibly a combination of both.

If you could install svn on the guilty machine you would'nt have to compile at all.

  • Thanks 1
Link to post
Share on other sites
Posted (edited)

If I see it right, I have to extract these and test the game each time:

changeset_ps_trunk_binaries_data_mods_public_shaders_24777.zip
changeset_ps_trunk_binaries_data_mods_public_shaders_25018.zip
changeset_ps_trunk_binaries_data_mods_public_shaders_25114.zip
changeset_ps_trunk_binaries_data_mods_public_shaders_25118.zip
changeset_ps_trunk_binaries_data_mods_public_shaders_25271.zip
changeset_ps_trunk_binaries_data_mods_public_shaders_25283.zip
changeset_ps_trunk_binaries_data_mods_public_shaders_25285.zip

Will have lunch now, though. ;)

Edited by Ceres
Link to post
Share on other sites

Is it possible for testing purposes to have public.zip extracted when running pyrogenesis.exe? I ask because public.zip is always repacked when I replace files by earlier changesets. Or shall I use "pack-only" without compression? Would that work?

Link to post
Share on other sites

Yes it's possible. It's how it works when using a dev copy.  Make sure the zip is no longer there though. One also can create a mod to override the default mod.

  • Thanks 1
Link to post
Share on other sites

What shall I say? Believe it or not, but now the last auto-built version works also on that PC with GLSL enabled. This drives me crazy. :crazy: I have not changed anything about the game. The PC windows resolution is also the same etc. I feel really embarassed that I have stolen your precious time for replying so kindly and patiently to my many questions. :blush: Even more I want to express my sincerest thanks for your help. And I have not yet given up, because I have already learnt a lot, want to give something back to the community, and also because I am really curious to find out what in fact was the problem. And as it happens sometimes, maybe the problem returns, and then I shall have made some progress at least in better understanding git, trac, etc. :)

Link to post
Share on other sites
1 minute ago, Ceres said:

Sorry, this was not correct, I guess. I meant the latest available exe file for download on the play0ad website.

Can you try the other options to see if you can reproduce the crash?

It's also possible that your driver got updated ?

Link to post
Share on other sites

Hm, yes, there was a driver update from Intel. I will look into this and also about the other options. Don't get me wrong - I will still post here in this thread and let you know what I found. Just for today, I would like to call it a day. Have a nice evening!

Link to post
Share on other sites
4 minutes ago, Ceres said:

Hm, yes, there was a driver update from Intel. I will look into this and also about the other options. Don't get me wrong - I will still post here in this thread and let you know what I found. Just for today, I would like to call it a day. Have a nice evening!

Sure thank you so far :)

Link to post
Share on other sites
Posted (edited)

Well, it still works with GLSL enabled and even with all the other gfx options enabled and set to the maximum, except for the fps limit, which I set to slightly above 60, because my monitor runs at 60 Hz (1920x1080 pixels); vertical sync is also enabled. The fps is then miserable (avg. 15, max. 20), but the game does not crash anymore on that PC. It seems to be likely that the Intel iGPU driver update (version 27.20.100.9466, dated 16 Apr 2021) plays a role, but I am not sure, nor would I know what exactly could have contributed.

Do you have some further hints or thoughts what I could do retrospectively?

Edited by Ceres
Link to post
Share on other sites

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.

Guest
Reply to this topic...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.


×
×
  • Create New...