Cactus Canyon (& Continued)

[fourbanks]

Hi friends:)

Cactus Canyon (& Continued​

cc plays fine and always has done. To recap, how does one get ccc to play as it's stopped working. Failing that, does someone have a working CCC i could have, please.
Thanks

ps i know this file is not supported here, but you don't get support in the other place, so this is just an off chance that someone has this file

 

[Cliffy]

Make sure you're running the dx version of vpx, not GL and make sure only in windowed fullscreen, not exclusive full screen. Read back through the posts here. The dmd settings are in the user_settings.yaml in the config folder

 

[fourbanks]

Iv'e had to reinstall proc and python, and now I am getting the error after python is installed STEP 1 - Install Prerequisites
any ideas as to what is wrong on a new installation thanks

 

[fourbanks]

Iv'e had to reinstall proc and python, and now I am getting the error after python is installed STEP 1 - Install Prerequisites
any ideas as to what is wrong on a new installation thanks

I have now installed correctly but back to the errors on CCC only

 

[fourbanks]

An update CC all working on Windows 11, and Windows 10. CCC no still with errors. Maybe an update mucked something up?
Can anyone here confirm CCC is working for them
Thanks

 

[Cliffy]

windows 24h2 update screwed up my b2s right click context menus too, I had to manually put them back in the registry. And sadly yes I can no longer get CCC to start Python and vpx script errors

 

[fourbanks]

windows 24h2 update screwed up my b2s right click context menus too, I had to manually put them back in the registry. And sadly yes I can no longer get CCC to start Python and vpx script errors

Thanks cliffy for your time and update
oh, well that's that then until someone can make an update to the table?

 

[fourbanks]

i should add my pup pack is no longer working on Windows 10 for the CC table, but is working on Windows 11

 

[Cliffy]

Not a table problem. It's a windows 11 python 2.7 problem. windows won't allow it I suppose because it's too old and too many security holes in in it. We'll likely need to update python to 3.1 but honestly I just don't have the time and will to attempt it right now

 

[fourbanks]

Not a table problem. It's a windows 11 python 2.7 problem. windows won't allow it I suppose because it's too old and too many security holes in in it. We'll likely need to update python to 3.1 but honestly I just don't have the time and will to attempt it right now

Thanks, my friend for all your help
hopefully someone will update the installation file at some point

 

[fourbanks]

In regard to the above, does anyone have the pup pack working on CC Windows 10? Windows 11 OK. I have refreshed my Windows 10 and CC pup pack still not working. All my other pup packs perfect

thanks

 

[fourbanks]

Release Visual Pinball X 10.8.0 · vpinball/vpinball

If you want to install Visual Pinball from scratch, please download and install VPX8setup.exe. Otherwise select the specific package(s). VP 10.8.0 Changelog LIMITATIONS: Broken PROC support Bro...

github.com

what do you think?
Could this be the culprit

VP 10.8.0 Changelog​

LIMITATIONS:

• Broken PROC support
• Broken SMAA postprocessing, will be fixed in 10.8.1

 

[fourbanks]

i have spent some time on this, and have got it down to just one error plus the screenshot above
Line: 550
Python Failed -- check the log
File "C:\P-ROC\tools\register_vpcom.py", line 222, in Run
os.chdir(newpath)
WindowsError: [Error 3] The system cannot find the path specified: 'C:\\P-ROC\\games\\cactuscanyon'

 

[Cliffy]

i have spent some time on this, and have got it down to just one error plus the screenshot above
Line: 550
Python Failed -- check the log
File "C:\P-ROC\tools\register_vpcom.py", line 222, in Run
os.chdir(newpath)
WindowsError: [Error 3] The system cannot find the path specified: 'C:\\P-ROC\\games\\cactuscanyon'

Hmmmm. Maybe try adding the path to the system environment variable?

 

[fourbanks]

Python Failed -- check the log
File "C:\P-ROC\games\cactuscanyon\cc_modes\base.py", line 56, in __init__
self.keys_index = {'beer_mug':list(range(len(self.game.sound.sounds[self.game.assets.quote_beerMug])))}
KeyError: 'quote_beerMug'
that's now the new error plus the screenshot above

the pup loads which is something but on pressing the key for the coin it then turns to the above. I can see this to be a big headache for someone like myself, determined to get it working, of which will be impossible.

 

[Cliffy]

yeah thats the error I get everytime

 

[fourbanks]

yeah thats the error I get everytime

The fact that there are more than 300 responses in another pinball forum suggests that the CCC table was not yet ready for release. The monthly updates from Microsoft don't typically cause problems with files, but as all software developers are aware, you should periodically review your work and make any necessary modifications because if you don't, your software will eventually malfunction.

 

[Cliffy]

Cactus Canyon Continued, as a conversion kit for the real game, still works today as intended. The visual pinball version was allowed but not supported by the proc developers. Basically then we are on our own

 

[fourbanks]

Cactus Canyon Continued, as a conversion kit for the real game, still works today as intended. The visual pinball version was allowed but not supported by the proc developers. Basically then we are on our own

Indeed, we are. I have reached out to some top table members from all the main pinball forums for some feedback, and it's not good. The installer will need to be rebuilt with the latest python, and also the table itself will need to be overhauled for the few outstanding errors like above.
As for finding someone to undertake this and also the table young Frankenstein, I have yet to find anyone so in reality both of these tables are never coming back sad to say

 

[fourbanks]

i have made some enquiries in a main python forum as to what may have happened and if any a possible way forward

 

[Carny_Priest]

Table starts for me, but my laptop is still using Win7.

 

[fourbanks]

Table starts for me, but my laptop is still using Win7.

Thanks :)

 

