3889 replies to this topic

[freneticamnesic]

yea that's the one. Looks related to the stuff brandrew has been working on. not a big deal but it should be noted somewhere if the change is going to be permanent

[toxie]

we have to fix the detection then i guess..  :/

[fuzzel]

Yes the message is just a warning that when the script editor can't find the core.vbs file then the code completion and function list with the information coming from that file won't work.

[toxie]

i just added the currently loaded table path to the search paths, that should hopefully fix it.

[32assassin]

sorry if this has been covered but I don't feel like going through 156 pages of posts.

 

I been adding lights as LED score displays for desktop users on all my VPX tables.

 

with this code

Dim DesktopMode: DesktopMode = Table1.ShowDT

'if Full Screen turn off Backglass lights
If DesktopMode = True Then
dim xxx
For each xxx in BL:xxx.Visible = 1: Next
else
For each xxx in BL:xxx.Visible = 0: Next
End if

I created a collection called BL, and added all the backglass lights to this collection

 

 

 

 Capture2.PNG   92.96KB   17 downloads

 

 

if the check (Yellow highlight)  Use DT

the table is in desktop mode and the backglass lights are visible.

 

if I un-check the Use DT option

the table is played in full screen and the backglass lights are hidden.

 

Everything works great.

 

 

But then I noticed the "Rotate for Cabinet Usage" (red highlight).

 

 

I'm assuming this is universal FS or DT switch.

 

1. DO we have to  add code to the script in order to enable this option 

I enabled the "Rotate for Cabinet Usage" and nothing happens.

 

2. if its not a universal DT/FS  switch,  can we move the "Use DT"  option to the Video Option menu

     I'm assuming that every one is going to either run their tables in DT or in FS.  It would be nice to be able to switch multiple tables from

DT to FS with just one click.

Edited by 32assassin, 24 October 2015 - 08:23 AM.

[ninuzzu]

After you check "rotate for cabinet usage"  , you need to close vp and restart if you want to see the changes.

The script is ok, I also use it and set options for DT only  or FS only

[fuzzel]

rev2266 is up:

 

- add currently loaded table path to search path for core.vbs
- add PlayfieldReflectionScale() on Balls and BallPlayfieldReflectionScale() on Table (and UI Options) to scale/dampen the Playfield contribution to the Ball reflection
- spinner overhang removed and hit shape for bracket adjusted
- fix seawitch reflection issue

 

Edited by fuzzel, 24 October 2015 - 09:49 AM.

[Brandrew]

yea that's the one. Looks related to the stuff brandrew has been working on. not a big deal but it should be noted somewhere if the change is going to be permanent

 

Sorry, hands up, guilty.   I wrongly assumed core.vbs working copy was kept in scripts folder, assumptions eh? Part of the human condition. As for making it permanent - that's up to you, the users! Just to confirm it is definately the tables folder.
BTW I know those colours are horrible in the code viewer, I'm doing colors/colours & fonts ATM, then the grunt work of intelisense.
Thanks for your patience during these troubling times.

[njamont]

Hi Guys,

 

can you help me on my specs for VP10 using in a cabinet

 

specs:

 

E7600 Dual Core Intel Proc 2.8

2Gb of ram

1GB GTS 250

 

above setup runs 9.x fine without any hickups

 

but vpx with the circus voltaire table from dozer runs with a lot of stutter

 

i can remember VP was only graphic card hungry and did not care for the internal 2 gb of memory on my motherboard has this changed?

 

Can anyone advise me what to upgrade?

Hi Guys,

 

can you help me on my specs for VP10 using in a cabinet

 

specs:

 

E7600 Dual Core Intel Proc 2.8

2Gb of ram

1GB GTS 250

 

above setup runs 9.x fine without any hickups

 

but vpx with the circus voltaire table from dozer runs with a lot of stutter

 

i can remember VP was only graphic card hungry and did not care for the internal 2 gb of memory on my motherboard has this changed?

 

Can anyone advise me what to upgrade?

 

 

*edit*

 

tested attack from mars beta and monster bash from UW those run speedy but they are not complete with the graphics

voltaire is a really heavy load my system it seems

Edited by njamont, 24 October 2015 - 11:37 AM.

[fuzzel]

Please open a thread in the help forum not here. This thread is for the beta test phase.

