Cactus Canyon VPX

VIRTUAL PINBALL Forums TABLES, DB2S,ROMS,MEDIA Cactus Canyon VPX

This topic contains 444 replies, has 96 voices, and was last updated by Carny_Priest Carny_Priest 1 month ago.

Viewing 15 posts - 136 through 150 (of 325 total)
  • Author
    Posts
  • #18301

    darren clipson
    Participant
      • Posts 16

    remove any vbs file that is not in the scripts folder of VP. Double check your tables folder: no vbs must stay inside this folder.

    Hey ninuzzu, thanks for the advice. i Had a vbs script left in there from the kiss LE table. Removed that at the mine does indeed seem to be fixed! Awesome, thank you. The train however is still missing for now.

    #18308

    Thomas
    Participant
      • Posts 235

    Ciao Ninuzzo … cos’è “force exclusive fullscreen” non uso niente di particolare .. ripeto.. ho problemi solo con questa tavola… quella base tra l’altro.

    #18309

    Thomas
    Participant
      • Posts 235

    ok Ninuzzo
    ho capito di che opzione dicevi… ho quindi tirato via la spunta su “force exclusive fullscreen mode” ma niente da fare.. il problema persiste

    Attachments:
    You must be logged in to view attached files.
    #18311

    darren clipson
    Participant
      • Posts 16

    remove any vbs file that is not in the scripts folder of VP. Double check your tables folder: no vbs must stay inside this folder.

    I thought it was fixed but I just had a ball stick in the mine again :(

    Havent figured out the missing train either.
    Thanks for the suggestion.

    #18312
    ninuzzu
    ninuzzu
    Moderator
      • Posts 461

    Nudging may help with the mine issue

    #18314

    Thomas
    Participant
      • Posts 235

    altri suggerimenti? :whistle: :whistle: :whistle: :wallbash: :wallbash: :wallbash:

    #18315
    manples
    manples
    Participant
      • Posts 17

    For my script error:

    Line:1
    Python Failed — check the log
    File “C:\P-ROC\games\cactuscanyon\cc_modes\bart.py”, line 262, in setup
    self.keys_index = {‘hit’:range(len(self.game.sound.sounds[self.hitQuote])),
    KeyError: ‘quote_hitBetty’

    I’ve checked C:\P-ROC\games\cactuscanyon\sounds\quotes and found this for Betty (see pic attached)

    do I miss a file or is something different, script related? Again it happened several times, right after hitting Bart.

    Thanks for your help guys :D

    Attachments:
    You must be logged in to view attached files.
    #18318
    ninuzzu
    ninuzzu
    Moderator
      • Posts 461

    Yes, we recently updated the rom with the new Betty quotes (it seems you ran the installer in these days):

    https://www.dropbox.com/s/iediouu8zkb9e9n/CCCforVPsoundsupdate20180207.zip?dl=0

    move the updated sounds folder into c:\p-roc\games\cactuscanyon

    #18319
    manples
    manples
    Participant
      • Posts 17

    You guys are awesome.

    I’ve been pounding Bart for the last 20mn with no error at all. Thanks!

    #18320
    Stefan Austria
    Stefan Austria
    Participant
      • Posts 407

    ninuzzu, i am late at the CCC Update, i have just to run: P-ROC Installer V3.1, that is all ?
    i already have the first CCC runing.

    #18321
    ninuzzu
    ninuzzu
    Moderator
      • Posts 461

    Yes, run uninstall, then step 1, 2, same as before

    #18361

    darren clipson
    Participant
      • Posts 16

    Nudging may help with the mine issue

    Hi Ninuzzu,
    I have the train now on the table but the mine issue remains. I set the table to allow 30x Nudge warnings but the ball still gets stuck in there. It does activate some kind of solenoid sequnce that cycles every 20 seconds as though the table is searching for the ball.
    Is there anything else you can think of that could be causing the issue?
    When it works its probably the most fun table I have ever played so thankyou for the great work.

    #18385
    senseless
    senseless
    Participant
      • Posts 48

    Double dash (–position) does the trick! pin2dmd working :)! Thanks manples for the help.

    #18407

    darren clipson
    Participant
      • Posts 16

    Just a quick update of my findings regarding my issue.

    It is now all working perfectly. I had set the z scale too high. Reduced to 1.0 and all is good.

    Thanks for the help and the great table :)

    #18408
    ninuzzu
    ninuzzu
    Moderator
      • Posts 461

    Never Change Z scale, leave it always at 1. Change Z offset instead.

Viewing 15 posts - 136 through 150 (of 325 total)

You must be logged in to reply to this topic.