86 replies to this topic

[DJ Wheels]

Thank you Htamas! worked like a charm!

 

getting the following error:

VBS Script

object doesn't support this property or method.

 

-I click on ok and the table works fine.

 

My guess is that you're using the UVP backglass.

The old UVP controller doesn't know the DoubleSize property. So go to the script and comment line 114 (put a single quote in front of it).

 

[htamas]

 

Thank you Htamas! worked like a charm!

 

Glad it helped... I had the same problem, but it was a quick fix.

However I wonder how the UVP backglass works on your system... for me, it was complete stutter-fest using UVP. The dB2S backglass fixed that problem, plus it looks much nicer too

 

I also had the occasional crash when starting the table. As it was mentioned earlier in this thread, resizing the unnecessarily huge images fixed that issue instantly. I mean, who needs images that are 4000+ pixels height, when 1080p is only 1920 pixels? Resizing those to a much more manageable size doesn't cause any degradation in visuals, but it reduced the table size by about 12 MB... now it starts every time without any problem.

 

By the way, my formatting / layback settings are 2/45/80/270/1.22/1.95/-297/230 if someone is interested

 

Great table, thank you very much Javier!

Edited by htamas, 08 August 2013 - 06:07 AM.

[fuzzel]

NB DirectX can only handle textures with a power of 2. Keep that in mind if you resize textures (512,1024,2048) for width and height.
If the textures have weirded size e.g 1000x2000 VP has to resize them to the next power of 2 size and that needs extra RAM

[JAM0]

 

 

Thank you Htamas! worked like a charm!

 

Glad it helped... I had the same problem, but it was a quick fix.

However I wonder how the UVP backglass works on your system... for me, it was complete stutter-fest using UVP. The dB2S backglass fixed that problem, plus it looks much nicer too

 

I also had the occasional crash when starting the table. As it was mentioned earlier in this thread, resizing the unnecessarily huge images fixed that issue instantly. I mean, who needs images that are 4000+ pixels height, when 1080p is only 1920 pixels? Resizing those to a much more manageable size doesn't cause any degradation in visuals, but it reduced the table size by about 12 MB... now it starts every time without any problem.

 

By the way, my formatting / layback settings are 2/45/80/270/1.22/1.95/-297/230 if someone is interested

 

Great table, thank you very much Javier!

 

Where can I get the DB2S for this table?

[htamas]

Where can I get the DB2S for this table?

 

Google is your friend...

[DJ Wheels]

UVP works fine on my cabs, which is one reason why I haven't switched over to b2s.  Not to mention B2S makes my tables hang up, when exiting a table through Hyerpin, I have to press "exit" twice for HP to regain focus.

 

 

Thank you Htamas! worked like a charm!

 

Glad it helped... I had the same problem, but it was a quick fix.

However I wonder how the UVP backglass works on your system... for me, it was complete stutter-fest using UVP. The dB2S backglass fixed that problem, plus it looks much nicer too

 

 

[JAM0]

 

Where can I get the DB2S for this table?

 

Google is your friend...

 

Thanks    This table is quite addictive....I have been playing it a lot the past couple of days.

[htamas]

NB DirectX can only handle textures with a power of 2. Keep that in mind if you resize textures (512,1024,2048) for width and height.
If the textures have weirded size e.g 1000x2000 VP has to resize them to the next power of 2 size and that needs extra RAM

 

Thanks for that insight, good to know.

 

Does this mean that both dimensions of an image need to be a power of 2? So in other words, if either the width or height of an image is not exactly a number that's ^2, then VP will re-size it?

In that case, it is probably best to only re-size huge images to be a tad larger than 1920 height / 1080 width, so that when VP re-sizes them again, it will make the image smaller instead of a dimension being increased which may degrade the image quality.

Do I make sense? OR how does this work exactly?

[JAM0]

 

NB DirectX can only handle textures with a power of 2. Keep that in mind if you resize textures (512,1024,2048) for width and height.
If the textures have weirded size e.g 1000x2000 VP has to resize them to the next power of 2 size and that needs extra RAM

 

Thanks for that insight, good to know.

 

Does this mean that both dimensions of an image need to be a power of 2? So in other words, if either the width or height of an image is not exactly a number that's ^2, then VP will re-size it?

In that case, it is probably best to only re-size huge images to be a tad larger than 1920 height / 1080 width, so that when VP re-sizes them again, it will make the image smaller instead of a dimension being increased which may degrade the image quality.

