Jump to content
Dazz

Errors when running PROC Games

Recommended Posts

I've been trying to get PROC running for a while now.  Took a break from it, but trying to get back to it.  I just did a fresh un-install and re-install of PROC using the new installer.  Everything appeared to have run fine without error. 

I do run VP from another drive (D:) other than my C: drive.  Tables are all on D: drive.  

Error when running CCC via VP.

28795676_10156167460839362_2503765868440846338_n.jpg

 

Error running Evil Dead.

28795951_10156167461649362_2315873157071651883_n.jpg

Share this post


Link to post
Share on other sites

Ninuzzu made a simple updated installer works perfectly no surprise! Just uninstall any old proc with uninstaller first and should work as long as your running win7 or win 10

Share this post


Link to post
Share on other sites
Ninuzzu made a simple updated installer works perfectly no surprise! Just uninstall any old proc with uninstaller first and should work as long as your running win7 or win 10


This is with using the new installer...


Sent from my iPhone using Tapatalk Pro

Share this post


Link to post
Share on other sites

Finally got CCC working fine using the installer. Running into issues with EvilDead still.  Seems like the .dll isn't registering correctly.  I've manually added the DLLs folder to my Windows Environment PATH.  Still no go. :(

Share this post


Link to post
Share on other sites

Anyone happen to know how to fix this?

>2018-03-16 12:19:00,467 - game.config - WARNING - pyprocgame configuration not found at ./config.yaml. Checking C:\Users\betat/.pyprocgame/config.yaml.
2018-03-16 12:19:00,467 - game.config - INFO - pyprocgame configuration found at C:\Users\betat/.pyprocgame/config.yaml
2018-03-16 12:19:00,545 - vpcom - INFO - Run received extra arg!?
2018-03-16 12:19:00,545 - vpcom - INFO - Arg was 5506032
2018-03-16 12:19:00,545 - vpcom - INFO - S11 is ...False
2018-03-16 12:19:00,545 - game.config - INFO - pyprocgame configuration found at ./config.yaml
2018-03-16 12:19:00,561 - game.config - INFO - pyprocgame configuration found at ./config.yaml
2018-03-16 12:19:00,858 - game.sound - INFO - Initializing sound...
2018-03-16 12:19:00,989 - vpcom - INFO - game instantiation error(UnsupportedError: 'FontManager requires sdlttf support')
2018-03-16 12:19:00,989 - vpcom - INFO - PYTHON FAILURE (Visual Pinball Bridge is now broken)
2018-03-16 12:19:00,989 - vpcom - INFO - Exception Name 'FontManager requires sdlttf support'
2018-03-16 12:19:00,989 - vpcom - INFO - Traceback (most recent call last):
2018-03-16 12:19:00,989 - vpcom - INFO -   File "C:\P-ROC\tools\register_vpcom.py", line 237, in Run
2018-03-16 12:19:00,989 - vpcom - INFO -     self.game = klass()
2018-03-16 12:19:00,989 - vpcom - INFO -   File "Game.py", line 49, in __init__
2018-03-16 12:19:00,989 - vpcom - INFO -   File "C:\P-ROC\games\evildead\procgame\game\skeletongame.py", line 128, in __init__
2018-03-16 12:19:00,989 - vpcom - INFO -     super(SkeletonGame, self).__init__(machine_type)
2018-03-16 12:19:00,989 - vpcom - INFO -   File "C:\P-ROC\games\evildead\procgame\game\basicgame.py", line 41, in __init__
2018-03-16 12:19:00,989 - vpcom - INFO -     self.desktop = Desktop()
2018-03-16 12:19:00,990 - vpcom - INFO -   File "C:\P-ROC\games\evildead\procgame\desktop\desktop_pysdl2.py", line 72, in __init__
2018-03-16 12:19:00,990 - vpcom - INFO -     self.setup_window()
2018-03-16 12:19:00,990 - vpcom - INFO -   File "C:\P-ROC\games\evildead\procgame\desktop\desktop_pysdl2.py", line 186, in setup_window
2018-03-16 12:19:00,990 - vpcom - INFO -     sdl2_DisplayManager.inst().fonts_init(None,"Courier")
2018-03-16 12:19:00,990 - vpcom - INFO -   File "C:\P-ROC\games\evildead\procgame\dmd\sdl2_displaymanager.py", line 170, in fonts_init
2018-03-16 12:19:00,990 - vpcom - INFO -     self.font_manager = FontManagerExtended(font_path = font_path, alias=default_font_alias, size = size)
2018-03-16 12:19:00,990 - vpcom - INFO -   File "C:\Python27\lib\site-packages\sdl2\ext\font.py", line 193, in __init__
2018-03-16 12:19:00,990 - vpcom - INFO -     "FontManager requires sdlttf support")
2018-03-16 12:19:00,990 - vpcom - INFO - UnsupportedError: 'FontManager requires sdlttf support'

Share this post


Link to post
Share on other sites
38 minutes ago, luvthatapex said:

I found some info on this for you.

copy sdlttf.dll to C:\P-ROC\DLLS and try again.

According to the notes this file should be in  setupHelper.zip from the evil dead download

Yup, that's been done.

Share this post


Link to post
Share on other sites

I had an issue where this method gave me an error on each table start. Then I overwrite my setup with Ninuzzu' installer and that is how I run as of now.

If you open a cmd and go to c:\p-roc\games\evildead and run 'python game.py' does it start the dmd ?

Cleanup the log in c:\p-roc\shared and try again - does maybe the log tell you something that is usable ?

Share this post


Link to post
Share on other sites
On 3/17/2018 at 9:53 AM, Thalamus said:

I had an issue where this method gave me an error on each table start. Then I overwrite my setup with Ninuzzu' installer and that is how I run as of now.

If you open a cmd and go to c:\p-roc\games\evildead and run 'python game.py' does it start the dmd ?

Cleanup the log in c:\p-roc\shared and try again - does maybe the log tell you something that is usable ?

I went through and un-installed the install from Ninuzzu.  Installed using Horsey method, got errors and unable to launch CCC... Overwrote install with Ninuzzu's and able to run CCC and ED, but I get the R6034 error.  According to mjocean this error should have been resolved with an updated register_vpcom that was dated 01.28.17.  

Share this post


Link to post
Share on other sites

That is exactly the opposite of what I did. I had the A6034 error following Dave's setup and he told me again and again how to get rid of it. I was never able. Not until I ran the Ninuzzu on top was it fixed.

I'm sorry. I don't know how to help you on this. No sane output in the log ? And did the dmd start at all running Dave's setup ? You can ignored the A6034 error at least at first to see if the actual code runs.

Share this post


Link to post
Share on other sites
7 hours ago, Thalamus said:

That is exactly the opposite of what I did. I had the A6034 error following Dave's setup and he told me again and again how to get rid of it. I was never able. Not until I ran the Ninuzzu on top was it fixed.

I'm sorry. I don't know how to help you on this. No sane output in the log ? And did the dmd start at all running Dave's setup ? You can ignored the A6034 error at least at first to see if the actual code runs.

Yeah, after clicking out of the R6043 error the code runs and the game/dmd load.  I'll try running Ninuzzu again to see if it will help.

 

Ok, I was able to fix it... had to remove a path from my windows environment.

Share this post


Link to post
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now


×