Loading...
  OR  Zero-K Name:    Password:   

Forum index  > General discussion   >

Engine testing replays

16 posts, 1261 views
Post comment
Filter:    Player:  
sort


AUrankAdminGoogleFrog
5 years ago
Some people, especially @[ffc], instantly crashed with the engine update (104.0.1-1051-ga756bf5). This is one of those near-impossible bugs to track down because it only affects a random selection of end users. In an attempt to get around this problem I made these replays:

Everyone can help as follows:
  • Run the top replay. It may take a few minutes to start, so just wait.
  • If the replay works, post that it works, and you are done.
  • If the top replay doesn't work, then run the rest of the replays and post which ones work.
+2 / -0
USrankJasper
5 years ago
Top works
+0 / -0


AUrankAdminGoogleFrog
5 years ago
(edited 5 years ago)
Works for USrankArchangel, PLrankCatLady, AUrankSortale.
+0 / -0

USrankAdminSteel_Blue
5 years ago
Top replay loads and completes, but looks funky.
+0 / -0

USrankkorn
5 years ago
Top Works.

WIN Version 10.0.17763 Build 17763
+0 / -0

USrankkorn
5 years ago
The map tiles were funky.
+0 / -0

USrankkorn
5 years ago
It looks like 2 Win updates are currently being pushed.

2019-02 Cumulative Update for .NET Framework 3.5 and 4.7.2 for Windows 10 Version 1809 for x64 (KB4486553)

2019-02 Cumulative Update for Windows 10 Version 1809 for x64-based Systems (KB4482887)

I'll retry the replay once these are installed. I'm on a super slow connection so I usually have updates installed a day or 2 later than most folks.
+0 / -0


AUrankAdminGoogleFrog
5 years ago
Here are all the engines
quote:
104.0.1-1051-ga756bf5
104.0.1-1049-g88de633
104.0.1-1044-g7e331d0
104.0.1-1031-g398cc7e
104.0.1-1025-g07748ef
104.0.1-1016-g1929a5d
104.0.1-1010-g3d26db6
104.0.1-998-g1e16912
104.0.1-990-gcb8f2ce
104.0.1-914-g0f9ac7b
104.0.1-907-g7f56688
104.0.1-901-g89b4773
104.0.1-893-g4d798fb
104.0.1-889-g0871f35
104.0.1-888-g15d6cc6
104.0.1-886-g0b800f1
104.0.1-873-g5fb4bb6
104.0.1-869-g204d265
104.0.1-817-gfa7aedc
104.0.1-781-g80f9374
104.0.1-755-g1327687
104.0.1-737-g14b7009
104.0.1-735-g0652173
104.0.1-723-ga9ad653
104.0.1-670-gc51c539
104.0.1-656-g453f3c9
104.0.1-621-g6f37f08
104.0.1-616-g52f5f2b
104.0.1-567-gc484c10
104.0.1-557-g1487736
104.0.1-527-gf2536df
104.0.1-483-g30d8543
104.0.1-409-g07c2800
104.0.1-373-gce823d3
104.0.1-358-gb58f0bb
104.0.1-355-g9aa8f99
104.0.1-351-g58d4066
104.0.1-350-gc2fb732
104.0.1-338-g911f59b
104.0.1-335-g36b6354
104.0.1-330-gf9cae9d
104.0.1-330-gae29b60
104.0.1-325-g9ad8116
104.0.1-322-ga77eef8
104.0.1-313-g3d4f772
104.0.1-311-g5adac5b
104.0.1-309-ga8b5ffc
104.0.1-308-g17ff6c0
104.0.1-303-g6a15411
104.0.1-299-g65ac81f
104.0.1-296-g0bcf2c0
104.0.1-294-gfb439d3
104.0.1-293-gf81e87d
104.0.1-288-gb77f061
104.0.1-287-gf7b0fcc
104.0.1-286-gd47727e
104.0.1-271-g2e1a220
104.0.1-263-g1299f0c
104.0.1-257-g02191c9
104.0.1-255-g20c73b0
104.0.1-247-gb738aa8
104.0.1-245-gdc95053
104.0.1-236-g23c7945
104.0.1-151-g11de57d
104.0.1-150-gd36042d
104.0.1-141-gae5ba3c
104.0.1-138-gf19449b
104.0.1-137-gb0a707e
104.0.1-136-g105a9e9
104.0.1-104-g2135e2e
104.0.1-92-g4409317
104.0.1-75-g341c771
104.0.1-55-g5d0ff28
104.0.1-49-g70f081f
104.0.1-7-gf03115b
+0 / -0

USrankkorn
5 years ago
top worked after windows update - map tiles now look normal. Did steam push out a fix to the game or map? I steam just downloaded a steam 3.3 meg file.
+0 / -0


AUrankAdminGoogleFrog
5 years ago
There was a fix for the tile map issue when launching replays. CArankAdminShadowfury333 has the issue and has helped narrow it down.
+0 / -0
CArankPorkchop
5 years ago
(edited 5 years ago)
Top replay - Hit start button and nothing loads even after many minutes.
Second through fourth play properly.
Fifth and sixth crash spring.exe when the replay ends.

Win 7 Pro 64-bit, Intel i5-2500K, Nvidia GTX 670 (Infolog)
+2 / -0
UAranklamer_steam
5 years ago
(edited 5 years ago)
Didn't test replays, but
104.0.1-1031-g398cc7e win32 - works
104.0.1-1044-g7e331d0 win32 and later - broken (0xc0000018)
104.0.1-1049-g88de633 win64 - works (there are no win64 build for 104.0.1-1044-g7e331d0)

win64 versions works fine.

Possible reason of 0xC0000018:
"If a DLL requires to be loaded at a fixed address(in process virtual address space), but the requirement cannot be fulfilled, Windows asserts the very 0xC0000018 error"
I guess something with build_process/dll_links (libcurl.dll?) for win32 was changed in between 104.0.1-1031-g398cc7e and 104.0.1-1044-g7e331d0.

Win 7 (64bit).

EDIT: After replacing libcurl (and adding libcrypto) 104.0.1-1044-g7e331d0 win32 runs.
https://curl.haxx.se/windows/dl-7.64.0_1/curl-7.64.0_1-win32-mingw.zip
https://bintray.com/vszakats/generic/download_file?file_path=openssl-1.1.1b-win32-mingw.zip

EDIT2: Cpt. Hindsight to the rescue! A bit late to the party, seems devs already fixed it in 104.0.1-1059-g3f0de44, 104.0.1-1060-g7f3541f works for me.
+1 / -0

GBrankAdminDeinFreund
5 years ago
Top works.
+0 / -0
DErankManu12
5 years ago
Top works for me.
+0 / -0
CNrankqwerty3w
5 years ago
(edited 5 years ago)
Windows 8.1 64bit

1031 works
1043, 1044, 1049, 1050, 1051 32bit crashed, 0xC0000018 error, but 64bit work
1060 works

So basically the same as lamer_steam.
+0 / -0


GBrankdyth68
5 years ago
(edited 5 years ago)
0xC0000018 with 1057, but 1060 is good for me.

EDIT: I mean 1057, not 1059
+0 / -0