Print

Please login or register.
1 Hour 1 Day 1 Week 1 Month Forever
Login with username, password and session length

[pst]

It's been a while, but since I haven't seen anyone else point it out I'll mention that v2.0.45, the version first available on tablets, for some time has been available in desktop versions as well.

It's v2.0.49.29, and the little I've tried it has been a good experience for me. In the release notes it says that the focus has been on fixes for the tablet version, and that most of the changes will have little affect for the desktop. Maybe because I never could use 2.0.44 lots of stuff has changed in my view, and I think it looks and behaves nicer. For one thing the chat window has a better font.

[Burning Skull]

For one thing the chat window has a better font.

Khem, "Good news: that rotten donkey in your bedroom, it now has Christmas tree decorations on him!"

[-Stef-]

It crashes a lot more often than the previous one for me.
And unlike the crashes with older versions, which were all when starting the client or starting a game, these crashes are mid-game.

This is bad

[SCSN]

While it's always easy to find something to be negative about, with Christmas coming up and stuff I'd like to point out one aspect of 2.0.45.29 that deserves our deep gratitude: the fact that they didn't release any of the 28 previous revisions.

[Hugovj]

I can play again, that's for now good enough

(Also, the logo has changed. It looks more... Modern now? Does it really matter?)

[Hugovj]

Okay, this sucks. I can't seem to move on to the next level of the campaigns? Even after beating them?

[SCSN]

I've done some data analysis on the missing VP counter and avatars problem.

[Mic Qsenoch]

It was news to me!

[sc0UT]

I've done some data analysis on the missing VP counter and avatars problem.

You can't force anyone to #vpon. The bot randomly changed their settings to prefer off. 

[assemble_me]

The one good thing I noticed is that my stream ran a lot smoother yesterday, also I never saw my OBS crying because the CPU would run at full load.
I yet have to check that again, though, I don't know if this is the common behaviour now.

[-Stef-]

For me, this really is their worst release so far.
Man I hate those middle-of-the-game crashes.

[markusin]

This release has been weird for me. Opponents possibly disconnecting mid-game, and in one of my last games I couldn't buy the last Knight Sir Destry. The plus sign was there but nothing happened when I clicked on it. I assume my opponent couldn't get it either. Next game Knights piled out with Dame Natalie as the last Knight.

Makes me want to stick to the campaign for my relaxing Dominion games.

[-Stef-]

Today both of the games I tried to play crashed mid-game.
Yesterday I had 3 crashes mid-game; think I tried to play approximately 7-10 games.
At this rate it's very unlikely I'll be able to play a league match of 6 games without at least 1 crash.

Is it as bad as this for more people?

[jsh357]

I have not experienced any crashes yet.

[Awaclus]

I haven't had any crashes either, just regular disconnections (because of my own connection and because the reconnect feature seems to be completely nonexistent).

[Limetime]

This release has been weird for me. Opponents possibly disconnecting mid-game, and in one of my last games I couldn't buy the last Knight Sir Destry. The plus sign was there but nothing happened when I clicked on it. I assume my opponent couldn't get it either. Next game Knights piled out with Dame Natalie as the last Knight.

I played a game where neither me or my opponent could by dame molly. I asked him if he could report it to making fun and he said he would. It was the fifth to last knight by the way

[Beyond Awesome]

No crashes for me either. Is the plugin potentially causing the crashes? I usually install it right away, but haven't done so yet.

[werothegreat]

No crashes for me either. Is the plugin potentially causing the crashes? I usually install it right away, but haven't done so yet.

I would laugh my ass off if that were the case.

[jsh357]

I have been using the latest plugin since the last update, so I don't think it's the problem. Maybe it has to do with Windows 10? I am still using 8.1.

[GendoIkari]

No crashes for me. The trick is to not to play.

[SCSN]

I have been using the latest plugin since the last update, so I don't think it's the problem. Maybe it has to do with Windows 10? I am still using 8.1.

I've been using an even later version of the plugin under Windows 10 and haven't experienced any problems since they shut down their defective server last week.

