4027 replies to this topic

[skillman]

Doing a bit more research, I see that error code 0xE0434352 is a .NET exception code. The exception trace would be valuable, but I see from reading the source that the "failed to save minidump" means that MiniDumpWriteDump returned an error. So although a crash.dmp file is present, it must be incomplete, which would explain why every Windows debug tool I've tried fails to open the .dmp file.

 

Is there a quick how-to anywhere on building VPX from source? I'm not a Visual Studio guy, but I have access to it through an MSDN subscription, so I can give it a go. Looks like I can use the GetLastError to get the error code back from MiniDumpWriteDump to get some insight on why the dmp file is failing, and maybe at least fix _that_. 

 

Assuming the E0434352 code is pointing the finger at .NET, I assume that also points the finger at FlexDMD.

[wiesshund]

Doing a bit more research, I see that error code 0xE0434352 is a .NET exception code. The exception trace would be valuable, but I see from reading the source that the "failed to save minidump" means that MiniDumpWriteDump returned an error. So although a crash.dmp file is present, it must be incomplete, which would explain why every Windows debug tool I've tried fails to open the .dmp file.

 

Is there a quick how-to anywhere on building VPX from source? I'm not a Visual Studio guy, but I have access to it through an MSDN subscription, so I can give it a go. Looks like I can use the GetLastError to get the error code back from MiniDumpWriteDump to get some insight on why the dmp file is failing, and maybe at least fix _that_. 

 

Assuming the E0434352 code is pointing the finger at .NET, I assume that also points the finger at FlexDMD.

 

Simple elimination test

 

Disable flexDMD in the table script, see if it crashes?

Also, does flexDMDUI work?
Can you play demo scenes in it?

As for building VPX

well VS 2017 is free, dont even need a sub

 

I just pull from github, load the solution, and build

[skillman]

Thanks, I'll test out building VPX.

 

Disabling FlexDMD completely isn't yet an option for me - my table depends heavily on it and I don't have every use of it wrapped in a flag yet 

 

All other FlexDMD tables that I've tried work - the Flex demo table, Snake, and some of JPSalas' tables all work. FlexDMDUI works and reports no problems. And my table will run from anywhere from a few seconds to 10-15 minutes, using FlexDMD the whole time. Whatever is causing the crash, it's not consistent

[Thalamus]

I believe that the vpinmame thread has some info about installing vs - or was it just helping me getting over a few gotchas ? I know that gtxjoe wrote as small guide about it though a few years back and that is what I used initially to be able to compile on my end. Now, it is just very convenient to get the builds directly from github, so my few lines of code changes/test has been ignored for many versions on my end.

[wiesshund]

Thanks, I'll test out building VPX.

 

Disabling FlexDMD completely isn't yet an option for me - my table depends heavily on it and I don't have every use of it wrapped in a flag yet 

 

All other FlexDMD tables that I've tried work - the Flex demo table, Snake, and some of JPSalas' tables all work. FlexDMDUI works and reports no problems. And my table will run from anywhere from a few seconds to 10-15 minutes, using FlexDMD the whole time. Whatever is causing the crash, it's not consistent

 

Hmm
Seems it is a flexDMD crash then bringing VPX down with it
May have to reach out to vbousquet also

[ludovids]

The "failed to save minidump" error could be due to an out of memory condition.

 

I assume that the VPX source includes the Visual Studio project file. So just open that up in Visual Studio and see what other software it links to, such as a particular version of dotNet.

[skillman]

Thanks everyone for your help with my crashing issue. I believe I have it resolved, and it was, of course, my fault. The .NET clue pointed me at my interface with FlexDMD and after reanalyzing the code, I found a place where I was modifying the FlexDMD "Stage" without calling the lock/unlock methods first. It was a a call I didn't use very often - a call to clear the stage - so that's why the crashes were so sporadic - it had to be called just when FlexDMD was updating the display.

 

For anyone reading this who happens to just be learning FlexDMD, if you're struggling with anything, DM me - I've probably seen it!

[wiesshund]

Just reminding that analog nudge is still borked in 10.7

[dan_shane]

Just reminding that analog nudge is still borked in 10.7

 

Is it?  I'm running a RC version and my Pinscape nudge works fine.

[GlueSniffinEd]

 

