2585 replies to this topic

[hauntfreaks]

wow, thanks dozer, JD looks so great and I have not experienced any slowdown.  Was able to get 3 balls locked, but failed to get multiball.  Cool game and can't wait to log more time on it.

 

I've gotten to the crazy mutiball stage with no slow down at all... also no problem with AMH, Kingpin, or TFTC....

 

i5 4.2 16gb gtx760 4gb

[Kaan]

That's the thing, your system is very powerful. The problems show up(at least it is very obvious for me since I see these problems when I underclock cpu) once you go down in cpu speeds then you start to notice hangs, and drops in fps. I don't know, it seems to me that with some tables the VPX system requirements are way too high(and it is not the graphical enhancements, since nothing helps even if you change or disable stuff only messing with the code or timers help). We are talking about hardwares that can run triple A games with ease yet they have trouble with vpx. Top hardware requirements for pinball seems wrong to me, and I'm trully sorry if I offended anyone by saying these things. I may be completely off my base here, and probably are. These are just my opinions on what I've gathered by my experience and others. Not blaming anyone, especially not the authors. I only voice my concers because I care about these things too much.

Edited by Kaan, 31 August 2015 - 09:37 PM.

[ScottyVH]

Is there a backglass for Mopar Madness?  Where can I find it?

[Dozer316]

Dozer, do you have any timer set to 1 that's doing a lot of work?  I'm only sharing my experience with AMH.  Remember, VPX's timers run at 1 MHz where as VP9's timers run at 100 Hz (even if you set them to 1; setting a VP9 to 10 and another timer to 1 is the same thing).  I just know that I had a timer set to 1 that did a lot of code that was causing Kaan's slow down.  Once I adjusted things to have the timer run at 10, it fixed his issues.  And my machine was running fairly smooth (not butter smooth, maybe like velour?) prior to the timer adjust (that's on a 4 year old AMD A6 and a 4 year old $50 video card).

Yeah, I'm having the slowdown on AMH on attract mode, when it loads, but as soon as you play the game it's fine. It doesn't really bother me, but I'd like to know why it's happening. 

Does it happen, say, a minute after it loads (but still in attract mode)?  Does hit happen after a game is done and it goes back to attract mode?

 

Heya Shoopity, well I have a couple of timers running set to 1 including the pinmame timer.

 

However, 1 is for a VUK ball animation and only runs for about a second when the VUK fires and the other monitors the deadworld position.  

 

The code in the planet_watch timer is as follows.

Sub Planet_Watch_Timer()
If jdbp = 1 AND Nipple.RotY >= 220 AND Nipple.RotY <=250 AND bout1 = 0 AND magon = 1 AND DeadWorld.enabled = FALSE Then
CX_action = 1:Crane_X.enabled = 1:me.enabled = 0
End If
If jdbp1 = 1 AND Nipple.RotY >= 320 AND Nipple.RotY <=360 AND bout1 = 0 AND magon = 1 AND DeadWorld.enabled = FALSE Then
CX_action = 1:Crane_X.enabled = 1:me.enabled = 0
End If
If jdbp2 = 1 AND Nipple.RotY >= 100 AND Nipple.RotY <=130 AND bout1 = 0 AND magon = 1 AND DeadWorld.enabled = FALSE Then
CX_action = 1:Crane_X.enabled = 1:me.enabled = 0
End If

If jdbp = 0 AND Nipple.RotY >= 220 AND Nipple.RotY <=250 AND bout1 = 0 AND magon = 1 AND DeadWorld.enabled = FALSE Then
CX2_action = 1:Crane2_X.enabled = 1:me.enabled = 0
End If
If jdbp1 = 0 AND Nipple.RotY >= 320 AND Nipple.RotY <=360 AND bout1 = 0 AND magon = 1 AND DeadWorld.enabled = FALSE Then
CX2_action = 1:Crane2_X.enabled = 1:me.enabled = 0
End If
If jdbp2 = 0 AND Nipple.RotY >= 100 AND Nipple.RotY <=130 AND bout1 = 0 AND magon = 1 AND DeadWorld.enabled = FALSE Then
CX2_action = 1:Crane2_X.enabled = 1:me.enabled = 0
End If
End Sub

