Custom deck either crashes my game or doesn't load

[Dovahbear ʕ • ᴥ • ʔ]

Decks in question - https://imgur.com/a/otT7E

I'm trying to create a game and felt that it was better to compact ''class'' cards into a single deck and then make another deck in order to give them their own unique bakgrounds. However whenever I do this, I get This[imgur.com] message. I don't know what I'm doing wrong. My card size is standard and when I export I do it with 4093 in the box next to ''Max Size Deck''.

I found a chunk of the error code that I think might explain it but I don't know what to take from it or how to fix it:
Unity Player [version: Unity 5.6.5f1_2cac56bf7bb6]

TTSMasterNativePlugin.dll caused an Access Violation (0xc0000005)
in module TTSMasterNativePlugin.dll at 0033:94c4bb69.

Error occurred at 2018-03-29_135812.
D:\Program Files (x86)\Steam\steamapps\common\Tabletop Simulator\Tabletop Simulator.exe, run by (my username)_.
78% memory in use.
8100 MB physical memory [1712 MB free].
11172 MB paging file [2749 MB free].
134217728 MB user address space [134214947 MB free].
Write to location 75281000 caused an access violation.

Context:
RDI: 0x829a7e7a RSI: 0x75276c40 RAX: 0x00000006
RBX: 0x75264040 RCX: 0x75281001 RDX: 0x00008840
RIP: 0x94c4bb69 RBP: 0x00012c01 SegCs: 0x00000033
EFlags: 0x00010202 RSP: 0x7093f330 SegSs: 0x0000002b
R8: 0x75264040 R9: 0x00000004 R10: 0x0d73123a
R11: 0x00000004 R12: 0xffffffff R13: 0x00000004
R14: 0x00012c00 R15: 0x00001d88

[locoparentus]

This deck image https://i.imgur.com/xvYUvqF.jpg

is

12,800 × 6,720

way, way to big. and the most likely reason for the game crashing.

[Dovahbear ʕ • ᴥ • ʔ]

Originally posted by locoparentus:

This deck image https://i.imgur.com/xvYUvqF.jpg

is

12,800 × 6,720

way, way to big. and the most likely reason for the game crashing.

Omg, so sorry for bothering you with such a stupid mistake. Thank you for your reply, I've seen your comment on my every post and I truly appriciate your answers :)

[SaltyO]

Images have to be around max 4,000 pixels x or y in any case, so you will have to shrink it down anyway. :)

[Baryonyx]

I also see a lot of duplicates in there, you don't really need those. Just make one of them and then duplicate them ingame as needed.

[ulia]

Originally posted by Elder_Salt:

Images have to be around max 4,000 pixels x or y in any case, so you will have to shrink it down anyway. :)

You can use images larger than 4096x4096 but it is generally percieved as bad practice and depending on how the deck importer script actually works it may be completely redundant to go beyond (because Unity might be compressing it down to 4096x4096 anyways as it tends to do).

[Dovahbear ʕ • ᴥ • ʔ]

Originally posted by Baryonyx:

I also see a lot of duplicates in there, you don't really need those. Just make one of them and then duplicate them ingame as needed.

I always thought that having duped cards in one deck is better for fps than taking a card and ctrl c + ctrl v ingame, is that not true?

[ulia]

Coincidentally I wrote a fairly extensive guide on everything sheets and decks just the other day http://steamcommunity.com/sharedfiles/filedetails/?id=1349263773

By having duplicates in your deck you are only wasting texture space, as you are with the layout of your cards because you have many empty slots which serve zero purpose. You can usually divide your card distribution to only end up with none to a couple of empty slots if it's an amount hard to divide evenly. No matter if you copy paste the card or spawn it in through the sheet, it is the same amount of mesh data, so having no duplicates in the sheet and copy pasting cards is the optimal way to go about having multiple identical cards.

For your sheet of custom hearthstone type cards, since there are 52 of them a grid of 8x7 cards would only waste four empty slots, which leaves you a lot more texture estate to keep it high res. You can however definitely cut out more than half of the cards because it is largely comprised of duplicates. I sloppily counted 24, which would leave you at a sheet that is 6x4 that leaves no empty spaces.

If you wanted unique backs for some cards you should import a deck as many times as you have unique card backs and delete the excess cards. This way you'll cut your sheets down to one face image and three individual card backs, which is far more memory efficient than your current sheets. If the front sheet is already loaded for one deck it will not be loaded in to memory again for the others.

[saltyking]

Originally posted by ulia:

Coincidentally I wrote a fairly extensive guide on everything sheets and decks just the other day http://steamcommunity.com/sharedfiles/filedetails/?id=1349263773

By having duplicates in your deck you are only wasting texture space, as you are with the layout of your cards because you have many empty slots which serve zero purpose. You can usually divide your card distribution to only end up with none to a couple of empty slots if it's an amount hard to divide evenly. No matter if you copy paste the card or spawn it in through the sheet, it is the same amount of mesh data, so having no duplicates in the sheet and copy pasting cards is the optimal way to go about having multiple identical cards.

For your sheet of custom hearthstone type cards, since there are 52 of them a grid of 8x7 cards would only waste four empty slots, which leaves you a lot more texture estate to keep it high res. You can however definitely cut out more than half of the cards because it is largely comprised of duplicates. I sloppily counted 24, which would leave you at a sheet that is 6x4 that leaves no empty spaces.

If you wanted unique backs for some cards you should import a deck as many times as you have unique card backs and delete the excess cards. This way you'll cut your sheets down to one face image and three individual card backs, which is far more memory efficient than your current sheets. If the front sheet is already loaded for one deck it will not be loaded in to memory again for the others.

is this guide still somewhere by anychance?