1790 replies to this topic

[Thalamus]

Yes. I started testing this because of a update to the table, not released yet. Believe I've included everything that could be relevant except export of registry for that rom. But, I highly doubt that changes anything. I'm a bit surprised to learn that you don't see this on your end. I'm on Win7 64bit by the way. Don't think you need anything but the table and db2s to verify, but, now at least you've got options

 

Thanks for all the work you do - trying to improve vp and pinmame !

 

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

[wiesshund]

Yes. I started testing this because of a update to the table, not released yet. Believe I've included everything that could be relevant except export of registry for that rom. But, I highly doubt that changes anything. I'm a bit surprised to learn that you don't see this on your end. I'm on Win7 64bit by the way. Don't think you need anything but the table and db2s to verify, but, now at least you've got options

 

Thanks for all the work you do - trying to improve vp and pinmame !

 

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

 

Have not had a chance to run it yet, but i ran a diff
and we definitely do not have the same table.

What i ran and tested last night, and what you gave me are considerably different
Script wise

Physical table wise, i would have to hand compare i think, but the file sizes differ, with your table being smaller

not that that means anything at face value aside from simply meaning they are different

[wiesshund]

@Thalamus

 

I am up to 22 plays so far, no sickness yet
(they are slap chop 1 handed plays, but that probably does not matter?)

 

this is the script out of the table version that i have
you could try running it just to see if there is any change for you

 

https://drive.google...iew?usp=sharing

 

And we both already had the exact same vpm and vpx revisions

I am not sure what it might be getting hung up on causing the issue

im on the laptop so variety of hardware is about 0

 

I am doing it correct right?
I play a game, go back to editor, relaunch, play a game, go back to editor....

Edited by wiesshund, 14 April 2021 - 08:05 PM.

[Thalamus]

Yes. Well, if you exit table and start it again, that is when it becomes sick for me. Playing games in a row is not. Doesn't matter HOW you play. I can start the table after clean boot. Press the flippers like a mad man, they respond as intended. Exit, load table again and then it is broken.

I'll test with your script soon. Thanks - appreciated.

Edited by Thalamus, 14 April 2021 - 08:15 PM.

[wiesshund]

Yes. Well, if you exit table and start it again, that is when it becomes sick for me. Playing games in a row is not. Doesn't matter HOW you play. I can start the table after clean boot. Press the flippers like a mad man, they respond as intended. Exit, load table again and then it is broken.

I'll test with your script soon. Thanks - appreciated.

are you exiting entirely, or just quitting to editor?

 

if exiting out of vpx entirely, i will try it that way and see what happens

[Thalamus]

Your script didn't change the behavior. Right now. Not sure what to try next. But, I guess I'll just have to write that on the odd things list and reboot if for some reason I want to play it a second time around later in the day or something Thanks again for trying.

 

Update : Yes, all the way out of vpx, Load the table all from start again. Second time around, it might - in very few cases work still. Maybe 10-15 % or so ?? Wild guess really. Guaranteed to be fucked on the 3rd round though. Seems to NOT be a problem with the other two sys 80 I mention so it is a bit of a mystery. I would expect maybe those to have the same kind of sickness IF it was a code thing.

Edited by Thalamus, 14 April 2021 - 08:34 PM.

[wiesshund]

Your script didn't change the behavior. Right now. Not sure what to try next. But, I guess I'll just have to write that on the odd things list and reboot if for some reason I want to play it a second time around later in the day or something Thanks again for trying.

 

Update : Yes, all the way out of vpx, Load the table all from start again. Second time around, it might - in very few cases work still. Maybe 10-15 % or so ?? Wild guess really. Guaranteed to be fucked on the 3rd round though.

 

well, it is good to know that your script changes are not the cause

Can you try a different rom? maybe the 6 digit rom?

 

Something is hanging, just a question of what

[Thalamus]

Weird shit this. So, went downstairs again in order to test different version of the rom. Forgot that you can easily get different rom names from the script itself. Started that setup.exe to list the available. Crash. I had just the other day fix that. Updated to git upstream - registered and listed like we talked about. So, now it crashed again. Rebooted, tried setup.exe again. Still crashing. Shrug my shoulders, lets try a different rom, is the machine sick now already ? No, it wasn't change to one of the other roms, same symptoms. First game is just fine. Decided to change rom without booting. No, it is still sick. Reboot, new the next rom is tried - no testing of setup.exe before running table. Works just like the problem described again, or I should say. This time I was actually within the 10-15% so it started acting up on 3rd loading. setup.exe is still now crashing - I can't used the list function. I now always - uninstall / install, doesn't seem to help at all.

 

So, I don't see a way around it, and I've got no clue to why setup.exe all of a sudden is being a bastard either.

[wiesshund]

Weird shit this. So, went downstairs again in order to test different version of the rom. Forgot that you can easily get different rom names from the script itself. Started that setup.exe to list the available. Crash. I had just the other day fix that. Updated to git upstream - registered and listed like we talked about. So, now it crashed again. Rebooted, tried setup.exe again. Still crashing. Shrug my shoulders, lets try a different rom, is the machine sick now already ? No, it wasn't change to one of the other roms, same symptoms. First game is just fine. Decided to change rom without booting. No, it is still sick. Reboot, new the next rom is tried - no testing of setup.exe before running table. Works just like the problem described again, or I should say. This time I was actually within the 10-15% so it started acting up on 3rd loading. setup.exe is still now crashing - I can't used the list function. I now always - uninstall / install, doesn't seem to help at all.

 