So it doesn't look too heavy to me but maybe it is? - The thing that I find weird is that the people with problems are getting 5 FPS?

 

Even with super high resolution timer intervals and the above code, do you think this would be enough to bog the CPU down to that extent?

 

It is a weird issue.

[Pinhead45]

 

Yeah, I'm having the slowdown on AMH on attract mode, when it loads, but as soon as you play the game it's fine. It doesn't really bother me, but I'd like to know why it's happening. 

Does it happen, say, a minute after it loads (but still in attract mode)?  Does hit happen after a game is done and it goes back to attract mode?

No it just happens on attract mode when it first opens. I checked it's getting 4.9 FPS. Then when I play the game it's fine, I'm getting 75 fps. When the game is over attract mode runs fine. I checked also if I close out the game go to the editor and restart the attract mode it's fine, but if I close the editor reload the editor and start a game I go back to the 4.9 fps attract mode.

[ClarkKent]

That's exactly what happens here, too. It's totally weird that fps always get down to 4.8 fps - and it's weird that starting VPX again and loading the table again it stays that way. Only a restart of the computer solves this until it happens again.

 

The starting point with the timers appear very reasonable to me. Sometimes this also happens in KingPin and I think it's the same problem.

[Dozer316]

That's exactly what happens here, too. It's totally weird that fps always get down to 4.8 fps - and it's weird that starting VPX again and loading the table again it stays that way. Only a restart of the computer solves this until it happens again.

 

The starting point with the timers appear very reasonable to me. Sometimes this also happens in KingPin and I think it's the same problem.

I might be missing something here but I can't see how the duty cycle of a timer is going to require a reset of the computer to achieve stable frame rates again.  As I said, I could be wrong but I'm guessing it's something else.

[StevOz]

http://www.vpforums....?showuser=84951

 

Any news on that front?

[chepas]

Ok I just got round to adding JD to my database. I thought I'd just capture the process with PinXCheck to show how simple it is.

 

I had a better play after this capture and whilst there's nothing wrong with the frame rate, it's way too fast in places. Like the upper left flipper shot > around the orbit (Wall60). You don't have any friction set. You might want to think about adding some to tame her a bit, especially there, because it's REALLY fast.

 

[Slydog43]

I didn't want to say anything, but the ball does seem to travel too fast at a few spots in the game.  Upper left as chepas stated, and I think in front of the slings some times it seems like the ball accelerates too quickly up/down.  Just doesn't feel right.  Must be a friction or ramp/wall/rubber thing.  Great table though, very close.

Edited by Slydog43, 01 September 2015 - 11:20 AM.

[ClarkKent]

 

That's exactly what happens here, too. It's totally weird that fps always get down to 4.8 fps - and it's weird that starting VPX again and loading the table again it stays that way. Only a restart of the computer solves this until it happens again.

 

The starting point with the timers appear very reasonable to me. Sometimes this also happens in KingPin and I think it's the same problem.

I might be missing something here but I can't see how the duty cycle of a timer is going to require a reset of the computer to achieve stable frame rates again.  As I said, I could be wrong but I'm guessing it's something else.

 

Could it be that PinMAME keeps some kind of values saved in some kind until the computer restarts?

[Les73gTx]

So reading these slowdowns described here make me think memory leak. I personally have not experienced this yet but I also have 16 gigs of memory on both my cab and gaming rig. However I will say that the longer the cab is up and running the more I experience unusual behavior that just doesn't happen on a fresh bootup.
The people that are having the slow performance. ... how much system ram are you using? I will pull half of my ram tonight and test this theory. ..

Sent from my SAMSUNG-SM-G870A using Tapatalk

[cyberpez]

 

 

Yeah, I'm having the slowdown on AMH on attract mode, when it loads, but as soon as you play the game it's fine. It doesn't really bother me, but I'd like to know why it's happening. 

Does it happen, say, a minute after it loads (but still in attract mode)?  Does hit happen after a game is done and it goes back to attract mode?

No it just happens on attract mode when it first opens. I checked it's getting 4.9 FPS. Then when I play the game it's fine, I'm getting 75 fps. When the game is over attract mode runs fine. I checked also if I close out the game go to the editor and restart the attract mode it's fine, but if I close the editor reload the editor and start a game I go back to the 4.9 fps attract mode.

 

 

 

