1972 replies to this topic

[Tiki]

Hi all! I have the mouse disappearing problem with 10.8. In the issue here https://github.com/v...ssue-1731115757 I can read that I have to copy scripts too but I copied everything. 
I do not run fullscreen mode. I am on 10.8.0 rev 1370
What did I miss?

[fourbanks]

From me following on from being up-to-date I'm pleased to report all tables working as expected with nothing to report on at this time

thanks to all involved  

[jpsalas]

Hi all! I have the mouse disappearing problem with 10.8. In the issue here https://github.com/v...ssue-1731115757 I can read that I have to copy scripts too but I copied everything. 
I do not run fullscreen mode. I am on 10.8.0 rev 1370
What did I miss?

 

I have learned to press D when I want the mouse cursor to appear, and then I press ESC to close the debug window Then I can move the ball, or throw a ball to test the table

[stampedem]

 

 

 

I'm using VPX 10.8 GL

 
We should all really try to get in the habit of posting our exact build numbers in this thread, as the updates come so rapidly many people are reporting issues that got fixed in a previous build.  This isn't always the case, but it would help out a lot if we all posted exact build numbers that we are using.

You are right. Sorry for the missing version.
I'm using VPX 10.8 GL build 1378

The mentioned monster bash tables is from VPW. Maybe someone want to try it and check if have the same problem.

 

 

I guess you get a memory error, at least in the DX version you get a memory error with most of those VPW tables. That's because they use 8k textures, so the 32 bits VPX runs out of memory.

 

In short: for those huge VPW tables, over 300Mb, use the 64 bits VPX version, or reduce the image memory to 2048. You can have now this setting, to reduce the image size, for an individual table just by using an ini file with the same name of the table with these lines:

 

[Player]

; Video options

MaxTexDimension = 2048

 

Where do we place this .ini jpsalas?

[Tiki]

 

Hi all! I have the mouse disappearing problem with 10.8. In the issue here https://github.com/v...ssue-1731115757 I can read that I have to copy scripts too but I copied everything. 
I do not run fullscreen mode. I am on 10.8.0 rev 1370
What did I miss?

 

I have learned to press D when I want the mouse cursor to appear, and then I press ESC to close the debug window Then I can move the ball, or throw a ball to test the table

 

if you want to edit a PupPack or Backglass Setting its hard to handle that without seeing your mouse. tried it with pressing esc - sometimes the mouse appears.. On tables with rom, I can press F1 to make the mouse appear. But on originals .. 

Edited by Tiki, 01 September 2023 - 03:01 PM.

[Drybonz]

Where do we place this .ini jpsalas?

 

In the same folder as the table, named the same as the table's file name.

[jpsalas]

 

 

 

 

I'm using VPX 10.8 GL

 
We should all really try to get in the habit of posting our exact build numbers in this thread, as the updates come so rapidly many people are reporting issues that got fixed in a previous build.  This isn't always the case, but it would help out a lot if we all posted exact build numbers that we are using.

You are right. Sorry for the missing version.
I'm using VPX 10.8 GL build 1378

The mentioned monster bash tables is from VPW. Maybe someone want to try it and check if have the same problem.

 

 

I guess you get a memory error, at least in the DX version you get a memory error with most of those VPW tables. That's because they use 8k textures, so the 32 bits VPX runs out of memory.

 

In short: for those huge VPW tables, over 300Mb, use the 64 bits VPX version, or reduce the image memory to 2048. You can have now this setting, to reduce the image size, for an individual table just by using an ini file with the same name of the table with these lines:

 

[Player]

; Video options

MaxTexDimension = 2048

 

Where do we place this .ini jpsalas?

 

In the same folder as the table.

 

I didn't saw Drybonz post

Edited by jpsalas, 01 September 2023 - 03:48 PM.

[licwip]

1) temp disable exclusive fullscreen mode in vpx vid prefs

That wasn't it but updating the Scripts worked. Thanks!

 

Regarding the ball, is there a way to change the ball texture globally? Not crazy about doing it for hundreds of tables, one at a time. If I don't hear an answer, I'll assume there isn't and pine away for my sparkle ball.

Edited by licwip, 01 September 2023 - 04:09 PM.

[studlygoorite]

 

 

Can you post both of your INI files as well ?
I'm doing almost the same, and never had issues with it
or is this issue introduced with 1370 ?

 

