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.

soundasleep

Basic Member
  • Posts

    8
  • Joined

  • Last visited

Recent Profile Visitors

603 profile views

soundasleep's Achievements

Member

Member (1/5)

1

Reputation

  1. Solved! The issue was indeed the DirectB2S server. For some reason I had the default set to "Start in EXE Mode". Once I changed this back to Standard, the problem went away!
  2. I'm setting up a new PinCab and have come across an odd problem. About a dozen tables so far launch fine through Visual Pinball directly, but when I try and load them via PinballX I get a "Index was out of range" error relating to a line that is setting a B2S variable. If I go into the script and disable the "Controller Run" line, then it works fine (but with no backglass). Any ideas?
  3. Is there a way of delaying the loading screen? I've replaced it with one with a few additional instructions, but it's not staying on screen long enough to be able to actually read it!
  4. So after two days of practically not sleeping trying to get the automatic table loading working I finally had everything 100% and a strange bug shows up. The first time I load a table everything is fine - I play, I exit, it goes back to PinballX. But the SECOND time the backglass is in the wrong position (showing part of the desktop behind it). After a few more hours trying different solutions I found upon one that worked... Bearing in mind I load the EXE from within the AHK file, using the WinWait/WinActivate statements if you switch focus back to PinballX and then back to Pinball Arcade, the backglass is back where it should be. Not sure if anybody else has had this problem, but if you do, there you go. Once I've had some sleep and cleaned up my dirty code I'll upload my version of the AHK files.
  5. Tim79: I had exactly the same problem. The way I solved it was to add a Run "C:\blah\blah\PinfallFX2.exe" to the AHK file, compile it, and run that instead of running PinballFX2.exe first and then loading the AHK afterwards. Make sure the AHK has these the WinWait/WinActivate/WinWaitActive in the right place or the key codes will start before PinballFX2 is actually ready. Just make sure you add the [TABLENAME] parameter
  6. Two questions: 1. What software are you trying to use? 2. Did you deselect "Hide BackGlass" in the Game Manager?
  7. I've been playing around with these scripts tonight and have encountered a strange bug. I can use an AHK script to launch PinballFX2 from within PinballX without a problem. Backglass stays up and FutureDMD stays in place (it just stops showing anything until it returns to the PinballX menu). If I leave key scripting (the Gosub Table) off it works fine. When I turn it on, the first keystroke causes focus to switch back to PinballX. Any ideas?
  8. Overall I've had no problems setting up PinballX to work with Future Pinball and Visual Pinball, but I'm having a strange issue with PinballFX2. When you choose a table, PinballFX2 loads, but PinballX quits - so when you finish playing and exit PinballFX2 you're back at the desktop again. Has anybody else seen this sort of behaviour?
×
×
  • Create New...