TAF: Kicker Hole Under Fester is skewed when played but looks fine in interactive mode (F6)

[BentonQuest]

First thing sorry I posted this in the wrong area...  I don't know how to move it or delete it.   

 

Excellent looking table with exceptional detail.  Fester is great.   I am having a weird issue though.  If I run the table in VPX the hole under Fester is stretched into the playing field.  I figured I needed to adjust the table but when I run the table in Interactive Mode it looks normal (no stretch). Any ideas?  I can run older versions of this table like Bigus's and it looks fine.

 

I also noted that the blue targets to the left of Fester are transparent thru the playing field and the Kicker hole on the Swamp has the same wierdness. 

 

TAF table that I am talking about:  

 

Picture of of table running in Interactive Mode: 

 

 

 

 

 

 

 

 

 

Picture of table running in normal run mode:  

[Wylte]

Doesn't look skewed, to me - it looks like the model is showing through the playfield image.  There are other under-pf things visible as well, like the target switches.

 

Try toggling the alternative depth buffer in VPX video preferences.

[BentonQuest]

Upon closer examination, you are correct Wylte the model is showing through.  I toggled the alternate depth buffer option and restarted the VPX and the target switches are showing still.  I went in and modified the ramp under fester and unchecked the visible option and it disappeared.  The target switches are showing still but I changed a few settings on the switches and most has disappeared.  The table looks good enough now and has always played great so I am good.  Thanks for responding.   

[Wylte]

What graphics card and driver version do you have?  Newer AMD cards had depth bias issues for a bit, but it was fixed in a driver update IIRC.

[BentonQuest]

That was it.  Thank you.  My graphics is a newer AMD one.  GIGABYTE Radeon RX 6600 EAGLE 8G.  I checked the driver on Gigabyte's web site but my driver was newer with Windows update.  Based on your post though I went to AMD.com and sure enough the driver had a newer timestamp and the AMD driver fixed the problem.