1972 replies to this topic

[Mike DA Spike]

With the introduction of 10.8, how do i make changes to the F1 default settings window?
The mouse courser does not appear.
 
Thanks 

Think it is mentioned in the following issue https://github.com/v...ssue-1731115757

[krusso222]

hi when i use 10.8 beta after i play a table vpx does not exit like previous versions did is there a setting im missing   thanks

[Mike DA Spike]

hi when i use 10.8 beta after i play a table vpx does not exit like previous versions did is there a setting im missing   thanks

What is the difference in behavior?
From a front end or from windows explorer?

[Drybonz]

hi when i use 10.8 beta after i play a table vpx does not exit like previous versions did is there a setting im missing   thanks

 

Was that your trouble ticket on github?  It was a bit vague.   

You might want to give a few more details.

[dacstyle]

I switched my cabinet to 10.8 this weekend (was using 10.8 for vr and for some testing and cab was still 10.7), but noticed that pinvol indeed is not on top.
Not sure if mjr will wix this, so lets hope

I just found a workaround for pinvol, just move the bar to the backglass.

[Mike DA Spike]

I just found a workaround for pinvol, just move the bar to the backglass.

Yeah, I did this a well. Workable for the time being

[SmedleyB]

I am jumping into 10.8 Windowed-mode POVs.

Considering this image:
 

https://raw.githubus...p-CameraDef.svg

 

...does 10.8 consider the entirety of the playfield when performing these calculations, including those portions that are not visible under the lockbar and the back wall?

If so, then technically if you imagine your monitor screen as the glass set at about 10 degrees, and assuming the table author maintained realistic proportions, then Window Bottom Y Offset should usually be set to a small positive value to compensate for what's hidden by lockbar and Windows Top Y Offset should usually be set to some comparatively larger negative number to compensate for the portion of the playfield that extends back behind the imaginary line dropped straight down on the Z axis from the top of the screen/glass.

 

Am I thinking about it correctly?

Edited by SmedleyB, 27 July 2023 - 04:13 PM.

[wiesshund]

all objects in playfield screen count as table geometry

 

if you put a peg 4000 units north of the backwall of the table
it counts

[SmedleyB]

all objects in playfield screen count as table geometry

 

if you put a peg 4000 units north of the backwall of the table
it counts

 

What should the feature request be, then? That the author is able to flag the playfield image/dimensions to be used for the POV calculations? Or is the identification/location of playfield image/dimensions already consistent from table to table within VPX?

[wiesshund]

playfield dimensions are already defined

 

But if you put objects outside of it, they still count
They have to or SSF tables would not work well. the SSF objects are outside the playfield.

Doesnt really come into play except for the author setting up the base POVs

[SmedleyB]

What about me trying to set up the Windowed POV on my cab? If I can count on VPX only counting the playfield dimensions and not being skewed by objects outside it, a lot of those settings could be static values per manufacturer and era of cabinet.

[wiesshund]

no, you cant count on vpx doing that nor should it.

 

if you want something that deviates from the norm i suggest starting with an autopov.pov

[SmedleyB]

I'm not following why I shouldn't want/ask VPX to know what should matter (the size of the true PF) when calculating POV, at least specifically for the Windowed POV feature, which is aimed at cabinet users? My hope was the POV could be formulaic - like, oh, this table is a Williams cab. A Williams cab has 3cm on z axis between glass and front of PF, has 20cm between glass and back of PF, the front 2cm of PF extends under the lockbar, the back of the PF extends 9cm under beyond where the glass ends, etc.

[wiesshund]

Huh?
Windowed POV has nothing to do with cabinet users

Windowed is some size other than the full screen

Cabs, and most desktop users for that matter, use the full screen.

 

And VPX doesn't do like the above, because authors do not make tables like the above

[SmedleyB]

I've been talking about the new Window Projection method to set POV in 10.8:

https://github.com/v...s/View Setup.md

[wiesshund]

I've been talking about the new Window Projection method to set POV in 10.8:

https://github.com/v...s/View Setup.md

 the above still applies

[SmedleyB]

I see why I am confused now, from Toxie's doc: "Window Top/Bottom X/Y/Z offsets define the position of screen bounds relative to playfield bounds"

 

I expected that meant the Window Top and Bottom Y offsets shrinks or expands the the screen compared to the top and bottom of the playfield. Like a Bottom Y offset of +3cm, would move bottom of the screen (I think of the screen as the glass on the cab) up 3cm compared to the bottom of the playfield. 

It doesn't do that, rather it seems to just move the whole screen up and down and the Window Top and Bottom settings seem to NOT be independent - they both do the same thing, they just move the whole screen up and down, the size of the screen doesn't change.

 

In vbousqet's doc (https://github.com/v...ball/issues/467), he says "The screen is supposed to be a window with the actual playfield beneath. Therefore the screen corners should correspond to (user defined) fixed points of the cabinet (only supported by BAM for the time being)."

 

Does that mean that in regular 10.8 without BAM, we cannot change the size of the screen? We can only move a fixed screen size around in space?

Edited by SmedleyB, 28 July 2023 - 01:50 AM.

[krusso222]

i should of said that after you quit the table it goes back to the editor and does not exit completely   thanks

[Drybonz]

i should of said that after you quit the table it goes back to the editor and does not exit completely   thanks

 

Hey Krusso... I could be wrong, but I think that's always been the case.  There's a command you can use to completely exit both game and editor (I think it's /exit).  I have my frontend setup to apply the command and totally exit, so that's something you could try.  (someone correct me on these details, I'm just going off memory).

Edited by Drybonz, 28 July 2023 - 04:28 AM.

[wiesshund]

 

i should of said that after you quit the table it goes back to the editor and does not exit completely   thanks

 

Hey Krusso... I could be wrong, but I think that's always been the case.  There's a command you can use to completely exit both game and editor (I think it's /exit).  I have my frontend setup to apply the command and totally exit, so that's something you could try.  (someone correct me on these details, I'm just going off memory).

 

 

yes, the exit flag will exit all the way out
so will just holding Q if not in a front end