4027 replies to this topic

[toxie]

crashed several times when clicking on the layers panel

No crash text, it just made a hasty exit with no goodbye :)

 

I couldn't repro this, but i found some other issues with the layer panel, maybe related to that?! I fixed these, so please try the next beta.

 

In the meantime, if you maybe have some clear repro steps on a specific table, that could also help me repro it.

Any possibility that on backglass, the REAR on the sound slider could send to CENTER surround channel?

 

DJRobX may be able to help here, i'd hope.

[Thalamus]

Yes. It's doable.

[wiesshund]

 

crashed several times when clicking on the layers panel

No crash text, it just made a hasty exit with no goodbye :)

 

I couldn't repro this, but i found some other issues with the layer panel, maybe related to that?! I fixed these, so please try the next beta.

 

In the meantime, if you maybe have some clear repro steps on a specific table, that could also help me repro it.

 

 

I was just making some layers and moving things into them
At the times it froze i think i was sliding the layer list up or down, a lot, as i was sorting out all the parts

 

And the beta layering has spoiled me.
I opened some work back in 10.6, and saved it by mistake
All my nice layer organization poof gone.

My fault.

Im lost enough as it is, those enhanced layer abilities help me be a bit less lost

 

Will try next beta as soon as it is posted

Edited by wiesshund, 05 August 2020 - 11:19 PM.

[toxie]

Okay. Just in general, for all here, the more repro steps we have for a problem, the easier to fix for us. Otherwise crash dumps are also very useful, of course (but then more detective work needed usually).

[wiesshund]

I can do this sort of at will.
Steps to reproduce seem to be simple launch, exit, relaunch table a few times
If you exit VPX between launches, will not happen, at least i can not make it happen.

I would honestly just blame the table, except i can simply launch it, leave it running and play it for hours and no problems
And i am still happy to have the table blamed, but i figure i will put it here incase it is helpful

Fails to make the dump each time it does this crash

but it does drop a crash text

Now sometimes it will not get to the crash part, it will just stop, you exit the table, it leaves pinmame running and leaves the ultradmd window running
I did try leaving it in that state to see if it would eventually bomb out and give a log, but it stayed there for a very long time, and so i just killed it.

Again, this is only if you are bouncing in and out of the table a bunch.
I have not been able to make it do that just being used to play tables, i have been fortunate enough to have the beta simply work well as a table player

Heh, sorry, you give me stuff, i will probably break it

 

Crash report VPX rev4257
============
Process: VPinballX.exe
Reason: 0xC0000005 - EXCEPTION_ACCESS_VIOLATION at 0023:776A8D4A
Attempt to read from 0x279DF000
Thread ID: 0xB74 [2932]

Call stack
==========
776A8D4A msvcrt.dll memcpy + 0x5A (0x24666C28 0x279DF000 0x00000600 0x24667cec)
7296886D gdiplus.dll GdipDrawImageRectRect + 0x254D (0x24660650 0x129EE698 0x129EE668 0x00000001)
729713F8 gdiplus.dll GdipCreateBitmapFromScan0 + 0x958 (0x24667CEC 0x24660650 0x129EE8A8 0x246684c8)
729A19D1 gdiplus.dll GdipCreateBitmapFromStream + 0xC11 (0x24667CEC 0x00000080 0x00000020 0x00000000)
7298FCB6 gdiplus.dll GdipBitmapSetPixel + 0x356 (0x129EEA18 0x129EE9DC 0x129EE8A8 0x13cc7590)
72965ED5 gdiplus.dll GdipCreateFromHDC + 0x54F5 (0x129EEA18 0x129EE9DC 0x2466C1E8 0x13cc0908)
729630B5 gdiplus.dll GdipCreateFromHDC + 0x26D5 (0x129EEF74 0x2466C1E8 0x00000003 0x129ef004)
72966EEF gdiplus.dll GdipDrawImageRectRect + 0xBCF (0x2466C1E8 0x129EF050 0x129EF060 0x00000000)
72977B8F gdiplus.dll GdipDrawImageRect + 0x1AF (0x2466C1E8 0x129EF0D8 0x129EF0C8 0x00000002)
72977AD5 gdiplus.dll GdipDrawImageRect + 0xF5 (0x13CC7590 0x2466C1E8 0x00000000 0x00000000)
72977BF2 gdiplus.dll GdipDrawImageRectI + 0x52 (0x13CC7590 0x2466C1E8 0x00000000 0x00000000)
688FDF70 System.Drawing.ni.dll (0x00000020 0x00000080 0x1829044C 0x2466c1e8)
688FA40B System.Drawing.ni.dll (0x00000020 0x00000080 0x00000000 0x00000000)
2400D569  (0x18285DB8 0x18286304 0x18286504 0x00000000)
23E6E73F  (0x18285DB8 0x1827D038 0x1827D094 0x00000000)
23E6E73F  (0x00000023 0x00000000 0x00000000 0x18285db8)
23E6E8B0  (0x18285DB8 0x1827CF38 0x1827CF74 0x00000000)
23E6E73F  (0x129EF384 0x001A00FC 0x00000020 0x182980ec)
23E6C1F7  (0x1833FA10 0x129EF490 0x6CC88604 0x1833f9a8)
6CC62E01 mscorlib.ni.dll (0x1833F9A8 0x00000000 0x00000000 0x00000000)
6CC88604 mscorlib.ni.dll (0x00000000 0x18285CB0 0x00000000 0x129ef4c0)
6CC88537 mscorlib.ni.dll (0x00000000 0x18285CB0 0x00000000 0x1833f9dc)
6CC884F4 mscorlib.ni.dll (0x18285CB0 0x00000000 0x00000000 0x129ef4f0)
6CC62D5B mscorlib.ni.dll (0x0D273140 0x129EF538 0x6E35231A 0x129ef580)
6E34F066 clr.dll (0x129EF580 0x129EF528 0x6E4423D0 0x129ef6b0)
6E35231A clr.dll LogHelp_TerminateOnAssert + 0x93A (0x129EF644 0x1833F9F0 0x00000004 0x129ef568)clr.
Environment
===========
Date/time: 6/8/2020, 01:55:08:22
Number of CPUs: 4
Processor type: 586
System: Windows 10 (10.0 19041)

