7 replies to this topic

[Tesla]

I really just need the one (global) graphics settings for all my Tables.

I set it with no Table loaded, and save it.

 

However, I noticed that I now have .ini files for a lot of my Tables. I think they might be getting created when I temporarily set "Exclusive Fullscreen" mode to Windowed for setup/testing.

 

So, are they needed for every table now, or can they be deleted? If a Table starts without an .ini file, will it just use the global settings (and not create a .ini file)? 

[Tesla]

I did some testing, so I'll just answer my own question...

 

AFAICT, if you just want the Table to use the global video options, no .ini file is required.

And as long as you don't have the Table loaded while messing with the video-options, nor does one get created.

 

So, (in the future) I'll just try to remember to not have a table loaded if I need to temporarily disable "Exclusive Fullscreen" mode.

Edited by Tesla, Today, 02:10 PM.

[Thalamus]

The tablename.ini file can be very useful for other things. Many tables now come with F12 options and those choices is supposed to go into the tablename.init

There are also, as you mentioned - options to override "globals" to the tablename.ini - it can be a good idea to be able to override global defaults from time to time and currently that is the way that the devs have implemented it.

Of course, this can also lead to confusion. All of a sudden one table is acting up differently from the rest.

 

In the future, you most probably want to take backup of these ini files, with the table itself. Some tables have like 20 or so options and having to adjust those all over again ...

[Emanoel299]

@Tesla

 

The .INI file is very important basically for two situations.

 

1 - Some Cabinet system is not power enough for some tables.

 

So it needs to change some video settings and override them.

 

2 - The main situation is for 3D players mode, so it needs to change the view settings from Legacy to Window and change some settings. So the .INI file will be created.

 

If you start a table and do nothing, this table will run in Legacy mode and in a flat 2D view for cabinet mode.

Edited by Emanoel299, Today, 12:33 PM.

[Tesla]

1. Many tables now come with F12 options and those choices is supposed to go into the tablename.ini . Some tables have like 20 or so options and having to adjust those all over again ...

 

2. Of course, this can also lead to confusion. All of a sudden one table is acting up differently from the rest.

 

3. In the future, you most probably want to take backup of these ini files, with the table itself. 

 

2. Exactly, that is what I was trying to avoid.

 

1. Really? Good call-out then. So, how are these F12-Enabled tables identified? 

Is it just a matter of loading table, no game started or ball in play, and press F12. I assume a menu appears? 

 

3. Of course. Only 3 of my 16 tables had them, but they were old-ish tables . I looked inside one of them, but it was just 5-10 lines of normal "video prefs page stuff". I already deleted all 3. I hope that wasn't a mistake. I assume they can be recreated if they are required.

Edited by Tesla, Today, 04:32 PM.

[Tesla]

@Tesla

 

The .INI file is very important basically for two situations.

 

1 - Some Cabinet system is not power enough for some tables.

 

So it needs to change some video settings and override them.

 

2 - The main situation is for 3D players mode, so it needs to change the view settings from Legacy to Window and change some settings. So the .INI file will be created.

 

If you start a table and do nothing, this table will run in Legacy mode and in a flat 2D view for cabinet mode.

 

1. I don't think I have that problem, but yeah. Or like "Balls Trails" on this one table. AFAIK, this is the traditional use-case.

 

2. What is "3D Players Mode"? You mean VR? If so, my only use for that on my 3-screen cabinet is to force all VR capability OFF (if I have to for a leaner config).

[Emanoel299]

Hi Tesla

 

1 - Yeah. I have one system with I7 3770 - GTX 1650 4GB.

 

      In VPX GL 3D stereo output I have some lags in some tables, so I need to a "specific table override settings"

      with GTX 1660 super/TI 6GB nothing is necessary

 

2 - I understand. I´m talking about 3D stereo output.

    VPX GL version is perfect. I bought some 42" and 47" 3D TV from some peopleo

    that are selling. The .INI file in window mode must create for a real perfect 3D view. I can say. VR is cool but glasses still heavy for me for a long time but 3D passive glasses not.

 

[Tesla]

1 - Yeah. I have one system with I7 3770 - GTX 1650 4GB.

 

      In VPX GL 3D stereo output I have some lags in some tables, so I need to a "specific table override settings"

      with GTX 1660 super/TI 6GB nothing is necessary

 

2 - I understand. I´m talking about 3D stereo output.

    VPX GL version is perfect. I bought some 42" and 47" 3D TV from some people

    that are selling. The .INI file in window mode must create for a real perfect 3D view. I can say. VR is cool but glasses still heavy for me for a long time but 3D passive glasses not.

 

 

1. Sounds like the (older) computer I was using (but my old Dell was only an Intel-i5) . The Nvidia GTX-1660 made it viable again. I finally retired it last year ... gave it to my grand-nephew as it still games in 1080p just fine. 

 

2. Gotcha ... 3D TV glasses. Cool that it is not only support but some are actually using it. Your screenshot should be helpful for others trying to get it working optimally.

 

So, I did find-and-see some F12 Menus. Not sure I knew that was part of VP for Windows v10.8.0 (and not just a feature of Visual Pinball Standalone). Yeah, F12-Menu is handy I suppose but I normally just set that stuff in VP-Prefs (and not mess with it again).

 

I can still look at it without saving anything. 

 

If my "master plan" wasn't to eventually get proper Instruction Cards for my 20-40 tables, I could just use this initial screen for basic-play-notes (and add F12 to my Pinscape buttons). We'll see.

Edited by Tesla, Today, 06:26 PM.