4027 replies to this topic

[BobAlbright]

First i would like to thank every one involved in this new version.

I downloaded the 10.7 installer but am just using the 10.7 EXE. file in my 10.6 cabinet and not the installer itself.

My question is am i missing some features of the installer or is this all i really need?

I have not tested all of my tables but so far i have not had any problems.

 

Thanks 

 

good question..I’m curious as well

[fuzzel]

You don't need the installer if you have a working installation. But you must update the script folder that comes with the standalone version of vpx and the dlls as well.

[tmpc]

You don't need the installer if you have a working installation. But you must update the script folder that comes with the standalone version of vpx and the dlls as well.

I will copy those over as well, thank you.

[fripounet]

on the whole it's ok.

we feel that you have embarked on a path strewn with pitfalls

good job all the same, even there are still a lot of bugs

the layers, it was laborious

still a small point concerning the procedures of setting in layers, to fix everything well.

__ when the layer is selected but not activated ; the element chosen on the work plan must disappear automatically.

__ when an image is imported it must appear automatically in the inspector

I await the good surprises announced concerning the future version 11.

Edited by fripounet, 28 December 2021 - 11:33 AM.

[millansoft]

Hello, 

 

The lastest VPX just closes (when opening Bow and Arrow from Goldchicco) and it left this txt log report:

 

Crash report VPX rev367 (e242d7c)

============

Process: VPinballX.exe

Reason: 0xC0000005 - EXCEPTION_ACCESS_VIOLATION at 0023:683E0C03

Attempt to read from 0x001A4000

Thread ID: 0x128C [4748]

 

Call stack

==========

683E0C03 DSOUND.dll DirectSoundCreate8 + 0x933 (0x0E080330 0x0019DF00 0x00006176 0x683e0b80)

683E01A3 DSOUND.dll DllGetClassObject + 0x3143 (0x0E080330 0x0019DF00 0x00006176 0x0019dda8)

683E47ED DSOUND.dll DirectSoundCreate8 + 0x451D (0x00000000 0x683EFAD0 0x0E07ED68 0x683efb26)

683E4731 DSOUND.dll DirectSoundCreate8 + 0x4461 (0x0019DDA8 0x00000000 0x683EF820 0x037406e8)

683EF84E DSOUND.dll GetDeviceID + 0x348E (0x0019DDA8 0x00000000 0x00000000 0x037408c0)

683F6175 DSOUND.dll DllCanUnloadNow + 0x1115 (0x0019DDA8 0x0019DDA4 0x0019DDD0 0x683e0684)

683F61CE DSOUND.dll DllCanUnloadNow + 0x116E (0x0019DDA8 0x0019DDA4 0x0E11D1F0 0x0019f958)

683E0684 DSOUND.dll DirectSoundCreate8 + 0x3B4 (0x037408C0 0x0019DEDC 0x0E11D1F4 0x00000000)

00548B7A VPinballX.exe (0x0876DDF0 0x0055C516 0x032DD080 0x0019e31c)

0055C516 VPinballX.exe (0x00000000 0x00000424 0x00000000 0x032dd188)

0055F189 VPinballX.exe (0x00010000 0x0869C370 0x0055E58B 0x086b5280)

0055E58B VPinballX.exe (0x0000004F 0x0019F354 0x00001388 0x20210001)

005DA1C9 VPinballX.exe (0x0019F2D8 0x00000000 0x005D8C14 0x032b2060)

005D8C14 VPinballX.exe (0x00001388 0x00000000 0x00000111 0x0019f354)

005DD090 VPinballX.exe (0x00000111 0x00001388 0x00000000 0x00000111)

005E4A3D VPinballX.exe (0x00428700 0x00070684 0x00000111 0x00001388)

75CCA33A user32.dll GetClassLongW + 0x7BA (0x00428700 0x00000000 0x00000111 0x00001388)

75CC809A user32.dll DispatchMessageW + 0x24A (0x75CB1F00 0x005DBD86 0x0019F224 0x00000000)

75CBA230 user32.dll DispatchMessageA + 0x10 (0x0019F224 0x00000000 0x00400000 0x0019f240)

005DBD86 VPinballX.exe (0x00000000 0x00000001 0x00237000 0x0076ec50)

005C8095 VPinballX.exe (0x00400000 0x00000000 0x03203C25 0x00000001)

005F5A26 VPinballX.exe (0x00237000 0x76B2FA10 0x0019FFDC 0x77a97a9e)

76B2FA29 KERNEL32.DLL BaseThreadInitThunk + 0x19 (0x00237000 0x749081C2 0x00000000 0x00000000)

77A97A9E ntdll.dll RtlGetAppContainerNamedObjectPath + 0x11E (0xFFFFFFFFFFFFFFFF 0x77AB8A5D 0x00000000 0x00000000)

