3889 replies to this topic

[lolo33]

 

Okay this is weird, the black screen is back! Does it on multiple tables. I blew everything back to 1730 and everything works. Reinstalled 1757 and black screen again?   Any thoughts?   

 

Strange.. Which tables work and which don't?

 

 

Same problem, tested with Papa Smurf, Vector VP10, Monster Bash.

[toxie]

So for you guys no table works at all? They are all black?

Top is no AA

Bottom is 4xaa

 

 

This just means that you are limited by your gfx board, not the CPU/driver overhead (on my office GTX TITAN 4xAA is basically for free). There is not much we can do for now (except for continuing the shader optimizations, but you cannot expect wonders from that), but you could rather enable FXAA in the gfx card control panel (i know its not the same quality, but..).

[lolo33]

yes for me first build with this problem.

[toxie]

Could you do some experiments, please?

 

1) en/disable 4xAA (Options->Table Graphics & Sound->AntiAliasing = 1 or 0)

2) en/disable AO (Options->Table Graphics & Sound->Ambient Occlusion = 1 or 0)

 

EDIT: 3) delete -all- table elements from the default table, then also open the script and delete all text from it, and try with that

Edited by toxie, 26 February 2015 - 02:49 PM.

[lolo33]

I have ATI card so Ambient Occlusion disable by default and Fast FXAA enable.

Disable Fast FXAA fixed the problem.

 

 

Tested with 4xAA enable and that work also.

The problem appears just with Fast FXAA or Quality FXAA enable.

Edited by lolo33, 26 February 2015 - 03:02 PM.

[Shadowsclassic]

So for you guys no table works at all? They are all black?

Top is no AA

Bottom is 4xaa

 

 

This just means that you are limited by your gfx board, not the CPU/driver overhead (on my office GTX TITAN 4xAA is basically for free). There is not much we can do for now (except for continuing the shader optimizations, but you cannot expect wonders from that), but you could rather enable FXAA in the gfx card control panel (i know its not the same quality, but..).

All the tables I have anyway.  Just seemed odd that everything worked fine with 1730 but upgrade to 1757 and everything is black.  That's not changing any settings just coping the files from the two updates.  So I guess something changed from 1730 to 1757 that my Nvidia 9800 can't handle.  That's fine I guess I will just have to upgrade this desktop to what I have in my cab.

 

edit: toxie, I will try the experiment tomorrow and let you know. I'm working a 24 to day and don't have access to my system.

Edited by Shadowsclassic, 26 February 2015 - 03:34 PM.

[toxie]

@lolo33: thanks! FXAA and stereo3D are currently not top priority as they need a restructure (they don't cooperate currently with AO and Bloom), so i didn't test these, sorry for that. maybe over the weekend i'll work on these again so that they are fully functional.

 

EDIT: but at least this brought up another potential bug i just found, so overall no work wasted..

 

@shadowsclassic: seems like lolo33 found the issue, could you also try with FXAA off?

Edited by toxie, 26 February 2015 - 03:20 PM.

[Shadowsclassic]

@lolo33: thanks! FXAA and stereo3D are currently not top priority as they need a restructure (they don't cooperate currently with AO and Bloom), so i didn't test these, sorry for that. maybe over the weekend i'll work on these again so that they are fully functional.

 

EDIT: but at least this brought up another potential bug i just found, so overall no work wasted..

 

@shadowsclassic: seems like lolo33 found the issue, could you also try with FXAA off?

Yes, I will play around with it when i get home tomorrow and let you know what I find.  No big deal toxie, I know it's beta, just wanted to report the issue.

[ClarkKent]

As display quality with 4xAA option turned on is that much better I decided to use constant 120 fps (as 60 fps results in occasionally ball stutter), 4xAA and prerendered frames at 1. At tables that can not provide at least 120 fps (like the current MB) I set the table option anti aliasing to 0. Best solution till now. I still hope that optimizing demanding tables (and VP10) will provide 120fps here in future...

[mpad]

Try 32 csaa, looks good IMHO.

Edited by mpad, 26 February 2015 - 09:57 PM.

[freneticamnesic]

 

 

This just means that you are limited by your gfx board, not the CPU/driver overhead (on my office GTX TITAN 4xAA is basically for free). There is not much we can do for now (except for continuing the shader optimizations, but you cannot expect wonders from that), but you could rather enable FXAA in the gfx card control panel (i know its not the same quality, but..).

 

This is acceptable

[ClarkKent]

Try 32 csaa, looks good IMHO.

I think all these AA methods (AA, MSAA, CSAA) should be configurable in the video prefs of VP. If I set it in the Nvidia control panel it effects all applications - I do not want this.

[BananaBoat]

Try 32 csaa, looks good IMHO.

I think all these AA methods (AA, MSAA, CSAA) should be configurable in the video prefs of VP. If I set it in the Nvidia control panel it effects all applications - I do not want this.

You can add the vpinball exe to nvidia control panel and make the changes specific to the exe.

[Sindbad]

I'd like to come back to one of my previous posts. Presently I have no idea how to place a reflection of a light on a wall. The problem is that the brightness of all objects depends on the position of the day/night slider. Only light objects and flasher objects are excluded from the slider. That means, that the light itself will always stay bright, but the reflection depends on the slider. So we can use a flasher to simulate the reflection on a wall. That works on non-curved objects. But I have the problem, that I need reflections at curved walls.

 

 

So the only way to simulate a reflection on a curved wall is to divide the reflection into several flasher pieces and place them correct to get in sum a curved flasher. This is very difficult, because when we rotate flashers in the editor, we don't see the result (the rotation) in the editor, we only see the result when hitting the Play button.

 

So what's the intend of my post? Is it possible to add a feature (check-box) to elements (walls and primitives), so they can be excluded from the ambient lightning (day/night slider)? This would make it much easier for me (and I beleive also for other devs) to simulate realistic reflections.

Edited by Sindbad, 27 February 2015 - 09:31 AM.

[fuzzel]

Oh yes that's one feature we missed to add Will be in in the next revisions but if you disable the lighting no material parameter is applied to the wall/primitive anymore.

Edited by fuzzel, 27 February 2015 - 09:11 AM.

[Sindbad]

Thanks fuzzel for the quick feedback.

 

For me it's absolutely okay when no material is applied to the objects that are excluded from ambient lighting. I'd like this feature only for reflections. So I'm glad that I can hope you'll add this feature.

[zany]

About materials and the material manager....it would be nice to have a duplicate material fuktion aswell. 
If it's already implemented....forget about this post!

[toxie]

phew.. actually i don't know if we should do that.. disabling the lighting/materials for all kinds of objects just screams for trouble later-on.. :/

[Sindbad]

Toxie,

 

what do you mean when writing trouble later-on? Do you mean trouble while developing VP or trouble with the tables? 

 

Please understand me right, I don't need the feature to disable ambient lighting, but I would be happy to have a solution for placing reflections on curved walls. Maybe there's another solution, but the "disable lighting and material" seems to be practical for me.

[fuzzel]

Well even though I've already implemented that I'm with Toxie. Adding exceptions to elements makes it always complicated to maintain the code and to add/change stuff.