16 replies to this topic

[bosvrucht]

i am using XP with a nvidia gtx 460,  and only the 270.xx driver series works flawlessly. I have tried many newer drivers, 301.xx, 314.xx etc etc. ,   to get FXAA to work.

 

These newer drivers work (and FXAA is awesome), but all have the same problem: after loading 2 or three tables in hyperpin, loading a new tables leads to a unresponsive/super slow system until the table is exited (which takes 30 seconds or so).

 

If you have XP, what driver are you using?

 

 

[pinball buzz]

Not sure at the moment, but will check when I get chance. Cheers Buzz:) Sent from my Nexus 7 using Tapatalk HD

[htamas]

Unfortunately, the same problem happens on my setup as well like you described when I'm trying to use a driver that supports FXAA. Many tables work fine but there are quite a few that will lock up. Guns'n'Roses, Lost in Space and a few more will always do this, others only sometimes. It sucks.

I have found that anything higher than 270.61 will cause the same issue, so FXAA is a no-go

[Gamester]

htamas, is your card a gtx460 as well? Wondering if this is related to the drivers alone, or the combination of the drivers and the 460 generation of cards... I have a 560, but don't have HP loaded yet. Will report back once I am able to test though.

[htamas]

No, mine is a GTX 550Ti.

[Aurich]

I'll have to look up the version number, but I'm running FXAA with if not the latest driver, then a version or two behind it. It was current as of maybe last October or so. No problems at all, tables look great. GTX 560 Superclocked 2048 running both PF and backglass @ 1008p.

 

Edit: This is under XP service pack 3.

Edited by Aurich, 11 March 2013 - 03:01 AM.

[teppotee]

I was just thinking about FXAA and drivers yesterday so nice time for this topic. I'm running the old driver version as well (270 series). The last update I tried was 306.02 and that caused many tables to freeze (randomly). CPU usage would go to 25% and everything became unresponsive. Running GTX470 1,5Gb here with XP 32-bit SP3.

[shanknitrate]

I'm running a 560ti on the 3.14 drivers with absolutely no issues. I have played around a lot with the FXAA and antialiasing settings recently within the nView software and compared them by taking screenshots and then flicking between them in an image viewer. I've eventually decided that although it smooths out the jaggys, I don't like the way FXAA softens some playfields. This is more noticeable on tables that have small text on the playfield. At this stage I think it comes down to what bothers you more - jaggys or lack of sharpness. For me it was the lack of sharpness so I'm going to keep FXAA off for now.

[bosvrucht]

I'm running a 560ti on the 3.14 drivers with absolutely no issues. I have played around a lot with the FXAA and antialiasing settings recently within the nView software and compared them by taking screenshots and then flicking between them in an image viewer. I've eventually decided that although it smooths out the jaggys, I don't like the way FXAA softens some playfields. This is more noticeable on tables that have small text on the playfield. At this stage I think it comes down to what bothers you more - jaggys or lack of sharpness. For me it was the lack of sharpness so I'm going to keep FXAA off for now.

 

Seeing as both you and Aurich have a 560 and both report no problems, the 560 is somehow different from the 460,470,550 that do report problems?

 

and i agree, FXAA looks great on some tables, but not on others. I really like it on JP's new star wars table, but not on AFM. 

 

Just an idea:  i was thinking you could use fplaunch wip 10 to choose different vp executables. You could use this to launch some tables with vpinballfxaa.exe and some with vpinball.exe. And use nvidia profiles for both executables with fxaa on and off.  And voila.... hardware fxaa on some tables, but not on all.

[shanknitrate]

I might give that a try. I am already using multiple executables as I'm running pinball rev 476 and I found that Congo and lord of the rings would cause the system to almost completely lock up unless running through pinball 9.14. Could this be the same issue you were having after trying 3 tables with fxaa? Though the problem occurred for me even with out fxaa, and it didn't matter if it was the first time running it or not.

