VIRTUAL PINBALL › Forums › TABLES, DB2S,ROMS,MEDIA › Star Wars Data East VPX
This topic contains 172 replies, has 73 voices, and was last updated by Dave Smith 1 day, 3 hours ago.
-
AuthorPosts
-
March 14, 2018 at 2:30 pm #19982March 14, 2018 at 4:10 pm #19995March 14, 2018 at 4:14 pm #19996March 14, 2018 at 4:27 pm #19998March 14, 2018 at 4:36 pm #20004
Thanks for this awesome table
March 14, 2018 at 4:36 pm #20005Thanks to everyone for another awesome table!
March 14, 2018 at 4:52 pm #20006hi,
thank you for this table but I have a problem :
table start ; DMD is OK but an error message : “incorect properties for ‘DropTargetLights’March 14, 2018 at 4:57 pm #20007Thanks for this nice release.
I got same error with 10.4 and 10.5 beta VPX. (Wrong number of arguments ‘DropTargetLights’).
March 14, 2018 at 4:58 pm #20008I have no idea what would cause that error, but there’s not much consequence to removing/commmenting out line 862 which calls this function
FadeLights.Callback(6) = “DropTargetLights ”
I’d be curious if the error moves to the next light though.
March 14, 2018 at 4:59 pm #20009March 14, 2018 at 5:05 pm #20010I’ve got the same error.
After commenting out line 862, there’s the next error.I have VPX_5_beta_rev3359.
Attachments:
You must be logged in to view attached files.March 14, 2018 at 5:06 pm #20013The only thing I can think of is a language/regional thing, vbscript may be giving decimals with commas, which would confuse the callback routine. (“1,23” instead of “1.23” would be interpreted as two parameters instead of one). You could try changing the decimal symbol in regional settings to “.” which ought to fix it until I figure out a fix for the script.
March 14, 2018 at 5:10 pm #20014March 14, 2018 at 5:25 pm #20015The only thing I can think of is a language/regional thing, vbscript may be giving decimals with commas, which would confuse the callback routine. (“1,23” instead of “1.23” would be interpreted as two parameters instead of one). You could try changing the decimal symbol in regional settings to “.” which ought to fix it until I figure out a fix for the script.
That’s helpful. Thanks.
March 14, 2018 at 5:28 pm #20016I did confirm that the comma decimal separator is indeed what causes this. You will have the same issue with Dr. Dude 2.0 as well. I will share what I found with nFozzy and Wrd1972. Try replacing the script with this.
-
AuthorPosts
You must be logged in to reply to this topic.