I've also noticed this on a table I'm working on that uses UltraDMD..  same thing first time loading in attract things stutter..  as soon as you coin up and start game its fine...  exit and start again things still run normally.  Happens on all of my systems also.

[Dozer316]

Ok I just got round to adding JD to my database. I thought I'd just capture the process with PinXCheck to show how simple it is.

 

I had a better play after this capture and whilst there's nothing wrong with the frame rate, it's way too fast in places. Like the upper left flipper shot > around the orbit (Wall60). You don't have any friction set. You might want to think about adding some to tame her a bit, especially there, because it's REALLY fast.

 

 

No way man, I want to be known for bad frame rates and fast orbits    

 

I personally love the speed but I will release an update in the next couple of days for people who want it a bit more accurate with greater friction in those areas.

[chepas]

The problem is importing from VP9 and they have 0 friction. If you check your Left & Right inlane too. One side had friction 1 and the Right has 0.

 

Join all the metal  guides into a collection so you can group and adjust all the same. 0.2 - 0.3

[Dozer316]

Can anyone who is experiencing the frame rate issue that results in super low frame rates < 10 FPS  try this version and let me know if you notice any difference.

 

This version simply has a GI sub that I use for Led Strips removed completely, there are no other differences.

The sub tends to thrash Direct Output a bit so I'm wondering if this is causing the issue.

 

If you are running Judge Dredd without issues, ignore this version.

 

https://mega.nz/#!vB...wL5jJrViwB5wVf0

The problem is importing from VP9 and they have 0 friction. If you check your Left & Right inlane too. One side had friction 1 and the Right has 0.

 

Join all the metal  guides into a collection so you can group and adjust all the same. 0.2 - 0.3

 

That back loop originally had a friction value but I removed it because it was actually causing an issue when the ball looped from the shooter lane.   The VP9 version had loop walls that were quite inaccurate based on the playfield layout so when I fixed this they got tighter.   I'll check all the friction values when I get an update out.  Anyway, get back to porting it to pygame

[chepas]

Yeah, gotta stay in the 0. values . Lol will do, depending on how much your script is changed from the old one it shouldn't take that long, but not started that yet.

[Kaan]

Can anyone who is experiencing the frame rate issue that results in super low frame rates < 10 FPS  try this version and let me know if you notice any difference.

 

This version simply has a GI sub that I use for Led Strips removed completely, there are no other differences.

The sub tends to thrash Direct Output a bit so I'm wondering if this is causing the issue.

 

If you are running Judge Dredd without issues, ignore this version.

 

https://mega.nz/#!vB...wL5jJrViwB5wVf0

 

 

It doesn't help for me, but my problem was right after I start the table the fps would drop instantly to 4.8~ and stay that way. It was the load_trough I think because messing with that restored fps and broke the table. I don't think this is as big deal as other problems, as it doesn't happen on a faster computer I have.

Edited by Kaan, 01 September 2015 - 02:39 PM.

[Dozer316]

 

Can anyone who is experiencing the frame rate issue that results in super low frame rates < 10 FPS  try this version and let me know if you notice any difference.

 

This version simply has a GI sub that I use for Led Strips removed completely, there are no other differences.

The sub tends to thrash Direct Output a bit so I'm wondering if this is causing the issue.

 

If you are running Judge Dredd without issues, ignore this version.

 

https://mega.nz/#!vB...wL5jJrViwB5wVf0

 

 

It doesn't help for me, but my problem was right after I start the table the fps would drop instantly to 4.8~ and stay that way. It was the load_trough I think because messing with that restored fps and broke the table. I don't think this is as big deal as other problems, as it doesn't happen on a faster computer I have.

 

Ok, thanks for the report.

[chepas]

Got it working. Didn't need to change much in the script, couple of things in the backend game though.

 

Would probably need to do the directB2S manually as well, that was never hooked up for P-ROC, I did ask Herweh ages ago but heard nothing for a long time.

 

https://github.com/h...y/JD-pyprocgame

Edited by chepas, 01 September 2015 - 03:13 PM.