Do I make sense? OR how does this work exactly?

 

Good question htmas. I thought "a power of 2" meant even numbers instead of odd numbers. Now I am not sure what it means. I am guessing that it is a number that you are able to take a square root of that turns out to be a whole number.

 

It is interesting that this table ran great when I was using a static backglass. Now that I added the DB2S, it had trouble loading and when it did, I had some stutter. That is the first time that has ever happened with DB2S or B2S for me. I resized some plastics, as was suggested, and now it seems to be OK, although the FPS's are only around 70. I am wondering if I didn't size them correctly re the power of 2. I am guessing that the DB2S is also large, as it appears high-resolution (looks nice!). My card has 2 gb video ram so I am thinking it could be the power of 2 issue.

 

EDIT... I had been running it on vp915 because it wouldn't load on vp916. Just tried it again on 916 after the re-size of the plastics and it runs great! I am getting 270 FPS, up from 70 on vp915!

Edited by JAM0, 08 August 2013 - 10:03 PM.

[oldskoolgamer]

beautiful table! Bravo my friend

[RipleYYY]

all settled well, but also got that ROM prob (not recognised), that can go no further with the game... will try reloading it, but...

[fuzzel]

Both dimensions should be a power of 2 e.g. 256x256 or 1024x1024. It's also possible to use other sizes like 300x256 or 500x1024 as long as the height is a power of 2.
Newer graphic cards can handle other sizes as well but I don't know how the drivers handle the backwards compatibility with DX7. So it's better to use sizes I mentioned above.

[numiah]

Am I the only one with a crashing table when the LedWiz is enabled ?

[luvthatapex]

I had the exact same problem as you until I resized the plastics to 75% of their size.

The plastics are too large.

 

Now it plays great on my cab with the flashers blazing!

 

Am I the only one with a crashing table when the LedWiz is enabled ?

 

[numiah]

Yeah, thanks, I tried reducing them to 75% earlier, but to no avail.

I'll check if there are any other weirdly large images present.

[htamas]

It is interesting that this table ran great when I was using a static backglass. Now that I added the DB2S, it had trouble loading and when it did, I had some stutter. That is the first time that has ever happened with DB2S or B2S for me. I resized some plastics, as was suggested, and now it seems to be OK, although the FPS's are only around 70. I am wondering if I didn't size them correctly re the power of 2. I am guessing that the DB2S is also large, as it appears high-resolution (looks nice!). My card has 2 gb video ram so I am thinking it could be the power of 2 issue.

 

EDIT... I had been running it on vp915 because it wouldn't load on vp916. Just tried it again on 916 after the re-size of the plastics and it runs great! I am getting 270 FPS, up from 70 on vp915!

 

Hm... interesting. I'm running the latest 9.16 build and average framerate is about 350. After replacing the UVP with dB2S, I thought all stuttering problems are resolved but then I noticed that when flashers are very active, there is still some stutter (whereas with UVP the ball stuttered constantly, so dB2S was a definite improvement).

So I ended up modifying the dB2S, got rid of the flasher snippets and replaced them with regular lamps (because they are easy to re-size). I also decreased the number of light frames tied to one solenoid, for the most part there is 1 light per solenoid now, only a couple of solenoids are still driving two lights. I also tweaked the performance of the backglass, skipping something like 20 solenoid frames, it still looks pretty active and the stutter is almost completely gone but not perfect. In some scenarios (like when I make the bridge shot and the ball is rolling towards the right flipper) I can still see some very slight stutter.

I suppose the way this table was built is very demanding and as you said, the backglass is also large with a lot of flashers, so that has its toll on performance.

I didn't have such issue with any other table / dB2S combination before, no stutter to speak of so this is the first. Oh well, it is a lot better now

Edited by htamas, 10 August 2013 - 04:38 AM.

[BobAlbright]

Very nice...and tough!

[fuzzel]

Btw the maximum texture size VP supports is 4096x4096 everything else will be downscaled

[rob046]

Will this ever see a desktop version?  If so I'd love to try it, been wanting to see this table updated for many years.

[mountaingamer]

I have two questions with this table. First, do the flippers seem laggy to anyone? And would adjusting them fix laggieness? And how do I update ledwiz to work on this table - is it the .ini file or .vbs??? Thanks!