I often get the 'Error 0' or something like that... Not sure what that is??? Any clue VWM?
I get disconnected and then the error...
Nate
I have seen that one. Error 0 and Error 2 are both types of disconnect. The numbers are not user friendly because they are just numbers, presented to the PLAYER, who has no access to an error code lookup table.
If MGS took the simple step of providing an error code lookup table in the player help pages, many players would be able to use "self help", and make further tests at "their end" before contacting the casino.
Some codes may be specific to an error on the players' PC, but how on earth can we tell without a "friendly error message" or lookup table.
Error codes are common in programming, but are worse than useless without some kind of documentation being provided to the end user as to what the codes indicate.
When I developed programmes for the UK Meteorlogical office, I used error codes, but we were told that we MUST produce user documentation that described what the codes meant, and whether there was any action the user could take, or even action the 24/7 help desk could take.
It was NOT acceptable to tell the customer that they would have to wait for the programmer to get in before so much as a description of the error could be offered.
Another method used by programmers is to have the software produce a log file. This would normally be discarded when all goes well, but would be used to determine the underlying causes of error conditions.
I know of no MGS log file, nor of any lookup table, relating the codes to specific errors.
Given that the MGS suite now occupies over 10Gigabytes, I don't buy any excuse that incorporating such a lookup table would "bloat" the software by any significant amount.
Maybe there IS such a log file function, but one normally turned off when the software is distributed, and with no switch provided to users to switch it on.
It is nevertheless possible to "log" the Viper client using a tool provided by Microsoft, and this MAY indicate something about such errors.
I recently used this tool on a MPV tournament to check whether anything my end was producing the server lag. I found NOTHING, it really IS the incoming results packet that seems to suffer the delays. I also found some VERY odd behaviour indeed, which was that when (in Tomb raider MPV) the result was a bonus round, that packet was NOT "lagged" - something I find VERY odd, and a bit suspicious about whether MGS have been "cheating" players in these tournaments in some way, rather than the games being a purely random series of outcomes as is the case with lobby play.
This all points to the MPV server itself having a coding error that leads to this lag, but this error does NOT kick in when the server RNG produces a bonus round. There is also the matter that in the idol bonus, the third idol ALWAYS pauses for several seconds before displaying the result, as though this one is delivered separately from the other two by the server.
It seems that a number of errors have been allowed to accumulate on the MPV software, just as often happens with the regular lobby updates.