Jump to content

All my products and services are free. All my costs are met by donations I receive from my users. If you enjoy using any of my products, please donate to support me. My bare hosting costs are currently not met so please consider becoming a contibuting member by either clicking this text or the Patreon link on the right.

Patreon

If neither of those of work for you, you can donate any amount by clicking here.

Recommended Posts

Posted

Visual Pinball990 has encountered a problem and needs to close is the error I receive on all UVP back glass tables when exiting from VP in PinballX. The standard Microsoft reporting error window will pop up when exiting a table. I have tested 1.91 on every other type of back glass configuration and it affects only UVP.

This is disappointing because I was previously running version 1.7? and had none of these problems when coupled with my own scripts used to close back glasses, but this version creates this error and I was forced to install this version because the previous version expired.

Attached is my log file but I it doesn't reveal any errors from within PinballX itself. Brave Team (Industria 1985) is the last table played that crashed VP upon exit. It crashes every UVP table however and the UVP server may or may not close out if I wait long enough for the Microsoft error Window to close on its own and then return back to the wheel menu. I have verified this via CTRL ALT DELETE.

The other problem that is a bit of a disappointment is that I don't really have a powerful machine and I had it running really nicely previously but now I have to deal with a slightly bigger delay when rotating the wheel. I have everything unnecessary turned off in the set up. There is only the standard wheel logo, fixed back glass/table along with music files for each entry on the wheel and nothing more enabled.

log.txt

Posted

For now I have found a remedial solution to this problem of windows error reporting popping up when exiting a UVP table. I have completely turned off error reporting in Windows XP, however, if sometimes UltraVPServer.exe doesn't shutdown, this would still be a problem.

Posted

Sorry, I've never tested with UVP. I thought it was pretty much dead now and replaced with B2S?

There should be performance improvements in the latest compared to 1.7. What exactly is the delay you are experiencing?

Posted

Unfortunately some tables don't have a B2S backglass created for them so I am pretty much stuck with UVP on those particular ones. The other reason for using UVP is because UVP takes less resources so even if I wanted to use a B2S and considering my machine does not support two graphics cards (one for the table and one for the backglass), I have to install my tables so that I don't have ball and graphics stutter by picking the installation that makes this possible. There are some cases in which a particular B2S has not been programmed correctly to enable all the necessary scoring elements but the UVP version does. In some of these cases I have had to use UVP on these as well. For these reasons, I don't see UVP ever going away. The case for using UVP on older equipment will remain especially considering that B2S consumes huge amounts of resources when using a single video card due to it's flashing lights and solenoids, etc, and even turn this down doesn't help in many cases.

The delay I am experiencing is the the time it takes for the table image and backglass to appear while rotating the wheel. If I rotate and then stop at a particular table and then time how long it takes, sometimes I find that it will first attempt to draw images that I just passed by before drawing the one I am stopped at. This could actually be many seconds for it to finally catch up and draw the correct table and backglass.

Posted

The crashing sounds like its an issue with UVP itself. With newer versions of PinballX it cleanly exits visual pinball by closing the window. Obviously UVP cannot cope with it. So it would likely need an update to work. The changes in more recent versions of PinballX are to allow smoother wheel movements and animations on lower power cpus. I don't think your CPU even has more than one core though (that is even older than an Athlon right?) and that is an issue for PinballX. In order to support such an old CPU I would have to make changes specifically for it at this point so I am sorry but you may have to bite the bullet and upgrade your hardware or try HyperPin.

Posted

PS: You could probably fix UVP crashing or staying open with an auto hotkey script and disabling the exit key in PinballX. Again, I am sorry though but at this point I really can't help with the CPU.

  • 2 weeks later...
Posted

Ok, so in order to fully rule out other problems, I have tested my memory and hardware, and reinstalled all software. I have even upgraded to the next version of VPINBALL991. I have installed a script that closes UVP as well. Even with a script that closes UVP, I get the error: VPinball991.exe - Application memory error window (with or without the script, it doesn't matter). Only tables running UVP generate this error when a table is closed from PinballX. It is true I have an older CPU and an older XP machine (3 gb of memory) with a good graphics card running PinballX, but this problem of just closing VP without an error upon exit back to the menu should not take a super fast machine. There are no errors to be found in the PinballX log file because it is VPINBALL that is generating the error window and somehow it doesn't like the way PinballX is shutting it down when the UVP server is running as well.

This error problem started after graduating from 1.7? versions of PinballX. PinballX is still far superior to Hyperpin and when configured correctly along with certain XP services and features turned off, I do get acceptable performance even on my older machine.

Posted

I have set up a temporary upload on my own ftp site for testing the Faeton table that runs a back glass that is UVP. Go here and download it:

www.nyx.net/~sscrivan/UVP-TABLE-TEST.zip

There is a readme pdf file so you can set it up the way I have it and see if you get a VP error window or if the UVP server does not shutdown.

Thanks

Guest
This topic is now closed to further replies.
×
×
  • Create New...