- This topic has 4 replies, 3 voices, and was last updated 3 years, 11 months ago by
.
-
Posts
-
Hello,
I am trying to figure out if this is a known issue across some VP10 tables or an issue with my setup.
A few games I have (CFTBL, a custom Pink Floyd table, and a few others show this problem). The ball will freeze repeatedly during a game. if I hit a flipper it will then unfreeze most of the time, only to freeze again a few seconds later. I am using a single 4k monitor for the table and a small LCD display for the DMD when applicable. (It’s a MAME cabinet, not a full on virtual pinball machine)
I am running:
i7 3770 3.4Ghz
8 GB RAM (I’ve only seen it max out at 5.5GB during a game, never seen the CPU come close to maxing out))
Nvidia RTX 2060 card with 6GB RAM
I don’t think this issue is a bottleneck with my system.
I am running VP 10.6.0
VPinMAME 3.3
Win 10
I am hoping this is an issue people have seen before.
You need to login in order to like this post: click here
OK, this is silly. It looks like the ball pauses when I only hit the left flipper. My left flipper is set to the keyboard letter “C”. I do not see anywhere in VPX that has “C” as a pause feature or something else. I must be missing something here…
You need to login in order to like this post: click here
the “C” is is scripted to enable and disable the manual ball control
you can use your arrow keys to move the ball after pressing “C”
many of the VPX keys are hard coded.
it is best if you use the default VPX keys, or you will find problems like this when you star to map custom keys.
if you wan’t to keep your “C” key mapping you are going to have to go into the table and remove
the script that enables and disables the manual ball control.
see a table you like help me find the resources so that I can finish it
https://www.dropbox.com/sh/7qtake9whi5ium2/AAB4K4W78oMVlqSxTzKtGHTHa?dl=0see a table you like help me find the resources so that I can finish it
https://www.dropbox.com/sh/7qtake9whi5ium2/AAB4K4W78oMVlqSxTzKtGHTHa?dl=0You need to login in order to like this post: click here
32a is of course right. I too urge you to change your left and right flipper keys to the default left and right shift. Fiddling with default keys will, even if the intentions has always been that you can map these keys to your own preferred ones often lead you down the rabbit hole in the long run. I’m pretty sure that 32a is correct about the issue being tables that has the Rothbauerw’ script for ball control being active too. Several ways to disable this. Search the script for “Manual Ball Control”. Comment out all that code. If you’re not sure what I mean by that. Then you should be able to search for just one line ‘contballinplay = true’ and change that to ‘contballinplay = false’. OR, delete the element on the table that is actually making this routine come to live in the first place. It is probably called “StartBallControl”.
Again, best solution, don’t change the default keys.
You need to login in order to like this post: click here
the “C” is is scripted to enable and disable the manual ball control
you can use your arrow keys to move the ball after pressing “C”
many of the VPX keys are hard coded.
it is best if you use the default VPX keys, or you will find problems like this when you star to map custom keys.
if you wan’t to keep your “C” key mapping you are going to have to go into the table and remove
the script that enables and disables the manual ball control.
32a is of course right. I too urge you to change your left and right flipper keys to the default left and right shift. Fiddling with default keys will, even if the intentions has always been that you can map these keys to your own preferred ones often lead you down the rabbit hole in the long run. I’m pretty sure that 32a is correct about the issue being tables that has the Rothbauerw’ script for ball control being active too. Several ways to disable this. Search the script for “Manual Ball Control”. Comment out all that code. If you’re not sure what I mean by that. Then you should be able to search for just one line ‘contballinplay = true’ and change that to ‘contballinplay = false’. OR, delete the element on the table that is actually making this routine come to live in the first place. It is probably called “StartBallControl”.
Again, best solution, don’t change the default keys.
That’s got to be it. Unfortunately I’ve mapped that button across multiple emulators. I’ve only had this issue in a few tables so far. I’ll have to decide if it’s worth remapping across my other emulators or just commenting out the code…
Thanks for both your help!
You need to login in order to like this post: click here
Forums are currently locked.
