My posts here have nothing to do with priorities. My posts here are concerning issues here, ValamirCleaver.
Eric is doing wonderfully, thanks for asking.
Kristian, I excluded me from the us already. And I explained that the us is those that upgrade to this new stripped down core.vbs. All of that us will get ball through the flipper problems on my tables because it used that code, with for the flipper return and now all of the people that play it with the new .vbs file are going to have a flipper return speed of .08 and that I know is not fast enough. It's close, but you obviously have no clue on the effort it takes to get flippers to work as you want. I spent years working on that and squashing some of VP's biggest problems, like high resolution plungers, the ball through the flippers, transparent ramps, more shapely and more animated drop targets as well as dynamic lighting, and swinging triggers, as well as other issues, and I shared every one of them with the community, often before I had them in my own release, indeed as I was discovering them. PacDude is not being truthful when he says this is as good, it's not even close. He is wrong to say that we should use values as he does and that the downswing should not be a separate value. That is just not his decision to make, it is each of ours. He might not like to see flippers coming down faster than going up, but that don't mean it should not happen. As it was you could use values that played well as well as not have the ball go through the flipper. There is just way to many version of tables that don't use that fast speed for playing, because have you ever seen a ball just go ballistic with that speed? I see it in Pacdude tables often, never in mine. Does that make mine better? more realistic? No. It makes it mine. I discovered the technique that ended the problem, and accepted that the core.vbs file if having it there was going to have a fast setting to end it on most if not practically all tables. Personally, I don't care what the down swing speed is, as long as it ends the ball through the flipper, instant resetting to start would be better that the btf IMO. I do however care about the upswing and as I said have spent a lot of time tweaking mine.
If I wanted someone, a user that has never even looked at a .vbs file, to play my table now without having the ball go through the flipper then I would have to reset my flippers to have at the least .09 flipper up speed which means many more hours seeing if I can come up with a power setting that would work with it.
Sure, I can re-release it and just put the .09 value in the script, but that is out of the question, don't you understand? there is thousands of it out there already, and thousands of people using it that never come to a forum. Many bought it on eBay, and it was indeed in every collection I have seen compiled, and would not even know how to fix it or even how to update it. Yes they would not even update the .vbs in those cases for the ez install kit will be updated and will have the new set. People are going to have a problem. The only reason I myself don't is because I know how to override it, but I have not. I have relied on the core.vbs file. a custom one for me and the default that still fixed it for everyone else.
My lunches with Eric have nothing to do with this community, and this problem has nothing to do with him. I can't believe you said that frankly. Seeing that the young ones brush their teeth is no reason to not brush your own, don't you understand?
I don't claim to represent the mainstream, I have never confined myself to a box.
I did fix the ball through the flipper problem for every one. I knew the pros and cons of it while every one else was writing it off as impossible and turning flippers over, and doubling flipper up and trying all sorts of fixes to get as much of the occurrences out that they could. I suggested it be put into the .vbs file with .135 because that is what I found worked on faster tables than mine. It was put in with that exact number, well same for all intents and purposes. Now it's out, and my table will not work the same if the stripped core is used.
He had no right to take the ball through the flipper fix out of the core. None at all, nor to tell us that we will have to use a much faster number or live with it. It's untrue. We don't have to limit our upswing value at all to have no balls through the flipper with a default table our one that has ANY value for the upswing, if he just left my fix alone. It was stupid to take it out and very disrespectful, not only to me but to anyone that would dare to play a table the hack did not build himself, unless they used a fast enough upswing BY CHANCE.
You really don't understand, do you?