Shockman
appropriate at this time
- Joined
- Oct 26, 2004
- Messages
- 3,199
- Solutions
- 5
- Reaction score
- 119
- Points
- 90
- Favorite Pinball Machine
- Star Trek
My tables were created with VP, Randy's VP v.3 through .7. If ultracade broke them, I would not use ultracade to play them. VP does not just go poof, and is gone when anything else might be released, you know that! Would you erase VP if ultracade released their mod of it? I don't think so, why do you think I would.
You don't understand. Of course it will use whatever setting you use in the editor. Do you know what I mean when I say that the script will over-ride the .vbs? You really don't understand. Yes it will return the flipper at the same speed you set in the editor or script for upswing. That is not good.
2 bytes to fix it. You don't understand.
You don't, it's clear you don't. The fact I edited the tables on my drive to comply with my temporary fix? What is a fact to you Kins? To me it is a truth and the truth is not that. I developed them for the permanent fix that was all of ours. He is a fucking liar.
I am not going to reupload my tables with the fucking speed set that fast. I spent too much time getting it to work as it is.
It is my opinion that folks should be able to set the upswing to anything they want and not have to do anything else to get the flippers to not swallow a ball.
THAT IS WHY RANDY PUT A Flipper.speed command in the program instead of a FlipperUp.speed, don't you think? I had it where you could do what PacDude does, you could do it as I do, but no matter how you did it you would not have to worry about the ball going through the flipper. You could do anything you want manually. You can make it where the flipper will NEVER hit thew ball if you really want to. But now PacDude says that It don't matter if people gets balls through the flippers, and because why? because he don't because he uses .137.
I don't believe any of you. I really don't. I can't. I just can't believe you think it is good if someone uses VP and does not know to or think to use .137 for their upswing as to get that for their downswing, I believe you are just fucking with me. How could anyone say that at default we SHOULD and MUST have balls through the flippers, AS A DEFAULT, unless they know exactly how to FIX it in their script.
I say as a default we should not have balls through the flipper. If we want balls through the flipper we should code it in, not code in a fix. And I say that you should be able to use any speed upswing, ANY SPEED and if you want a slower downswing then put it the fuck in.
I say the ball through the flipper fix is better than this, better than dictating a upswing swing that is no where near default, and to know how to code a separate value to the downswing just to stop the problem. Some table builders may not ever figure that out, hell the whole community could not figure this out for what? 2 and a half, three years?
It's a sad day when a man can set a program like this back like this and still get support. And PacDude was yapping at Black for threatening to do the same type of thing.
It's sickening to see so much stupidity at the forefront.
You don't understand. Of course it will use whatever setting you use in the editor. Do you know what I mean when I say that the script will over-ride the .vbs? You really don't understand. Yes it will return the flipper at the same speed you set in the editor or script for upswing. That is not good.
2 bytes to fix it. You don't understand.
You don't, it's clear you don't. The fact I edited the tables on my drive to comply with my temporary fix? What is a fact to you Kins? To me it is a truth and the truth is not that. I developed them for the permanent fix that was all of ours. He is a fucking liar.
I am not going to reupload my tables with the fucking speed set that fast. I spent too much time getting it to work as it is.
It is my opinion that folks should be able to set the upswing to anything they want and not have to do anything else to get the flippers to not swallow a ball.
THAT IS WHY RANDY PUT A Flipper.speed command in the program instead of a FlipperUp.speed, don't you think? I had it where you could do what PacDude does, you could do it as I do, but no matter how you did it you would not have to worry about the ball going through the flipper. You could do anything you want manually. You can make it where the flipper will NEVER hit thew ball if you really want to. But now PacDude says that It don't matter if people gets balls through the flippers, and because why? because he don't because he uses .137.
I don't believe any of you. I really don't. I can't. I just can't believe you think it is good if someone uses VP and does not know to or think to use .137 for their upswing as to get that for their downswing, I believe you are just fucking with me. How could anyone say that at default we SHOULD and MUST have balls through the flippers, AS A DEFAULT, unless they know exactly how to FIX it in their script.
I say as a default we should not have balls through the flipper. If we want balls through the flipper we should code it in, not code in a fix. And I say that you should be able to use any speed upswing, ANY SPEED and if you want a slower downswing then put it the fuck in.
I say the ball through the flipper fix is better than this, better than dictating a upswing swing that is no where near default, and to know how to code a separate value to the downswing just to stop the problem. Some table builders may not ever figure that out, hell the whole community could not figure this out for what? 2 and a half, three years?
It's a sad day when a man can set a program like this back like this and still get support. And PacDude was yapping at Black for threatening to do the same type of thing.
It's sickening to see so much stupidity at the forefront.