[dyopp21]

I tried the vsync settings set to 120. This made the tearing on the disappear but when flasher go on and of I can still see the tearing lines in the area lit by the flasher.
Also when I rapidly move the flippers multiple times in a row, I can see some vertical lines separating the flippers a little bit, like it's a pre-rendered image not aligned properly.

Thanks for the help

Edit: the lines seem to have moved to another part of the playfield, a not so eye-catching one but they're still there.

I've experienced the breaking line moving to another part of the screen as well. During the last few months I've tried 0/1/2/60/120, with different pre-render options and a different setting will make the line move around, but it's still there. And if the flipper is in the break line it's pretty visible as well. If you have the old EM table "Space Walk" load it up and check out the top right flipper. I would imagine it's going to be right on the line and it makes a mess of it.


Sent from my iPhone using Tapatalk

I tried the vsync settings set to 120. This made the tearing on the disappear but when flasher go on and of I can still see the tearing lines in the area lit by the flasher.
Also when I rapidly move the flippers multiple times in a row, I can see some vertical lines separating the flippers a little bit, like it's a pre-rendered image not aligned properly.

Thanks for the help

Edit: the lines seem to have moved to another part of the playfield, a not so eye-catching one but they're still there.

I've experienced the breaking line moving to another part of the screen as well. During the last few months I've tried 0/1/2/60/120, with different pre-render options and a different setting will make the line move around, but it's still there. And if the flipper is in the break line it's pretty visible as well. If you have the old EM table "Space Walk" load it up and check out the top right flipper. I would imagine it's going to be right on the line and it makes a mess of it.


Sent from my iPhone using Tapatalk

[jpsalas]

 

yea that's the one. Looks related to the stuff brandrew has been working on. not a big deal but it should be noted somewhere if the change is going to be permanent

 

Sorry, hands up, guilty.   I wrongly assumed core.vbs working copy was kept in scripts folder, assumptions eh? Part of the human condition. As for making it permanent - that's up to you, the users! Just to confirm it is definately the tables folder.
BTW I know those colours are horrible in the code viewer, I'm doing colors/colours & fonts ATM, then the grunt work of intelisense.
Thanks for your patience during these troubling times.

 

 

Actually the vbs files should be in the scripts folder. The reason that they were copied to the tables folder was a wrong line in the Sub LoadVBS. But that was fixed more than 10 years ago. But it is good that you can put another set of vbs files in the table's folder for testing purposes (not taht many of us do core.vbs testing ). The vbs files are much easier to update when they are just in one place and not in my 20 or more folders with tables (you know, some sorted by author, other by year, and then you have vp7 tables, vp8 tables, vp9 tables, pm5 tables, vpx tables which may also be sorted by other categories, original, computer, EM, vpm, etc )

[toxie]

But then I noticed the "Rotate for Cabinet Usage" (red highlight).

 

I'm assuming this is universal FS or DT switch.

 

1. DO we have to  add code to the script in order to enable this option 

I enabled the "Rotate for Cabinet Usage" and nothing happens.

 

2. if its not a universal DT/FS  switch,  can we move the "Use DT"  option to the Video Option menu

     I'm assuming that every one is going to either run their tables in DT or in FS.  It would be nice to be able to switch multiple tables from

DT to FS with just one click.

 

1) No

2) The switch in the backdrop settings is just for authors to quickly test DT vs FS parameters and is -not- saved. The 'average user' will just use the global video option.

Edited by toxie, 24 October 2015 - 01:36 PM.

[mpad]

Actually the vbs files should be in the scripts folder. The reason that they were copied to the tables folder was a wrong line in the Sub LoadVBS. But that was fixed more than 10 years ago. But it is good that you can put another set of vbs files in the table's folder for testing purposes (not taht many of us do core.vbs testing ). The vbs files are much easier to update when they are just in one place and not in my 20 or more folders with tables (you know, some sorted by author, other by year, and then you have vp7 tables, vp8 tables, vp9 tables, pm5 tables, vpx tables which may also be sorted by other categories, original, computer, EM, vpm, etc )

So why does no one update those crappy install instructions manuals on this page. Or at least get rid of them. Not following them could save a lot of time and false truths. Noobs are doomed if they read them.

