4027 replies to this topic

[Segovia11]

 

Dear Development Team  please find enclosed a political question,
                                                                                                           should the VPX title be changed to VPXI due to the loss of its backward compatibility?  A popup menu that warns the user before saving the file would also jog a memory or two, or more!. 
 
Thanks a million Devs for the time you have dedicated to the upgrades
VPX is a joy 
      

No VPX is fully compatible to older versions. If you save a table with 10.7 you will get a notification message when you load that table in earlier versions.

 

Dear Fuzzel i beg to differ,                         

                                         I can also confirm that you will get a notification message when the 10.6 version loads the 10.7.

                                         Quote "Error This table was saved with version 10.70 and is newer than the supported version 10.60! You might get problems loading/playing it!"

                                       

                                         When you run a 10.7 build in the 10.6 version it will not load the images & there is a sound buffer load issue. That is a sign & a symptom of incompatibility.

                                         Although, why would you want to revert to 10.6 after building in 10.7. 10.7 is a better program thanks to your upgrades & error corrections.

                                 

                                         But why do I want to run a 10.6 table that has been saved in 10.7 in an earlier version ?  In fact, there will be no need to run the table in 10.6  if the table runs in 10.7 without problems.   

                                           

                                         However, you will not be able to run the new saved file in 10.6 without issues if there is a problem when running a 10.6 table in 10.7 after saving it. 

                                         The table user / designer will need to open the original file in the 10.6 to rid of the known issues

 

                                         Can 10.7 identify an earlier version, if it can the table user / designer would appreciate a warning notification prior to saving a later version in 10.7.

                                         In fact 10.7 does not need to be able to identify an earlier version, just a warning would be enough prior to saving in 10.7.                                       

                      

   

Edited by Segovia11, 03 May 2021 - 09:16 PM.

[Thalamus]

This is the way it has always been handled before. If you are changing the table in 10.7 and saving it. Well, it has a 10.7 or never requirement. Simple as that. If that is an issue for you. Then I recommend you wait for the official 10.7 release.

[wiesshund]

This is the way it has always been handled before. If you are changing the table in 10.7 and saving it. Well, it has a 10.7 or never requirement. Simple as that. If that is an issue for you. Then I recommend you wait for the official 10.7 release.

 

think the same thing happens if you edit a table in 10.6.1 and then try loading it into like 10.1 or such?

[gtxjoe]

This is the way.

Does anyone using VPX6 ever go back and use VPX, VPX1, VPX2, VPX3, VPX4 or VPX5?

[Thalamus]

Correct. Save it in 10.6.1 and it requires 10.6 - the last DOT is just "hot fixes". The idea is that all VPX, if using the latest exe, should be able to load and run older versions. But, using old versions to load games saved in newer versions will give you a warning that it is saved in a higher version and that it most probably will not work as expected. The "might" is there because you could in theory just have a table with NOTHING, and to the best of my knowledge, that won't break

[Wylte]

Honestly, I was surprised how *few* things break when trying to move a .7 table to .6!

Well, it has a 10.7 or never requirement.

I assume you meant "newer", but never makes it sound very ominous lol

[wiesshund]

This is the way.

Does anyone using VPX6 ever go back and use VPX, VPX1, VPX2, VPX3, VPX4 or VPX5?

 

Only if i want to embark on an adventure of

 

WTF NOTHING WORKS!

 

And i have that adventure enough without choosing to go on it.

[gtxjoe]

This is the way.

Does anyone using VPX6 ever go back and use VPX, VPX1, VPX2, VPX3, VPX4 or VPX5?

 
Only if i want to embark on an adventure of
 
WTF NOTHING WORKS!
 
And i have that adventure enough without choosing to go on it.

So you you stick with VPX6. Thats fine.

Do you use VPX, VPX1, VPX2, VPX3 VPX4 or VPX5?

[wiesshund]

 

 

This is the way.

Does anyone using VPX6 ever go back and use VPX, VPX1, VPX2, VPX3, VPX4 or VPX5?

 
Only if i want to embark on an adventure of
 
WTF NOTHING WORKS!
 
And i have that adventure enough without choosing to go on it.

So you you stick with VPX6. Thats fine.

Do you use VPX, VPX1, VPX2, VPX3 VPX4 or VPX5?

 

 

