Is there any chance that MWS has some sort of set cap of how many cards it can hold? It seems that many people are getting this same error.
This is making me wonder if there indeed is a card limit. Menmarch, if you don't mind me asking, how many cards do you have in your master.mwbase? I just want to compare our numbers. I currently have 18,667 cards in my library before adding your patch.
Prior to the MBS patch, 18,667. Now, add 155 to that, and you get 18,822. I should note that my pre-MBS patched master base was not the SlightlyMagic version, as my SOM still appears as the pseudo-patch (I've not been using Workstation since I have MTGO).
1. i reinstalled and set every thing up to m11
2. i added just the MBS patch and it worked fine.
3. I then added SOM and when i restarted the program i got the debug error again
ive done this the other way around too adding som first and when i add the second set i start getting the errors.This leads me to believe there is indeed some type of "set cap" or limit.
Private Mod Note
():
Rollback Post to RevisionRollBack
"Some day the piecing together of dissociated knowledge will open up such terrifying vistas of reality that we shall either go mad from the relevation or flee from the deadly light into the peace and safety of a new dark age." H.P. Lovecraft
Idea: Could you break up the file into Mirran and Phyrexian halves so we could put each one in as an individual set and practice sealed for the pre-release?
I tried to do everything as described (3 times) and always, when adding cards it says "17 done 0 errors" and I get a popup with "Error calling MWSDraw.dll -Undefined situation." Anyone got any clues?
I should note that my pre-MBS patched master base was not the SlightlyMagic version, as my SOM still appears as the pseudo-patch (I've not been using Workstation since I have MTGO).
This might explain why some people are getting the debug error, rather than it properly functioning like yours.
I, like many others, are repeating the steps you have outlined perfectly. However, the DEBUG error and the crashing of MWS still occur.
1. I have the most recent(I think), registered version of MWS.
2. I have downloaded and installed the Sets.dat and Masterbase up to SOM from slightlymagic.net.
-- Note that everything works fine, and has since September of last year.
3. I then attempt to add your MBS file exactly as defined by your steps.
--Everything appears OK.
4. Then I close MWS and attempt to reopen
DEBUG ERROR --Insufficient memory operation.
The results are repeatable, consistent, and have appeared on more than one system.
I appreciate the work that you do on this, but please understand:
If you use a different environment than other users, you should account for different results.
Halp! I've added these spoilers in the past but I've run into an issue. Added just fine, added to the deck just fine but when I try to play in solo mode the deck review is completely empty. When I load it from the deck review window it says "Load Deck Error: Cards not found in Base." I tried loading reloading restarting redownloading the lastest patch and then adding the spoiler. All of my pre-MBS decks load just fine so I've certain its something with either the way I'm patching or along those lines.
Private Mod Note
():
Rollback Post to RevisionRollBack
They are adding YET ANOTHER RARITY to M13! And the first card they spoiled with it? DARK RITUAL! PROOF BELOW!!?!!
To everyone having problems who is using Windows Vista or Windows 7, try running MWS as an adminitrator. If this works, I suggest you reinstall MWS somewhere other than the program files directory. Either install in your documents or make a Games folder in your C directory.
Thought I'd add I've used these spoilers every release to date although I usually end up replacing with Slightly Magic base each time later. I am getting the same Debug issue after restart as everyone else.
For Vista/Windows 7 users. If you want to completely clear the data you need to go into
For x64:
C:\Users\"Your User Name"\AppData\Local\VirtualStore\Program Files (x86)\Magic Workstation
For x86
C:\Users\"Your User Name"\AppData\Local\VirtualStore\Program Files\Magic Workstation
There may be copies of the masterbase being used here even after you have replaced it in the main program directory. This is where it stores changes to stuff in Program Files when you don't have administrative rights.
Anyway, I don't think it will help cause it still doesn't work for me. But I thought that might help people having trouble resetting to what they had before after a failed attempt.
Private Mod Note
():
Rollback Post to RevisionRollBack
Current Decks: GWUKnightfall Modern UWTempo Legacy UGRBurning Wish Cobra Vintage
To everyone having problems who is using Windows Vista or Windows 7, try running MWS as an adminitrator. If this works, I suggest you reinstall MWS somewhere other than the program files directory. Either install in your documents or make a Games folder in your C directory.
My Magic Workstation is located in Program Files (x86), so take that as you will.
Memnarch, could you PLEASE upload your version of patched mwbase file?
I tried .zip-ping the file, but it's too big to upload here. The forum software also doesn't let me just upload the .mwbase file as it isn't a recognized extension.
My Magic Workstation is located in Program Files (x86), so take that as you will.
If you install correctly the first time, it won't matter. However, if you mess up and want to overwrite an older master base, vista/7 will make it a little difficult. You can install somewhere other than program files, or you can do this every time you want to change it:
Thought I'd add I've used these spoilers every release to date although I usually end up replacing with Slightly Magic base each time later. I am getting the same Debug issue after restart as everyone else.
For Vista/Windows 7 users. If you want to completely clear the data you need to go into
For x64:
C:\Users\"Your User Name"\AppData\Local\VirtualStore\Program Files (x86)\Magic Workstation
For x86
C:\Users\"Your User Name"\AppData\Local\VirtualStore\Program Files\Magic Workstation
There may be copies of the masterbase being used here even after you have replaced it in the main program directory. This is where it stores changes to stuff in Program Files when you don't have administrative rights.
Anyway, I don't think it will help cause it still doesn't work for me. But I thought that might help people having trouble resetting to what they had before after a failed attempt.
so you can directly extract to c:\program files\Magic Workstation\
after 2 day of errors this version works 100% for me both on Win 7 and Win XP
Cheers, and thanks for all of those who stuck it out to make it work. Still dunno why the patch doesn't autowork this season, but that's not something I'm familiar with, at any rate.
If you install correctly the first time, it won't matter. However, if you mess up and want to overwrite an older master base, vista/7 will make it a little difficult. You can install somewhere other than program files, or you can do this every time you want to change it:
I think the problem is the number of cards. The Goblin Hero masterbase has 18667 cards while the masterbase that works is around 18500. If I use the masterbase that works and then add few extra made up sets to it, somewhere around 18700ish cards it craps out and shows the same errors as the Goblin Hero masterbase.
Hey, what does 'current grid must be MASTER-like type' mean?
I need help with this.
It wont load for me. still fairly new at the program so pardon the ignorance.
And thank you for the help.
Private Mod Note
():
Rollback Post to RevisionRollBack
~Intelligence is Bliss; Ignorance is Denial.
Skill is an ability that relates more so to the type of deck that's built and how said player pilots it. It also relates to the ability to assess the board and use the cards available to you in the most optimal way relative to each situation.
When a deck is filled with above par cards and every play is solid, there comes a diminishing need to "think" for the lack of wanting to use a better word.
I think the problem is the number of cards. The Goblin Hero masterbase has 18667 cards while the masterbase that works is around 18500. If I use the masterbase that works and then add few extra made up sets to it, somewhere around 18700ish cards it craps out and shows the same errors as the Goblin Hero masterbase.
I just got the same DEBUG error installing this text spoiler, so I decided to go back and test this assertion. I replaced the Master Base with my old one to fix the "debug" problem, then deleted all the reprint sets (Duel Decks, etc.) to bring my library down to a more respectable 16886 cards.
After reinstalling this text spoiler, I got the error again. It doesn't look like there's an issue with too many cards, so that points to a problem in the text file or SlightlyMagic's SOM Master Base.
!! EDITZ !!
I tried wolfer's Master Base and that works with this text spoiler but apparently his Base is missing a lot of the filters? ZEN, ROE, and SOM are missing as categories in the card filter and that's just Standard-legal sets. The cards are there but it's kinda hard to sort through ~5500 cards of Weatherlight, Nemesis, and other completely random "unfilterable sets" to pick through the new MBS cards.
...Oh, nevermind, adding the Sets.dat file that came with it fixed everything. Looks like he still has the old definitions for Standard/Extended, though, how annoying. (Alara, in MY Standard?) At any rate, it's not the size of the library/base that appears to be causing the compatibility problem with the normal Master Base.
Yes, I do have the old definitions of standard, but those can't be changed unless you completely re-build the master base as far as I know. For now it's pretty easy to just uncheck what you don't need. If someone had a text spoiler for all the sets saved up somewhere I'd be happy to fix it, though.
A few other differences from GoblinHero's version:
-My base stopped adding the miscellaneous product releases since I started maintaining it separate from GoblinHero's. It would be nice if all of them were gone, though.
-Mythic rarity is not marked with a "M". This will let you generate sealed packs without having mythics generate as commons.
-Scars of Mirrodin cards are not "watermarked", which means equipment and auras can attach to permanents (tribal equipment/enchantments still can't).
-All rarity lacking basic lands (from random product releases) have been given a rarity. Note that adding a card to your deck that is lacking a rarity will cause mwsplay to error, and it's pretty easy to accidentally add those versions of basic lands.
-An additional set "Alara Reborn Limited" was added to properly generate alara reborn packs.
The only other problem with my masterbase is that some sets don't properly account for the basic land included in the booster pack. As long as whoever you're playing sealed against has the same thing, it shouldn't matter too much though.
As for the error that everyone has been having, I'm pretty sure it's caused by using the remove set function. If you're someone who adds partial spoilers, then uses remove set when they update, it will cause problems eventually. If you're going to add temporary stuff to your masterbase, you need to back up the permanent one.
Private Mod Note
():
Rollback Post to RevisionRollBack
To post a comment, please login or register a new account.
Prior to the MBS patch, 18,667. Now, add 155 to that, and you get 18,822. I should note that my pre-MBS patched master base was not the SlightlyMagic version, as my SOM still appears as the pseudo-patch (I've not been using Workstation since I have MTGO).
[GTC] Gatecrash Patch for MWS (249/249)
1. i reinstalled and set every thing up to m11
2. i added just the MBS patch and it worked fine.
3. I then added SOM and when i restarted the program i got the debug error again
ive done this the other way around too adding som first and when i add the second set i start getting the errors.This leads me to believe there is indeed some type of "set cap" or limit.
"Some day the piecing together of dissociated knowledge will open up such terrifying vistas of reality that we shall either go mad from the relevation or flee from the deadly light into the peace and safety of a new dark age." H.P. Lovecraft
Xbox Live - eidtelnvil
PlayStation Network - eidtelnvil
Currently reading It by Stephen King
Currently playing Persona 4
This might explain why some people are getting the debug error, rather than it properly functioning like yours.
I, like many others, are repeating the steps you have outlined perfectly. However, the DEBUG error and the crashing of MWS still occur.
1. I have the most recent(I think), registered version of MWS.
2. I have downloaded and installed the Sets.dat and Masterbase up to SOM from slightlymagic.net.
-- Note that everything works fine, and has since September of last year.
3. I then attempt to add your MBS file exactly as defined by your steps.
--Everything appears OK.
4. Then I close MWS and attempt to reopen
DEBUG ERROR --Insufficient memory operation.
The results are repeatable, consistent, and have appeared on more than one system.
I appreciate the work that you do on this, but please understand:
If you use a different environment than other users, you should account for different results.
For Vista/Windows 7 users. If you want to completely clear the data you need to go into
For x64:
C:\Users\"Your User Name"\AppData\Local\VirtualStore\Program Files (x86)\Magic Workstation
For x86
C:\Users\"Your User Name"\AppData\Local\VirtualStore\Program Files\Magic Workstation
There may be copies of the masterbase being used here even after you have replaced it in the main program directory. This is where it stores changes to stuff in Program Files when you don't have administrative rights.
Anyway, I don't think it will help cause it still doesn't work for me. But I thought that might help people having trouble resetting to what they had before after a failed attempt.
GWU Knightfall Modern
UW Tempo Legacy
UGR Burning Wish Cobra Vintage
My Magic Workstation is located in Program Files (x86), so take that as you will.
I tried .zip-ping the file, but it's too big to upload here. The forum software also doesn't let me just upload the .mwbase file as it isn't a recognized extension.
[GTC] Gatecrash Patch for MWS (249/249)
If you install correctly the first time, it won't matter. However, if you mess up and want to overwrite an older master base, vista/7 will make it a little difficult. You can install somewhere other than program files, or you can do this every time you want to change it:
That works!!
WOOOOOOHOO!
Thanks guys!
works!
And for the masterbase, I'm still curious why it doesn't work. Oh well.
Cheers, and thanks for all of those who stuck it out to make it work. Still dunno why the patch doesn't autowork this season, but that's not something I'm familiar with, at any rate.
[GTC] Gatecrash Patch for MWS (249/249)
Whoop, my bad. Thanks
Thank bra worked like a charm
I need help with this.
It wont load for me. still fairly new at the program so pardon the ignorance.
And thank you for the help.
Skill is an ability that relates more so to the type of deck that's built and how said player pilots it. It also relates to the ability to assess the board and use the cards available to you in the most optimal way relative to each situation.
When a deck is filled with above par cards and every play is solid, there comes a diminishing need to "think" for the lack of wanting to use a better word.
I just got the same DEBUG error installing this text spoiler, so I decided to go back and test this assertion. I replaced the Master Base with my old one to fix the "debug" problem, then deleted all the reprint sets (Duel Decks, etc.) to bring my library down to a more respectable 16886 cards.
After reinstalling this text spoiler, I got the error again. It doesn't look like there's an issue with too many cards, so that points to a problem in the text file or SlightlyMagic's SOM Master Base.
!! EDITZ !!
I tried wolfer's Master Base and that works with this text spoiler but apparently his Base is missing a lot of the filters? ZEN, ROE, and SOM are missing as categories in the card filter and that's just Standard-legal sets. The cards are there but it's kinda hard to sort through ~5500 cards of Weatherlight, Nemesis, and other completely random "unfilterable sets" to pick through the new MBS cards.
...Oh, nevermind, adding the Sets.dat file that came with it fixed everything. Looks like he still has the old definitions for Standard/Extended, though, how annoying. (Alara, in MY Standard?) At any rate, it's not the size of the library/base that appears to be causing the compatibility problem with the normal Master Base.
A few other differences from GoblinHero's version:
-My base stopped adding the miscellaneous product releases since I started maintaining it separate from GoblinHero's. It would be nice if all of them were gone, though.
-Mythic rarity is not marked with a "M". This will let you generate sealed packs without having mythics generate as commons.
-Scars of Mirrodin cards are not "watermarked", which means equipment and auras can attach to permanents (tribal equipment/enchantments still can't).
-All rarity lacking basic lands (from random product releases) have been given a rarity. Note that adding a card to your deck that is lacking a rarity will cause mwsplay to error, and it's pretty easy to accidentally add those versions of basic lands.
-An additional set "Alara Reborn Limited" was added to properly generate alara reborn packs.
The only other problem with my masterbase is that some sets don't properly account for the basic land included in the booster pack. As long as whoever you're playing sealed against has the same thing, it shouldn't matter too much though.
As for the error that everyone has been having, I'm pretty sure it's caused by using the remove set function. If you're someone who adds partial spoilers, then uses remove set when they update, it will cause problems eventually. If you're going to add temporary stuff to your masterbase, you need to back up the permanent one.