77A97A6E ntdll.dll RtlGetAppContainerNamedObjectPath + 0xEE (0x0311F4D0 

Environment

===========

Date/time: 27/12/2021, 16:59:30:51

Number of CPUs: 6

Processor type: 586

System: Windows 10 (10.0 19044)

 

Memory status

=============

Total Reserved: 77080K (75M) bytes

Total Commited: 267600K (261M) bytes

Total Free: 3849560K (3759M) bytes

Largest Free: 2095452K (2046M) bytes

 

Registers

=========

EAX=00200008 EBX=00006176 ECX=00000004 EDX=00000006

ESI=001A3FF0 EDI=0E086420 EBP=0019FFEC ESP=0019FFE4 EIP=77A97A6E

FLG=00010202 CS=0023 DS=002B SS=002B ES=002B FS=0053 GS=002B

 

 

Mini dump saved successfully.

[Gravy]

Many thanks to the VPX team for the new release. Excellent work.

[jpsalas]

 

Hello, 

 

The lastest VPX just closes (when opening Bow and Arrow from Goldchicco) and it left this txt log report:

 

Crash report VPX rev367 (e242d7c)

============

Process: VPinballX.exe

Reason: 0xC0000005 - EXCEPTION_ACCESS_VIOLATION at 0023:683E0C03

Attempt to read from 0x001A4000

Thread ID: 0x128C [4748]

 

Call stack

==========

683E0C03 DSOUND.dll DirectSoundCreate8 + 0x933 (0x0E080330 0x0019DF00 0x00006176 0x683e0b80)

683E01A3 DSOUND.dll DllGetClassObject + 0x3143 (0x0E080330 0x0019DF00 0x00006176 0x0019dda8)

683E47ED DSOUND.dll DirectSoundCreate8 + 0x451D (0x00000000 0x683EFAD0 0x0E07ED68 0x683efb26)

...

 

It works fine in my computer. Since most of the errors are about the DirectSound, then I should suggest you update your drivers for your sound board (Realtek, probably). I also should reinstall the directx9 from Microsoft. Another person had this kind of error on some other tables, and the reason was an automatic overclocking of the memory in the bios settings. Removing the overclocking in the bios solved his problem.

[millansoft]

 

 

Hello, 

 

The lastest VPX just closes (when opening Bow and Arrow from Goldchicco) and it left this txt log report:

 

Crash report VPX rev367 (e242d7c)

============

Process: VPinballX.exe

Reason: 0xC0000005 - EXCEPTION_ACCESS_VIOLATION at 0023:683E0C03

Attempt to read from 0x001A4000

Thread ID: 0x128C [4748]

 

Call stack

==========

683E0C03 DSOUND.dll DirectSoundCreate8 + 0x933 (0x0E080330 0x0019DF00 0x00006176 0x683e0b80)

683E01A3 DSOUND.dll DllGetClassObject + 0x3143 (0x0E080330 0x0019DF00 0x00006176 0x0019dda8)

683E47ED DSOUND.dll DirectSoundCreate8 + 0x451D (0x00000000 0x683EFAD0 0x0E07ED68 0x683efb26)

...

 

It works fine in my computer. Since most of the errors are about the DirectSound, then I should suggest you update your drivers for your sound board (Realtek, probably). I also should reinstall the directx9 from Microsoft. Another person had this kind of error on some other tables, and the reason was an automatic overclocking of the memory in the bios settings. Removing the overclocking in the bios solved his problem.

 

 

Thanks for your help, I tried with that, and not luck.

 

Finally doing some try & error, I found how to deal with the bug (I guess it is one)

When I open the table from File menu, using the numbered list with last opened tables, it just crash while opening. But from the open menu, works fine.

 

Hope it helps to fix something

Edited by millansoft, 28 December 2021 - 12:45 AM.

[jpsalas]

 

 

 

Hello, 

 

The lastest VPX just closes (when opening Bow and Arrow from Goldchicco) and it left this txt log report:

 

Crash report VPX rev367 (e242d7c)

============

Process: VPinballX.exe

Reason: 0xC0000005 - EXCEPTION_ACCESS_VIOLATION at 0023:683E0C03

Attempt to read from 0x001A4000

Thread ID: 0x128C [4748]

 

Call stack

==========

683E0C03 DSOUND.dll DirectSoundCreate8 + 0x933 (0x0E080330 0x0019DF00 0x00006176 0x683e0b80)

683E01A3 DSOUND.dll DllGetClassObject + 0x3143 (0x0E080330 0x0019DF00 0x00006176 0x0019dda8)

683E47ED DSOUND.dll DirectSoundCreate8 + 0x451D (0x00000000 0x683EFAD0 0x0E07ED68 0x683efb26)

...

 

It works fine in my computer. Since most of the errors are about the DirectSound, then I should suggest you update your drivers for your sound board (Realtek, probably). I also should reinstall the directx9 from Microsoft. Another person had this kind of error on some other tables, and the reason was an automatic overclocking of the memory in the bios settings. Removing the overclocking in the bios solved his problem.

 

 

Thanks for your help, I tried with that, and not luck.

 

Finally doing some try & error, I found how to deal with the bug (I guess it is one)

When I open the table from File menu, using the numbered list with last opened tables, it just crash while opening. But from the open menu, works fine.

 

Hope it helps to fix something

 

 

I get the same error when loading the table from the menu list The table loads fine when using the File Open, or when I right click on the file in explorer and choose "Edit", but when selecting the file from the file list, VPX simply crashes,

 

I tried saving the table again with 10.7, and it still crashes.

 

I tried removing all the sounds, saving the table, and then it works fine.

 

I tried importing all the sounds again, saving the table, close it, and then trying to open the table from the file list then it crashes again.

 

So the problem must be the number of sounds, as there are many

 

toxie/fuzzel: could you take a look if you can find the error? The table uses the Fleep sounds, and they are many

 

The table is this one:

Bow And Arrow (Bally 1974) - VPForums.org

 

There must be other tables that also crash using the file list

A little more info about the bug: Loserman's EM table also crashes the same way:

Bow and Arrow EM (Bally 1975) - VPForums.org

And a little more info for toxie/fuzzel: reducing the number of sounds fixes the problem.

[wiesshund]

I hardly ever use the file list
But yea um, a whole ton of tables crash that way
Basically, all of my EM's, and a lot of ROM tables that use custom sounds instead of the ROM

 

File > Open > pick a table works fine
file manager play or edit works fine

 

Must be some little thing with how the last used list tries to short cut things?

 

@JP lol yea Deadpool is dead in the pool if i load that way

Edited by wiesshund, 28 December 2021 - 09:55 AM.

[rony49]

Many thanks to the VPX team for the new release.

 

I upgrade VPX 10.6 to 10.7

 

version : VPX rev367 (e242d7c)

 

Now, I can't edit script

Button Toggle script editor not working.

I see an empty window on status bar.

 

Thank you for your help.

[Outhere]

Many thanks to the VPX team for the new release.

 

I upgrade VPX 10.6 to 10.7

 

version : VPX rev367 (e242d7c)

 

Now, I can't edit script

Button Toggle script editor not working.

I see an empty window on status bar.

 

Thank you for your help.

Try downloading again
Works fine for me

[rony49]

 

Many thanks to the VPX team for the new release.

 

I upgrade VPX 10.6 to 10.7

 

version : VPX rev367 (e242d7c)

 

Now, I can't edit script

Button Toggle script editor not working.

I see an empty window on status bar.

 

Thank you for your help.

Try downloading again
Works fine for me

 

 

Thank you for your super fast response.
I have already tried twice
I will try again later

 

 

[toxie]

Maybe you could try the new "Reset Window Positions" button in the "Editor/UI" settings?

[toxie]

@millansoft and the other helpers: Seems like some tables use 32bit float wav samples, and for whatever reason dsound digests them as-is when opening a table one way, but not the other, although ALL of the file loading code is equivalent. So must be some sideffect with the init of memory structs. I found a tiny remark on MSDN for float samples and implemented that and it seems to work now all the time..

 

Please test via https://github.com/v...runs/1631236361 if all samples still work as intended for the previously affected tables..

[millansoft]

@millansoft and the other helpers: Seems like some tables use 32bit float wav samples, and for whatever reason dsound digests them as-is when opening a table one way, but not the other, although ALL of the file loading code is equivalent. So must be some sideffect with the init of memory structs. I found a tiny remark on MSDN for float samples and implemented that and it seems to work now all the time..

 

Please test via https://github.com/v...runs/1631236361 if all samples still work as intended for the previously affected tables..

 

Thanks a lot, seems to be fixed 

[fripounet]

it's great, I just noticed it a moment ago, there is now a real browser (double click on the layer element and the table element appears).

the connection is made.

Edited by fripounet, 29 December 2021 - 01:29 PM.

[jpsalas]

 

@millansoft and the other helpers: Seems like some tables use 32bit float wav samples, and for whatever reason dsound digests them as-is when opening a table one way, but not the other, although ALL of the file loading code is equivalent. So must be some sideffect with the init of memory structs. I found a tiny remark on MSDN for float samples and implemented that and it seems to work now all the time..

 

Please test via https://github.com/v...runs/1631236361 if all samples still work as intended for the previously affected tables..

 

Thanks a lot, seems to be fixed 

 

 

Yes, those tables work here too

 c'est super , je viens de le remarquer à l'instant , il y a maintenant un véritable navigateur (double clic élément calque et l'élément de table apparait).

la liaison est faites.

 

it's great, I just noticed it a moment ago, there is now a real browser (double click on the layer element and the table element appears).

the connection is made.

 

 

I have my superior plastic (for decoration) 60/55, non-collidable, and I have a collidable clone at 25/20. sometimes no collision....!! all primitives

 

Yes, very useful I use it a lot

Edited by jpsalas, 29 December 2021 - 01:27 PM.

[fripounet]

you cannot integrate vbs factory (freeware),

instead of the seedy vpx script editor.

 

[jpsalas]

you cannot integrate vbs factory (freeware),

instead of the seedy vpx script editor.

 

 

 

And the question is "why do you want to use that editor for VPX?" I know the VPX program uses VBS as the base of its script but VPX includes hundreds of commands that VBS factory do not understand, so what's the point? And what's wrong with the VPX editor? I don't ask to be sarcastic, but if you have some good points to why that editor should be better then I should like to know I have tried others like notepad++, but I don't see why I should use it.