Well actually i just stick with 10.7 but no, i dont go to VPX 1 2 3 4 5
Because like i said, i dont want to purposely go on that adventure of nothing works

 

Even 10.6.0 can at times be problematic with a semi recent table due to script changes

 

 

Things made in the New always reach a point where they dont run in the Old
It's either that, or you smother the development

Edited by wiesshund, 04 May 2021 - 03:29 AM.

[Segovia11]

This is the way it has always been handled before. If you are changing the table in 10.7 and saving it. Well, it has a 10.7 or never requirement. Simple as that. If that is an issue for you. Then I recommend you wait for the official 10.7 release.

 

Dear Thalamus,

                          if you read my comment properly you will identify that it was not an issue for me.  I said,  quote " Although why would you want to revert to 10.6 after building in 10.7. 10.7 is a better program thanks to the devs upgrades & error corrections" . You need to take on board what people write before responding to a forum note.  

 

1. My comment was referring to a recommended upgrade. May be a warning sign that is similar to the one you get when loading a 10.7 build from a later version such as 10.6. You and the forum have identified that 10.7 is incompatible with older versions & there is good evidence to support that - even the warning comment in 10.6 does that for you. Which could not be any more clearer. 

2. 10.7 could do this before the save. It makes much more sense to manufacture a warning regarding compatibility issues from the front end, apposed to leaving it to a later date. The earlier the better. You could say its a decent thing to do. I am sure the majority of table users and designers would appreciate the notice devs.

3. Putting the warning notice in 10.7 would make better sense. (without a shadow of doubt) 

 

     

Edited by Segovia11, 04 May 2021 - 01:24 PM.

[onemanproject]

First i have a compile error than VPX.7 crashed:

 

Crash report VPX rev153 (1856040)
============
Process: vpinballx.exe
Reason: 0xC0000005 - EXCEPTION_ACCESS_VIOLATION at 0023:004D6BAD
Attempt to read from 0x00000000
Thread ID: 0x4C0 [1216]

Call stack
==========
004D6BAD vpinballx.exe (0x0AD69E50 0x00000000 0x0019E5A0 0x00000000)
004D684A vpinballx.exe (0x0AD69E50 0x000908F0 0x5DE06C70 0x0019e588)
004D8B3B vpinballx.exe (0x00000004 0x0019EDD0 0x00426E80 0x004d5001)
004D5001 vpinballx.exe (0x0000C2AE 0x0AD69E50 0x00426E80 0x00000000)
00427783 vpinballx.exe (0x0000C2AE 0x00000000 0x00000000 0x000908f0)
004E81E4 vpinballx.exe (0x0000C2AE 0x00000000 0x00000000 0x0000c2ae)
00426ED8 vpinballx.exe (0x00426E80 0x000908F0 0x0000C2AE 0x00000000)
763E5E7A user32.dll GetClassLongW + 0x7AA (0x00426E80 0x00000000 0x0000C2AE 0x00000000)
763E3BEA user32.dll DispatchMessageW + 0x24A (0x0019F3BC 0x005C3A52 0x0019F28C 0x00000000)
763D5D70 user32.dll DispatchMessageA + 0x10 (0x0019F28C 0x00000000 0x00000001 0x0019f2a8)
005C3A52 vpinballx.exe (0x00000000 0x00738034 0x00000000 0x00000000)
001A006E  (0x00738034 0x00000000 0x00000000 0x00000000)

Environment
===========
Date/time: 4/5/2021, 18:13:52:53
Number of CPUs: 16
Processor type: 586
System: Windows 10 (10.0 19042)

Memory status
=============
Total Reserved: 752300K (734M) bytes
Total Commited: 1587592K (1550M) bytes
Total Free: 1854348K (1810M) bytes
Largest Free: 438144K (427M) bytes

Registers
=========
EAX=00000000 EBX=52BDF1A0 ECX=00000006 EDX=0019E0C0
ESI=24D0A8A0 EDI=0AD69E50 EBP=0074EA38 ESP=0019F3C4 EIP=001A006E
FLG=00210206 CS=0023 DS=002B SS=002B ES=002B FS=0053 GS=002B


Failed to save minidump.
 

[mrjcrane]

 

 

 

This is the way.

Does anyone using VPX6 ever go back and use VPX, VPX1, VPX2, VPX3, VPX4 or VPX5?

 
Only if i want to embark on an adventure of
 
WTF NOTHING WORKS!
 
