2585 replies to this topic

[Shockman]

@ Newer VP10 is here (beta) first post. It's broken with the latest build though.

 

@ jpsalas I understand that it is the analog method that screws with the keyboard method. It's an axiom.

 

I usually use an Xbox360 for the plunger but I certainly would not want to release a version that did not work as well with the keyboard. I use a impulse plunger though it might be the best disguised application of one you ever saw.

 

I have known the VP plunger object a very long time and have no real interest in it other than visual effect. 

 

All I would care to have as far as using the VP plunger object for anything involving physics is knowing when the release stroke ends.

 

Sub Plunger_EndOfStroke

  IMPlunger.Fire

End Sub

 

I'll revisit timers based on pull time and release speed though.

[Talantyyr]

 

 

good performance, do you need both fxaa and 4xaa though? I've kind of considered "if you can't use 4xaa...use fxaa" but maybe I'm wrong. I've never ran both at the same time .....

Pew, i don't know

But it looks really good, as you can see in my screenshot.

If you're interested i can give you the fps with only one of the options? 

I received my new graphics card yesterday, but i'll try the new "performance boost" build today before i change it. I'll try the performance boost version when i'm home from work and give you the updated fps values

 

Btw, how many fps do i need ?

Imho the gameplay is very smooth.

 

@Sindbad: I have the latest version from the #1 post here. I'll have a look at the setting when i come home. Maybe i have a wrong rom, It was late when i tried it and i was tired

Edited by Talantyyr, 11 March 2015 - 08:15 AM.

[chepas]

 

The table crashes for me when you coin up, but it's looking pretty awesome.

 

You need to set script for normal physics testing :

'Enable proc
Dim BasicScript:BasicScript=True

[Practicedummy]

A bit late for the latest listing, Mr. & Mrs. Pac-MAN has been updated to Beta6

 

https://www.dropbox.... Beta6.vpx?dl=0

Flippers are sticking in the up position. Can't find where to fix this in the script.

[Shockman]

You can not fix this in the script. It can only be fixed by using the .vbs files set that is in the folder you downloaded VPX to. It's the core.vbs that fixes the issue,

 

Edit: If you have already done that you will need to download the late beta and do it again. At some point in the cycle the .vbs set was updated.

Edited by Shockman, 11 March 2015 - 05:04 PM.

[Practicedummy]

I'll check that out. I do have the most recent versions of VP 10 and your table.

[Shockman]

The reason for the .vbs update was specific to this flipper issue.

[Practicedummy]

Still have the problem, even after making sure I have the current vbs files.

[The Loafer]

Practicedummy: Are you only having this issue with this one vp10 table?
Btw, I know I need to update the first post in this thread with new version numbers etc., however I am a little under the weather health wise the past two days due to recent surgery so please be patient with my tardiness

[Practicedummy]

Yes. I also tried JP's Papa Smurf table, and the flippers work as normal.

[Talantyyr]

@fren: 

 

I've got 80fps with the latest VP build with the performance enhancements. Disabling Extreme FXAA and just leaving 4xAA on gives me 10 more fps, but i can see the "stairs effect" on the ramps, it looks way better with both options enabled. (at least to me ^^) 

With my new graphics card, the Sapphire Radeon Vapor X R9 290 i get 200fps with your table at 1440p  

But for my cab i'll use a far weaker (and cheaper) card.

 

 

@Sindbad Oh, you've remapped the insert coin buttons

It's working when you press the right buttons ^^

 

Your table plays great! I've spend half an hour playing it!  

I have about steady 240 fps on your table with everything maxed out.

 

Still have to try the other tables.

[Sindbad]

Thanks Shockman for your kind words.

 

I interrogated your warning. 

 

And I interrogated your feeling about the crap in Vector.

 

I hope you'll feel better now.

Edited by Sindbad, 11 March 2015 - 08:55 PM.

[Slydog43]

Hope for a quick and complete recovery from surgery, Loafer!

Edited by Slydog43, 11 March 2015 - 08:58 PM.

[Shockman]

I only encountered the flipper problem on my table as well. I too thought I had the latest .vbs files and remember unzipping the folder even. I tried a lot of coding options including putting each rotate to end in the key up Sub-routine, which did make them come back down, but the left flipper was giving me some trouble sometimes. It was only a few day ago that I checked again and I did not have the latest core.vbs like I thought I did. 3.44 is the latest, and an absolutely necessary update. 

 

I have my .vbs scripts only in the scripts folder, but I read to be safe they might otta be in the scripts folder AND in the tables folder.

Edited by Shockman, 11 March 2015 - 09:15 PM.

[Sindbad]

Lolo33 reported cropped playfield with Vector an Buck Rogers.

 

Has anyone else the same problem?

[Shockman]

Thanks Shockman for your kind words.

 

I interrogated your warning. 

 

And I interrogated your feeling about the crap in Vector.

 

I hope you'll feel better now.

I almost always use my Xbox 360 controller to casually play tables. So I always have enable mechanical plunger enabled. That is mostly what was wrong when I tried vector with my keyboard. The tables don't suffer nearly as much with that off.

[Sindbad]

I don't comment that anymore.

 

@Rob: Would you please so kind and remove the links to my WIP tables? I want them to be tested in the test team without public comments.

Edited by Sindbad, 11 March 2015 - 09:20 PM.

[chepas]

Links for motu (rom).

MOTU : MOTU.vpx

Basic script for table : Script

update_info: update_info

[parabolic]

Dammit - I should ave grabbed vector and Buck before they were taken down...

[sliderpoint]

Lolo33 reported cropped playfield with Vector an Buck Rogers.

 

Has anyone else the same problem?

 

I hadn't tried the FS settings yet, but I guess they are cut off  on Vector for me as well.  Just a scaling issue, nothing broken.  I didn't see BR so I can't confirm there.