1488 replies to this topic

[lukpcn]

My just closed during playing the table

[Umpa]

I noticed in the scripts folder a lot of the files are dated 7/29/2018 in version 10.5 but in the the latest Beta 10.6 the same files are dated 3/5/2018. So is this correct install these older scripts with 10.6? Thanks.

Sent from my SAMSUNG-SM-G935A using Tapatalk

[Carny_Priest]

Yes, it's safe to overwrite all scripts.. Official releases such as all-in-one installer tend to use date of release as a datestamp. Betas use last date modified as datestamp. The fact that the datestamp is older just means that the file has not been modified during the beta cycle. Same content. Always backup, though!

[Umpa]

Yes, it's safe to overwrite all scripts.. Official releases such as all-in-one installer tend to use date of release as a datestamp. Betas use last date modified as datestamp. The fact that the datestamp is older just means that the file has not been modified during the beta cycle. Same content. Always backup, though!

Thank you!

Sent from my SAMSUNG-SM-G935A using Tapatalk

[Rajo Joey]

@toxie: that error happened after playing a table, ESC Q, then the VPX editor closed automatically. No error was displayed on the screen.

That happened to me with different Tables in the last days. Thought it was a error with my PC.

Gesendet von meinem SGP512 mit Tapatalk

[scutters]

Thanks for all the dev work going on (most of which is way over my head!).. I do have what i think is one small request;

 

When exporting a pov can the 'Save as' dialogue auto/pre populate the filename field with the current table name?.. Yes i really am that lazy typing, especially with the mini keyboard!

[Thalamus]

FYI : POV can be extracted easily with the filenames intact today via the cmd prompt. I basically make a wrapper to extract table scripts ( same thing - just and option change )

 

See what pov exists - see what tables exists - for tables that pov doens't exists already - run a loop and extract - done.

Edited by Thalamus, 01 February 2019 - 08:21 AM.

[Thalamus]

Second crash : same table. Same computer Not hitting anything special, feeze. Sound and flippers came back for a small period of time 1-2 sec ? Then total freeze and crash.

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

 

 

Just tell me if you want the table too.

 

Deleted after seeing Fuzzel explaining first line in call stack needs to be VPinballX.

Edited by Thalamus, 13 February 2019 - 01:39 PM.

[toxie]

Is that a new thing for you guys? Since roughly which revision are the crashes happening? (and thanks for the reports!!)

[Thalamus]

Yes. I haven't crashed in a very long time except for one post that is in this thread already. But, I don't think it is related. Fuzzel told me it looked to be related to USB and it was a modded CV with two DMD's running. Guessing now, but, have a feeling it is Freezy "slowdown" related so I don't want to put too much into it.

 

Since then I've played hours upon hours without any problems on the cab. I must admit. Still haven't played much on the cab with this latest release though, and the computer I'm getting crashes on isn't the most powerful. But, then again. It has been very stable on previous releases.

[jpsalas]

The latest revision crashes in places were the old revisions never did. The old revisions crashed when opening several tables, do some editing, copy/paste, then the editor could freeze and crash. That was ok for me, just like when you open a VP9 table in VP9 and you had VPX open at the same time. The VPX used to crash. But the latest revision crashes in new ways: run a table, quit and crash, or run a table and suddenly VPX quits and crash. These kind of crashes are new to the latest revision. These are the ones reported in the latest posts.

[jpsalas]

Here it is an example of a crash while playing. VPX rev 3608 simply crashed and closed.

 

Crash report VPX rev3608-while playing.ZIP

 

JP

 

 

[tss]

Ghostbusters (LE) (Stern 2016) doesn't even load with VPX rev3608
It works fine with rev3592

[Thalamus]

@tss : It works for me. Not that it is super important but bass.dll is updated in VP and VPM since then. You probably should update the one in VPinSPA.

My VPinSPA md5sum is A381B6C6A53ED5F92BC601D8043FBE6F

Edited by Thalamus, 03 February 2019 - 12:32 PM.

[Carny_Priest]

VPinSPA works with rev3608 for me too. No change in bass.dll within the VPinSPA folder.

[fripounet]

bug with 3608

 

1er message :  after

 

2e message :  and afterward closing vpx (((

[Thalamus]

@fripounet : That error is probably related to this https://www.vpforums...=41180&p=422067 - said it will be fixed in the next version.

Edited by Thalamus, 03 February 2019 - 03:04 PM.

[fuzzel]

rev3618 is up:

 

- check for null pointer (crash reported from jpsalas)

- fix SMAA crash

[Ben Logan]

Thanks for all your work fuzzel and toxie. Also, thanks to Thalamus, JP, Carny and other community members for so consistently testing and reporting crash results / successes on bleeding edge builds. I've been out of the loop with recent builds lately. Hope to show up for testing more frequently in near future.

Edited by Ben Logan, 03 February 2019 - 08:15 PM.

[xenonph]

Thanks again Toxie and Fuzzel!!

Spending your personal time helping the community and catering to our needs.

I am sure this work is not easy, and the only pay you get, is a very thankful community.

And it seems like the work never stops for you guys, as there is always new requests.

This has got to be stressfull, trying to accomodate each request, and making sure it doesn't break what you guys have already so masterfully put together.

You both go above and beyond, when it comes to helping this pinball community.

It is appreciated!!!

Thanks again for fixing the DT lights!!

Carry on.