And i have that adventure enough without choosing to go on it.

So you you stick with VPX6. Thats fine.

Do you use VPX, VPX1, VPX2, VPX3 VPX4 or VPX5?

 

 

Well actually i just stick with 10.7 but no, i dont go to VPX 1 2 3 4 5
Because like i said, i dont want to purposely go on that adventure of nothing works

 

Even 10.6.0 can at times be problematic with a semi recent table due to script changes

 

 

Things made in the New always reach a point where they dont run in the Old
It's either that, or you smother the development

 

Likewise, I never go backwards in the VPX version once I am on the latest build OR I'll just wait for a table to be revised and released under the VPX beta 7 OR I wait for some of the VP9 tables to be converted to vp10.

[Bendo]

I must be missing something because I never see anyone talking about this issue.  When I make changes to a table in 10.7 and go to save them, saving fails. I keep updating to the latest version thinking it will be fixed. But like I said, no one else has mentioned it. Is there a trick to saving a table after you have made a change?  Thanks

[wiesshund]

I must be missing something because I never see anyone talking about this issue.  When I make changes to a table in 10.7 and go to save them, saving fails. I keep updating to the latest version thinking it will be fixed. But like I said, no one else has mentioned it. Is there a trick to saving a table after you have made a change?  Thanks

click file and save

 

Is the table file read only?
Or in a read only folder?

[Robsoie]

I often read that DDS format for textures at real time is always a good idea because it's directly read "as it is" by the GPU without said GPU having to uncompress it first internally like in most other texture format like JPG or PNG.

 

I know VPX support JPG and PNG, but does it support DDS ?

[wiesshund]

I often read that DDS format for textures at real time is always a good idea because it's directly read "as it is" by the GPU without said GPU having to uncompress it first internally like in most other texture format like JPG or PNG.

 

I know VPX support JPG and PNG, but does it support DDS ?

As far as i know, not right now

[Bendo]

Bendo, on 04 May 2021 - 6:35 PM, said:

I must be missing something because I never see anyone talking about this issue.  When I make changes to a table in 10.7 and go to save them, saving fails. I keep updating to the latest version thinking it will be fixed. But like I said, no one else has mentioned it. Is there a trick to saving a table after you have made a change?  Thanks

click file and save

 

Is the table file read only?
Or in a read only folder?

 

Click file and save, yup the same way I have been doing on 10.6 for two years.

Folder is same as all the VP10.6 tables, so I will check to see if somehow every 10.7 I download is read only. I have never seen that before, but I will check it out. Thanks

[hitman2304]

https://support.lumi...g-DDS-textures-

 

Maybe its not so bad idea to add support for this texture format.

Edited by hitman2304, 05 May 2021 - 08:31 AM.

[fuzzel]

rev169 is up:

 

- fix scaling of primitive property controls

- some other UI scaling updates

- fix applying property edit box changes when used pressed tab or clicks another element (hopefully)

- low impact FPS-only stats display

  first press of 'F11' will now show a minimalistic FPS-only text, then pressing it the next time will continue with the already known detailed statistics/profiling displays (as the latter had too much impact on the FPS itself)

  also only show FPS for static-object-only & AO-only F11 views

- add support for capturing any window content into a flasher texture (intended to be used with PUP content thx @Nailbuster)

 

a word for the new capturing feature of the flasher element:

Flashers can now be used to capture another window and render it as a texture in VPX. For example open VLC and play a video in the background and grab the frames.

 

To do this do the following in the script:

set flasher.VideoCapWidth=xxx and flasher.VideoCapHeight=yyy (where xxx is the capture width and yyy is the capture height in pixels) before the timer calls VideoCapUpdate

 

Sub flasher_Timer()

   flasher.VideoCapUpdate = "<name of the window title you like to capture>"

End Sub

 

The name of the window title must be a 100% match otherwise it won't work.

 

Edited by fuzzel, 09 May 2021 - 10:47 AM.

[wiesshund]

 

 

To do this do the following in the script:

flasher.VideoCapWidth=500

flasher.VideoCapHeight=500

 

Sub flasher_Timer()

   flasher.VideoCapUpdate(<name of the window title you like to capture>)

End Sub

 

The name of the window title must be a 100% match otherwise it won't work.

 

 

 

And Viola!
Netflix inside any table

 

dont laugh, it works LOL