16 replies to this topic

[cjoli]

Hi,

 

I am having a Script error on a few tables giving me a Index out of range error and I have been banging my head on this for the last few days, it only happens on a few table but all of these tables us to work fine.

 

I have looked through some of the forum trying to find a similar problem but have not found a solution, I have unblocked the B2S dll files and made sure the permission are set, like I said they where working and I don't know what changed, and its only about 4 or 5 tables.

 

I attached screen shots of the errors on a few of the tables to see if anyone has any suggestions?

 

Thanks

Attached Files

•  flash.JPG   131.93KB   15 downloads
•  Fast Draw.JPG   87.09KB   9 downloads
•  lost world.JPG   100.67KB   4 downloads
•  road show.JPG   182.73KB   6 downloads

[allknowing2012]

Do you have DOF? if not dont set the parameters on .. any chance you overwrote some of the .vbs files in the tables directory? perhaps grab fresh copies from Getting Started vbs scripts link in the top left.

[cjoli]

No I am not using DOF yet (someday) its only 5 tables that are doing it and its a new problem, is there a .vbs file that efects these, not sure how it chaged? So should I just change table script file?

[allknowing2012]

Well that first pic of Flash Gordon - another person had the same issue the other day. I believe the issue was a DOF file was placed in the tables directory that makes the tables thing you have DOF (hardware goodies in your cabinet).

Do you see anything like that?

Also try F6 - see if there is an option to disable DOF.

[Outhere]

This may be it

   message can intermittently occur in VP9.x where your max textures in vp are set to unlimited and your gfx card can't handle it. This may happen on some of the more graphically intense tables.  I'm hoping that the error handler in vp10 is improved over vp9 to correctly detect problems with the max textures and show a more informative error rather than lead you on a wild goose chase looking for rom file issues when there aren't any.  I had the same issue with ACDC intermittently showing that error in vp9 and for me I had to change the max textures setting from unlimited to 1024 (2048 still gave me the same error). Once at 1024 it ran every time without error.  It's worth a try to eliminate that possibility especially if the error returns intermittently for you.

[Sindbad]

Ii seems that you tried to play Flash Gordon that was built by me. 

 

You're using the wrong controller type. Uncomment line three to make sure that you go through the config dialog. Then start the table, the config dialog will automatically pop up. Select the proper controller type. Because you don't use DOF, select PinMame and not BS2 Server. When everything works as expected comment line 3 again.

[cjoli]

Thanks for the feedback guys, i will try some of these things later today and let you know how i make out.

 

Still don't understand why these particular tables went from working to not and what i did to case this but hopefully i can get them working again.

 

Not that this matters but just in case my system specs are, i7 16gig of ram, Nvida GTX 660 running windows 8.1

[cjoli]

Fixed! 

 

I just wanted to pass along that i was able to resolve all these problem and i thought i would share the simple fix that corrected everything. 

 

So i am still fairly new to this and its been a learning experience as i resolve one issue a new one pops up but even though i have a few more little issue i want to tackle eventually this particular one has been resolved, i had to stop running the B2S backglass in exe mode, tuning that off on each of these tables fixed the problem!

 

A few days ago, i was doing some research on the forum because a few of my tables where running a little choppy i saw that it was recommended to run the backglass in exe mode and i didn't notice that the default drop down in the backglass menu changed that for all tables (duh) so that is what happened. I now have the default set to exe as it fixed all my tables that stuttered but the 5 table I had the errors with unclicking the run in exe mode button did the trick.

 

Most of you probably already knew this but maybe it will help the next noob.

 

Thanks Guys!

[blackvulcan3]

Seems to be an error that cannot be resolved that easily. I am getting this error also. Win 10, Fresh install of VPX 10.2 Final, i5, 16gb ram, GTX 970 in a cab.

 

My backglasses are running in exe mode but still I get the errors.

 

Not all games are affected 9.93 is clean and working, Bad Cats works on 10.2, Evil Knievel, Ghostbusters, do not. Haven't been through all my tables yet. Frustrating.

[IRONBERG]

I'm having this issue right now. Running b2s as exe makes a lot of my tables run smoothly. But several of the most laggy ones gets out of range error in vp 10. Tried different versions of b2s same error. Tron cv, jurassic Park. Are some of the effected tables. Has anyone found a solution to this. Or cause for that matter?

[xenonph]

Try updating to the newest B2S Backglass Server 1.3.0.2 found here...

http://www.vpforums....&showfile=12553

 

Hope this helps you.

[IRONBERG]

I have that already it seems to be a table issue, dozer cv redux works fine but the other dozer version does not. I just have too look further to see what might cause this and look what exactly is different in the tables. Maybe a vp 10.2 table vs 10.4 table script difference.

[xenonph]

10.4 scripts are backwards compatible.

Edit:

Are you sure you have copied the 10.4 scripts into your scripts folder?

And you have no other copies of scripts anywhere else? Specially your tables folder.

 

Double Edit:

If you are using Win10,

Try right clicking your VPX.exe and click properties, then compatibility, then make sure you are not running it as administrator.

Edited by xenonph, 10 April 2018 - 10:28 AM.

[Armyaviation]

Just switched to vpx and having the same errors on about 10 out of 80 vpx tables. Tried everything so far any other suggestions

[Armyaviation]

Switched b2s to standard mode and fixed everything. Had to edit b2s settings xml file also

[butterz1977]

Fixed...I had the line 1 error ( Index out of range error) while running (Ghostbusters) windows 10...Compatibility mode was set to run for windows 7.. I unchecked windows 7 and it loaded right up.

Hope this helps 

[Encrypted]

Fixed...I had the line 1 error ( Index out of range error) while running (Ghostbusters) windows 10...Compatibility mode was set to run for windows 7.. I unchecked windows 7 and it loaded right up.

Hope this helps 

I just had this error a week ago on only select tables, it seemed right after I upgraded pinballx to 4.85. Currently running 4.87 cause i thought that was the issue. I did what you said and right clicked on pinballx and it was set for windows 8. I unchecked that and everything seems to work now. Hooray. Thanks for this.