Edited by mpad, 24 October 2015 - 02:40 PM.

[vampirolatino2]

I like to have the scripts separated in their script folder, not in tables

so... a vote to fix them in one place hehe

 

I tried the vsync settings set to 120. This made the tearing on the disappear but when flasher go on and of I can still see the tearing lines in the area lit by the flasher.
Also when I rapidly move the flippers multiple times in a row, I can see some vertical lines separating the flippers a little bit, like it's a pre-rendered image not aligned properly.

Thanks for the help

Edit: the lines seem to have moved to another part of the playfield, a not so eye-catching one but they're still there.

I've experienced the breaking line moving to another part of the screen as well. During the last few months I've tried 0/1/2/60/120, with different pre-render options and a different setting will make the line move around, but it's still there. And if the flipper is in the break line it's pretty visible as well. If you have the old EM table "Space Walk" load it up and check out the top right flipper. I would imagine it's going to be right on the line and it makes a mess of it.


Sent from my iPhone using Tapatalk

I tried the vsync settings set to 120. This made the tearing on the disappear but when flasher go on and of I can still see the tearing lines in the area lit by the flasher.
Also when I rapidly move the flippers multiple times in a row, I can see some vertical lines separating the flippers a little bit, like it's a pre-rendered image not aligned properly.

Thanks for the help

Edit: the lines seem to have moved to another part of the playfield, a not so eye-catching one but they're still there.

I've experienced the breaking line moving to another part of the screen as well. During the last few months I've tried 0/1/2/60/120, with different pre-render options and a different setting will make the line move around, but it's still there. And if the flipper is in the break line it's pretty visible as well. If you have the old EM table "Space Walk" load it up and check out the top right flipper. I would imagine it's going to be right on the line and it makes a mess of it.


Sent from my iPhone using Tapatalk

 

 

I think I know what you are experiencing .... but I think is a combination of things... because I can't notice anything anymore in my new VP PC build + TV I'm using right now. But in the past I had the exact same problem you are having. What are your PC specs and TV?

[sliderpoint]

My scripts are also in the scripts folder.

-Mike

[Brandrew]

Code viewer core.vbs file folder search order:

1. vpinbal.exe\scripts\core.vbs

2. CurrentTablePath\core.vbs ,

3. LoadDir\core,vbs

4.Code Viewer Warning - It just means that highlighting (and intelisense ) will not be available.

Hope that's clarified that!

 

@Mr Salas: Hello sir! Pleased to meet you. I don't feel as bad now in that the knowledge that I dusted off a 10 year old bug!

Edited by Brandrew, 24 October 2015 - 04:19 PM.

[32assassin]

After you check "rotate for cabinet usage"  , you need to close vp and restart if you want to see the changes.

The script is ok, I also use it and set options for DT only  or FS only

 

 

But then I noticed the "Rotate for Cabinet Usage" (red highlight).

 

I'm assuming this is universal FS or DT switch.

 

1. DO we have to  add code to the script in order to enable this option 

I enabled the "Rotate for Cabinet Usage" and nothing happens.

 

2. if its not a universal DT/FS  switch,  can we move the "Use DT"  option to the Video Option menu

     I'm assuming that every one is going to either run their tables in DT or in FS.  It would be nice to be able to switch multiple tables from

DT to FS with just one click.

 

1) No

2) The switch in the backdrop settings is just for authors to quickly test DT vs FS parameters and is -not- saved. The 'average user' will just use the global video option.

 

 

 

got it thanks. everything works 

 

 

and on a side note.  

I'm not having the missing script errors.

 

then again,  I did not install my VPX in my VP9 folder.

Each system has its own scripts folder.

[hauntfreaks]

 

Woosh. VPX no longer recognizes vbs in the tables folder, bug or intentional?

 

i'm getting the same error....only in 2260

 

 

still getting this same error 2266... I read the explanation why, but I think what we dont understand is why the change?.... 50 beta's in and make this change?.... is there really a good reason?.... some of run clean folder structures (not just one folder jumbled with all the VP versions)... this seems more like a wrench in the gears.... just my opinion

[freneticamnesic]

 I simply added the vbs files to the scripts folder and it worked fine, is there a reason you aren't able to do that?

I can confirm that 2266 didn't "fix" it though