-
Posts
1883 -
Joined
-
Last visited
-
Days Won
162
Content Type
Profiles
Forums
Events
Downloads
Store
Articles
Everything posted by scutters
-
Sounds like a classic focus issue.. Is it all tables or just some? Attach you ini file and log.txt after launching one of the tables that has the issue, and please also confirm if pinballx or visual pinball has any windows compatibility settings set in file properties.
-
I don't use FP so can't show you mine... but check this post - https://www.vpforums.org/index.php?showtopic=46528 The launch before command you need will depend on the type of DMD you use (virtual or real etc) and also install locations - so if someone does post their settings it may not work on your setup (and we don't know what that is - always attach your log.txt and pinballx.ini files!)
-
Are you using buttons or a keyboard when testing, is it the same behaviour with both?
-
[RESOLVED] Another Non PinMAME tables (GOT/CCC) - Focus issue
scutters replied to Schreibi34's topic in General
Good find. I've often wondered about if i turned off full screen optimisations in compatibility settings if i could get a bit more FPS, but i think it would come at the price of a lot of screen flickering when VPX started so never got round to trying it. Probably best just not to use compatibility settings. It would be a nice thing to have, but just change the topic name -
That was one thing that jumped out at me, the only other thing i can see is that in your pinballx config you have Left and Capture Videos mapped to the same key code (V) - which is pretty odd and i assume must not be intentional, maybe that confuses ledblinky somehow(?) I'd try changing the capture videos key and reverting your changes to LEDBlinkyControls.xml to see if that helps.
-
Is your LEDBlinkyControls.xml correct? You have sections for PinballX with P1_BUTTON8 mapped rather than 'LEFT' <frontEnd fename="PinballX"> <controlGroup groupName="DEFAULT" defaultActive="0,0,0" defaultInactive="0,0,0,0" ledwizGlobalPulse="3"> <player number="0"> <control name="PAGELEFT" voice="Page Left" color="Orange"/> <control name="PAGERIGHT" voice="Page Right" color="Orange"/> <control name="SELECT" voice="Select" color="Blue"/> <control name="RIGHT" voice="Right" color="24,0,24"/> <control name="P1_BUTTON8" voice="left flipper" color="Lime"/> </player> </controlGroup> </frontEnd> <controlDefaults groupName="PinballX" description="Default voice only used by LEDBlinky Controls Editor."> <control name="QUIT" voice="Quit"/> <control name="LEFT" voice="Left"/> <control name="RIGHT" voice="Right"/> <control name="SELECT" voice="Select"/> <control name="ROTATE" voice="Rotate"/> <control name="PAGELEFT" voice="Page Left"/> <control name="PAGERIGHT" voice="Page Right"/> <control name="EXITEMULATOR" voice="Exit Emulator"/> <control name="SCREENSHOT" voice="Playfield Screenshot"/> <control name="SCREENSHOTBACKGLASS" voice="Backglass Screenshot"/> <control name="INGAME" voice="Game Pause"/> <control name="INSTRUCTIONS" voice="Instructions"/> <control name="VOLUMEUP" voice="Volume Up"/> <control name="VOLUMEDOWN" voice="Volume Down"/> <control name="P1_BUTTON8" voice="left flipper"/> </controlDefaults> *** Note/disclaimer - i don't use LEDBlinky so please backup your files before making any changes based on anything i say, it might be garbage **
-
Not really sure what you mean by that... but hey, glad you got a workaround going!!
-
I think how B2S works is it'll look for a tablename.res file first, then use the screenres.txt file if that isn't found. So keep the screenres.txt file for your default settings. That would need to be a feature request (https://forums.gameex.com/forums/topic/22259-pinballx-enhancementsfeatures-requests/). There is another option though but it would require some work as well, create different systems in PinballX for each of your subfolders and set the Tables path for each system to the subfolders you have.
-
Just to be clear - you've moved a table back from a subfolder to the main 'tables' folder, and then created a tablename.res file in there as well? If you launch the table from VPX does the tablename.res file have any effect on the backglass then? (i know this is a bit off the off topic from the first post about using subfolders and more of a B2S topic now, but if a workaround can get you by then it's a result. If the B2S tablename.res file doesn't work from VPX then i'm afraid that need raising as an issue on vpforums or github)
-
Hmm, not sure on that, it should do. Think that functionality was added recently to B2S Server so maybe you need to update?
-
Not that it helps for the use of sub folders (i've never tried that either), rather than using subfolders (and i assume a different a screenres.txt file in each) could you use the ScreenResTemplates to create tablename.res files in the same folder instead? (see https://github.com/vpinball/b2s-backglass) - might be a workaround for you.
-
[RESOLVED] Help Me Obi-Wan Kenobi, you are my only hope...!
scutters replied to ComputerMan's topic in General
It's the fat fingered Denglish when you try to type on your phone that i struggle with! Ok, so a 2nd hand cab with tables and software preloaded by the previous owner then, in which case yes there will be a learning curve if you want to keep things updated and add/remove stuff. For your systems Visual Pinball is VP 9 so can maybe be disabled as most tables are now available in VPX (VP 10) and will look and play better. VPXPup is probably just VPX tables that use 'pup packs', where videos are played on the backglass during game play. All the systems will have their own settings and configs as well as PinballX. Sorry, lots to learn and even more stuff to tweak! My advice would be to concentrate on VPX first as it has most tables available (and many people would say is also the most realistic pinball emulator). Always good to have more Yorkshire on the forum! -
[RESOLVED] Help Me Obi-Wan Kenobi, you are my only hope...!
scutters replied to ComputerMan's topic in General
If the screen locations are correct in PinballX, and the issue is only with the backglass after launching a table then that points to an issue with the screenres.txt file (changing monitors around messes with windows id's). From https://www.vpforums.org/index.php?app=tutorials&article=136, this is what the screenres files contents mean; 1920 <-- Playfield screen X resolution (width) 1080 <-- Playfield screen Y resolution (height) 1280 <-- Backglass screen X resolution (width) 1024 <-- Backglass screen Y resolution(height) 2 <-- Display number for the backglass monitor 0 <-- offset for the backglass on the selected display (normally left at 0) 0 <-- offset for the backglass on the selected display (normally left at 0) 600 <-- Width of the DMD area in pixls 200 <-- Height of the DMD area in pixels 1280 <-- X position of the DMD area relative to the upper left corner of the backglass screen 0 <-- Y position of the DMD area relative to the upper left corner of the backglass screen 0 <-- Y-flip, flips the LED display upside down The bottom few entries aren't relevant to you as you have a 2 screen setup without a dedicated DMD. The 3rd,4th and 5th entries are the ones you need to check / change (mainly the display number - try 1 first, but the backglass resolution set in PinballX is 1280x1024 but 1366x768 in your screenres file). -
For anyone having problems using pbxrecorder after updating the B2S Backglass program to the newest version please see this comment about removing comments from screenres.txt - https://www.vpforums.org/index.php?showtopic=33552&p=512834 Sounds like the pbxrecorder ahk script will need updating to ignore the comment lines as a proper fix
-
You wouldn't be running a 'flipped' orientation in windows would you?. Think i had similar issues with my old screen before changing it and swapping the screens orientation round at the same time. Can you post your screenres.txt and pbxrecorder log file in the pbxrecorder thread?, might be something someone can fix in the ahk script.
-
Apparently the latest version of ffmpeg grabs the screen at a lower level, so should now be able to record future pinball media too. I don't have FP loaded anymore, but if someone wants to try it then please let us know / confirm if it works ok with pbxrecorder (you will need to amend the ahk script to pick up FP systems as well as VP)
-
[RESOLVED] Another Non PinMAME tables (GOT/CCC) - Focus issue
scutters replied to Schreibi34's topic in General
@Schreibi34Do you run VPX in exclusive fullscreen, and if so if you turn that off do does GOT then launch without any focus issues (as it does for @grunger)? If i had the issue i'd be tempted to play around with the GOT table script too, maybe move the DMD_Init call to the top of the Table1_Init (to try force the flex dmd to initialise before the table). That might help. -
Flagged as resolved already so i guess the answer was found (in the documentation? ), and yes there are a lot of options to do what you want. I'd agree active filters are probably the easiest and most flexible (especially if using database manager to build the filters - see bottom of this post https://forums.gameex.com/forums/topic/23840-app-pinballx-database-manager-2211220-supports-touch-play-and-pbx-w7vista-version-as-well/?do=findComment&comment=201644)
-
Keyboard Input Settings Dialog Box Closes Too Soon
scutters replied to MarkyMarkUK's topic in General
Any chance you have a button stuck? that could cause that issue for key and joystick input screens if you have joystick to keyboard mapping software running. -
V2.1 Released & attachment updated in 1st post with changes as shown in change log. Thanks @Mike_da_Spike for keeping me busy!
- 96 replies
-
- 1
-
- plugin
- statistics
-
(and 5 more)
Tagged with:
-
PinballX Enhancements/Features Requests
scutters replied to Draco1962's topic in FAQs, Guides, & Other Useful Information
@Tom SpeirsThis would be for plugin code, something like Event_MenuShown and Event_MenuExit would be useful. The nearest i've found is using the Event_Input and checking the PinballXStatus flag but there's issues with that as the flag doesn't change while the menu is exiting (it has changed on the next input event), and the menu can also exit without user input on attract mode start. -
I guess you killed PinballX in taskmanager then rather than exiting out?. As Mike says, the mouse is restored during PinballX exit.
-
@dielated the windows feature to turn off if you don't have a low disk space issue is 'storage sense'. That should resolve the wheel issue. For the exit game issue can you post a screenshot of your visual pinball key / button config screen and let us know what button (number) you use to exit a game. Also, is it only some games that you can't exit out of, but some exit ok?
-
You're still on a very old version of PinballX Try installing the latest version (even if just to new a different directory just to test)