318 replies to this topic

[cestmoi]

Merci Pinball wizard

 

après modification dans la base de registre cela fonctionne . Le message e22 apparaît toujours mais la table se lance

 

Quelques lags apparaissent cependant dès lors que la bille heurte le coffre, pas trop gênant mais quand même

 

Merci beaucoup en tout les cas

 

Super table !

[PEandS1Ws]

WOW!! Nice work team...this was the table that started me on my virtual pinball journey. I played this everyday on my Xbox One S in Pinball FX3. It's the reason I know have a pinball cabinet with 830 tables.

 

 

I did run into a lost ball on game number 2. It was during trunk mutliball and after 2 balls drained I waited for the machine to find the ball but it did not. I nudged left and right trying to dislodge it then nudged forward and could see the ball stuck in the upper left playfield:

Ball search-https://drive.google...D-CmfrCtQY6etLx

Ball stuck-https://drive.google...DCFH-o1IaEMl977

[Genesis38]

Geez! The Loafer wasn't kidding about the table punishing you for missed shots. 5 games in and 1 multi ball game, drained within seconds. Though it's difficult as nails, it's quite enjoyable to play. Back at it again after lunch

[The Loafer]

Merci Pinball wizard

 

après modification dans la base de registre cela fonctionne . Le message e22 apparaît toujours mais la table se lance

 

Quelques lags apparaissent cependant dès lors que la bille heurte le coffre, pas trop gênant mais quand même

 

Merci beaucoup en tout les cas

 

Super table !

 

Il y a des options dans le script qui peut aider le frame rate de la table.  En disant cela, c'est une pin de haute qualité donc sa pousse les specs.  Quelles sont les specs de ton PC?

[meek424424]

This will be great! I can't wait to play this one tonight! Thank you for sharing! Great details in the description and I can't wait to try the modular flashers. Thank you for your hard work and contribution to this wonderful community! You all are awesome!

[Armyaviation]

I went to the registry and changed the cheat to 1 for the hb rom and still the same.  I have tom13 also in the directory.  Still get the U22 error but the game plays. 

[Nemo]

Just another remark: I have an insanely big-ass subwoofer in the cab accompanied by an exciter setup and if that wasn't enough a rediculously powerfull bass shaker.

 

Now in the bottom section of the script you can dial in EVERY sound setting to one's specific setup, i tinkered with it for more than an hour and got it to be 100% to my liking.

 

 

I will say this, it's bloody stunning, and a HUGE thanks to the guy(s) who came up with this excellent piece of scripting......BRAVO !! 

[The Loafer]

Until someone comes up with another option, you have two choices Armyaviation:

 

- Since the game does allow you to play, just ignore the short duration message.  The instructions provided earlier are for those of us who could not get past that message (it would not go away strangely)

- Perhaps seek out an alternate rom set, perhaps the two roms you have are not complete?

 

I have a feeling perhaps the version of VPM is causing some issues?  I know for me, message went away after doing the steps I outlined earlier but it went from "won't bypass that message at all" to "no more message".  I never went to a "message goes away shortly".

 

Maybe there is another VPM option that enabled/disabled is preventing the rom message from disappearing completely.

[Mike DA Spike]

Wow ! One of my favorites real tables.
Pretty impressive !
Good job !

[JLouLoulou]

If I can make a feedback, here what i think:

 

I am amazed!!! But something bothers me ... The physics with the 2 flippers .. Personally I find it not realistic or something weird .. The flips restore the effects of "overspin" too much ... Suddenly, even with the fast flip at 2ms, I the impression that it takes 1 second to kick the ball, because the angle of the ball is extremely open when it leaves flippers, it takes too much the side rolling effect. Also I often lose it on a retro effect, while it bounces online very quietly, and paf .. it goes towards the center and returns to the middle to fall into the hole ... there are too many rebound for control and too much rolling on flippers. It gives the impression that the flip wants to play on its own. I never played this flip .. But Williams is Williams, and I never had that feeling for real.

Likewise I often do improbable rescues between the 2 flippers

By cons the physics of the table itself is perfect I think! Graphically it's a slap, but then the sound ... Popopopopopopopopopopopopopopo !!!! It's the death of mechanical DOF !!! poa poa poa poa !! How it is a killing !! And I only have 2 speakers, I burnt my ssf amp during reassembly.

 

