1972 replies to this topic

[djredick]

anyone else have tables that don't render certain parts in the beta?

using Firepower II (1.1 through Bigus 1.4) the apron refuses to render, even though it is checked visible.

If I change it in live editor, I can get it to render by turning it off and on, but then it still won't show up when I go to play the table.

 

Works for me with r1369.  If yours is newer than mine, then might open a ticket on Github.

[Kikwik]

 

Hi !

 

Using VPX8 x64 and really appreciate it, so thanks a lot for your work ! I see the difference, excellent !

 

I have only one little question : In VPX7 we could launch and play a table directly by double clicking on it in the explorer folders. But when doing it with VPX8 it open the VPX8 launcher, ask you to choose the file and launch it. So is there a way to do it like in VPX7, in a more direct way ?

 

I'm not interested in a frontend though.

 

Thanks in advance for your help.

 

I had same issue and resolved it by making a change in the registry.  Follow through by reading posts 761 - 772 in this thread.

 

 

Thanks a lot it worked perfectly !

 

Thanks to wiesshund too for your tip but like the others said it don't work with the VPX8 64 bits version unfortunately.

[a2597]

 

anyone else have tables that don't render certain parts in the beta?

using Firepower II (1.1 through Bigus 1.4) the apron refuses to render, even though it is checked visible.

If I change it in live editor, I can get it to render by turning it off and on, but then it still won't show up when I go to play the table.

 

Works for me with r1369.  If yours is newer than mine, then might open a ticket on Github.

 

Interesting. I tried on a different PC, and it worked in desktop mode, but broke when I switched to cabinet view. So it's specific to cabinet view.

[Drybonz]

anyone else have tables that don't render certain parts in the beta?

 

Hi a2597... I'm guessing you are probably using an old 10.8 build and need to update, but I could be wrong.  You haven't listed any information about what model (GL, DX, 86, 64) or build number you are using.

[wiesshund]

 

 

Hi !

 

Using VPX8 x64 and really appreciate it, so thanks a lot for your work ! I see the difference, excellent !

 

I have only one little question : In VPX7 we could launch and play a table directly by double clicking on it in the explorer folders. But when doing it with VPX8 it open the VPX8 launcher, ask you to choose the file and launch it. So is there a way to do it like in VPX7, in a more direct way ?

 

I'm not interested in a frontend though.

 

Thanks in advance for your help.

 

I had same issue and resolved it by making a change in the registry.  Follow through by reading posts 761 - 772 in this thread.

 

 

Thanks a lot it worked perfectly !

 

Thanks to wiesshund too for your tip but like the others said it don't work with the VPX8 64 bits version unfortunately.

 

Do you have the 64bit up to date?

and both 32 and 64 should read the INI file
which is where that setting is stored

 

10.8 only stores editor window positions and dock state in the registry.

the only other registry entries pertain to shell, like what to do when double click, right click etc

 

Has to be an underlying cause that might be best discovered and rectified in case it may present a worse issue later

[Itchigo]

How can I stop this little annoyance? Also, what is the last 10.8 that the cursor worked in?
 

[wiesshund]

How can I stop this little annoyance? Also, what is the last 10.8 that the cursor worked in?
 

 

 

Which annoyance?
I am missing something in the screen shot obviously

 

Cursor i am not sure?
I have a cursor in the latest build

[Itchigo]

 

How can I stop this little annoyance? Also, what is the last 10.8 that the cursor worked in?
 

 

 

Which annoyance?
I am missing something in the screen shot obviously

 

Cursor i am not sure?
I have a cursor in the latest build

 

Look how the table is buried under the editor. I have to drag the editor so I can click the table to give it focus. Then it doesn't remember the focus. I don't have a cursor so I have to guess about dragging the editor.

[wiesshund]

 

 

How can I stop this little annoyance? Also, what is the last 10.8 that the cursor worked in?
 

 

 

Which annoyance?
I am missing something in the screen shot obviously

 

Cursor i am not sure?
I have a cursor in the latest build

 

Look how the table is buried under the editor. I have to drag the editor so I can click the table to give it focus. Then it doesn't remember the focus. I don't have a cursor so I have to guess about dragging the editor.

 

funky

 

i am not seeing an open bug report though?

 

On the editor thing, it looks like VPX was not launched with minimize flag
how was said table launched?

 

For your issue, seems like a few things useful to be in the bug report would be

OS, exact build number number as well as version

DX Diag report

Put VPX into logging mode (its in vpx prefs) and include VPX log
Everything else you can think of that is relevant.

 

Im not sure how to replicate that, ive a number of machines here, some pretty old too
and machines with nothing but a intel iGPU.

But can't replicate it.

I dont have any presently imaged with an older OS except the one Retro machine with a mobile voodoo GPU, for running old Glide games

but it runs Win98SE, so no help there at all, cant run vpx on it, definitely not 10.8.

[Itchigo]

While I may not have a typical system, I can't believe with the thousands of vp users that I'm the only one with these issues.

 

Asrock X470

Ryzen 5 2600

16gb ddr4 ram

Nvidia 1050ti

Windows 7

 

Bug report created.

Edited by Itchigo, 19 September 2023 - 09:43 AM.

[Drybonz]

I haven't heard about anything like this in this thread yet, but that doesn't mean it hasn't happened to someone else.  I doubt it has to do with your hardware, and Win7 is old, but there are plenty of VP guys still running it, so it's probably not related to that.

 

