-
Posts
1883 -
Joined
-
Last visited
-
Days Won
162
Content Type
Profiles
Forums
Events
Downloads
Store
Articles
Everything posted by scutters
-
It looks like Windows actually uses two text to speech engines (WinRT and SAPI) which probably explains some of the weirdness and differences we see in the voices listed. @wrd1972 have a look at this post https://stackoverflow.com/a/54680704 it explains things a lot better than i can and provides a possible way of getting the RT voices visible in SAPI. I haven't tried it, do so at your own risk!!!
-
Strange, I just tried Run -> C:\Windows\SysWOW64\Speech\SpeechUX\sapi.cpl to change the voice and that didn't change the voice in PinballX speech plugin. But when i went through Control Panel -> Speech Recognition -> Change text-to-speech Settings (Win10) it did change the voice in PinballX!... which doesn't make much sense, and weirder still i had less voices available to choose from. Now when i go back and open the sapi.cpl file again some voices are now removed, but any changes there are now reflected in PinballX as well. So i'd suggest trying to change the voice via control panel method and see if that works.
-
[RESOLVED] Playfield videos extremely washed out in PBX
scutters replied to MulletLife's topic in General
One thing that springs to mind is make sure in Nvidia settings that you have 'Full' dynamic range selected and not 'Limited' (under Display - Change Resolution in Nvidia Control Panel); and also under Video - Adjust Video Colour Settings; (don't know what AMD equivalent would be) -
Thanks, please note that you can just attach the files, it's easier for us to read and there's no need for you to take all the screenshots From what i can see though the Future Pinball launch parameters look suspect. Can you change them to; Parameters=/open "[TABLEPATH]\[TABLEFILE]" /play /exit /arcaderender /STAYINRAM If that doesn't work please attach (as files!!) fresh copies of your pinballx log.txt & pinballx.ini files.
-
Can you also attach your pinballx\log\log.txt and pinballx\config\pinballx.ini files Make sure the log file is from after seeing the issue. Thanks.
-
I did a quick test (i only let 7 or 8 tables record) and the order there was by game description / display name alphabetically (not by the table / file name). Maybe i didn't let it run long enough, but it did include a mix of EM & SS tables and decades but those properties didn't seem to have any effect on the order.
-
Dunno, read only pinballx.ini file or maybe it's corrupt somehow? Can you attach the pinballx.ini file and log.txt file in case there's something obvious there.
-
I've updated the attachment in the first post with the latest version & fixes (same version you already have so no need to update again). Thanks for your help!
-
Ok.. thanks for the extra info. The stats plugin showing later than the clock on game exit but then staying on when the clock doesn't may be the clue i'm looking for. Last test version for the day so hope this works, i've re-jigged some of the event code ordering on game exit.. (still not sure why i can't reproduce the issue but i guess it's just different hardware causing different processes to take different times)
-
Interesting, i can't see anything obvious in the logs or settings - and i'm unable to reproduce the behaviour. Even stranger that the stats plugin works ok for you! (it's very similar code for the display logic). Anyway, here's another version to try with another attempted guess fix; If that doesn't work then can you let me know what C:\Pinball\Scripts\VisualPinball\VPXKill.bat does (just if it does anything that might affect focus in windows)?. I guess it's just killing / cleaning up processes like b2s / pinup on game exit, but worth confirming. Please also try with the stats plugin deactivated in plugin manager just in case that's a factor somehow too, and also confirm if the behaviour affects all systems on table exit (FX2, FX3 etc) Thanks
-
Not seen that before.. can you attach your pinballx\config\pinballx.ini & pinballx\log\log.txt files along with the pinballx\plugins\PBXClock.ini and pinballx\plugins\PBXClock_log.txt files (all after running pinballx, exiting a game and seeing the issue). By the sounds of it you have the clock located on the playfield screen and PinballX 'covers' it after returning from a game, can you confirm that as well (press ALT+TAB and see if the clock is still running just behind another screen). Edit - Can you give this version a go as well (just extract and replace the file in the pinballx\plugins folder). Think i may have found something but i'm guessing a bit, and it would only be a factor if you're running the plugin with a 'rotated' option.
-
Looking at the image, not sure - but are you just hitting a limit of visible 'list' entries (like this feature request), and the VP*** just happen to be the last alphabetically so they are the ones that get missed out?
-
I've given the scenario a bit of thought and i tend to agree. As far as i can see the easiest way to achieve what @PcTeknic wants would be to use 'groups' of systems (pinballx\databases\groups). So adding each single table exe as its own system with its own launch parameters and launch before/after etc, but that would show still all the individual systems in the 'systems' list and the 'group' would only be visible from the 'lists' menu.... so the feature request would be to add an option / tag in system setup / xml to hide or show individual systems in the systems wheel, and then a similar tag in the database group xml to make that group visible in the systems wheel (and also hide it from the lists menu). Think that would work and be fairly flexible (it would work with other systems that aren't single table too), but there might be a better way i haven't thought of and i've no idea how many changes it would need in PinballX. Edit - one problem with the above i hadn't considered would be what to do about database group media (wheel image etc) if they were to be used as a system, where would PinballX store it?
-
So you want one 'system' that has multiple different single table executables? I think you'd have to use the alternateexe flag in the database xml to set the alternate executables for all but one game (which would use the default system exe). There's details in the pinballx documentation about the <alternateexe> flag. Sorry if i've misunderstood..
-
I think Tom would need an example video (and any custom loading gif files you might have added) if you wanted the problem on your setup with 'use playfiled images' looking into. But if you're happy with 'use loading folders' then i guess it's resolved for you
-
My gut feeling is that it's the path change to B2S server that is the problem - but that was changed before you saw the issue. So as a test you could try copying just screenres.txt and B2SBackglassServerEXE.exe back to the Tables folder (don't re-register B2S or anything, just copy those files for a test so they can be removed later without changing anything else), and see if that makes any difference in PinballX. Not sure what else to suggest unless you have experience using procmon to see what's happening under the hood when you run PinballX and the calls to vPinMAMELauncherx86.exe that PinballX uses to launch B2S files.
-
I don't normally use B2S in PinballX, but i just tried it with V5.94 and it worked for me I'm using V2.0 of B2S Server, with vpinmame 3.6beta (i forget the revision), and B2S is still installed in the Visual Pinball\Tables folder. Any chance you updated B2S server at the same time you updated PinballX, and/or did you move B2S to a new location (this was added as an option in V2.0 i think) - i'm not sure if PinballX assumes B2S Server is always located in the Tables folder as it always used to be.
-
PinballX allows you to have custom media (images or videos) for the tables as you browse, for most people they're just images or videos of the games playfield so you can view it before launching. It is that media i'm talking about (but you might not have got that far in your setup yet)
-
Is this using B2S Server in PinballX instead of backglass media?, can you attach your PinballX Log.txt & PinballX.ini files and let us know what version of B2S Server you're using. Thanks.
-
Good to know. Interesting that it causes such a slow down on your system, are you using a long 4k playfield video as media in pinballx or something? Maybe it is something @Tom Speirs can look at as it definitely causes an issue in your case. Not sure on that, don't know if the loading images are cached or not when extracted from playfield videos. I don't use that option either.
-
There does seem to be a delay in the log file after 'set plugin data', before the actual launch 09:17:51.62 2023/04/24: Set Plugin data 09:19:13.68 2023/04/24: D:\Future Pinball\Future Pinball.exe /open "D:\Future Pinball\Tables\Batman Joker Edition ULTIMATUM 1.04.fpt" /play /exit /arcaderender One my setup this step only takes 1 sec, and i have several plugins enabled. I'm not sure what PinballX is doing during that period on your setup, but a guess is maybe that's when it grabs a screenshot before table launch to use as a loading image. So one thing to try is in Settings.exe under General Settings -> Table Loading Media Mode change to 'Use Loading Folders' as a test. This would use a default loading image instead of a screenshot / video frame. If that doesn't help then as your hardware isn't high spec then maybe running 'PinballXLite' might be worth trying instead of PinballX.exe. (and yes, your FP launch parameters still need updating)