- This topic has 84 replies, 35 voices, and was last updated 5 years ago by
.
-
Posts
-
@scgamer2k9 : That error can come from time to time. It can be many reasons for it. One being your graphics drivers. Not closing VPX in between games, a mix between graphics drivers and restart too. Do you get it every time that you start the table ? I still run quite old nVidia drivers on my cab, don’t really want to change them because they seem to work just fine. But, for Firepower, where the screen space reflections was “forced to on”, via the table itself, it would crash on loading. So, experimenting with some of the graphics options under the table and globally might be the trick. Or, consider upgrading your graphics drivers and get 10.6.1 release.
You need to login in order to like this post: click here
1 user thanked author for this post.
Thanks for the reply. I just started into this whole hobby last week and am running on a laptop. So you think upgrading VPX to 10.6.1 would help on a laptop?
You need to login in order to like this post: click here
It surely won’t hurt, but, I don’t really think that it will. It is more likely that the other things I mentioned is the real culprit.
You need to login in order to like this post: click here
1 user thanked author for this post.
I didn’t know what you meant at first, but then I realized it. I lowered max texture dimension down one level to 3072. That solved the problem not only with this table, but several others. Thanks for the pointers!
You need to login in order to like this post: click here
Happy to hear that. If your family can afford it, maybe ask Santa for a better GPU this year ?
You need to login in order to like this post: click here
Forums are currently locked.