I did find that if I pressed F3 to reset vpinmame, and waited about 10 seconds for it to catch up, that once it had reset it would play flawlessly. Did you try resetting vpinmame at all? I know it's not a satisfactory solution but it would be interesting to know if vpinmame was the cause of your massive slow down too.

I see you just replied to me in another thread about exactly what I mentioned above. I guess I could try the 2.70 drivers to see if those tables work in rev 476 but using fplaunchs option to use multiple executables and switching the few troublesome tables to 9.14 is not that much hassle. What version of vpinball are you running?

Edited by shanknitrate, 18 March 2013 - 09:52 AM.

[shanknitrate]

I eventually found a table that would always freeze (well, almost) my cabinet, even on 9.14 - Gun's n Roses. So I downgraded my nvidia drivers back to 270.61 and it will work. Also the tables that would go into super slow mode when loaded under 9.15 (Congo, Indy 500, etc) all work fine with the old drivers when loaded with 9.15now.

 

Is this something I should make the developers aware of? The fact that 9.14 could play all tables under the newest drivers (except GNR) but 9.15 is more problematic (about 9 tables out of 123 last time I checked go into super slow) seems like a step backward. Or is just something that is unique to everyones' machines? For me it is always the same tables - there is no randomness to it.

[koadic]

To be able to try and fix it, we would have to isolate exactly what the issue is and why it is happening on those tables. Unfortunately (or not) I have yet to encounter any issues such as you are experiencing, so I would have a really hard time trying to narrow it down. Is there a specific revision between official 9.1.4 and now that this starts happening for you? That would be a helpful first step in identifying the possible cause. In my sig, there are many different revisions, sometimes there are gaps in the numbers so if you find it starts on a certain revision, but there are missing revisions between that and the next oldest, let me know and I will try to make those available as well.

[htamas]

Unfortunately on XP, only the old (270.61) driver will work 100% correctly with all tables. Doesn't matter what VP version is used, Guns'n'Roses will always freeze and will require F3 (after a long hiccuping period) to run with any newer driver.

On my rig, Lost In Space is another table that always does this. It happens randomly with other tables too when I try a newer driver, but those two always act up.

[teppotee]

I just tried the latest vp rev (496 I think) with beta drivers 314.14 and I'm cautiously optimistic... Tried about 10 tables without freezes with fxaa turned on (on my cab with xp). Including GnR. I have always had freezes before so hopefully this combimation would finally work... I will test more tomorrow.

[shanknitrate]

I might give those drivers a try tonight teppotee. Have you had troubles with the newer drivers before? For me, having FXAA switched on or off has never made a difference though.

 

Can anybody with table scripting knowledge see anything dramatically different with the GNR table compared to others? If we could isolate what it is about the table that causes the slow down it may help? As I said, I have 122 other tables that run on the 314.07 drivers. But perhaps it is something to do with the ROM since resetting VPinmame corrects it.

 

Kodaic, if I have no luck with the newest nvidia drivers I'll try some early revisions of 9.15 and and try to see when the tables (except GNR) started freezing. Are you running XP as well?

[shanknitrate]

No luck for me with the new drivers. GNR did work the first time I started it but has not since. In fact, some tables were even freezing in 9.14 which has not happened before. Makes me wonder what sort of difference not doing a clean install would make (I checked "do a clean install"). I'm not too fussed though. Not sure whether to go right back to 270.61 to be able to run GNR or stay on 314.07 and run some tables through VPinball 9.14. Will probably go back to 270 as I don't use FXAA because it loses the sharpness of the textures.

[pinball buzz]

Using nvidia driver version 314.22 with nvidia gtx 650 ti boost under windows xp. Not tried fxaa yet, and can play Guns n Roses, and LIS, but Congo locks up. This is weird some play fine, such as JP,s latest Medieval Madness, but others lock up. Using VP latest build 9.15 Sent from my Nexus 7 using Tapatalk HD

Edited by pinball buzz, 20 April 2013 - 06:01 PM.