Not sure when it started but it wasn't that long ago. I just updated to v1383 and still have the issue, thanks Mike  INI files are here  https://drive.google...q8u?usp=sharing
 

[wiesshund]

 

1) temp disable exclusive fullscreen mode in vpx vid prefs

That wasn't it but updating the Scripts worked. Thanks!

 

Regarding the ball, is there a way to change the ball texture globally? Not crazy about doing it for hundreds of tables, one at a time. If I don't hear an answer, I'll assume there isn't and pine away for my sparkle ball.

 

in video prefs

[Halen]

A noob question about BAM headtraking: Can I work with Visual Pinball GL or DX or just Visual Pinball GL?

[Pinballman]

 

Is there a guide or tutorial anywhere explaining the features of 10.8?  Obviously more complex than 10.7 and trying to understand and learn how to navigate through it. Thanks!

Presently the notes and change logs are the best way
As it is still running in beta, no official Docs have been drawn up yet.

 

A lot of changes kind of pertain to authoring, but you are probably not asking about those.

 

From a player standpoint
10.8 has two new POV methods instead of just the old legacy method
Camera and Window
They provide a more accurate view of the table and a more realistic 3 dimensional appearance

10.8 has more control over anti aliasing instead of just force 4X FSAA or none at all
You can now chose how much, by percent, anti aliasing you wish to apply.

 

10.8 has better lighting, and now casts real ball shadows from the lamps (if the author implements things right)
so no fake ball shadow is needed anymore.

 

The renderer overall is much cleaner and looks nicer.

VPX settings are now stored in INI instead of registry, and you can even make table specific INI's if you need a custom per table setting for special tables

 

10.8 VR and normal are now unified, same exact code, only the renderer is different, DirectX vs OpenGL, and you can run the VR OpenGL version on your cab or desktop
and simply turn VR on and off as needed.

 

10.8 now allows mapping staged flipper keys and buttons in the UI itself, removing the need to use joy2key or other hacks to get the buttons themselves recognized.

 

insert 1000 other things i forgot.

 

Thank you very much for this useful info, appreciate it!

[Vercingetorix]

Hi all! Somehow 10.8 seems to have messed up the POV on every table on my cab.....whether I run it it in 10.8 or not. Let me see if I can lay it out without sounding completely crazy: 

 

1. I am running 10.8 64-bit beta 5 (1347, non-GL). The latest binary available on github. I have been running it for a couple of weeks without any apparent problems. (I downloaded 10.8 for a table that required it.) 

 

2. Yesterday I downloaded the new Police Force table and went in to adjust the POV as I always do. This is the first time I had seen or even been aware of the new Windowed POV mode. I messed around in the camera editor for awhile, trying (incompetently) to figure out how it works. 

 

3. Now every table on the cab launches in a flattened-out, almost desktop-ish POV that looks like something out of that editor. Well this sucks, I said, so I went back to 10.7. But same thing. 

 

4. The table files have not been updated; I am launching tables that have a last modified date of a year or two old from within 10.7 and the POVs are still messed up. I do not know where the new POV can possibly be coming from. 

 

5. I read about the INI files in %appdata%, so I blew them away. No change. 

 

6. I blew away my entire Visual Pinball directory (and the ini file) and restored from a backup from earlier this week, when everything worked. No change. 

 

Anybody got any ideas? 

Edited by Vercingetorix, 01 September 2023 - 09:57 PM.

[Drybonz]

Hi all! Somehow 10.8 seems to have messed up the POV on every table on my cab.....whether I run it it in 10.8 or not. 

 

I had this problem... it's actually posted somewhere in this lengthy thread.  Vbousquet had fixed something that I reported, but I also had to manually re-make a lot of .pov files that had been "corrupted/changed".  I can't really give you any good news about it, but you might want to back up your .pov's and make a new one for a table you know is having problems and then go from there.  Luckily, when this happened to me, I knew which tables I had opened and didn't have to re-do them all.

 

*edit*  If you want to refer to the github issue I had opened for this, it's issue #594 (now under closed issues).

Edited by Drybonz, 01 September 2023 - 10:41 PM.

[wiesshund]

when you get to step 6, do you mean tables folder as well?

if the answer is no, do you happen to have an autoPOV.pov file in there?

 

While it is possible to have buggered an individual table by adjusting the POV with a bug present
that will have no affect on unopened non edited tables.

 