Of course this is only my opinion, but I do not take pleasure. When I move from your table to another, or to my real pinball machine, I immediately feel that something is not consistent with the flipper phyiscs.. Like if there is a randomness.

 

It takes nothing away from the quality of your work, which I will never be able to do, and what you have done is really fantastic. It's just an opinion that I give on a detail of the table ...

 

Thank you all for your work! Thank you thank you thank you for your 2 years of efforts!

[arngrim]

table is gorgeous, 5 stars like totan, wcs, cv, taf, afm releases

 

To benefit from the latest DOF update in the configtool, here is a code to be added in the script in bold.

 

Sub UpdateGI(no, step)

'TextBox.text = no & " " &  step

Dim xx

If step = 0 then exit sub 'only values from 1 to 8 are visible and reliable. 0 is not reliable and 7 & 8 are the same so...

gistep = (step-1) / 7

If step = 8 then 'GI is on

DOF 101, DOFOn

Else

DOF 101, DOFOff

End If

Select Case no

.

.

.

 

I have put 0.1 to VolumeDial, sounds are much more discrete like that, to test it i shut down the rom sounds, this is how you can test the mech sound level.

 

i have to say it seems there is a latency about the flippers, like if the Const UseSolenoids = 1, are there others feeling it?

 

edit : seems that JLouLoulou agrees with me

Edited by arngrim, 08 April 2020 - 06:41 PM.

[cestmoi]

quelques latences pour moi aussi

[rothbauerw]

WOW!! Nice work team...this was the table that started me on my virtual pinball journey. I played this everyday on my Xbox One S in Pinball FX3. It's the reason I know have a pinball cabinet with 830 tables.

 

 

I did run into a lost ball on game number 2. It was during trunk mutliball and after 2 balls drained I waited for the machine to find the ball but it did not. I nudged left and right trying to dislodge it then nudged forward and could see the ball stuck in the upper left playfield:

Ball search-https://drive.google...D-CmfrCtQY6etLx

Ball stuck-https://drive.google...DCFH-o1IaEMl977

 

Thanks for the videos.  Very helpful and we'll address in an update.  Just out of curiosity, did you make any adjustments to flipper strength?

[kds70]

 

If I can make a feedback, here what i think:

 

I am amazed!!! But something bothers me ... The physics with the 2 flippers .. Personally I find it not realistic or something weird .. T

 

Thank you all for your work! Thank you thank you thank you for your 2 years of efforts!

 

Same here. An amazing table release ... bombastic and many thanks all involved, really.  But, like he always said, something´s going wrong with flipper physics.

[jpsalas]

That flipper latency are the nFozzy/Roth flippers code. If your cpu is a fast one then you won't notice any latency, but if it is not, then you'll notice it. And if the cpu is older, you even if may play other tables at 60 fps, but with these nFozzy flippers settings then the flippers may take a long time to react, being complete useless. I tested those flipper settings on my computer at work, which uses an Intel Xeon CPU E5-2630 running at 2.30 Ghz, and that cpu is way too slow to handle those flippers. But if you cpu is fast (3.6 -4 Ghz) then the flippers should work quite well. I have only implemented those flippers setting in my latest Speakeasy table, and I have received a lot of messages about how slow those flippers are, I guess not everybody has a fast cpu.

 

I have not seen a variable to disable those flippers, and it will be too complicated to disable them manually, maybe the authors will add a variable to disable that nFozzy flipper code.

 

 

edit: my English sound like Yoda

Edited by jpsalas, 08 April 2020 - 07:02 PM.

[JLouLoulou]

That flipper latency are the nFozzy/Roth flippers code. If your cpu is a fast one then you won't notice any latency, but if it is not, then you'll notice it. And if the cpu is older, you even if may play other tables at 60 fps, but with these nFozzy flippers settings then the flippers may take a long time to react, being complete useless. I tested those flipper settings on my computer at work, which uses an Intel Xeon CPU E5-2630 running at 2.30 Ghz, and that cpu is way too slow to handle those flippers. But if you cpu is fast (3.6 -4 Ghz) then the flippers should work quite well. I have only implemented those flippers setting in my latest Speakeasy table, and I have received a lot of messages about how slow those flippers are, I guess not everybody has a fast cpu.
 
