|
Post by Majo on Jun 3, 2020 16:14:04 GMT
Hello,
if I try to Play online, sometimes the game closes itself; it tries to download warband data (=> "Error, could not download warband data"), then goes back to main menu and quits the game.
Best regards
Majo
|
|
|
Post by GS_LuciusCastus on Jun 3, 2020 17:25:50 GMT
We'll take a look. Is this with a fresh one?
|
|
|
Post by Majo on Jun 3, 2020 17:28:56 GMT
Yes, now it is also Happening, when I try to Play offline (deployment-phase -> main menu -> Exit )
|
|
|
Post by GS_LuciusCastus on Jun 3, 2020 21:12:13 GMT
We'll take a look at this ASAP.
|
|
|
Post by Majo on Jun 4, 2020 20:48:21 GMT
Still in 1.1.6
(btw.: Big thanks for your quick support !)
|
|
|
Post by GS_LuciusCastus on Jun 4, 2020 22:04:40 GMT
Same error with the same steps?
|
|
|
Post by Majo on Jun 5, 2020 15:22:40 GMT
yes
|
|
|
Post by Majo on Jun 5, 2020 15:38:33 GMT
I sent you the Player.log-files of my 2 shutsowns today by mail.
|
|
|
Post by GS_LuciusCastus on Jun 5, 2020 18:27:03 GMT
Got it and sent to our programmer to take a look.
|
|
|
Post by Majo on Jun 6, 2020 8:31:32 GMT
Eils, I did own Research on this, it only seems to happen, if I press the "Skip" button under the development-timeline; perhaps the bool to Escape the screen is not reset after leving the timeline, so I escape everything (even the game) … Lesson learned: Never press "Skip"-button on intro/credits, developers might get Angry
|
|
|
Post by Majo on Jun 6, 2020 12:48:36 GMT
Same happens, if I press a "previous menu" button [<-], the, I also go back and back until I leave the game (propable reason like mentioned in last post)
|
|
|
Post by GS_LuciusCastus on Jun 6, 2020 15:14:41 GMT
We'll investigate if this is what's causing the crash. Thank you for the update.
|
|
|
Post by Majo on Jun 11, 2020 15:37:39 GMT
Fixed in 1.1.7 To all, who read this: now you should press the skip-button in the intro ! (If you don't you miss something good …)
|
|
|
Post by GS_LuciusCastus on Jun 11, 2020 15:47:00 GMT
Good to know another big bad bug is fixed. Thanks for your heads-up as always.
|
|