1972 replies to this topic

[Urko]

Its a lot smaller file size build 1873 than before , is that correct ?

Edited by Urko, 01 February 2024 - 12:14 AM.

[wiesshund]

Its a lot smaller file size build 1873 than before , is that correct ?

 

Same size to me, where are you looking?

 

Sure you are not looking at a debug build, which is a lot larger (and runs a lot slower)

[Drybonz]

Its a lot smaller file size build 1873 than before , is that correct ?

 

Unpacked, mine is like .1 mb away from the previous build I had.

[choda]

tried reading through the thread but couldn't find a solution. the image only takes up a quarter of the screen is used in my quest 2. other apps and games don't have this issue. 

[SmedleyB]

i have not checked against today's RC, but in earlier beta releases, the Player Y POV setting was the real measurement between the bottom of your playfield monitor and your eyeballs on the Y plane. For me, I usually used around 8 cms. Then somewhere along the line, the reference point changed so that I have been using around 23 cms.

 

Does anyone know what the new starting reference point for Player Y is? Perhaps it is the top of the apron or something like that?

[Umpa]

After a few weeks, and many many bugs squashed, here is a first release candidate: https://github.com/v....0-1873-bdd0673
It is supposed to be mostly bug free albeit a few known bugs: SMAA is off, the UI is no good in VR, and you won't be able to overlay anything over the OpenGL window.

Thank you!

Sent from my SM-A536U using Tapatalk

[studlygoorite]

tried reading through the thread but couldn't find a solution. the image only takes up a quarter of the screen is used in my quest 2. other apps and games don't have this issue. 

Make sure your Supersampling is set to "disabled" or 100%

[Urko]

 

Its a lot smaller file size build 1873 than before , is that correct ?

 

Same size to me, where are you looking?

 

Sure you are not looking at a debug build, which is a lot larger (and runs a lot slower)

 

https://github.com/v....0-1873-bdd0673  <<< 36.3 meg.

 

36 meg release, has been 56 meg release before.

https://github.com/v...runs/7511400373  <<< 56 meg.

 

Also there must be something that im not doing right because even if i choose window , stretch to fit or not stretch to fit, when i have made the playfield the right size for my monitor , the balls seems larger at the top area of the table than the bottom. (using cabinet)

Table YZ Scale stretches the table, no matter what you pick.

Tried altering different things but ball still definately more mishapen/larger at top area, not massively but noticeable.

 

This ball issue is not there atall using legacy.

Edited by Urko, 01 February 2024 - 09:40 PM.

[wiesshund]

 

https://github.com/v....0-1873-bdd0673  <<< 36.3 meg.

 

 

36 meg release, has been 56 meg release before.

https://github.com/v...runs/7511400373  <<< 56 meg.

 

Also there must be something that im not doing right because even if i choose window , stretch to fit or not stretch to fit, when i have made the playfield the right size for my monitor , the balls seems larger at the top area of the table than the bottom. (using cabinet)

Table YZ Scale stretches the table, no matter what you pick.

Tried altering different things but ball still definately more mishapen/larger at top area, not massively but noticeable.

 

This ball issue is not there atall using legacy.

 

 

I see 56megs
Are you looking at the right thing?

 

10.8.0 rev 1874

port DMD noise improvement · vpinball/vpinball@4e92fd6 (github.com)

 

10.8.0 rev 1873

Fix transmitted bulb light wrong with only 1 light for DirectX · vpinball/vpinball@bdd0673 (github.com)

[Urko]

 

 

https://github.com/v....0-1873-bdd0673  <<< 36.3 meg.

 

 

36 meg release, has been 56 meg release before.

https://github.com/v...runs/7511400373  <<< 56 meg.

 

Also there must be something that im not doing right because even if i choose window , stretch to fit or not stretch to fit, when i have made the playfield the right size for my monitor , the balls seems larger at the top area of the table than the bottom. (using cabinet)

Table YZ Scale stretches the table, no matter what you pick.