I'm curious what causes this stuff though. The client hang that is announced by this gong sound that Stef has experienced is particularly hilarious. If everyone who experiences hangs and crashes would run their client in admin mode from now on and post the output_log.txt (located in C:\Program Files (x86)\Dominion\Dominion_Data) here, or on the MF forums and put a link here, I'll see whether it's something client-side in which case I might be able to fix it.

[MdLC]

This release has been weird for me. Opponents possibly disconnecting mid-game, and in one of my last games I couldn't buy the last Knight Sir Destry. The plus sign was there but nothing happened when I clicked on it. I assume my opponent couldn't get it either. Next game Knights piled out with Dame Natalie as the last Knight.

I played a game where neither me or my opponent could by dame molly. I asked him if he could report it to making fun and he said he would. It was the fifth to last knight by the way

My son playing on iOS had a game where he couldn't buy province. I assumed it was due to a desync of state between his client and the server because it occurred after he had "connection troubles" (he plugged the iPad in and pulled down the notification window so he could make sure it was charging).

[-Stef-]

I strongly doubt it has anything to do with the plugin. At least this exact same thing started before I installed the plugin.
This particular problem started for me shortly after I upgraded my OS from Windows 7 to Windows 10. No clue if it's related.

When it crashes, I always get a message from windows stating
"Display driver has stopped working and has recovered".

Now I googled a bit for that and found a suggestion to add some registry value.

I tried that and indeed it does affect the problem; it just doesn't improve the situation. I don't remember the exact error message but now apparently my display driver just completely crashed. It also happened a lot more frequent. So I removed the line again and back to the old situation.

There appears to be some correlation to the number of applications I have opened. If I do a clean reboot and don't touch anything but Dominion there is a reasonable chance it just runs. If I first click on 2-3 other programs it's just hopeless. This, and also the messages in the output_log.txt give the impression that my GPU runs out of memory. I have no clue how that happens. My computer is less than a year old and Dominion is... well a cardgame.

I've been looking through the output_log.txt after every crash, and it always contains a couple of thousand lines like these:

Code: [Select]

Unloading 0 Unused Serialized files (Serialized files now loaded: 0)

Unloading 0 unused Assets to reduce memory usage. Loaded Objects now: 26091.
Total: 22.156116 ms (FindLiveObjects: 3.144672 ms CreateObjectMapping: 0.992724 ms MarkObjects: 17.973387 ms  DeleteObjects: 0.044190 ms)

Unloading 0 Unused Serialized files (Serialized files now loaded: 0)

Unloading 0 unused Assets to reduce memory usage. Loaded Objects now: 26091.
Total: 23.913198 ms (FindLiveObjects: 3.225641 ms CreateObjectMapping: 1.129003 ms MarkObjects: 19.511227 ms  DeleteObjects: 0.045331 ms)
...

(it spends 23 seconds looking for objects it can clean up, only to find none?)

... followed by a couple of thousand lines like these...

Code: [Select]

d3d11: failed to create vertex buffer of size 33840 [0x887A0005]
d3d11: failed to create index buffer of size 1692 [0x887A0005]
d3d11: failed to create vertex buffer of size 893760 [0x887A0005]
d3d11: failed to create index buffer of size 44688 [0x887A0005]
d3d11: failed to create vertex buffer of size 348720 [0x887A0005]
...

(I assume this is when the crash actually happens, but unfortunately no timestamps in their log)

and it always ends like this:

Code: [Select]

NullReferenceException
  at (wrapper managed-to-native) UnityEngine.Component:get_gameObject ()

  at Card.removeRender () [0x00000] in <filename unknown>:0

  at Card.OnDestroy () [0x00000] in <filename unknown>:0
 
(Filename:  Line: -1)


You could wonder why I post this here and not at the MF forums. Well, I wonder about that too. Maybe I will later on.
At the moment I just can't handle another suggestion to reboot my firewall because that solved some problem for someone.

[yed]

Stef: You have probably done that, but if not: Did you try to update your video card driver?
On MF forums some people reported, that video card driver update helped them.

[markusin]

I have been using the latest plugin since the last update, so I don't think it's the problem. Maybe it has to do with Windows 10? I am still using 8.1.

I haven't been using the plugin at all. I'm on Windows 7.

But we'll, I'm not the one getting disconnects/crashes.

Edit: "but we'll...". The typos I make sometimes.