So, I don't see a way around it, and I've got no clue to why setup.exe all of a sudden is being a bastard either.

 

Try this, just for giggles

 

Uninstall vpinmame from setup

Move or rename your existing vpinmame folder
export the pinmame registry, then delete it

Now unzip a new copy of pinmame into a new vpinmame folder

run setup and install it
toss blkhole7 rom in the roms folder, since it seems to be the most sickly
and try the table.
See if you can make it sick

 

If it still acts up, then at least out rules out any kind of corrupted config issue with pinmame

If it does still act up, could try swapping in pinmame 3.2 just to see if same issue happens

 

I think blkhole7 will start with no pre-existing nvrams
 

Edited by wiesshund, 14 April 2021 - 09:32 PM.

[Thalamus]

I'll consider that what you suggested, but, in the opposite direction. Too late tonight. And, I want to compare more to what happens on my desktop machine. I hate it when I don't understand why things happens.

Edited by Thalamus, 14 April 2021 - 11:08 PM.

[wiesshund]

I'll consider that what you suggested, but, in the opposite direction. Too late tonight.

Too late?

 

Do humans really sleep so much?

[Thalamus]

Timezones do come to play at times. 01:14 - up a around 05. Too many days in a row and you end up like a zombie on Friday for the first beer, sleeping on the couch. Been there, too often while mod Vpinball. Trying to change, but, well, just end up doing something else VP related - LOL.

[wiesshund]

Timezones do come to play at times. 01:14 - up a around 05. Too many days in a row and you end up like a zombie on Friday for the first beer, sleeping on the couch. Been there, too often while mod Vpinball. Trying to change, but, well, just end up doing something else VP related - LOL.

im up 18+ hours a day, whether i want to or not
i have no time zone (no time left to have one LOL)

[toxie]

Thanks guys for testing. So far i think there is some uninitialized mem with some Gottliebs and that then leads to different outcomes on different test setups?!

[wiesshund]

Thanks guys for testing. So far i think there is some uninitialized mem with some Gottliebs and that then leads to different outcomes on different test setups?!

 

Not sure.
I have 3 things here with which to run VPX on.
They all have the same software setup
VPX 10.7
VPinMAME 3.4
DMD_Extentions 
FlexDMD

But they are all 3 widely different in hardware

 

LAPTOP
I5 3230m

8gb generic ddr3 ram

integrated intel HD4000 graphics
1366x768 LCD
generic audio

 

Main Desktop
Ryzen 5 1500x @3.8ghz 4.0ghz boost
32gb DDR4 3800 ram
Radeon X580x
7.1 channel digital audio out

2560x1440 playfield, 1600x900 backglass

 

POSSIBLE MINICAB
AMD Athlon II X2 250
10gb DDR3 maybe pc3200? it ain't matched ram, that's for sure, unless mix N match counts

ATI Radeon HD4850

Realtek audio set up as 4 channel
720p screen @1280x768, backglass to be determined by what ever shows up free, not even sure on permanent playfield

All 3 have only standard drivers, no ASIO audio manipulators etc
All have the same windows 10 install and same VC++ installations
None have DOF so no directoutput loaded, no controller software loaded etc
None have a real DMD, so none of that loaded

 

all 3 have black hole though, same rom, table file, and backglass file, and i can not replicate the issue Thalamus is having
but i also can not replicate his set up either, so my results might not really mean anything.

[toxie]

At least you also found that blackhole behaves differently 32 vs 64bit.. So there is something with that machine (at least).. 

[wiesshund]

At least you also found that blackhole behaves differently 32 vs 64bit.. So there is something with that machine (at least).. 

Probably what you said there

different memory registers in 64bit
it is probably just barely squeaking past the problem since it still gets a sore throat.

 

But i have no way to run it properly so i can log exactly what it does the 1st time it plays the attract loop as opposed to what
it does after the game ends, and plays the game over explosion and then resumes playing the attract loop

I know i could compile a debugging version that would do that, but i haven't the remotest clue how to do so

[toxie]

No problem. I 'just' have to try to get some memory sanitizer running again with PinMAME and hopefully find something fishy.

[Thalamus]

Just as a added info. To remind you guys. I'm on Win7 64bit. I used an old setup.exe to list supported roms with. This works on my Win10 install still with the very latest on github right now. Just for laughs. And I kind of expected this, in that the dll changed, going back all the setup.exe I could find back to 2.6 - renaming them to just setup_list<ver>.exe - to see if I could use them to at least list the roms, there is now recently a no go area for me. I can not use recent vpinmame and get a listing.

 

I use that listing from time to time, so I just did a quick test - uninstalled upstream, went back to 33b and it works again.

 

Is it to the devs - interesting to know when this stops working on Win7 maybe ?

Edited by Thalamus, 15 April 2021 - 11:44 AM.

[Thalamus]

@toxie / @jsm174 : Interesting observation. Rebooted, and did the downgrade mentioned. Of course I had to re-test the mentioned issue, verifying that the list was working. 5 restart/exit of Black Hole with no issues at all. Have a feeling that this happens on Win7 and not Win10.