I have not seen a variable to disable those flippers, and it will be too complicated to disable them manually, maybe the authors will add a variable to disable that nFozzy flipper code.
 
 
edit: my English sound like Yoda

Yep I know this JPSalas..My cpu is not the problem. It's visible when i play, it's not the latency, its how the ball roll on the Flipper, it affect too much the accuracy for a same shot with static ball compare to moving ball for example.

Envoyé de mon Redmi Pro en utilisant Tapatalk

[kds70]

JP, thats not the latency i´m talking about ... your speakeasy tables flippers work really good. I can´t tell it in english in my words sorry. but, you think (u know) the ball must be shot in this direction now and ... no, unbelievable, the ball goes into a direction you didn´t ever believe.

 

I took the g5k AFM flipper physics for testings and it plays better now (for me) inclusice base / end radius of flipper bats, but strength 3700 and not over 5000. lets see and thanks for you answer.

[JLouLoulou]

table is gorgeous, 5 stars like totan, wcs, cv, taf, afm releases
 
To benefit from the latest DOF update in the configtool, here is a code to be added in the script in bold.
 
Sub UpdateGI(no, step)
'TextBox.text = no & " " &  step
Dim xx
If step = 0 then exit sub 'only values from 1 to 8 are visible and reliable. 0 is not reliable and 7 & 8 are the same so...
gistep = (step-1) / 7
If step = 8 then 'GI is on
DOF 101, DOFOn
Else
DOF 101, DOFOff
End If
Select Case no
.
.
.
 
I have put 0.1 to VolumeDial, sounds are much more discrete like that, to test it i shut down the rom sounds, this is how you can test the mech sound level.
 
i have to say it seems there is a latency about the flippers, like if the Const UseSolenoids = 1, are there others feeling it?
 
edit : seems that JLouLoulou agrees with me

i have this feeling on my desktop computer too, and friend too

Envoyé de mon Redmi Pro en utilisant Tapatalk

[rothbauerw]

Thanks for chiming in JP! 

 

I've been wracking my brain trying to figure out why we're getting that kind of feedback on the flippers.  These flippers use the same or very similar code as Twilight Zone, Medieval Madness, and Totan and I didn't hear any of this feedback on those.

 

But since you mention cpu performance, that might make sense.  There is scripting that adjusts various parameters of the flippers throughout the flipper stroke to simulate the behavior of real flippers.  Strangely, I do most of my testing on an under powered desktop and I haven't seen any issues on it.  That said, if someone that's is experiencing issues would make a change to the following line of code in the script, it would help us determine if that's really the issue.  Search for,

 

Rightflipper.timerenabled=True

 

And replace it with:

 

Rightflipper.timerenabled=False

JP, thats not the latency i´m talking about ... your speakeasy tables flippers work really good. I can´t tell it in english in my words sorry. but, you think (u know) the ball must be shot in this direction now and ... no, unbelievable, the ball goes into a direction you didn´t ever believe.

 

This would tell me you're just too accustomed to VP flipper physics which do not accurately simulate the trajectory of real pinball flippers.

[JLouLoulou]

Thanks for chiming in JP! 
 
I've been wracking my brain trying to figure out why we're getting that kind of feedback on the flippers.  These flippers use the same or very similar code as Twilight Zone, Medieval Madness, and Totan and I didn't hear any of this feedback on those.
 
But since you mention cpu performance, that might make sense.  There is scripting that adjusts various parameters of the flippers throughout the flipper stroke to simulate the behavior of real flippers.  Strangely, I do most of my testing on an under powered desktop and I haven't seen any issues on it.  That said, if someone that's is experiencing issues would make a change to the following line of code in the script, it would help us determine if that's really the issue.  Search for,
 
Rightflipper.timerenabled=True
 
And replace it with:
 
Rightflipper.timerenabled=False

great i'will test that Tomorow. I need to don't forget it lol.. For information, on totan i don't play with nfozzy physics too. I even don't like it.
For information, i have recent i5 en i7 ( which is not make difference, i7 instructions are not used ) processor with gtx1660ti, cpu load is never more, 40% with full graphics options.

Envoyé de mon Redmi Pro en utilisant Tapatalk