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. Thank you for your support. Tom Speirs

Patreon

OzStick

GameEx Lifetime Member
  • Posts

    4
  • Joined

  • Last visited

Recent Profile Visitors

560 profile views

OzStick's Achievements

Member

Member (1/5)

1

Reputation

  1. Hi All, As the title suggests, I got hold of a build on Win10 Ghost Spectre (v2009) and thought i'd give it a bash to see if it does indeed allow games to run faster, smoother etc. It gives you multiple install options so I went for Win10 Pro Compact with Defender. THe install went well and everything seemed to work correctly so I set about installing all the relevant pinball apps. I had been running an older version of PBX (v3.96 I think) so after installing VPX All In One, DirectX and a few other apps and utilities, I ran the PinballX install. I got the popup asking what language to install., left that on English then clicked OK. THe popup disappeared, then a few seconds later the mouse cursor flashed an hourglass next to it for about a tenth of a second, then nothing. I waited about a minute but still nothing, so I opened Task Manager but could find no evidence of the installation app running, either as an app or a service. I retried a couple of times with the same result then decided to go back and reinstall the previous version of Win10 I'd been using, on which the same version of PinballX installed no problems at all! Very weird....... Has anyone else installed a Ghost Spectre version of Win10 and been successful in installing PinballX? If so, please let me know whether I've done something wrong or forgotten a step. Equally, if you've used Ghost Spectre and had the same issues as me then please reply - maybe there's something its missing that can be allowed for in the PBX install to enable it to work correctly.
  2. Are you using the <alternateexe>YourVPVersionHere.exe</alternateexe> tag in your XML file for VPX tables?
  3. I have two enhancement suggestions: FIRST I'd like to have the option of storing media files in a user defined location, instead of PinballX generating a new "subset" of directories for each system added. For example, I'm running 4 different versions of Visual Pinball, therefore I have 4 separate media directory structure for all of them: C:\PinballX\Media\Visual Pinball C:\PinballX\Media\VP990 C:\PinballX\Media\VP_PM5 C:\PinballX\Media\VPX With the ever changing landscape of Visual Pinball in particular, it then becomes messy when updating to a new version of a table which runs in a different version of VP. Switching the table from one XML to another is one thing, but then having to do the same thing with media files seems like an unnecessary hassle. In short I reckon it's far easier to manage them all under the one directory. **UPDATE** - apologies - I just scanned back a few pages and noticed that apparently the slow exiting when using the <alternateexe> tag has been fixed in 2.12 which I have not yet updated to! I will test to confirm for myself and if it has indeed been resolved then this enhancement wouldn't be necessary! SECOND In PinballX\Media\Videos if the generic No DMD and No REAL DMD videos are present they override game specific DMD Images. It would be nice if the hierarchy could be changed so that if you have DMD Images, they show up instead of the generic video. As a further possible enhancement, include the ability to add a DEFAULT image and video file to the relevant DMD Media directories for each individual system so that they show up instead of the aforementioned generic videos.
  4. Using PinballX 2.01, trying to use the new <AlternateExe> tag so I can use a single XML file etc for VP. Now I find with tables using that tag, when quitting them to go back into PinballX they take an excessive amount of time to close - typically in the order of 15 - 20 seconds. If I swap those tables into the "version related" XML file and remove the <AlternateExe> tag (whihc is no longer required) then they close in a short amount of time as expected. Have I missed a setting or is there maybe something in the source code creating a delay when this tag is used? Here's the contents of my INI file just in case it's something I've done:
×
×
  • Create New...