Just reminding that analog nudge is still borked in 10.7

 

Is it?  I'm running a RC version and my Pinscape nudge works fine.

 

It is borked for me as well; RC 338 with Pinscape controller.  Very slight nudging left and right works'ish, but anything meaningful and it slams the ball hard North and many times induces a tilt.

Edited by GlueSniffinEd, 23 November 2021 - 03:35 PM.

[Halen]

Same here: It is borked for me as well; RC 338 with Pinscape controller.  Very slight nudging left and right works'ish, but anything meaningful and it slams the ball hard North and many times induces a tilt.

[wiesshund]

 

Just reminding that analog nudge is still borked in 10.7

 

Is it?  I'm running a RC version and my Pinscape nudge works fine.

 

 

If you are running anything within the last 20 builds i think you will find it is not working fine.

Open the nudge test table

Try and nudge ball sideways

ball only goes UP

 

Nudge it Realllllly hard

Ball only goes UP

 

Got a joystick?
Plug it in
Hold it to 1 side
All balls should slam into the side of the table right?
But they dont, in fact they do not continue to do anything, but they should due to the continued input
all they do is bump UP and come back.

 

Also, you have to increase the nudge a hell of a lot to get the balls to do anything

 

Now while the balls are not doing a damned thing you tell them to, look at the indicators on the apron
they are moving correctly, but the balls are definitely not

[TallaNasty312]

 

 

Just reminding that analog nudge is still borked in 10.7

 

Is it?  I'm running a RC version and my Pinscape nudge works fine.

 

 

If you are running anything within the last 20 builds i think you will find it is not working fine.

Open the nudge test table

Try and nudge ball sideways

ball only goes UP

 

Nudge it Realllllly hard

Ball only goes UP

 

Got a joystick?
Plug it in
Hold it to 1 side
All balls should slam into the side of the table right?
But they dont, in fact they do not continue to do anything, but they should due to the continued input
all they do is bump UP and come back.

 

Also, you have to increase the nudge a hell of a lot to get the balls to do anything

 

Now while the balls are not doing a damned thing you tell them to, look at the indicators on the apron
they are moving correctly, but the balls are definitely not

 

 

I second this man.

[dan_shane]

I'm glad I stuck with an older build then.  I rely on analog nudge when I hit those jet bumpers.

 

I appreciate the warning.

[wiesshund]

I'm glad I stuck with an older build then.  I rely on analog nudge when I hit those jet bumpers.

 

I appreciate the warning.

how old?

this issue goes a ways back

[Segovia11]

Dear forum,

                    increasing the nudge values in the Nudge Test and Calibrate Table script will improve the nudge force.

 

Sub Table_Keydown(ByVal Keycode)

 

If Keycode = LeftTiltKey Then

   Nudge90, 100

End If

 

If Keycode = RightTiltKey Then

   Nudge270, 100

End If

 

If Keycode = CentreTiltKey Then

   Nudge0, 100

End If

   

End Sub

 

The catapult force is very strong with the values above.  I have just tested the values above & it's working perfectly fine in the latest 10.7 revision.

 

[gtxjoe]

That only applies to button key nudges. The others are talking about analog nudge with an accelerometer like Pinscape/kl25z

[wiesshund]

 

Dear forum,

                    increasing the nudge values in the Nudge Test and Calibrate Table script will improve the nudge force.

 

Sub Table_Keydown(ByVal Keycode)

 

If Keycode = LeftTiltKey Then

   Nudge90, 100

End If

 

If Keycode = RightTiltKey Then

   Nudge270, 100

End If

 

If Keycode = CentreTiltKey Then

   Nudge0, 100

End If

   

End Sub

 

The catapult force is very strong with the values above.  I have just tested the values above & it's working perfectly fine in the latest 10.7 revision.

 

 

Aber das ist nicht analog, es ist digital

[Segovia11]

hoppla,

            danke shen !

 

   

Edited by Segovia11, 24 November 2021 - 11:18 PM.

[dan_shane]

 

I'm glad I stuck with an older build then.  I rely on analog nudge when I hit those jet bumpers.

 

I appreciate the warning.

how old?

this issue goes a ways back

 

 

Rev270rc

 

Have there been substantial new features since that rev that I'm missing?  270rc seems to work well with all of my VPX tables, so I've been content to stick with it.