Memory status
=============
Total Reserved: 167972K (164M) bytes
Total Commited: 782728K (764M) bytes
Total Free: 3243540K (3167M) bytes
Largest Free: 2095424K (2046M) bytes

Registers
=========
EAX=279DF600 EBX=24660650 ECX=00000180 EDX=00000000
ESI=279DF000 EDI=24666C28 EBP=129EF5AC ESP=129EF540 EIP=6E3585BB
FLG=00010216 CS=0023 DS=002B SS=002B ES=002B FS=0053 GS=002B


Failed to save minidump.

One other thing i have noticed, and there is no error or anything, is sometimes the editor will decide it does not want to display the playfield graphic and plastics etc
Does not give any error, just simply does not show it, whether you toggle it on or off, no change.
This also seems to happen when you are going back and forth from running the table to editing quite a bit.

 

And i will fully admit to probably going in and out of a table way more than a sane person, hopefully i will do it less when i actually know what i am doing

[jpsalas]

Another editor bug for you

 

Here it is a demo table. It has 3 lights all in different size.

 

- If you select all 3 lights by drawing a rectangle around them, then all the lights get the same Falloff size.

 

- The 3 lights are in a collection, If you select the option "Group Elements together" in the collection, and then select one light, all the lights get selected (as expected) but then all the lights get the same Falloff size of the selected light.

 

That's all for now

[onemanproject]

I had yesterday a VPX crash:

 

Crash report VPX rev4257
============
Process: VPinballX.exe
Reason: 0xE06D7363 - UNKNOWN at 0023:75FC9862
Thread ID: 0x3204 [12804]

Call stack
==========
75FC9862 KERNELBASE.dll RaiseException + 0x62 (0xFFFFFFFFE06D7363 0x00000001 0x00000003 0x0019ca74)
005EEF20 VPinballX.exe (0x0019CAA0 0x00773CDC 0x030F07EC 0x00000000)
00425EC5 VPinballX.exe (0x00000000 0x030D3D20 0x00000000 0x40000000)
004254F5 VPinballX.exe (0x00000000 0x00000001 0x030F07E0 0x0019d014)
0044209F VPinballX.exe (0x0019D238 0x00080F4C 0x030F07E0 0x00425c80)

Environment
===========
Date/time: 5/8/2020, 21:33:43:138
Number of CPUs: 4
Processor type: 586
System: Windows 10 (10.0 19041)

Memory status
=============
Total Reserved: 173508K (169M) bytes
Total Commited: 325900K (318M) bytes
Total Free: 3694832K (3608M) bytes
Largest Free: 2095296K (2046M) bytes

Registers
=========
EAX=0019C9F8 EBX=19930520 ECX=00000003 EDX=00000000
ESI=00743E10 EDI=00773CDC EBP=00000000 ESP=0019CDDC EIP=004264F0
FLG=00000212 CS=0023 DS=002B SS=002B ES=002B FS=0053 GS=002B


Failed to save minidump.
 

[fuzzel]

