1353 replies to this topic

[shadowshd]

But you use the same core scripts for both tests?

If yes, could you search core.vbs for Private Function PinMAMEInterval and then replace the following code block (up to, but excluding End Function) with just PinMAMEInterval = 3 and retest please with 10.2? Thanks!

 

Hi Toxie,

 

Yes I run VPX 10.1 with 10.2 scripts (located in VP\Scripts with no duplicates).

All executables relatives to VP are run as administrator.

 

I've just tested by replacing all code between Private Function PinMAMEInterval and End Function with PinMAMEInterval = 3 and get a little less stutter, but it's still here.

 

It's flagrant in Scared Stiff when the ball hits the woodbox or in Medieval Madness X when the ball hits the castle door then goes down to the flippers, and in multiball modes.

 

My VPX 10.1/10.2 video options :

 

 

I've updated nVidia drivers to 376.19 12/05/2016 two days ago but they don't help.

 

With 10.1 exe + 10.2 vbs, tables run very smoothly with no lag or stutter.

 

Thanks

Edited by shadowshd, 08 December 2016 - 02:32 PM.

[toxie]

phew.. thats complicated then.. could be all kinds of stuff that we tweaked.. I'll try to think about it somemore..

Is it possible to code (if it doesnt already do this) less bounce near the ends of the rubber compared to the middle of a rubber? Just thinking about this .. the ball would bounce more in the center (lengthwise) versus hitting the rubber close to the posts.

 

hmmm.. that would mean that somehow the physics parameters would be varying over the rubber..

do you have any idea what that would mean in the VP world? e.g. which parameter(s) would be more/less towards the ends? maybe we could hack this in reasonably simple.

@shadowshd: one more thing: is there anything majorly different in the "F11" statistics between VP10.1 and 10.2?

[fuzzel]

I fear that's not so easy. You can't tell from the control points where the rubber is bent over a post or not to everything else not

[toxie]

hmmm.. also true.. couldn't we guess something about the neighborhood though, e.g. if its bent or straight? (of course there could still be a post behind a straight rubber segment )

[Ben Logan]

Maybe there could be a way to split flipper rubbers in half. Set high elasticity at the base, low elasticity toward the tip of bat.

[shadowshd]

@Toxie : Here's my VPX 10.1 & 10.2 stats with MMX, after playing some minutes :

 

VPX 10.1 :

 

 

 

VPX 10.2 :

 

 

I don't really know what some of these values mean, but FPS are stables, so are they with Scared Stiff.

When stutters happen FPS won't drop.

 

++

[BorgDog]

I fear that's not so easy. You can't tell from the control points where the rubber is bent over a post or not to everything else not

 

Would it be possible to set parameters for sections of the rubber based on control points? And can we also distinguish hit events by section (active slingshot vs hit like on walls maybe).

[toxie]

Not easily, as fuzzel pointed out already. :/

 

@shadowshd: Thats strange. Basically almost all stats look better in 10.2. But it at least once happened in 10.2 that you got a ~4-frame delay (the 61.1 max value), but in 10.1 only a ~2-frame delay. This does not have to mean anything, could have been just a glitch when the table started (e.g. when the gfx driver uploads some textures or so, on-demand), so overall there is not really anything there that points to something specific.  :/

[fuzzel]

I fear that's not so easy. You can't tell from the control points where the rubber is bent over a post or not to everything else not

 
Would it be possible to set parameters for sections of the rubber based on control points? And can we also distinguish hit events by section (active slingshot vs hit like on walls maybe).

Sure we could all do that but it would make things much more complicated again. And even if we had the information we had to add another weird hack to the physics. So i wouldn't add such stuff to VP.

[Epistaxis]

I don't know if this is the right place to post this. So sorry in advance if it's not. 

 

I update to the new 10.2 beta from 10.1 and I keep getting the error message.

Fatal error D3DERR_INVALIDCALL (0x8876086c: Invalid call) at RenderDevice,cpp:830

 

And it dose it on any table I play on. 

 

So if any one could hep that would be great. Thanks 

 

 

 

Edited by Epistaxis, 08 December 2016 - 06:54 PM.

[toxie]

@shadowshd: you could also try to add a registry key: Under the Visual Pinball/VP10 registry folder:

"Player" / "EnableLegacyMaximumPreRenderedFrames" as a DWORD with value 1

 -> always force old VP9.X-like hack to force the driver to discard pre-rendered frames
 

this will make the behavior of Maximum pre-rendered frames in the video preferences the same as in VP10.1 then

[shadowshd]

I've just tried the registry key but I can't see any improvements.

 

I also tried with FXAA and AO disabled, but still no improvements 

 

Anyway thanks for trying to find what can cause the issue

 

++

[toxie]

Very weird, really..

[shadowshd]

I agree Toxie, these two tables run perfectly with VPX 10.1 but lag with 10.2

 

++

[Mark70]

I agree Toxie, these two tables run perfectly with VPX 10.1 but lag with 10.2

 

++

could it be due to VPX 10.1 is not using the new lightning features?

[shadowshd]

I will test on a fresh and clean Windows 10 installation, the issue may come from something in my system

 

++

[toxie]

But thats a good theory. Is there something with these tables that is only triggered when using 10.2? Like the modulated flashers?

[Mark70]

Yes, both table use the new modulated flashers.

I had similiar issues with scared stiff and one other table, but in my case I could solve it with the pre-rendered frames value, as reported on page 50.
http://www.vpforums....=35311&p=364824
 

[ICPjuggla]

I've also noticed significant lag in 10.2 it started in the last few revs.

Sometimes animations seem to run in slow motion..

[toxie]

any specific table(s) where the animations problem happens?