3889 replies to this topic

[hauntfreaks]

39" in a standard size cab 1080p@60hz  (1920x1080) no dof  i'm lame

19" mini cab 1080p@60hz  (1920x1080) no dof

[BananaBoat]

Hard to see but those are the parameters I'm achieving with my rig. Should not be tearing or stuttering. Clean Windows install, no other software has ever run on this machine. I am doubting its a setup issue given VP9 runs extremely smooth.

I'm going to give up and see where this development lands and if others have this issue when it's eventually released. I just hope further optimizations are made between now and then.


Edit: one last thing where is the latest vpinmame.dll, worth testing as I havent updated it in a while. Thanks

Edited by BananaBoat, 01 November 2015 - 08:16 AM.

[evilantal]

And it must have started with later revisions of vpx, because it wasn't always like this...

Sent from my XT1092 using Tapatalk

Any luck finding a fix? I haven't yet.

No. I'm hoping maybe fren can shed some light on this as he's the author of both our example cases.

I know you don't actively support tftc, fren. But maybe it's something simple...

Sent from my XT1092 using Tapatalk

[vampirolatino2]

Hard to see but those are the parameters I'm achieving with my rig. Should not be tearing or stuttering. Clean Windows install, no other software has ever run on this machine. I am doubting its a setup issue given VP9 runs extremely smooth.

I'm going to give up and see where this development lands and if others have this issue when it's eventually released. I just hope further optimizations are made between now and then.


Edit: one last thing where is the latest vpinmame.dll, worth testing as I havent updated it in a while. Thanks

 

Weird, you have good results. Maybe try and put 1 in the max pre-render frame in the video options.

[toxie]

Or 0, which disables it.

 

Visual PinMAME: http://www.vpforums....ic=27063&page=1

Edited by toxie, 01 November 2015 - 08:40 AM.

[vampirolatino2]

My setup is relative new, New Vizio 43 inch, i5, 970 gpu iirc lol, 8gb ram, 254gb ssd, etc. Have the options all at max. Using B2S. Resolution is UHD, so it is triple of 1080p, don't remember it right now. No DOF atm because I have not completed the cabinet yet.

 

No stuter, but "low FPS" because of max settings and resolution.

 

Oh, it is a clean install of Windows 10, up to date drivers and updates. Internet enabled. FP, PA, PFX2, VP9.x, VP9.9, VP PM5 and VP10 installed. Some benchmark programs. Windows Defender enabled. Malware bytes enabled. Network monitor enabled. Steam. ... and I think that's it. Maybe some other programs installed, but not much.

Edited by vampirolatino2, 01 November 2015 - 08:58 AM.

[BananaBoat]

No stutter on six million dollar man, same settings.
Frame rate 415
Period 2.6

[toxie]

Maybe its really 'just' related to some of the tables.

Some feature insanely detailed primitives that are also used for collisions, and this can be the cause for micro-stuttering.

 

So maybe you can track down if the stutter is correlated to certain regions where the ball is travelling, and then the author can fix that in the next table update.

@Shockman: I'll look into these issues. This clearly shouldn't happen. Also the kickers are currently not rendered correctly, as kiwi and fuzzel pointed out, which is also not intended.  :/

 

Fixed.

 

@Shockman: btw: You can also use alpha cutouts on the playfield image instead of kicker holes to make holes into the playfield, like chepas did on the EvilDead table. This is faster to render in the end.

[BananaBoat]

Maybe its really 'just' related to some of the tables.
Some feature insanely detailed primitives that are also used for collisions, and this can be the cause for micro-stuttering.
 
So maybe you can track down if the stutter is correlated to certain regions where the ball is travelling, and then the author can fix that in the next table update.

I think this is actually the most accurate determination so far in this diagnosis and I'll try do as you suggest.
The other thing I noticed is that the ball tends to build up crazy spin (more than a real pinball arguably) and that spinning gives the impression of micro-stutter. That's just my observation.

[toxie]

I've done searches but can't seem to find the solution to this problem.  I have a few VPX tables that have a horizontal shaded portion of the table.  Not all tables have this issue.  Attached is an example of one of them.  Any solutions?

 

I just re-checked. This was introduced with the stereo3D-changes. So i fear Fren has to update the tables in question, basically the big GI lights have the 'wrong' height setting now (they reach partially 'behind' the camera, which wasn't that much of a problem before in this special case).

[toxie]

I also just limited the ball spin artificially, to avoid extreme ball spins in some strange cases.

[BananaBoat]

How is that done?

[toxie]

@BB: Limiting the maximum angular momentum the ball can have.

 

 

@all: The next build will feature static AO that is always enabled. So all people that needed to disable ambient occlusion before due to performance reasons will now get at least AO for all the static elements 'for free' (still NVIDIA only though for now).

[Kaan]

That is fantastic!

[vampirolatino2]

No stutter on six million dollar man, same settings.
Frame rate 415
Period 2.6

 

Do you have stutter in Kingpin too?

[chepas]

I also just limited the ball spin artificially, to avoid extreme ball spins in some strange cases.

 

This slowed the game down quite a lot for me. I did wonder what was going on.

 

Will have to adjust some physics settings to compensate for this change? 

[toxie]

i'll make it less then.. let me know if that makes it better..

[chepas]

A little more would be good, it's hard to make up ramps.

[fuzzel]

rev2324 is up:

 

- add static AO that is always enabled (still NVIDIA only though for now), 'old' AO is now renamed to dynamic AO
- artificially limit ball angular momentum
- fix kicker cup/hole rendering
- disable pre-rendered frames code by default
- Introducing new SciLexerVP.dll, simply drop it in VPx root - That's it! The old SciLexer.dll can be deleted.
 

[chepas]

Just bumping up the flippers strength is good enough to compensate for the momentum changes. Will that be available to set in editor?