3889 replies to this topic

[toxie]

here it is with field height at 100

 

seawitch.zip

 

 

thanks, will look into it this evening!

[fuzzel]

I had a quick look at it and it's really strange. I can see that the reflection of the bumper rings are too low but if I place a new bumper on the table with the same settings as a reference everything looks as expected. Was this table built with an earlier version of VPX? Maybe something went wrong while loading from an older format?

[unclewilly]

It is actually just the vp9 version saved as vpx then slowly changing everything to models. So maybe it has to do with the change from the old bumper object to a new one

[fuzzel]

Ah ok. So a quick replacement of the bumpers is the best solution then.

[fuzzel]

Is it possible for you guys to add a feature to the wall object? It would be great if we could adjust a wall on the x, y and z axis. With a feature like this it would be much easier to add bits and parts to ramps and make specialized angled plastics etc. etc. I'd love to see a feature like this...

Well it is possible but it's not easy to implement. Things like that are going into a direction where VP would become a more and more 3D editing tool or some kind of and I think we don't want to go this way. There are better tools for creating custom meshes. I understand that it's not so convenient than a modelling option embedded into VP but we can't add everything 3D related into VP

[fuzzel]

feature time: I added a new function to the kicker element called "LastCapturedBall". With this function you can get an instance of the last captured or currently captured ball in that kicker. But be aware when using this function outside of the Hit/Unhit event function. You can crash VP when it's called and the kicker never captured a ball or the ball was destroyed before.

[toxie]

Maybe you could add a test for this case?

Cause i already sense that this might give use some debugging trouble at some point. 

[ICPjuggla]

Is it possible for you guys to add a feature to the wall object? It would be great if we could adjust a wall on the x, y and z axis. With a feature like this it would be much easier to add bits and parts to ramps and make specialized angled plastics etc. etc. I'd love to see a feature like this...

Well it is possible but it's not easy to implement. Things like that are going into a direction where VP would become a more and more 3D editing tool or some kind of and I think we don't want to go this way. There are better tools for creating custom meshes. I understand that it's not so convenient than a modelling option embedded into VP but we can't add everything 3D related into VP

Well that's a bummer as I figured it would be similar to ramps but shapable/thickness.. So I guess there is no way of getting around using blender or a 3D modeling program, some of us aren't that good at it unfortunately.. I guess I'll have to take a few months and try and wrap my head around how to actually use the program, but to be honest it's not that user friendly. I was trying to think of an easier way for some of us without 3D modeling skills to accomplish the same effect(s).. :-)

Anyway, how exactly dose the table field hight work? I've been playing around with it. If I raise the table field hight to say 50 how do I get a ball to fall though a hole in a pf? I know there are other ways to do this like using a good old fashioned wall object with a hight of 50 as my pf and cut a hole out of the wall. So it got me thinking and wondering exactly how the table field hight works as I can't seem to make a ball fall though it with anything I'v tried so far.

[fuzzel]

Maybe you could add a test for this case?

Cause i already sense that this might give use some debugging trouble at some point. 

Yep I've already done that If no ball could be found an error message is displayed and the game will stop playing but VP won't crash anymore.

 

Well that's a bummer as I figured it would be similar to ramps but shapable/thickness.. So I guess there is no way of getting around using blender or a 3D modeling program, some of us aren't that good at it unfortunately.. I guess I'll have to take a few months and try and wrap my head around how to actually use the program, but to be honest it's not that user friendly. I was trying to think of an easier way for some of us without 3D modeling skills to accomplish the same effect(s).. :-)

Anyway, how exactly dose the table field hight work? I've been playing around with it. If I raise the table field hight to say 50 how do I get a ball to fall though a hole in a pf? I know there are other ways to do this like using a good old fashioned wall object with a hight of 50 as my pf and cut a hole out of the wall. So it got me thinking and wondering exactly how the table field hight works as I can't seem to make a ball fall though it with anything I'v tried so far.

 

Yes I can understand that but the point is that editing the height of a wall can become really complicated if you have a complex wall shape. A ramp is much simpler.

[BorgDog]

I've been getting a lot of crashes with the latest, 2239, doing simple things like closing a table, on both computers I've been using it on.  Here is the crash.txt from the last one I got.  Crash.dmp HERE

 

Crash report

============

Process: vpinballx.exe

Reason: 0xC0000005 - EXCEPTION_ACCESS_VIOLATION at 0023:0043CC40

Attempt to read from 0x00000014

Thread ID: 0x19F8 [6648]

 

Call stack

==========