Are you just opening the tables through the editor, or do you have some frontend running?  Are you using any command line stuff?

 

Just trying to think of possibilities.  When you said you don't have a typical system, did you mean the hardware, or something else?

[JanK]

Is there, quality wise, a best way to setup the camera view with an old table? At the moment, I switch to camera mode and then do a reset by pressing the trigger button. Next I rotate the table with Player Z a little bit to my taste, zoom in or out using Field of View and finally I adjust the Vertical Offset.

 

So I don't use the table scale (as a group) to zoom in or out.  And, by using the reset option all the scale values reset to 100%. So if the original table uses, for example, a X scale value of 100% and an Y scale value of 95% the table will look slightly different as the author intended. Am I correct to assume that this is almost never the case?

 

Please note that I'm using tables in desktop mode and that I used to save my table settings directly to the table instead of a POV file. 

[wiesshund]

Is there, quality wise, a best way to setup the camera view with an old table? At the moment, I switch to camera mode and then do a reset by pressing the trigger button. Next I rotate the table with Player Z a little bit to my taste, zoom in or out using Field of View and finally I adjust the Vertical Offset.

 

So I don't use the table scale (as a group) to zoom in or out.  And, by using the reset option all the scale values reset to 100%. So if the original table uses, for example, a X scale value of 100% and an Y scale value of 95% the table will look slightly different as the author intended. Am I correct to assume that this is almost never the case?

 

Please note that I'm using tables in desktop mode and that I used to save my table settings directly to the table instead of a POV file. 

 

Unless an author used skewed graphics, those scales should be perfectly fine at 100%

people stretch them, but that is a personal thing, not a correct thing

[Itchigo]

I haven't heard about anything like this in this thread yet, but that doesn't mean it hasn't happened to someone else.  I doubt it has to do with your hardware, and Win7 is old, but there are plenty of VP guys still running it, so it's probably not related to that.

 

Are you just opening the tables through the editor, or do you have some frontend running?  Are you using any command line stuff?

 

Just trying to think of possibilities.  When you said you don't have a typical system, did you mean the hardware, or something else?

Thanks Drybonz.

 

I'm running through the editor, or Pinball X. (I adjust everything the way I want it in the editor before I add it to Pinball X). I don't use any command line stuff.

 

When I say not a typical system I mean that when I built my cab computer I hated windows 10 and all the telemetry. My cab doesn't support 7, but I made it work anyway. (Hint) you have to either inject the usb drivers in the install disk or install then add them via a ps2 mouse.

[Drybonz]

When I say not a typical system I mean that when I built my cab computer I hated windows 10 and all the telemetry. My cab doesn't support 7, but I made it work anyway. (Hint) you have to either inject the usb drivers in the install disk or install then add them via a ps2 mouse.

 

Well, I don't know that anyone else running Windows 7 has been talking about a similar problem.  I saw that you had made a bug report, so that was probably the best thing to do, and we will see what happens with it.

[wiesshund]

 

 

 I hated windows 10 and all the telemetry..

 

turn telemetry off.

you do not web browse on the cab right?

[Kikwik]

 

 

 

 

Hi !

 

Using VPX8 x64 and really appreciate it, so thanks a lot for your work ! I see the difference, excellent !

 

I have only one little question : In VPX7 we could launch and play a table directly by double clicking on it in the explorer folders. But when doing it with VPX8 it open the VPX8 launcher, ask you to choose the file and launch it. So is there a way to do it like in VPX7, in a more direct way ?

 

I'm not interested in a frontend though.

 

Thanks in advance for your help.

 

I had same issue and resolved it by making a change in the registry.  Follow through by reading posts 761 - 772 in this thread.

 

 

Thanks a lot it worked perfectly !

 

Thanks to wiesshund too for your tip but like the others said it don't work with the VPX8 64 bits version unfortunately.

 

Do you have the 64bit up to date?

and both 32 and 64 should read the INI file
which is where that setting is stored

 

10.8 only stores editor window positions and dock state in the registry.

the only other registry entries pertain to shell, like what to do when double click, right click etc

 

Has to be an underlying cause that might be best discovered and rectified in case it may present a worse issue later

 

 

Yes I have the latest VPX8 10.8.0 beta 5, the very latest one.

 

If you want more informations or if it can help even a little, I'll gladly do so.

[wiesshund]

 

 

 

Yes I have the latest VPX8 10.8.0 beta 5, the very latest one.

 

If you want more informations or if it can help even a little, I'll gladly do so.

 

 What registry setting are you tinkering with?

[Kikwik]

I exactly followed Milos' post, which is post N°770 of this thread, page 39.

Edited by Kikwik, 20 September 2023 - 06:08 PM.

[wiesshund]

 

I exactly followed Milos' post, which is post N°770 of this thread, page 39.

 

 

Technically there are no shell commands for VpinballX64.exe, because it is never installed (beta has no installer yet)

but that only pertains to what happens if double clicking or right clicking a table

one can simply rename VpinballX.exe to VpinballX32.exe, and vpinballX64.exe to VpinballX.exe and accomplish same thing

 

and a front end doesnt need or care about the shell/context commands/menu

 

Which would have no bearing on what Kikwik described, which is the file dialog menu that vpx will display upon opening and exiting

if those options are checked in editor/UI prefs