93 replies to this topic

[SPARKY70]

Hi guys.  Thanks for the replys.  I understand what you mean, however, the older version of this table that i have been using worked correctly. 

I am not home right now to check the table version  (it may be 9.1.1 from memory, but not sure. 

 

Also, the other table may be calling for a different rom. I will have to check on that too. 

 

But either way, i havnt experienced this problem on the older table. I will check rom, and older table version when i get home. Thanks. Sparky

Edited by SPARKY70, 18 November 2022 - 11:35 PM.

[SPARKY70]

ok, fully working drop targets table version i am using is confirmed as  --- Medusa_VP9_1.1FS

 

 

both tables are using the same rom: medusa

Const cGameName = "medusa"

Const cGameName = "medusa"

 

since both tables are using the same rom, and 9.1.1 is working correctly. i would imagine, that it is not a software rom issue.

 

let me know what you think... thanks////sparky

[jpsalas]

I have just tested the table and the droptargets and they work fine in my desktop computer too. The script is the same as in the VP9 table.

[SPARKY70]

 thanks for checking JP. Could it be an object on the playfield getting in the way causing it to not always work?

 

thanks...sparky

[wiesshund]

set table up with a couple auto slingshots and just let it self play for like 45 minutes
targets worked fine as far as i could tell

 

score was retardedly high but the targets worked fine

[jpsalas]

 thanks for checking JP. Could it be an object on the playfield getting in the way causing it to not always work?

 

thanks...sparky

 

I guess it is all about timing. The new droptargets takes longer time to drop at that may not work too well with older roms and older computers, or a combination of both

So I have replaced the droptargets with older droptargets made of walls. I guess this will work better for you:

 

 Medusa (Bally 1981) v4 - Droptargets.zip   6.76MB   8 downloads

[wiesshund]

 

 thanks for checking JP. Could it be an object on the playfield getting in the way causing it to not always work?

 

thanks...sparky

 

I guess it is all about timing. The new droptargets takes longer time to drop at that may not work too well with older roms and older computers, or a combination of both

So I have replaced the droptargets with older droptargets made of walls. I guess this will work better for you:

 

Medusa (Bally 1981) v4 - Droptargets.zip

 

 

cant you do the same by enabling legacy mode?

You can also set drop speed to like 0.07 and i think they will drop really fast?

[jpsalas]

 

 

 thanks for checking JP. Could it be an object on the playfield getting in the way causing it to not always work?

 

thanks...sparky

 

I guess it is all about timing. The new droptargets takes longer time to drop at that may not work too well with older roms and older computers, or a combination of both

So I have replaced the droptargets with older droptargets made of walls. I guess this will work better for you:

 

Medusa (Bally 1981) v4 - Droptargets.zip

 

 

cant you do the same by enabling legacy mode?

You can also set drop speed to like 0.07 and i think they will drop really fast?

 

 

Legacy mode only does that the droptarget can be hit on the sides and back too, otherwise can only be hit by at the front side.

 

I tried increasing the speed of the droptargets, but it didn't work. I tried that in an EM table were I did a check after a "droptarget_hit" to check if it was dropped, and it never was (I know about the droptarget_Dropped ). The cpu speed is always much faster than the animation. So I guess some roms and some cpu will have problems with the VPX droptargets, but in those rare cases we can always use a wall instead of a droptarget, or both, using the VPX droptarget only for the animation, and the walls for the hit events

 

But I guess that now the droptargets will work fine for SPARKY70.

[SPARKY70]

hi JP, i have downloaded and tried the drop target version you posted above. after playing many many times, it seems that the drop targets are working correctly. i did not have any issues with about 30 games played.

thank you sooo much for checking into this and making a fix.

 

 

there is one other strange thing i had noticed on both this AND the older 9.1.1 table.

 

the BLUE COLOSSUS BONUS INSERT 90, is lit at the start of the game, and i always thought that was strange.

after looking into the owners manual, and also playing many games. i believe that the control for the 90 insert, and the 30 insert are swapped.

the lights advance from 90 to 60 to 30 to 120, instead of 30,60,90.

 

thank you again to everybody for helping with my drop target situation......sparky

Edited by SPARKY70, 20 November 2022 - 11:36 PM.

[jpsalas]

hi JP, i have downloaded and tried the drop target version you posted above. after playing many many times, it seems that the drop targets are working correctly. i did not have any issues with about 30 games played.

thank you sooo much for checking into this and making a fix.

 

 

there is one other strange thing i had noticed on both this AND the older 9.1.1 table.

 

the BLUE COLOSSUS BONE INSERT 90, is lit at the start of the game, and i always thought that was strange.

after looking into the owners manual, and also playing many games. i believe that the control for the 90 insert, and the 30 insert are swapped.

the lights advance from 90 to 60 to 30 to 120, instead of 30,60,90.

 

thank you again to everybody for helping with my drop target situation......sparky

 

Thanks for the info about the 90 and 30 being swapped. I'll fix that.

 

Good that the targets are working better for you. I'll add the fix to the released version. 

[jpsalas]

UPDATE

 

4.0.1 Updated 20.11.2022

- Fixed top droptargets.

- Fixed the colossus bonus lights.

Thanks SPARKY70 for reporting the bugs.

[SPARKY70]

HI JP, thanks for the update. 30/90 working well now.

 

i also noticed something strange with the playfield numeric display.

 

if the "shield of gods" number is other than "05"  (its default 05 at startup) and the game is reset using F3, when the game is restarted, the fourth digit, (right extra ball number), and the 6th digit, (right shield of gods digit), become scrambled. in other words, 05 displays as 08, and 04 displays as 0H etc.

 

im not sure why this is , or if it is a VPX issue or conflict. but i thought i should mention it here.

 

i think it goes back to normal after a new game is started, and it also works correctly, from a fresh launch.

 

unrelated to that issue, i have also played with the middle 2 digit colors to make them orange rather than yellow.

 

the b2s backglass orange color is R255 G65 B46.

 

i am not sure if i am doing it right, but through trial and error, if anyone is interested, i came up with COLOR = R64 G12 B6 & FULL = R254 G14 B1

 

This gives orange colored 3rd and 4th digits, but as to matching the backglass, its probably not a perfect match.

 

you likely know better than me on how to do this.... thank you for all your help/////sparky

[wiesshund]

 

 

i also noticed something strange with the playfield numeric display.

 

if the "shield of gods" number is other than "05"  (its default 05 at startup) and the game is reset using F3

 

dont reset the ROM using F3

it rarely ends well, quit to editor and relaunch

nothing to do with the table, just how vpinmame works

[jpsalas]

UPDATE

 

4.0.2 Updated 23.11.2022

- made the center playfield leds orange instead of yellow. Thanks SPARKY70 for the info.

 

Just a cosmetic change this time