0043CC40 vpinballx.exe (0x00000000 0xFFFFFFFFD4F217A0 0x00000000 0x081514d0)

00438469 vpinballx.exe (0x00000000 0x081514D0 0x004908D7 0x081514d0)

00437364 vpinballx.exe (0x081514D0 0x00490996 0x00000001 0x00000000)

004908D7 vpinballx.exe (0x00000001 0x00000000 0x085E2310 0x00479ab4)

00490996 vpinballx.exe (0x081514D0 0x01588FF0 0x00000000 0x085e2310)

00479AB4 vpinballx.exe (0x085E2310 0x004F45DE 0x00000001 0x000a090e)

004F4618 vpinballx.exe (0x00000001 0x000A090E 0x76539A55 0x004e3d39)

004F45DE vpinballx.exe (0x085E2310 0x000A090E 0x085E2310 0x0018fa78)

004E3D39 vpinballx.exe (0x000D0AEC 0x00000020 0x000D0AEC 0x02000005)

765374BB user32.dll ReleaseDC + 0x75 (0x000D0AEC 0x000000A0 0x00000005 0x002b070d)

765374BB user32.dll ReleaseDC + 0x75 (0x000D0AEC 0x0000A918 0x000000A0 0x00000000)

7653717A user32.dll IsWindow + 0x44 (0x76543623 0x6FFA6DA2 0x0018F834 0x00000000)

 

Environment

===========

Date/time: 22/10/2015, 10:03:18:587

Number of CPUs: 4

Processor type: 586

System: Unknown Windows version - 6.1 (Service Pack 1)

 

Memory status

=============

Total Reserved: 92616K (90M) bytes

Total Commited: 155240K (151M) bytes

Total Free: 3946384K (3853M) bytes

Largest Free: 2096704K (2047M) bytes

 

Registers

=========

EAX=00000004 EBX=00000000 ECX=081514D0 EDX=00566AEC

ESI=00000000 EDI=D4F217A0 EBP=00000000 ESP=0018F81C EIP=76540DB2

FLG=00210207 CS=0023 DS=002B SS=002B ES=002B FS=0053 GS=002B

 

 

Mini dump saved successfully.

[toxie]

Ah ok. So a quick replacement of the bumpers is the best solution then.

 

I also looked into this table-problem for way too long now, and i cannot explain this effect.

My best guess is that its actually a more general bug, that is somehow not happening most of the time otherwise, but showing itself here.  :/

[fuzzel]

rev2260 is up:

 

- added LastCapturedBall function to the kicker. With this function you can get an instance of the current/last captured ball as long as it is still in play. It is save to use this inside of the Hit/Unhit event function.
- shuffle code around in ball reflection to make disabled reflection balls early out faster
- increase accuracy of rubber's hit shape. The old hit shape had a too low detail/shape and that could be the reason why the ball behaved strange when the rubber ring was a tad higher than the ball.
- script editor updated again and fixes some crashes
 

[toxie]

@BorgDog: Please try again with this new build. Hopefully cures the crash.

[Ben Logan]

Toxie - Thanks for all your hard work. I'm seeing so many fixes and added features from you lately. Speaking strictly as a player, we really appreciate all you do for this great hobby!

[BorgDog]

@BorgDog: Please try again with this new build. Hopefully cures the crash.

 

Haven't done a lot, but tried a bunch of the stuff that seemed to cause issues before and seems to be good.  I'll let you know if I run into more problems.  

[toxie]

Toxie - Thanks for all your hard work. I'm seeing so many fixes and added features from you lately. Speaking strictly as a player, we really appreciate all you do for this great hobby!

 

Maybe because i was away/busy for quite a while..

So hungry for Pinball again..

 

But don't forget Fuzzel and Brandrew!

[Shockman]

nor Mukuste

[freneticamnesic]

i like turtles

Edited by freneticamnesic, 23 October 2015 - 12:51 AM.

[J3SteR]

Thanks everyone including the table authors for you time and effort. Devs, think maybe vp10 will be officially released and out of beta before 2016? Im looking to build a new cabinet early next year. Would be awesome to see VP 10 on it. Looking great!

Sent from my SCH-I545 using Tapatalk

[hauntfreaks]

I notice people waiting for the release of 10?... its a 2minute or last update to bring the beta's up to date (as well as when it's fully released)... a whopping 6mb so

dont let that scare ya or left in the dust... its so not a big deal... this is coming from a pretty lazy dude... I do nothing that might mean more work for myself...

so people bite that bullet and dont look back.... plus ya get to have all your fav vp8, 9, pm5's as well...