1790 replies to this topic

[wiesshund]

hmmmppf.. i guess this is the price for cleaning up some 15 year old todos..  ;-/

No good deed goes unpunished

[jsm174]

I built debug versions of both versions, and recreated the crash:

 

 Screen Shot 2021-04-08 at 8.40.48 PM.png   413.38KB   10 downloads

 

 Screen Shot 2021-04-08 at 8.44.15 PM.png   534.71KB   7 downloads

 

v3.4-165-c43e706 vs latest

[Joe]

hmmmppf.. i guess this is the price for cleaning up some 15 year old todos..  ;-/

15 year old any way to get it on the newer mame cores?

 

I think the old WPCmame stuff is still there.

[toxie]

@Joe: This is just some old chunk in the VPinMAME interfaces that was declared deprecated waaaaaay before my dev time. So nothing with the actual emulation cores.

I built debug versions of both versions, and recreated the crash:

 

Screen Shot 2021-04-08 at 8.40.48 PM.png

 

Screen Shot 2021-04-08 at 8.44.15 PM.png

 

v3.4-165-c43e706 vs latest

I guess we can just remove that version check anyway? This is also extreeeeeemely old.

[toxie]

I built debug versions of both versions, and recreated the crash:

 

Screen Shot 2021-04-08 at 8.40.48 PM.png

 

Screen Shot 2021-04-08 at 8.44.15 PM.png

 

v3.4-165-c43e706 vs latest

Is in the cmake builds MultiByte chars or Unicode chars used?

[jsm174]

I didn't explicitly put anything in the cmake files, however, by default it's multibyte:

 

 Screen Shot 2021-04-09 at 7.13.19 AM.png   207.28KB   6 downloads

 

 

[toxie]

Can you then please retry with the changes i did, and maybe also when removing that stone-old version check on your setup?

And does it happen for you both in debug and release?

[Thalamus]

Errr. You want me to test again with both all 4 ?? Am I right ? debug vs nodebug vs no sc vs sc - or was this addressed to jsm174 ?

[toxie]

To jsm174, at least until we know a bit more.. Thanks!

[jsm174]

So still a crash.

 

Reproducing steps:

 

1) VPinMAME-3.4-165-c43e706-win-x86

 

   a) Uninstall

   b) Reinstall

   c) Test

 

2) Build debug version of latest (currently0f35306)

(open visual studio developer command prompt)

git clone https://github.com/vpinball/pinmame
move pinmame pinmame_latest
cd pinmame_latest
copy cmake\vpinmame\CMakeLists_win-x86.txt CMakeLists.txt
cmake -G "Visual Studio 16 2019" -A Win32 -B build/vpinmame
cmake --build build/vpinmame --config Debug
copy cmake\instvpm\CMakeLists_win-x86.txt CMakeLists.txt
cmake -G "Visual Studio 16 2019" -A Win32 -B build/instvpm
cmake --build build/instvpm --config Debug
copy build\vpinmame\Debug\VPinMAME.dll build
copy build\instvpm\Debug\setup.exe build
copy ext\bass\Bass.dll build

3) launch build\setup.exe

 

4) without Install, click Test

 

 Screen Shot 2021-04-09 at 4.09.54 PM.png   537.15KB   7 downloads

 

 

FWIW, instead of doing step 4, and clicking Install first, clicking Test works. (Probably because newer function is there?)

Edited by jsm174, 09 April 2021 - 08:13 PM.

[wiesshund]

@Toxie

 

Want to know something bizarre?

 

vpinmame64 appears to do a bit better job of emulating the votrax in blackhole than 32bit

not perfect, but it is not going totally unintelligible after the 1st game.

 

not sure why, maybe something as silly as simply different memory addresses/maps simply dodging the issue partially

[toxie]

Interesting. Maybe really some missing init/reset somewhere.  :/

[wiesshund]

Interesting. Maybe really some missing init/reset somewhere.  :/

Not sure.

It is not perfect in 64bit, it still resembles a bad cap or lost ground after the 1st table play, but it is still understandable.

So issue still exists but for what ever reason the effect is greater in 32bit.
Dont suppose that could be at91jit, since this is an old non stern ROM.
Maybe just a bonus side effect of what a 64bit app does differently?

 

That aside, i temporarily have everything defaulted to run as 64bit.
It actually works good, so far seems very viable

It's latest build of VPX, vpinmame 3.4 from the github, recent build, freezys 1.9 r10, flexdmd 1.7.1, and b2s server just compiled as 64bit, no changes to existing code

so beta playing with a beta, playing with a beta, playing with a beta, with a beta. 
In other words, asking for trouble.

 

But i have been running stern roms, star trek, acdc, metallica, avengers, ironman, and williams bally DMD stuff

plus lots of old stuff

i have not had a crash, or a dmd go out of sync or anything, i left star trek run on auto play for over 3 hours, score was in the trillions when i stopped it
it was still perfectly in sync

 

might be that some of the improvements you have been making for other reasons have had an unexpected benefit of improving the 64bit?

 

Some things i can not test, like DOF or PUP, but so far i have like nothing at all to write down in the "little big list of stuff that doesnt work in 64bit"

 