Another editor bug for you

 

Here it is a demo table. It has 3 lights all in different size.

light-test.zip

 

- If you select all 3 lights by drawing a rectangle around them, then all the lights get the same Falloff size.

 

- The 3 lights are in a collection, If you select the option "Group Elements together" in the collection, and then select one light, all the lights get selected (as expected) but then all the lights get the same Falloff size of the selected light.

 

That's all for now

Fixed in the next build. However there is one thing to keep in mind when dealing with multi-selections. If you select multiple elements of the same type and change a value don't forget to press the enter key to really assign the value to all elements in the selection. 

Without pressing the enter key but instead clicking some other element the new entered value won't be saved to the previous selected elements.

[wiesshund]

bug in layers

create a new layer
change name of layer
press enter

Layer panel dies, it suddenly shows no layers, you have to quit and restart vpx to get it back.
VPX keeps running, it does not crash, but the layer display is no longer functional

 

If you rename the layer, and do not press enter and instead go click the mouse some place else, it saves the name and the layer panel keeps working

[Mister Transistor]

Hey all.  First, thank you all very much for your many hours of hard work making VPX the best!

 

Second, I recently switched to the latest beta 7's, and I'm experiencing some weirdness, maybe it's me or maybe it's bug, not sure.

 

Here's what's happening:  In the global Properties, Physics pane, it seems that values changed there do not get saved out when they have been modified.  Notably it does not even "notice" that values there have changed, by prompting to save the modified table upon exiting.

 

I am mostly working with the first 3 values there, Gravity Constant, Playfield Friction, and Playfield Elasticity, and also sometimes make changes to the table slope, min and max.  Exporting and Importing seems to work, but the new imported values are not saved out with the table as they did in VPX Beta 6.  I have only tried some of the latest versions of VPX 7, so I'm not sure when it broke but the versions I have used are 4224 and the latest as of this writing, 4257.

 

Am I missing something, or is there some new procedure where physics aren't saved with tables in VPX 7 the same way they were with VPX 6?  Or, could this be a bug, perhaps?

 

Thanks very much for your time, hopefully I am just doing something wrong, but I hope it's not actually a bug for your sake - you all have enough work to do as it is! 

Edited by Mister Transistor, 09 August 2020 - 08:20 AM.

[toxie]

bug in layers

create a new layer
change name of layer
press enter

Layer panel dies, it suddenly shows no layers, you have to quit and restart vpx to get it back.
VPX keeps running, it does not crash, but the layer display is no longer functional

 

If you rename the layer, and do not press enter and instead go click the mouse some place else, it saves the name and the layer panel keeps working

Should be fixed with next build, please test then.

One other thing i have noticed, and there is no error or anything, is sometimes the editor will decide it does not want to display the playfield graphic and plastics etc
Does not give any error, just simply does not show it, whether you toggle it on or off, no change.
This also seems to happen when you are going back and forth from running the table to editing quite a bit.

 

This is now a 'feature' actually, although i'm still unsure if i should keep it like that. If one plays a table via the command line, then these things are simply not loaded.

If one opens a table 'normally', this should not happen.

Here's what's happening:  In the global Properties, Physics pane, it seems that values changed there do not get saved out when they have been modified.  Notably it does not even "notice" that values there have changed, by prompting to save the modified table upon exiting.

 

I am mostly working with the first 3 values there, Gravity Constant, Playfield Friction, and Playfield Elasticity, and also sometimes make changes to the table slope, min and max.  Exporting and Importing seems to work, but the new imported values are not saved out with the table as they did in VPX Beta 6.  I have only tried some of the latest versions of VPX 7, so I'm not sure when it broke but the versions I have used are 4224 and the latest as of this writing, 4257.

 

Am I missing something, or is there some new procedure where physics aren't saved with tables in VPX 7 the same way they were with VPX 6?  Or, could this be a bug, perhaps?

 

Yup, bug that sneaked in via the UI rework, thanks for the report!

[fuzzel]

rev4274 is up:

 

- fix light blinking state handling

- fix multiselect issue where a value is assigned to all other selected elements just by selecting them

- fix problem with early-on error outputs (like dll not found)

- block input to layer panel if no table opened, avoid an empty panel if assigning an element to a layer with 'nothing' (=table only) selected, and filter ESC key in layer panel (as there is otherwise a hickup when changing a layer name and pressing this)

- fix potential crashes in "Save as" and "Export Blueprint" triggers

- fix import of POV

[fuzzel]

FYI: I just found another issue with the latest 4274: the light state combo box isn't updated with the correct state. So if you set the light state from on/off/blinking to something else the combo box will show the old state but the new state is updated. This bug is already fixed and comes with the next update.

