What casino game is decided only by the player?

The speed of the processor tells you nothing of the frequency or cycle of the rng to even begin to think of timing it.

It could be randomizing 2 different cards for all you know and you never will.

Your missing the point.

And we should all just let this thread die...
Quote

Originally posted by: slapinfunk
The speed of the processor tells you nothing of the frequency or cycle of the rng to even begin to think of timing it.

It could be randomizing 2 different cards for all you know and you never will.

Your missing the point.

And we should all just let this thread die...


The speed of the processor will determine how many cycles can be processed in a given amount of time. However, as you state, there are other factors as well. The program may be doing other things instead of shuffling constantly. But just how many other things could it really be doing? In addition, RNG algorithms are very basic science and well understood. IGT is not going to go off and build something that takes 1000s of more cycles when it is completely unnecessary. They might take a few more cycles, but not orders of magnitude different.

As for how VP machines work, I think that has been well established so we know your comment about "randomizing 2 different cards" is pure nonsense.

The only ones "missing the point" here are you and money (and a couple of others). It's not surprising you want to "let this thread die". However, you and money would look better if you just admitted you were wrong. (Like that's going to happen.)

BTW, I see the latest Dancer article mentioned some of the comments right here at LVA:

"Dozens of people countered that since I ended up losing more than the car was worth, it was a really stupid play or I was a terrible player."

To which he responded:

"People with a clue about successful gambling know that you need to look at the parameters of a play BEFORE you see the results --- and the actual results for one particular play are largely irrelevant"

In other words, Dancer pretty much said you guys don't have a "clue". I think that pretty much sums it up.
I have always maintained that this:

https://www.youtube.com/watch?v=zrzMhU_4m-g&feature=related

sums it up.
400mHz will cycle through 200,000 cards a second... good luck

400mHz will cycle through 200,000 cards a second... good luck
Quote

Originally posted by: slapinfunk
400mHz will cycle through 200,000 cards a second... good luck


How do you calculate the number of cards per mHz?

I can see that a faster CPU will generate more random numbers per second, but I see no way that you can estimate the number of random numbers generated given just the speed of the CPU.
Quote

Originally posted by: arcimedes
Quote

Originally posted by: slapinfunk
The speed of the processor tells you nothing of the frequency or cycle of the rng to even begin to think of timing it.

It could be randomizing 2 different cards for all you know and you never will.

Your missing the point.

And we should all just let this thread die...


The speed of the processor will determine how many cycles can be processed in a given amount of time. However, as you state, there are other factors as well. The program may be doing other things instead of shuffling constantly. But just how many other things could it really be doing? In addition, RNG algorithms are very basic science and well understood. IGT is not going to go off and build something that takes 1000s of more cycles when it is completely unnecessary. They might take a few more cycles, but not orders of magnitude different.

As for how VP machines work, I think that has been well established so we know your comment about "randomizing 2 different cards" is pure nonsense.

The only ones "missing the point" here are you and money (and a couple of others). It's not surprising you want to "let this thread die". However, you and money would look better if you just admitted you were wrong. (Like that's going to happen.)

BTW, I see the latest Dancer article mentioned some of the comments right here at LVA:

"Dozens of people countered that since I ended up losing more than the car was worth, it was a really stupid play or I was a terrible player."

To which he responded:

"People with a clue about successful gambling know that you need to look at the parameters of a play BEFORE you see the results --- and the actual results for one particular play are largely irrelevant"

In other words, Dancer pretty much said you guys don't have a "clue". I think that pretty much sums it up.


Well guys you have a few things way wrong here:

The processor speed doesn't really isn't the prime mover, its the speed of the memory. At 200Mhz processor speed, your going to need memory at least 5 microseconds or faster as to not have extra clock cycles run by before you can process anything. On board L1 and L2 cache can speed things up a bit but then you get into the video display slowing things down. You'll have your answer but you can't do anything with it as you can't see it until the video portion can do its processing. That's at least a couple of clock cycles as video memory normally is much slower than CPU cache memory or on board memory.
I agree with you on the memory speed (I'm guessing you actually meant the frontside bus speed there; the backside bus goes to the cache, if it exists), but I'm pretty sure the video driver has nothing to do with it. After all, you're not sending images of those cycled cards to the screen, just the final result, right?

For any tech weenies out there, some details here.
Quote

Originally posted by: shlomo
I agree with you on the memory speed (I'm guessing you actually meant the frontside bus (FSB) speed there; the backside bus goes to the cache, if it exists), but I'm pretty sure the video driver has nothing to do with it. After all, you're not sending images of those cycled cards to the screen, just the final result, right?

For any tech weenies out there, some details here.


The FSB doesn't have anything to do with the speed of the memory. The processor does the RNG calculation and passes the result to the memory for use elsewhere, in our case the video card. The FSB controls the speed of the data that is being passed around (like a highway). The RNG numbers hit the video card and then either gets the images from the video card memory or from the on board memory and then displays the result. The card images have to be held somewhere so they can be displayed. Your only going to be passing the numbers and then pull up the correct card that matches the RNG result.

roger that, but I think your point was that the clock wasn't the bottleneck for cycling the RNG. My point is, the bus would be such a bottleneck, in the context of someone actually trying the ultimate in silliness and timing the RNG somehow to pick the correct time to press 'draw' or 'deal'.

I really think the video card is completely irrelevant to such a timing discussion - after all, it will get the result from the installed program and show a picture, that's it. I can't think of a reason why any of the logic would happen at the card. In fact, it's not impossible that it happens in some kind of static memory, like bubble memory - that way, in case of power failure, spike, etc, and someone claims to have hit a royal flush or something, they could actually check on the latest state of the machine with some kind of confidence in the result.
Already a LVA subscriber?
To continue reading, choose an option below:
Diamond Membership
$3 per month
Unlimited access to LVA website
Exclusive subscriber-only content
Limited Member Rewards Online
Join Now
or
Platinum Membership
$50 per year
Unlimited access to LVA website
Exclusive subscriber-only content
Exclusive Member Rewards Book
Join Now