230 replies to this topic

[gigalula]

Still same problem after loading table i press play it terminates no warnings or errors

 

vp 921 works fine

 

 

Ensure to have DirectX installed and also if you tried "SweetFX" in the past like I did then make sure that "SweetFX" folder is present in Tables folder... When I made a full install on my cab after that I copied file from PC to CAB and by doing this I omitted to copy SweetFX folder inside Tables folder and the problem was exactly like you describe... so the best is a fresh full install including DirectX. So now all SweeFX trace or modification have been remove from PC as well as CAB so that way I'm sure if something strange happen then it's not coming from any modification ...Always the best to stick to default setup

 

You can always take a look at the LOG file from VP folder to see if you can find any possible error logged.

Edited by gigalula, 29 October 2014 - 05:07 PM.

[toxie]

All I have tried with VP9.9.1 works just like it did in V9.9.a or VP9.9

I agree with kruge99, it looks like an anti -aliasing error. Maybe the ball have anti-aliasing in the image, or the Antialiasing Mode is forced in the graphics card driver.

 

The balls aren't sorted back to front, maybe i'll add that to this release as an exclusive VP9.9.1 (as in VP10 the ball rendering is finally done in -real 3D- ) feature though, lets see..

Edited by toxie, 29 October 2014 - 05:27 PM.

[BigHein]

yes i have directx version 11  windows 8.1

 

i instalt the directx web installer as well

[toxie]

Do other directx based programs run?

Which graphics card(s) do you have?

[BigHein]

yes all the games running fine

 

videocard is nvidea geforce gtx 780m

 

d3dxcreateEffectfromfile failed

Edited by BigHein, 29 October 2014 - 05:58 PM.

[BigHein]

i fix the problem copy windows system  d3d9.dll to vp dir overide the existing d3d9

[toxie]

i updated the 9.9.1 (potential) release in the original post: http://www.vpforums....e=9#entry286625

it has the correct version number (forgot that one), and overlapping balls will be nicely anti-aliased now.. 

[kruge99]

i updated the 9.9.1 (potential) release in the original post: http://www.vpforums....e=9#entry286625

it has the correct version number (forgot that one), and overlapping balls will be nicely anti-aliased now.. 

 

I'm not sure what happened, but somewhere along the way, VP9.9.1 (both versions) crashes when the table is loading, after I click the play button on my Windows 7 64bit PC.  It seems to run fine on my Windows 8 64bit notebook.

 

 

VP9.9.0.a runs perfectly fine. 

 

Were there any changes to the registry and what if I delete my whole vpinball registry entry?  (not the vpinmame part)

 

Best Regards,

Todd.

 

p.s. deleting the the whole VP registry key did not solve this problem.  Also, VP9.9.1 crashes with and without running the EXE as administrator.

Edited by kruge99, 30 October 2014 - 10:28 AM.

[StevOz]

Tried the new version and the same render errors, banding on ball seems to miss the occasional frame and flipper rendering errors also, whilst with VP9.90a this just does not occur whatever setting I force through the nvidia latest driver or VP options. It's impossible to capture a shot of these errors, as every captured shot render is without fault. W7, core i3, GTX660.

Edited by StevOz, 30 October 2014 - 10:47 AM.

[toxie]

Both stuff is very very weird.. The only reason i can think of is that maybe Mukuste used a different compiler version than me (i had that issue already at some point a while back when doing test releases)..

@Kruge99: Is that only for a specific table or in general?

 

Apart from that there weren't any major changes, as said, the only "new" thing is the addition of the new nudge & plunger code by mjr (which just adds a new checkbox in the key settings).

[kruge99]

Both stuff is very very weird.. The only reason i can think of is that maybe Mukuste used a different compiler version than me (i had that issue already at some point a while back when doing test releases)..

@Kruge99: Is that only for a specific table or in general?

 

Apart from that there weren't any major changes, as said, the only "new" thing is the addition of the new nudge & plunger code by mjr (which just adds a new checkbox in the key settings).

 

To be honest, I only tried two tables that are compatible or made with VP9.2.1 because that was all I had time for before leaving for work this morning.  I'll try and download a VP9.9.x specific table and try again on my Windows 7 64bit PC tonight.

 

That being said, I recall testing both of those tables on my Windows 8 64bit notebook and they played fine.

Edited by kruge99, 30 October 2014 - 02:37 PM.

[toxie]

Cool, keep me updated please..

[jpsalas]

Those errors with the ball only happen to me if I force anti-aliasing in the Nvidia Control panel. If I only activate anisotropic filtering and the antialiasing-FXAA, then all the tables I have tried work very well with no graphical errors. I have tried the latest night modes which include a lot of flashers. I have also tried some of my older tables which use alpha ramps as flashers and they also work fine. I use W7 64bits, GTX-680.

[kruge99]

Cool, keep me updated please..

 

OK, I tried this table:

 

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

 

and the latest VP9.9.1 crashed exactly the same way as with the VP 9.2.1 tables.

 

That table plays fine in VP9.9.0a btw which totally doesn't make sense.

 

How do I fix this?  Any chance that running physmod5 caused this?  I know I haven't run physmod5 on my notebook.

Edited by kruge99, 30 October 2014 - 10:50 PM.

[StevOz]

Well for what it's worth I never forced any Nvidia Control panel adjustments with the new VP9.91 and I still got those render errors? Very strange, running W7 64bit Home edition with an haswell i3, 8GB, GTX660 and the latest drivers, as I said with VP9.90a I can, have adjusted any, all settings and those render errors never occur?

 

Additionally I have used physic mod 5, though I generally don't use it as it also produces various render errors like green spots on the ball?

Edited by StevOz, 30 October 2014 - 11:00 PM.

[Slydog43]

green spots are a toggle to show spin, f11 to turn off (I hope thats the key) with physicsmod

Edited by Slydog43, 31 October 2014 - 03:50 AM.

[kruge99]

 

Cool, keep me updated please..

 

OK, I tried this table:

 

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

 

and the latest VP9.9.1 crashed exactly the same way as with the VP 9.2.1 tables.

 

That table plays fine in VP9.9.0a btw which totally doesn't make sense.

 

How do I fix this?  Any chance that running physmod5 caused this?  I know I haven't run physmod5 on my notebook.

 

 

I solved my VP9.9.1 crashing problem!!

 

It was an outdated vpinmame.dll - I 'upgraded' to the recently released 'alpha' version uploaded by Toxie and now VP9.9.1 is running so it's back to testing!

[toxie]

???

 

Thats pretty strange.. Whatever, it seems like except for StevOz's weird rendering problems everybody else is problem-free so far??

[BobAlbright]

Working ok for me, Toxie

[kruge99]

???

 

Thats pretty strange.. Whatever, it seems like except for StevOz's weird rendering problems everybody else is problem-free so far??

 

Just to note, I'm playing desktop tables on a 42" TV in widescreen mode, I am not testing on a cabinet.

 

I had some time to spare and I played a few 9.x tables as well as the Road Kings 9.9.x table and the only things I noticed so far are a 'feeling' of flipper lag (probably due to using the default physics adjustments?) that couldn't be corrected setting the max pre-rendered frames to 1 in VP and in the nvidia control panel and there were two times where VP lost focus.  This was easily resolved by alt-tabbing to bring VP to the foreground and then vpinmame if it was rendering a window and not integrated into the desktop backdrop. 

 

The VP9.x tables I had time to test are:

 

Nitro Ground shaker by Eala

TOTAN 3.1.1 by JP

Eight Ball 2.0 by Megapin

Black Knight 2.1 by JP

High Speed 1.05 by Kruge99