616 replies to this topic

[toxie]

If we can sort out the closing crash, too, i guess its time for a 10.3.1 bugfix release.. 

[jpsalas]

Here it crashed again while selecting with the mouse. It had worked fine mostly all the day.

 

https://app.box.com/...lsk0t8zmpa391df

 

JP

[toxie]

Thanks!

 

@Fuzzel: I fear this is also one for your expertise again, as it seems like m_pvsel was deleted while UpdatePropertyPanes was called for one of its elements.. (propbrowser.cpp line 354ff)

[fuzzel]

Ok here is another build with debug information. I tried to improve the critical section handling. So give it another test please 

Edited by fuzzel, 26 June 2017 - 09:10 AM.

[jpsalas]

Thanks, I'll give it a try.

[jpsalas]

This error came quite quickly. After playing with a table for about 10 minutes, I simply clicked the playfield with the mouse pointer. I did play the table a few times, making small adjustments in some of the lights, and I run the table to check the results. The crash was while in the editor not when running the simulation.

 

https://app.box.com/...dvxhetjzbq7jme4

 

JP

 

PS: Maybe this was my fault, I had an open vpt file in the vp994 editor. I know this has caused problems before (to have both open the VPX and one of the older VP9 editors)

Edited by jpsalas, 25 June 2017 - 12:57 PM.

[toxie]

Still, this should not happen.. Weird.. Thanks for all the reports!!

[fuzzel]

Well I'm not 100% sure if it's really ok to run VP9 besides VPX. All the COM madness that we use in VP can cause unpredictable issues. VP9 and VPX uses the same GUIDs when registering against the COM interface. So it's better to run VPX without VP9 in parallel.

[jpsalas]

Yes, that's what I have learned But I didn't know I had the Vp9 open while I was editing with VPX. I haven't used the editor very much this evening. I guess I'll have more time tomorrow.

[jpsalas]

Ok, here it is another crash. This time there was no VP9 editor open

 

I simply clicked on the table menu when it crashed. I had two tables loaded (the idea was to copy/paste the table rules for the table info)

 

https://app.box.com/...nvgh9dn9nbz084a

[randr]

I had on crash tonight but was not running the version you upped for debugging. I'll make sure I run that one next time

[jpsalas]

Here it is another crash with the latest debug version. But this time it is running under Windows 7, using a build in Intel graphics 4000, and running under RDP (remote desktop), I'm at work

The dump was very small. The crash was produced after selecting several objects and delete them.

 

[fuzzel]

Ok I fixed the problem loading multiple tables. I will upload another test build later...

[Brer Frog]

I know there is a VPX 10.3 all-in-one installer and also a 10.3 stand alone version.

Also the last couple of new VPX tables that I downloaded had a message saying they were saved with version 10.30 and is newer than the supported version 10.21 and I might have problems playing it.

But I see this VP 10.3 beta thread is still active & changes are still occurring.

Is it recommended to get the VP 10.3 update or am I better off keeping VP 10.21?

[fuzzel]

VPX 10.3.0 is released and you can use it playing tables with it. However the released version has issues when you build tables with it and we are trying to fix these and release an update soon (10.3.1)

[vogliadicane]

not sure, if this is a bug:

Open material manager and change something (e.g. colors)

Do not close material manager window and start table to see changes.

stop simulation (Q Q)

change again some color in the still open material manager

 

From here on some weired stuff happens. After all the iputs are either not correct (in my case resulted in other colors than I chose) or some other (probably always the first one) not highlighted material is affected... Can't explain better.

 

Everything is ok, if you click ok before starting the table. Maybe that's, how it is meant to be used don't know, just wanted to report my observation.

[Brer Frog]

VPX 10.3.0 is released and you can use it playing tables with it. However the released version has issues when you build tables with it and we are trying to fix these and release an update soon (10.3.1)

Thank you.

I will get the update.

[fuzzel]

So here is another test version. It should fix the crashing if you try to load more than one table. 

 

@JP: both crashes you reported seems to have to do with this fix. So hopefully that is solved now

 

not sure, if this is a bug:

Open material manager and change something (e.g. colors)

Do not close material manager window and start table to see changes.

stop simulation (Q Q)

change again some color in the still open material manager

 

From here on some weired stuff happens. After all the iputs are either not correct (in my case resulted in other colors than I chose) or some other (probably always the first one) not highlighted material is affected... Can't explain better.

 

Everything is ok, if you click ok before starting the table. Maybe that's, how it is meant to be used don't know, just wanted to report my observation.

Thanks for the info. I didn't know this but actually it's not a surprise. The non modal dialogs (image, material, sound manager) are not prepared to work that way. It has something do to with the internal data management. Every VP table is saved (backup) when you start to play it and the backup is loaded back into the editor after you quit the player. I guess there is some synchronization missing after the backup is restored

Attached Files

•  vpinballx_dbg_rev3112.rar   5MB   25 downloads

[BorgDog]

If you are going to put out a bug fix, can you squeeze in an option to turn off the fancy "navigating around the table with the arrow keys (and left alt key)" or make an option to change the keys to something besides arrows?  My cab uses arrows for other things and it basically makes the camera mode useless now. And yes I consider this a bug.

[toxie]

Indeed. I added a checkbox to the keys dialog.