Tried altering different things but ball still definately more mishapen/larger at top area, not massively but noticeable.

 

This ball issue is not there atall using legacy.

 

 

I see 56megs
Are you looking at the right thing?

 

10.8.0 rev 1874

port DMD noise improvement · vpinball/vpinball@4e92fd6 (github.com)

 

10.8.0 rev 1873

Fix transmitted bulb light wrong with only 1 light for DirectX · vpinball/vpinball@bdd0673 (github.com)

 

https://github.com/v....0-1873-bdd0673

 

Dohhhh i figured it out , the file is zipped on that release link above.

I notice both links have them zipped but the non release page one has the unzipped file size typed. https://github.com/v...runs/7739147763

36.3 zipped, 56 meg unzipped. Be better if the runs page stated the zipped file size rather than the unzipped too (imo(seeing as its actually a zipped file even though it doesnt state that)

 

I was just looking at the file sizes without thinking.

Probably not confusing for those who have been in the hobby for years.

Apologises.

Edited by Urko, 02 February 2024 - 02:10 AM.

[wiesshund]

 

Probably not confusing for those who have been in the hobby for years.

 

 

 

Not confusing for me
 

 

Only because i always go directly to the actions to see what is the latest, also to see what has been going on between point A and point Today

[Urko]

 

 

Probably not confusing for those who have been in the hobby for years.

 

 

 

Not confusing for me
 

 

Only because i always go directly to the actions to see what is the latest, also to see what has been going on between point A and point Today

 

I usually do myself, but as a relatively new individual to this, seeing a different file size stated on the screen when both files are zipped is confusing.

I know now, so alls well.

[kaledev]

Although upgrading my beta to the version in actions helped the ball squish / POV issue - it's definitely not fixed 100% for me. The tables that are still on legacy are just slightly (or sometimes majorly) distorted. Still having to switch most of mine to window mode... I don't think backwards compatibility worked here.

[Dipkid]

hi experts. On the latest RC 64bit version I can't for the life of me get the tweak button (default F12) to work as a cabinet button. F12 opens the vpinmame volume, so I changed it to another keyboard button, and it works with a keyboard, but assigning a a USB controlled button just dosent work. I tried several just to rule out faulty wiring, but everything seems to work fine. any leads..?

[kaledev]

hi experts. On the latest RC 64bit version I can't for the life of me get the tweak button (default F12) to work as a cabinet button. F12 opens the vpinmame volume, so I changed it to another keyboard button, and it works with a keyboard, but assigning a a USB controlled button just dosent work. I tried several just to rule out faulty wiring, but everything seems to work fine. any leads..?

I haven't tried the release candidate, but the vpinmame volume is now back?? I was really sad that it was taken away.

[Drybonz]

Although upgrading my beta to the version in actions helped the ball squish / POV issue - it's definitely not fixed 100% for me. The tables that are still on legacy are just slightly (or sometimes majorly) distorted. Still having to switch most of mine to window mode... I don't think backwards compatibility worked here.

The ball thing is an ongoing issue.  The latest ticket (1322) was closed.  You can leave new comments there or open a new ticket.

[MarkPinHead]

Just upgraded to GL64 Visual Pinball X 10.8.0 Release Candidate 1 from GL64 Visual Pinball X 10.8.0 beta 8 and also went to VpinMAME 64 v3.6-822-66be20f and now the EXIT GAME button doesn't work anymore. I tried re-assigning it but nope! 

 

It sort of freezes the game but you can still here sounds.

 

Any one else stuck / fixed this on the latest candidate?

[makmak]

Anyone else having wird sound issues with rc1? Tried for fishtales... No rom sound at all (also no altsound) and sound options changed without notice to some strange output sources. Tried with different tables.

[Drybonz]

Anyone else having wird sound issues with rc1? Tried for fishtales... No rom sound at all (also no altsound) and sound options changed without notice to some strange output sources. Tried with different tables.

I think they were saying you need to upgrade VPinmame.

[makmak]

I did