740 replies to this topic

[shadowjuggalo]

I just had a question, with these new vpx versions they dont do anything to the tables already made correct? The table has to be made with the new features in the table already correct?  Meaning if I have all the tables I want and they play and they play there is no reason I should upgrade any further.

[sliderpoint]

I've  been getting alot of crashes in the editor in the last few builds.  Since you made an official thread, I thought I would post a dump and see you can find where it's coming from.

 

https://www.dropbox..../crash.zip?dl=0

 

Thanks

-Mike

[wrd1972]

The tables like Flash Gordon and Bug Bunny do have nice saucer physics. But it took some tedious hacks and a tone of T&E to get the effect as good as it is. Would be nice if the kicker object itself could be tweaked to provide the effect.

[DJRobX]

I rarely crash when I just have VPX open and nothing else.  If I open Vp9 at the same time (in my case because I was converting a VP9 table), I crash often. 

 

I've  been getting alot of crashes in the editor in the last few builds.  Since you made an official thread, I thought I would post a dump and see you can find where it's coming from.

 

https://www.dropbox..../crash.zip?dl=0

 

Thanks

-Mike

 

The call stack doesn't give any hints.   Would need the matching PDB from this build to make use of the dump.

Edited by DJRobX, 09 August 2017 - 01:56 AM.

[sliderpoint]

What is PDB?  is that something I can provide? or is it cool dev code stuff?

[RustyCardores]

I rarely crash when I just have VPX open and nothing else.  If I open Vp9 at the same time (in my case because I was converting a VP9 table), I crash often. 

 

I've  been getting alot of crashes in the editor in the last few builds.  Since you made an official thread, I thought I would post a dump and see you can find where it's coming from.

 

https://www.dropbox..../crash.zip?dl=0

 

Thanks

-Mike

 

The call stack doesn't give any hints.   Would need the matching PDB from this build to make use of the dump.

 

As I mentioned to you previously Rob, I too have been getting a lot of crashes while editing. For me it seems to be if I go too fast from "save" to "play" it will hang on loading. 

Edited by RustyCardores, 09 August 2017 - 01:59 AM.

[hauntfreaks]

only crashes i'm getting is still having more than one table open and closing one.... this only happens after tinkering in the editor for a while....

[randr]

Bill does great  physics his handle is rothbe...(sp) raised playfield is key otherwise the ball never not goes in. with a raised playfield it can swirl and miss

[jimmyfingers]

The kicker / saucer object needs to be revisited as to it's physics and have it behave closer to a real one without hacks like raising the playfield.  Really it should just be a minus / lowering deal for just that object and the ability to "punch through" or create objects and system / below the playfield accomplished without raising everything else up.

 

Biggest detriment of the raised playfield building style is that tables that do this method forego the playfield reflections of objects (including the ball itself) when they use a wall to raise and build everything else around that.  The playfield reflection of objects is one of the best things to come to VP / VPX and going in a direction that fails to take advantage of that / loses this option is not ideal.    

[BorgDog]

I get a lot of crashes if I'm working on a table that is stored on a synced folder, within something like a onedrive or google drive, or  dropbox or whatever.  If I remember to turn that syncing off while I'm working I seem to have less issues but still occasionally do.

[DJRobX]

What is PDB?  is that something I can provide? or is it cool dev code stuff?

 

Program DataBase.  It's generated by Visual Studio alongside the .EXE when built.   It contains the data which translates the memory addresses you see.  So in this case, your crash shows:

 

004FF529 vpinballx.exe (0xFFFFFFFF80010000 0x0019D6B0 0x00000000 0x00000001)

004FFDAE vpinballx.exe (0x001D0902 0x01640008 0x01645188 0x203bf98c)

762FE1F7 GDI32.dll ScriptShape + 0x127 (0x28EC810C 0x56000004 0x01113D57 0xffffffff870f0000)

458BF0E4  (0x56000004 0x01113D57 0xFFFFFFFF870F0000 0x00000513)

28EC810C  (0x01113D57 0xFFFFFFFF870F0000 0x00000513 0xffffffffe8837874)

56000004  (0xFFFFFFFF870F0000 0x00000513 0xFFFFFFFFE8837874 0xffffffffeb840f02)

01113D57 vpinballx.exe (0x00000513 0xFFFFFFFFE8837874 0xFFFFFFFFEB840F02 0x2d000005)

 

870F0000  (0xFFFFFFFFE8837874 0xFFFFFFFFEB840F02 0x2D000005 0x0000010e)

 

