-
Posts
113 -
Joined
-
Last visited
-
Days Won
4
Content Type
Profiles
Forums
Events
Downloads
Store
Articles
Everything posted by mace
-
[APP] NukeLauncher - NukePA for (The Pinball Arcade)
mace replied to time299's topic in User Projects
AWM = actual Window Manager from Actual Tools........set a profile for a program, drag a crosshairs to the window, tick four boxes and that window will be border less - I also use it on the TPA main window as well as the DMD displays.- 252 replies
-
- The Pinball Arcade
- TBA
- (and 4 more)
-
[APP] NukeLauncher - NukePA for (The Pinball Arcade)
mace replied to time299's topic in User Projects
Yep cheers, I have Pinball FX2 running fine, DMD on separate monitor and AWM removing the border :-), I've also got AWM mirroring the DMD to my DMD display resized with no border on TPA with AWM too I was using the AHK solution but AWM is more elegant (at a cost)- 252 replies
-
- The Pinball Arcade
- TBA
- (and 4 more)
-
[APP] NukeLauncher - NukePA for (The Pinball Arcade)
mace replied to time299's topic in User Projects
Yep, I can get DX11 v1.40.9 to launch and it does shun NukePA :-) But this is not the Safecracker bug as my version has this fixed, this is the 'only damn well exists on my cabinet' bug where for some reason as you click through the interminable screens when you finally get to the selected tables screen with the big yellow button (the one where the table scrolls in the background) none of the controls are highlighted and they only come into focus with a left or right arrow press. It does not do this on my desktop, there it behaves immaculately so it would be good for someone else to tell me if I have an odd issue with my cab or my desktop is the only place where its working............ And AMEN to command line launches - if they allow for a separate DMD to save me mirroring the screen area to my second monitor that would be cool too...... And maybe even they may allow us to adjust the screen position natively, after all free cam mod does that now..... I'm beginning to sound like the kids, want, want, want.....that's it I'm sending myself to bed ;-)- 252 replies
-
- The Pinball Arcade
- TBA
- (and 4 more)
-
[APP] NukeLauncher - NukePA for (The Pinball Arcade)
mace replied to time299's topic in User Projects
I've not managed to get anything past 1.40.x working correctly, its not NukePA though for some reason on my cab when the selection gets to the table the large yellow start button in the middle of the screen is not selected - it only will go live if the right key is pressed. Gawd knows why that is, the older 1.3x.x version works fine and the new 1.40.x versions seem to behave on our desktop - who knows.... As for the DX11 build well that just ignores most of the keystrokes, you can hear the ding as they go in but plainly the window is not in focus so they are not being seen.... This is playing up my OCD no end.....- 252 replies
-
- 1
-
- The Pinball Arcade
- TBA
- (and 4 more)
-
Hmm, as a point of interest try running just VP and dragging the window onto your backglass screen. Then close it and run VP and see if that makes any difference - I seem to remember a post on that a while back.
-
No idea I'm afraid - there's nothing in your files that I can see as an error and if its just four tables (assuming you have others installed :-) ) it's probably the table and related files rather than the main programs or nothing would work I guess. Let me know if taking out the error selection helps.
-
Jannek, sorry you said a few tables were not working - this affected all of my tables so I assumed as you had some working yours issue may have been a little different.....see if the setting helps. Looking at your files the entries look fine - are the non working backglasses confined to one VP system enry of the three you are using?
-
I think that's it Dave, I'm running it from the VP entry section so the system type will be hardcoded to "1" by default - I just ran it up with TaskManager visible and VPauto is definitely running all the time the table is open along with Virtual Pinball.exe (obviously) and your VisualPinballExchanger.exe too. They only close when the table is exited. It's not slow loading, its really slow exiting, for some reason if you use Tom's <alternateExe> tags if another version of VP is used other than the default the tables hang for 23 odd seconds on close back to the selection menu. That's why I use your script, it shuts in three seconds and that's with my kill all script running hot on its heels too.
-
Right managed to sort out my issue properly by modifying Horsey's script which is linked in #2 above, it needed a couple of lines REM'ed out - don't ask me why though as I said earlier I'm no script expert but I am a patient fiddler - here's the modified script:- #Include, %A_ScriptDir%\xpath.ahk default_exe = VPinball991.exe PinballX_Config = C:\PinballX\Config\PinballX.ini ;Read PinballX config for paths IniRead, WorkingPath, %PinballX_Config%, VisualPinball, WorkingPath TablePath = %1% TableName = %2% SplitPath, TableName, ,, ext,, ; Add extra check rename for VP10 If ext = vpx { StringReplace, table, TableName, .vpx,, All } else { StringReplace, table, TableName, .vpt,, All } ; Read exe tag from xml, if no tag use default_exe databaseFile = C:\PinballX\Databases\Visual Pinball\Visual Pinball.xml xpath_load(dbXML, databaseFile ) ; need to read the existing xml otherwise xpath deletes all existing nodes exe := XPath(dbXML, "/menu/game[@name= . table . ]/exe/text()") If exe = { exe = %default_exe% } Run, %WorkingPath%\%exe% /Play -"%TablePath%\%TableName%" MouseMove, 200, 100 ;WinWait,ahk_class VPinball ;WinHide WinWait, Visual Pinball Player WinWaitClose, Visual Pinball Player ;WinClose, ahk_class VPinball ExitApp It looks like some form of delay??? Anyhow my tables now running flawlessly again and the script is once again allowing my tables to exit in 3 seconds rather than half a minute. Now if I could only work out how to mark these posts with [Resolved] :-) M
-
Hi Jannek, You can get that error with old .b2s backglasses and when there is no .dir3ectb2s file available - the first thing is to double check that those backglass files are named exactly the same as the table files that correspond to them. The second is to uncheck the error box in the setting I've indicated in the image attached (right click on the backglass to access these), it's a good idea anyway as it prevents tables without B2Server backglasses not running. M
-
Excellent point CP - it would help if I explained a bit more. You're right PinballX has nothing to do with the issue, in fact to solve it I'm using the default <\alternateExe> tag which TYom introduced in version 1.96/7 and it works perfectly apart from the hugely irritating 23 second exit delay whenever an alternative version of Virtual Pinball is called with the <alternateExe> tag.......which is the reason I was using Horseys script in the first place <sigh>. This one is a bit weird as using Horseys script as long as the plugin box is not selected in the B2Sserver settings the animated backglasses are displayed perfectly, but the second you tick that box the DirectB2S backglasses do not get displayed as the usual backglass image from the selection window remains stubbornly in place. I've even set the 'Use B2S in front end' flag in PinballX and that results in the B2s backglass being shown up until the table starts and then its back to the static one again. I'm not having much luck tracking this down at the moment, I'm no AHK script guru so it all plod and poke stuff - I'm guess it may be a timing thing. Would you share your script, it may help a bit... My VirtuaPlunger board died this week too, no reason just stopped working suddenly and when I went to reset it I found that it was red hot :-( Lucky Paul is sending me a replacement board at a reduced price (mine was out of warrenty) which is decent of him....
-
Sorted! I was using Horsey's <exe> solution to run multiple instances of VPinball because the supported <alternateExe> function in the program takes for ever to close a table, unfortunately the script outlined in his article here will not support the launch of any Direct B2S glasses: http://www.gameex.info/forums/topic/14632-multiple-exe-for-vp/
-
Here's an odd one, my cabinet has been running perfectly for some months now, all my VP tables have directb2s backglasses and they are named the same as the tables - and they did all work! I added a ledwiz and the DOF config tool recently and followed the setup to the letter, now however when I load up my tables in PinballX the static backglass image from the main table selection screens remains on view - the ledwiz and effects all work just fine but you can't see the directb2s backglass. I've tried shifting focus with ALT- Tab but that makes no difference. If I run VP outside of PinballX it works perfectly, in PinballX if I uncheck the 'use plugins' box on the DirectB2s server setting it works fine again with backglasses loading and animating happily but of course that stops the ledwiz effects. The folder locations and link shortcuts are right, the dll's are all unblocked and the b2s sever is properly registered - I'm stumped! The only thing I can think of is the server has a 'locate vp.xml' button but I didn't think that was necessary from the set up to work. I'm running a Intel 4570 with 8Gig of 1600 Ram and a Nvidea 680GTX, it makes no odds if I use Visual Pinball 921/991/P5 as soon as I activate the b2s plugin the backglasses stop appearing? Help me Obi Wan Spiers you're my only hope etc etc....
-
[APP] NukeLauncher - NukePA for (The Pinball Arcade)
mace replied to time299's topic in User Projects
Yep spot on, should have been 'Roadshow' no space - my bad :-)- 252 replies
-
- The Pinball Arcade
- TBA
- (and 4 more)
-
[APP] NukeLauncher - NukePA for (The Pinball Arcade)
mace replied to time299's topic in User Projects
Agree, I have the same issue - no keys sent to DX11. Additionally since I've just had the v139.7 update I've also struggled with the DX9 version on my cab (Win7x64/i5-4570/8Gb/GTX670) which now will only 'see' the key sends if Pinball Arcade is set to run in Full Screen Windowed mode which previously only affected my Win8 build. It would also be good if anyone knows how to get Red & Ted's Road Show selecting, at present no matter how I name it in the xml/nukepa.ini it will not select and sits firmly on Addams - this does not affect Xenon which selects perfectly, I'm guessing it's not supported yet- 252 replies
-
- The Pinball Arcade
- TBA
- (and 4 more)
-
PinballX Enhancements/Features Requests
mace replied to Draco1962's topic in FAQs, Guides, & Other Useful Information
Nope I'm still using yours but the Games Manager has no scruples about wiping out <exe>'s too HH. Whenever I have a memory slip and load some instructions or a flyer - bang the whole XML gets trashed. -
PinballX Enhancements/Features Requests
mace replied to Draco1962's topic in FAQs, Guides, & Other Useful Information
It would be very handy if the Games manager could be modified to stop it stripping out the <AlternateExe>, <SendKeysOnStart> and <SendKeysOnExit> entries which are so useful for those of us who want to simplify and automate the use of multiple program versions and extra script commands. -
Thanks for the kind comments, I'll put a full cabinet post together in the rigs section too as there are some parts of the build that I would like to share, in the mean time this is my special Pinball/Rugby mode :-) http://tinyurl.com/kl4wmdu
-
[APP] NukeLauncher - NukePA for (The Pinball Arcade)
mace replied to time299's topic in User Projects
I think that this may fix it for you, open the Pinball Arcade.xml file in the PinballX/Database/Pinball Arcade folder (or whatever yours is named) and add the following line as the last line of every entry: <SendKeysOnStart>{Sleep 8000}{Enter}</SendKeysOnStart> Thanks to Tom for adding the ability to use VB SendKeys this will give the extra 'Enter' keypress needed, note you may have to increase the 8000 to 10000 or 12000 and so on depending on the speed of your system. As Jeff indicated though please leave the NukePA.ini timings at stock until its all working, when it is you can drop the initial delay time there (15000) to (2000) and speed things up considerably.- 252 replies
-
- 1
-
- The Pinball Arcade
- TBA
- (and 4 more)
-
Thanks, I will when its all ready....eventually :-) In the mean time here's a short video clip I made for Phil who made the speaker panel: http://tinyurl.com/mnnqxhv ignore my wittering its a reasonable demo of Future Pinball and a Kinect set up.
-
Long post alert.... I've been hanging around the group commenting now and again since I started building my cab about six months ago. It's now mechanically complete and running three versions of VP, Future Pinball, Mame, FX2 and PBA. I've put in all the lights and hardware for force feedback and so on through a Ledwiz setup but I've not implemented this yet as I wanted the video running as smoothly as possible. I'm a bit of a perfectionist so I've tried just about every combo of Nvdia settings, Video settings per program and compatibility settings per program too no matter how much I changed this around (and we are talking about three months of tinkering) I could not get the ball flow in VP and FP as smooth as I really wanted......until this weekend. I'm running a three screen cab set up with a i3-4150 at stock, the DMD and backglass displays are handled by the Intel chip in my mobo and the main card a GTX560GT is handling the main screen, there 4Gb of very fast RAM and SSD's to hold the data. I have everything switched off in Windows 7 x64 so it only has to worry about pinball. Most of the wisdom on the site talks about disabling compatibility mode and there are several guide which indicate that this should be done in the individual program settings, I've found that on my set up this causes micro stuttering. If you are suffering with the issue try the following: - Back up your current settings first (always do this), the easy way is simply to use the snipping tool to grab snapshots of the various pages below - Set your Nvidea settings to stock, then change max pre-rendered frames to '1', ensure that triple buffering is 'on' and leave vsync to 'use program settings' - Enable Vsync in all VP and FP programs, in VP programs where available put '1' in the vsync and max pre rendered frames boxes . Then make sure that these programs compatibility settings do not have 'disable desktop composition' checked (you just need 'run as admin' and the correct 'run this program in compatabilty mode for....' selected) by right clicking their exe files. - Right click 'My PC', click 'Advanced System Settings', click the 'settings' button under the Performance section uncheck everything other than 'Enable Desktop Composition Mode' and 'Use Visual Styles on Windows and Buttons', apply changes close the window then open it again and uncheck any settings that have rechecked themselves (there are usually two) to ensure that only the two settings above are all that is checked. - (Optional) open the Service program by typing 'services.msc' in the run box under the Start menu and stop the 'Themes' and 'Desktop' entries then change their start properties to 'manual' - Reboot and give things a try On my set up this has resulted in nice smooth gameplay in FP, VP 921,991 & P5, PBA, FX2 and Mame (although the last three were never an issue). I'd like to stress that this is my set up only however I have built test tables in the programs, run frame rate lag analysis with help from the tech team at Microsoft where I work (note here: frame rates shown in the programs are not a measure of smooth video performance). Please note that this may mess up the older versions of VP - particularly VP8 in which case you will need to tick the 'disable desktop composition' settings in those programs compatibility settings. This is the first post where I've tried to give advice and I hope that it helps someone, I've had tons of assistance from the folk here so I hope this may pay a little of that guidance back.
-
PinballX Enhancements/Features Requests
mace replied to Draco1962's topic in FAQs, Guides, & Other Useful Information
I posted on this one separately here: http://www.gameex.info/forums/topic/14632-multiple-exe-for-vp/ and ended up using Horsey Horsey script which looks for a <exe>/</exe> switch in the database instead - it's a better solution for now as the tables using an alternate program now close in three seconds. Ideally I would rather go with Tom's native support to cut down on the additional scripting so once the timing is sorted I'll simply use the notepad 'replace all' command to change the tags back to <alternateExe>/</alternateExe> and then switch off the script in the run before option. -
[APP] NukeLauncher - NukePA for (The Pinball Arcade)
mace replied to time299's topic in User Projects
Hmm, looking at your video I noticed that you have an extra screen advertising The Addams Family, that was posted up back last Halloween so I'm guessing that the script that sends the key commands is missing one key press as that screen will need an {enter} to clear, in other words that screen is knocking out the key sequence. You may be able to see this better if you start NukePA from an elevate Dos prompt with the command: NukePA.exe "Table name" Jeff may be able to comment if it's possible to add a small .ahk script like: sleep 14000 send {enter} If this was compiled to enter.exe and placed in the [Launch] section of NukePA.ini like this [Launch] LaunchBefore = enter.exe LaunchAfter And the other NukePA.ini timings were left as default it may give you the extra enter you need one second prior to the normal NukePA.exe script taking over. ....or we ask Jeff if it's possible to do this a little more elegantly (I'm no expert in these things)- 252 replies
-
- The Pinball Arcade
- TBA
- (and 4 more)
-
PinballX Enhancements/Features Requests
mace replied to Draco1962's topic in FAQs, Guides, & Other Useful Information
It would also be good to understand the <alternateexe> switch too, if it uses the same parameters as the main program and why the programs evoked by the switch appear to pause for an additional 15-20 seconds on table exit. -
Yep it's a function of the PinballX code, tried everything else today from building an .exe to slam all the Vpinball.exe's and B2SServer shut when the tables close to modding the scripts to add No Launch and the exit lines in the B2SServer document - all no go. Ran it through a debugger cycle in the end. I will be patient until Tom may be able to get to this, the world will not end over a 20 second wait :-)