Pacdude2 Posted January 16, 2015 Share Posted January 16, 2015 Weird.....tables load up normal, coin up fine, and then VP9.9 crashes with an error message with "Can't create ball" upon startup of a game? Anyone know what causes this? Seems to happen more frequently I've noticed with the newer scripts being used with B2B collision scripts. Is there a tweak so XP Pro users can get by this? Does not seem to happen in Windows 7 or 8. Any help is appreciated. Link to comment Share on other sites More sharing options...
Pacdude2 Posted January 16, 2015 Author Share Posted January 16, 2015 To clarify my post...the example from the table I had this issue with first was Creature From the Black Lagoon, VP9 Version 1.1 by unclewilley. It errors out at line 1376 with the message: Variable is undefined:'bsize'. This also happens on many other tables I have. Is this a compatibility issue with using VP 9.9 exe on tables created with other versions previous? Is there a "CNT" akicker adjustment in the script that can be made to resolve? Link to comment Share on other sites More sharing options...
randr Posted January 16, 2015 Share Posted January 16, 2015 Odd..not sure if it's issue but make sure your up to date on all vbs files Link to comment Share on other sites More sharing options...
Pacdude2 Posted January 16, 2015 Author Share Posted January 16, 2015 I've noticed in the script a line regarding over riding vbs core with another ball type message. I am using the 3.43 vbs scripts. Is there another Core script I missed somewhere? Link to comment Share on other sites More sharing options...
randr Posted January 16, 2015 Share Posted January 16, 2015 Nope. Your good there are they in tables folder? Link to comment Share on other sites More sharing options...
Pacdude2 Posted January 16, 2015 Author Share Posted January 16, 2015 Yes, same folder. I may try to just reload them in the folder, delete them and then reload them. Not sure why otherwise. Link to comment Share on other sites More sharing options...
randr Posted January 16, 2015 Share Posted January 16, 2015 Might help. Make sure non are blocked also Link to comment Share on other sites More sharing options...
Pacdude2 Posted January 16, 2015 Author Share Posted January 16, 2015 non? Link to comment Share on other sites More sharing options...
randr Posted January 16, 2015 Share Posted January 16, 2015 None. Sorry on phone Link to comment Share on other sites More sharing options...
Content Provider unclewilly Posted January 17, 2015 Content Provider Share Posted January 17, 2015 Bsize is part of the updated core vbs for the create sized ball method. that should be the issue Link to comment Share on other sites More sharing options...
Pacdude2 Posted January 18, 2015 Author Share Posted January 18, 2015 UNCLEWILLY-How can I adjust this? This happens on quite a few tables I have. Thought maybe its because I'm using VP9.9 and I know some tables have to be tweaked a bit. I don't mind modding scripts, but I have a nice blend of over 150 tables ranging from early 70's to the current SAMs. Any help is appreciated, as I am kind of banging my head on the wall with this. Its usually the "Set CurrentBall(cnt) = aKicker.Createsizedball(bsize) line in the script that is redlined. Link to comment Share on other sites More sharing options...
Pacdude2 Posted January 18, 2015 Author Share Posted January 18, 2015 *RESOLVED** Sometimes we tend to overthink things when configuring tables. The simple solution was to dump my vbs scripts and reload the updated versions I thought I did already in the tables folder, and like magic-- no more ball errors. Core.vbs was outdated, as were a few others. *Great tip unclewilly, should have thought of that myself and it was easily overlooked. Charlie Link to comment Share on other sites More sharing options...
Recommended Posts
Archived
This topic is now archived and is closed to further replies.