The numbers on the left in bold should reference blocks of code in VP.    So in order to get a clue what caused your crash we really want to know what function 004FF529 is in.   The PDB has that info.   If you have the correct source plus the PDB and the crash dmp file, you can actually fire up the Visual Studio debugger and somewhat inspect the state of things. 

 

ScriptShape has  something to do with unicode text.  But it seems like it's probably a red herring, I don't think it it has a callback function (it shouldn't be in the middle of a stack trace).   

[hauntfreaks]

this is what inside my head feels like right now          

[toxie]

I just had a question, with these new vpx versions they dont do anything to the tables already made correct? The table has to be made with the new features in the table already correct?  Meaning if I have all the tables I want and they play and they play there is no reason I should upgrade any further.

 

in principle, yes.. sometimes there are some features though, like now the surround sound option that will provide benefit apart from that (e.g. no two soundcards necessary anymore)..

[fuzzel]

What is PDB?  is that something I can provide? or is it cool dev code stuff?

 
Program DataBase.  It's generated by Visual Studio alongside the .EXE when built.   It contains the data which translates the memory addresses you see.  So in this case, your crash shows:
 
004FF529 vpinballx.exe (0xFFFFFFFF80010000 0x0019D6B0 0x00000000 0x00000001)
004FFDAE vpinballx.exe (0x001D0902 0x01640008 0x01645188 0x203bf98c)
762FE1F7 GDI32.dll ScriptShape + 0x127 (0x28EC810C 0x56000004 0x01113D57 0xffffffff870f0000)
458BF0E4  (0x56000004 0x01113D57 0xFFFFFFFF870F0000 0x00000513)
28EC810C  (0x01113D57 0xFFFFFFFF870F0000 0x00000513 0xffffffffe8837874)
56000004  (0xFFFFFFFF870F0000 0x00000513 0xFFFFFFFFE8837874 0xffffffffeb840f02)
01113D57 vpinballx.exe (0x00000513 0xFFFFFFFFE8837874 0xFFFFFFFFEB840F02 0x2d000005)
 
870F0000  (0xFFFFFFFFE8837874 0xFFFFFFFFEB840F02 0x2D000005 0x0000010e)
 
The numbers on the left in bold should reference blocks of code in VP.    So in order to get a clue what caused your crash we really want to know what function 004FF529 is in.   The PDB has that info.   If you have the correct source plus the PDB and the crash dmp file, you can actually fire up the Visual Studio debugger and somewhat inspect the state of things. 
 
ScriptShape has  something to do with unicode text.  But it seems like it's probably a red herring, I don't think it it has a callback function (it shouldn't be in the middle of a stack trace).   

You don't really need the pdb file. Just compile the revision with debug info. Start VP in the debugger and pause the app then jump to the given address.

[lizard]

 

Great stuff Thanks, looking forward to testing the sound options i have had a 5.1 sound system in my cab for 6 years only using the fronts for the backbox speakers. Will have to dig out the other speakers and plug them in and have a bit of a play.

 

Cheers

 

note that a table also has to use this functionality in order to have the effect. the default table in VP has it implemented, and also the world cup soccer 94 table to my knowledge..

in the future, hopefully a lot more authors will do the support for it, especially as its super simple to do (not more complicated then not doing it, actually, just take a look at the new helper functions in the default table script)..

'*********************************************************************
'                 Positional Sound Playback Functions
'*********************************************************************

' Play a sound, depending on the X,Y position of the table element (especially cool for surround speaker setups, otherwise stereo panning only)
' parameters (defaults): loopcount (1), volume (1), randompitch (0), pitch (0), useexisting (0), restart (1))
' Note that this will not work (currently) for walls/slingshots as these do not feature a simple, single X,Y position
Sub PlayXYSound(soundname, tableobj, loopcount, volume, randompitch, pitch, useexisting, restart)
	PlaySound soundname, loopcount, volume, AudioPan(tableobj), randompitch, pitch, useexisting, restart, AudioFade(tableobj)
End Sub

' Similar subroutines that are less complicated to use (e.g. simply use standard parameters for the PlaySound call)
Sub PlaySoundAt(soundname, tableobj)
    PlaySound soundname, 1, 1, AudioPan(tableobj), 0,0,0, 1, AudioFade(tableobj)
End Sub

Sub PlaySoundAtBall(soundname)
    PlaySoundAt soundname, ActiveBall
End Sub

Thanks for the info i will look at adding it to one of my tables.

[toxie]

 

 

What is PDB?  is that something I can provide? or is it cool dev code stuff?

 
Program DataBase.  It's generated by Visual Studio alongside the .EXE when built.   It contains the data which translates the memory addresses you see.  So in this case, your crash shows:
 
004FF529 vpinballx.exe (0xFFFFFFFF80010000 0x0019D6B0 0x00000000 0x00000001)
004FFDAE vpinballx.exe (0x001D0902 0x01640008 0x01645188 0x203bf98c)
762FE1F7 GDI32.dll ScriptShape + 0x127 (0x28EC810C 0x56000004 0x01113D57 0xffffffff870f0000)
458BF0E4  (0x56000004 0x01113D57 0xFFFFFFFF870F0000 0x00000513)
28EC810C  (0x01113D57 0xFFFFFFFF870F0000 0x00000513 0xffffffffe8837874)
56000004  (0xFFFFFFFF870F0000 0x00000513 0xFFFFFFFFE8837874 0xffffffffeb840f02)
01113D57 vpinballx.exe (0x00000513 0xFFFFFFFFE8837874 0xFFFFFFFFEB840F02 0x2d000005)
 
870F0000  (0xFFFFFFFFE8837874 0xFFFFFFFFEB840F02 0x2D000005 0x0000010e)
 
The numbers on the left in bold should reference blocks of code in VP.    So in order to get a clue what caused your crash we really want to know what function 004FF529 is in.   The PDB has that info.   If you have the correct source plus the PDB and the crash dmp file, you can actually fire up the Visual Studio debugger and somewhat inspect the state of things. 
 
ScriptShape has  something to do with unicode text.  But it seems like it's probably a red herring, I don't think it it has a callback function (it shouldn't be in the middle of a stack trace).   

You don't really need the pdb file. Just compile the revision with debug info. Start VP in the debugger and pause the app then jump to the given address.

 

 

Plus, you need to compile with the same compiler version! (i think 2013 in your case, right?)

[fuzzel]

Yes visual studio 2013

[sliderpoint]

 

What is PDB?  is that something I can provide? or is it cool dev code stuff?

 

Program DataBase.  It's generated by Visual Studio alongside the .EXE when built.   It contains the data which translates the memory addresses you see.  So in this case, your crash shows:

 

004FF529 vpinballx.exe (0xFFFFFFFF80010000 0x0019D6B0 0x00000000 0x00000001)

004FFDAE vpinballx.exe (0x001D0902 0x01640008 0x01645188 0x203bf98c)

762FE1F7 GDI32.dll ScriptShape + 0x127 (0x28EC810C 0x56000004 0x01113D57 0xffffffff870f0000)

458BF0E4  (0x56000004 0x01113D57 0xFFFFFFFF870F0000 0x00000513)

28EC810C  (0x01113D57 0xFFFFFFFF870F0000 0x00000513 0xffffffffe8837874)

56000004  (0xFFFFFFFF870F0000 0x00000513 0xFFFFFFFFE8837874 0xffffffffeb840f02)

01113D57 vpinballx.exe (0x00000513 0xFFFFFFFFE8837874 0xFFFFFFFFEB840F02 0x2d000005)

 

870F0000  (0xFFFFFFFFE8837874 0xFFFFFFFFEB840F02 0x2D000005 0x0000010e)

 

The numbers on the left in bold should reference blocks of code in VP.    So in order to get a clue what caused your crash we really want to know what function 004FF529 is in.   The PDB has that info.   If you have the correct source plus the PDB and the crash dmp file, you can actually fire up the Visual Studio debugger and somewhat inspect the state of things. 

 

ScriptShape has  something to do with unicode text.  But it seems like it's probably a red herring, I don't think it it has a callback function (it shouldn't be in the middle of a stack trace).   

 

 

So I get quite a few, should I be looking for a pattern in the call stack?  The ones I'm checking all seem different.  Or will those addresses be different each time VP is run?

-Mike

[DJRobX]

 

So I get quite a few, should I be looking for a pattern in the call stack?  The ones I'm checking all seem different.  Or will those addresses be different each time VP is run?

-Mike

 

 

If it's the same crash the stacks should look similar, or at least have some commonality to them.  The addresses shouldn't change. 

[fuzzel]

The crash happens in propbrowser.cpp line 860 m_pvsel seems to be NULL. I've already fixed the null pointer access and it will be available in the next build.