[NailBuster]

fyi.  close issue still there with 4274.  can't use v10.7 version with frontend.

 

using -play xxx commandline

 

v10.6   close msg sent to vpx/editor while game is playing... closes everything fine.

 

v10.7  close msg sent to vpx/editor while game is playing... vpx dialog comes up "table changes made save yes/no?"  and keeps vpx editor exe open.

[wiesshund]

One other thing i have noticed, and there is no error or anything, is sometimes the editor will decide it does not want to display the playfield graphic and plastics etc
Does not give any error, just simply does not show it, whether you toggle it on or off, no change.
This also seems to happen when you are going back and forth from running the table to editing quite a bit.

 

This is now a 'feature' actually, although i'm still unsure if i should keep it like that. If one plays a table via the command line, then these things are simply not loaded.

If one opens a table 'normally', this should not happen.

 

Question.
Should said feature activate if you open from file/open, edit table, launch it, then come back to the editor to make changes?
Cause it doing that.

Also noticing another bug, but i do not for sure if it is VPN, or Ultra/FLexDMD.
If you are editing a table that uses ultradmd or flexdmd, and the DMD content is video rather than gif or png
If you go from editor to launching the table, and back to editor, if you do not save and exit and reopen before you launch again, the DMD will freeze
and VPX will not cleanly exit the table, pinmame stays running and everything.
Have to kill it in task manager 
I am not sure if the bug is VPX or ultra/flexDMD, but i do know that in 10.6 EXE it does not do this using exact same table.
Of course that could simply mean that the DMD's need updated to suit 10.7.xx, i am not sure
 

[Thalamus]

Stopping the controller properly on <table>_exit ?

Edited by Thalamus, 10 August 2020 - 04:28 AM.

[wiesshund]

Stopping the controller properly on <table>_exit ?

I wont claim that i am, i may well be doing it wrong since i havent really a clue what i am doing but, this is my table exit

 

' Table Exit 
Sub table1_Exit
    If Not UltraDMD is Nothing Then
        If UltraDMD.IsRendering Then
            UltraDMD.CancelRendering
        End If
        UltraDMD.Uninit
        UltraDMD = NULL
    End If
	If Not FlexDMD is Nothing Then FlexDMD.Run = False
Controller.Stop
End Sub

[Thalamus]

Looks to be ok. I recommend that you go to https://github.com/s...pxtable_scripts - press that green button and download zip. Get yourself a efficient search utility ( I use linux, so, I don't know what is best - maybe grepwin ) for text files and then you have a lot of code examples. I was mostly concerned that you've left out that exit routine completely. It is recommended to do what you've done.

[wiesshund]

Looks to be ok. I recommend that you go to https://github.com/s...pxtable_scripts - press that green button and download zip. Get yourself a efficient search utility ( I use linux, so, I don't know what is best - maybe grepwin ) for text files and then you have a lot of code examples. I was mostly concerned that you've left out that exit routine completely. It is recommended to do what you've done.

 

Astrogrep is what i use in windows, i will take a look at those tomorrow.
probably beats looking through bunches of tables randomly searching for what looks like the thing that did the thing i wanted to do, that turned out to be absolutely not the thing i wanted at all 

 

Issue may simply be that something in VPX is changing, to work better, and the DMD doesn't quite get it.
It almost acts like what you suspected, that it was not being shut down at table exit, or it is not flushing something out of itself or memory space etc.
You can launch and run the table for hours no problems at all, it is only when hopping in and out back and forth for editing.

You guys probably dont do it so much since you know what your doing when editing.
I do it lots cause im going by trial and error, to see what things do or how they work, right now i have just made it a habit to alt F S, alt F X
then reload, it only takes a second so no big deal.

Edited by wiesshund, 11 August 2020 - 08:33 AM.

[GInsonic]

The closing problem is not located in the scripts! I just tested, here are the result:

 

When you close VPX player (how in fact it should be closed) using the defined exit key (e.g. "Q") VPX closes flawlessly.

 

When you "close" it using ALT-F4 or TASKKILL command, the "save pending changes" message always appears. This is the difference to VPX 10.6, here VPX closes without any message regardless how you close it.

Frontends normally do not send a "Q", they try to close VPX forced, so this behaviour shows up immediately.

 

Maybe the VPX developers can give us a statement, what they think about it, since until now there was no reaction on mentioning the closing issue!

But I definitely emphasize, this is absolutely no offense guys, your outstanding work is really appreciated, it is only a quest for finding possible bugs in a beta version!

Edited by GInsonic, 11 August 2020 - 05:43 PM.