Blackhole, heh i really wish i could say something that would make any sense codewise, as to what it is doing
but eveything i want to say entails grabbing a multi meter and a soldering iron and emulation does not work that way (it just sounds like it)

[toxie]

Neat, thanks for testing!

In theory there can be a bit of a perf improvement in general for 64bit apps, but it always depends on a lot of details.

[wiesshund]

Neat, thanks for testing!

In theory there can be a bit of a perf improvement in general for 64bit apps, but it always depends on a lot of details.

 

Heh think it benefits my laptop the most noticeable

but then again, it suffers the most, so anything is noticeable with it

[toxie]

 

So still a crash.

 

Reproducing steps:

 

1) VPinMAME-3.4-165-c43e706-win-x86

 

   a) Uninstall

   b) Reinstall

   c) Test

 

2) Build debug version of latest (currently0f35306)

(open visual studio developer command prompt)

git clone https://github.com/vpinball/pinmame
move pinmame pinmame_latest
cd pinmame_latest
copy cmake\vpinmame\CMakeLists_win-x86.txt CMakeLists.txt
cmake -G "Visual Studio 16 2019" -A Win32 -B build/vpinmame
cmake --build build/vpinmame --config Debug
copy cmake\instvpm\CMakeLists_win-x86.txt CMakeLists.txt
cmake -G "Visual Studio 16 2019" -A Win32 -B build/instvpm
cmake --build build/instvpm --config Debug
copy build\vpinmame\Debug\VPinMAME.dll build
copy build\instvpm\Debug\setup.exe build
copy ext\bass\Bass.dll build

3) launch build\setup.exe

 

4) without Install, click Test

 

Screen Shot 2021-04-09 at 4.09.54 PM.png

 

 

FWIW, instead of doing step 4, and clicking Install first, clicking Test works. (Probably because newer function is there?)

 

This behavior is 'okay' though. One needs to press Install due to the interface changes. It's just bad if one presses Install AND THEN it also crashes.

[Thalamus]

Seems our old friend Black Hole is still a bastard. First of all, this test is made with CP's 1.1 version, and I'm writing this here as I can't see it being anything by pinmame. So, the issue that I'm seeing is that after a boot, first time you play the game/load the rom it is just fine. If you exit and try again. You have a very high chance of needing to reboot. I say high chance because from my 7-8 rebooting I was able to play it the second time around twice, before the emulation got sick.

 

Sick in that sense that the flippers where delayed, sometimes my very much. I saw once that the ball didn't even get ejected. Sometime the flippers could feel fast and nice, but would all of a sudden manage to not even notice that I've released the flippers and stayed up/enabled. Pressing fast on the flipper, the could notice it and fall back, but, not always. Only way to fix it was reboot.

 

During my testing. I tried different versions of VP - 1.6.2 - 10.7.127 and a compile I did yesterday changing some constants for the nudge filter. Different version used as the "first one" after clean boot. No difference. After 6 reboots. Upgrade to pinmame created 3 days ago, currently latest "sc" 32bit. Setup via uninstall/install. No change. Reboot, and it would still working perfectly, first time around. Last time I was able to start the emulation twice before it got "sick". Decided to fire up a couple of other sys 80. Panthera and Incredible Hulk, when I was still in this Black Hole being sick situation, restarted those 3 times each, no issued with flippers.

 

So, to me it seems like a isolated problem to the title. What I have NOT tested yet. Is a different rom for that title. Only tried with blackhole7.

Edited by Thalamus, 13 April 2021 - 08:07 PM.

[wiesshund]

Seems our old friend Black Hole is still a bastard. 

 

I am unsure which table i have, author did not fill out table info (not even a little)

and the script only says

'==============================================================================================='
'																								' 			  	 
'											BlackHole	     									'
'          	              		         Gottlieb (1981)            	 	                    '
'		  				  	 http://www.ipdb.org/machine.cgi?id=307			                    '
'																								'
' 	  		 	 	  	            Created by: cyberpez		  			                    '    					 
'																								' 			  	 
'==============================================================================================='

ROM used is blkhole7
Rom Contents

 

DATA - for verification

 

With this backglass (in case it matters)

https://www.vpforums...s&showfile=8106

 

Not able to replicate sickness (except the votrax sickness), played, quit to editor, hit F5, repeated 16 times, but

 

Do you know which table download this is though?
I would like to test using same table you have and see if that table version gets sick.

 

not sure where mine came from, it was like one of if not the 1st vpx table i ever had

I do not think it is this one, as there are no references to DOF in the table script at all

https://www.vpforums...&showfile=12893

[Thalamus]

Have to hit the bed now. But I'll zip that all together for you for soon. Probably correct table - don't think it is the same db2.

Edited by Thalamus, 13 April 2021 - 11:46 PM.

[wiesshund]

Have to hit the bed now. But I'll zip that all together for you for soon.

 

I am thinking mine is probably really old
as it has a lot of vp921 references in it, but i do not remember when i got it from, possibly not from here
 

It may do no good, but never know, might find a difference between the two
that relates to the issue you are seeing.

 

Or not, it is black hole after all