[Carny_Priest]

I'm not seeing any compatibility reports for Win 11 24H2 and any version of Python. That said, if all your other pinball stuff was working fine before then you could try to revert back to 23H2.

The underlying dependencies for the P-ROC controller are linked here: https://www.multimorphic.com/software-development/

But you can see when you dig into it that there have not been any updates in years. Any Python source code was written for Python 2.6 and is proven to work with Python 2.7. I have no idea if current Python 3+ is backwards compatible for the existing source code.

If you thought it was just a matter of current Windows compatibility with the compiled game code, then a cheap thing to do would be to recompile. Delete out all files with PYC extension which are compiled code. C:\P-ROC\games\cactuscanyon. When you launch the game again, it will compile any code and recreate any PYC files that are missing. Backup first of course! I don't know that it will make any difference.

You might check with freezy on VPE. It's a different architecture, and he was planning on adding a P-ROC/MPF plug-in that's closer to native support. It would run the original game code and would no longer require my port for VP. I don't have details beyond a discussion with freezy a few years ago. I'm sure this would still require Python.

Sorry, I can't be more help. I don't have Win 11 or access to any machines with Win 11. My cabinet needs work, but I don't have immediate plans to upgrade. My current hardware is not compliant. I had looked at the controller.vbs issue when that issue came up, but I'm not sure what the VPX team did that caused that issue. It's not been a high priority for them to look at it as it has been just CCC that has any profile on that platform. Aside from a couple of demos, there is not much else publicly available. Too bad, because CCC is a nice update for CC.

 

[fourbanks]

I'm not seeing any compatibility reports for Win 11 24H2 and any version of Python. That said, if all your other pinball stuff was working fine before then you could try to revert back to 23H2.

The underlying dependencies for the P-ROC controller are linked here: https://www.multimorphic.com/software-development/

But you can see when you dig into it that there have not been any updates in years. Any Python source code was written for Python 2.6 and is proven to work with Python 2.7. I have no idea if current Python 3+ is backwards compatible for the existing source code.

If you thought it was just a matter of current Windows compatibility with the compiled game code, then a cheap thing to do would be to recompile. Delete out all files with PYC extension which are compiled code. C:\P-ROC\games\cactuscanyon. When you launch the game again, it will compile any code and recreate any PYC files that are missing. Backup first of course! I don't know that it will make any difference.

You might check with freezy on VPE. It's a different architecture, and he was planning on adding a P-ROC/MPF plug-in that's closer to native support. It would run the original game code and would no longer require my port for VP. I don't have details beyond a discussion with freezy a few years ago. I'm sure this would still require Python.

Sorry, I can't be more help. I don't have Win 11 or access to any machines with Win 11. My cabinet needs work, but I don't have immediate plans to upgrade. My current hardware is not compliant. I had looked at the controller.vbs issue when that issue came up, but I'm not sure what the VPX team did that caused that issue. It's not been a high priority for them to look at it as it has been just CCC that has any profile on that platform. Aside from a couple of demos, there is not much else publicly available. Too bad, because CCC is a nice update for CC.

Many thanks, my friend, for your expertise and depth of knowledge in finding a way forward. It was just odd that both my tables of CCC one on window 10 and 11 stopped working at the same time. I am sure someone will be able to get in up and running again at some point in the future.