Also, from God's lips to your ears
When adjusting POV, NEVER EVER save the table.

Export the POV and when quitting the table, DO NO SAVE.
Then you have changed nothing in the table and instead only created an external POV.

 

If the answer to step 6 is Yes, then i do not know since the POV is only stored 2 places

In the table itself (which would not exist in your backup)

Or in an external POV file (which would also not be in your backup)

[Vercingetorix]

 

 

 

> you might want to back up your .pov's

 

I don't actually have ANY .pov's. Everything is saved in the table file for me. At least until now. 

 

>  I knew which tables I had opened and didn't have to re-do them all.

 

This is what kills me. I can A) delete the entire VP folder, B) delete the INI files that are hanging around in the appdata folder, C) restore my VP folder from a backup from a week ago when everything was working, and then D) use a 10.7 executable to open a table that I haven't opened at all in a year and the same thing still happens. How does 10.7 have any idea that I ever opened 10.8 at all?? 

 

None of this happened right when I started using the 10.8 beta, because that was a couple weeks ago. It was only when I loaded a table in something other than legacy mode for the first time. 

 

>  If you want to refer to the github issue I had opened for this, it's issue #594 (now under closed issues).

> There is unwanted horizontal positioning of the table, as well as adding a diagonal slant to the table. 

 

You have described it much better than I did! 

Edited by Vercingetorix, 02 September 2023 - 02:21 AM.

[Vercingetorix]

 

> when you get to step 6, do you mean tables folder as well?

 

Yes. The whole thing. VP, tables folder, Vpinmame, etc. I keep impeccable backups on an external drive so it's always been very very easy if I screw something up to just wipe the whole thing out and restore from a known good point. Not this time.

 

> When adjusting POV, NEVER EVER save the table.≈

 

I have been at this since VP 8 and I've never heard that that's best practice. I tend to dick around in the script to tweak things to my taste anyway so it's never occurred to me that overwriting the original table might be a problem.  

 

> If the answer to step 6 is Yes, then i do not know since the POV is only stored 2 places

 

As I said in a post above: I can 1) delete the entire VP directory structure, including tables, 2) delete the INI file that 10.8 puts in appdata, 3) restore the VP tree from a week-old backup when everything worked, and 4) use a 10.7 binary to open a table I haven't opened in two years and it's still messed up. I do not understand it. 

 

I have not gone into the registry yet to hack away every single thing that looks VP-related. I suppose that's next. 

Edited by Vercingetorix, 02 September 2023 - 02:43 AM.

[wiesshund]

POV is not stored in the registry, unless you are maybe not presenting the issue well?

 

settings wise 10.7 and 10.8 share nothing because one reads registry exclusively
the other reads an INI file exclusively.

 

Maybe it is time for some screenshots?

 

If you really think it is a POV issue try this

open Any table in the editor

 

hit F6 and try to adjust the POV
If you can adjust the POV, then quit back to editor, click File > Export > POV
and name it AutoPOV.pov

 

Now launch exit VPX and say no to saving table
Now go launch any other random table and see if it follows that POV

 

Though i would have no idea how all your POV's even from a backup would become totally screwed in both 10.7 and 10.8 since
POV is only saved in table or to POV file, and is not saved in the registry nor the ini

And 10.7 would not read or acknowledge anything in the INI anyways it only uses the registry.

And 10.8 stores everything in the INI with the exception of window docking settings of the editor, those are still in registry for some reason.

 

Open regedit, go to
Computer\HKEY_CURRENT_USER\Software\Visual Pinball

export entire key as a backup, then delete the entire key.

See if it makes any difference to your issue, but i doubt it, nothing in there or the INI pertains to POV

 

Again, some screenshots would help
maybe one showing the table running, one showing the untouched POV values in the editor etc?

[Vercingetorix]

Edit: Wait wait wait wait wait........somehow my video preferences got overwritten and it appears I got switched over to running in desktop mode on my cab

 

I did not change it and yet "Run in FS mode" is unchecked. 

 

A ha!!!

 

Thanks for helping me think through it. 

Edited by Vercingetorix, 02 September 2023 - 03:50 AM.

[wiesshund]

somehow my video preferences got overwritten and it appears I got switched over to running in desktop mode on my cab

 

 

this be why screenshots are good
we could have helped you think faster

 

maybe