Mike_da_Spike

I was still running on older version of PinballX (5.85, I can't keep up with Tom :P) I tested the External launch : 5.85 - works 5.86 - works 5/87 - works I enabled logging for DMDext and it is showing (for me), almost the same if I run a table for VPX: 2023-04-20 06:36:46.9771|INFO|DmdExt.DmdExt|Launching console tool v1.10.2 2023-04-20 06:36:47.0181|INFO|LibDmd.Output.PinDmd3.PinDmd3|Checking port COM1 for PinDMDv3... 2023-04-20 06:36:47.0181|ERROR|LibDmd.Output.PinDmd3.PinDmd3|Error: Access to the port 'COM1' is denied. 2023-04-20 06:36:47.0181|INFO|LibDmd.Output.PinDmd3.PinDmd3|Checking port COM3 for PinDMDv3... 2023-04-20 06:36:47.1441|INFO|LibDmd.Output.PinDmd3.PinDmd3|PinDMDv3 device not found. 2023-04-20 06:36:47.1441|WARN|DmdExt.Common.BaseCommand|Device PinDMDv3 is not available. 2023-04-20 06:36:47.1441|ERROR|DmdExt.DmdExt|No output devices available. PinballX has still my PinDMDv3 in use and DMDext isn't able to use it When I 'turn off' the real DMD for PinballX (by setting the com port in PinDMD.ini to a port that isn't used), DMDext is able to launch it. 2023-04-20 06:41:13.7244|INFO|DmdExt.DmdExt|Launching console tool v1.10.2 2023-04-20 06:41:13.7568|INFO|LibDmd.Output.PinDmd3.PinDmd3|Checking port COM1 for PinDMDv3... 2023-04-20 06:41:13.9186|INFO|LibDmd.Output.PinDmd3.PinDmd3|Found PinDMDv3 device on COM1. 2023-04-20 06:41:13.9186|DEBUG|LibDmd.Output.PinDmd3.PinDmd3| Firmware: REV-vPin-01014 2023-04-20 06:41:13.9186|DEBUG|LibDmd.Output.PinDmd3.PinDmd3| Resolution: 128x32 2023-04-20 06:41:13.9186|DEBUG|LibDmd.Output.PinDmd3.PinDmd3| Revision: 1014 2023-04-20 06:41:13.9186|INFO|LibDmd.Output.PinDmd3.PinDmd3|Colored 4-bit frames for PinDMDv3 enabled. 2023-04-20 06:41:14.0367|INFO|DmdExt.Common.BaseCommand|Added PinDMDv3 renderer. 2023-04-20 06:41:14.0438|INFO|LibDmd.RenderGraph|Setting up Render Graph for 1 destination(s) 2023-04-20 06:41:14.0560|INFO|LibDmd.RenderGraph|Connecting Pinball FX3 to PinDMD v3 (ColoredGray2 => ColoredGray2) 2023-04-20 06:41:14.0560|INFO|LibDmd.Input.MemoryGrabber`1|Waiting for Pinball FX3 process to start... 2023-04-20 06:41:14.0844|INFO|DmdExt.DmdExt|Press CTRL+C to close. Can you check if your logs shows a bit the same ? To enable log, make a copy of your dmdext.log.config (this config contains to log in a window) replace it with the config file I attached. Launching DMDext will now make a log called DmdExt.log Maybe with the info you provided, Tom can find the answer to this issue (that is bugging me for a very long time ) dmdext.log.config

Gotcha, i didn't have time today, but will trst it tomorrow as well. I have also fx3 launcher with batch files for dmd etc.

Is dmdext.exe starting when launching your fx3 table? Tom was busy to fix an issue that I (and properly other have) that the real dmd was not closing down properly and causes that it was in use. This normally happen with vpinmame, but same could happen with dmdext or flexdmd. I could see in de dmddevice.log (for pinmame), that it gets an access denied when using the device, maybe dmdext will show something in the window as well

At least I'm not the only one with pindmd3 issues now ...

You can upgrade pinballx, but also downgrade it as well. In the pinballx documentation that is shipped with pinballx, it will be explained. So curious if you can pinpoint which updat it broke (or is it working with 5.85 and did 5.86 break it?)

Thanks! I'm not at the cab now, but i have fx3 with a pindmd3 as well, so will check it tomorrow morning if I have the same. To be continued...

if @Tom Speirs adds new features to PinballX, @scutters and @Mike_da_Spike cannot get away with NOT updating DBM AND leave you with a product that will not work correct with PBX Why are NOT and AND uppercase ? Well, that's the extra function that Tom added for filters. Starting of Pinball 5.83, filters can contain not only OR , but also AND and NOT For DBM, we wanted to make it a bit easier, to not use the characters |(pipe), & and !. Within advanced search a search could already be don with the ' OR ' command as well (note that this must be in capitals and with spaces , to see the differences). But it now also can do AND and NOT. There are some rules that are explained in the PinballX documentation and Within the Database manager documentation. With DBm you can see directly the records that should match to your criteria (if you use the system filter) For example : All tables where display name contains '24' or display name contains 'Batman': If we just want display names that contains 'Batman' and '66' : If we just want display names that contains 'Batman' and '66' and not contains 'Original': AND and OR cannot exists on 1 line, but you can use them on multiple lines (but don't make it yourself too hard :D) (AND, NOT and OR can be replace with |(pipe),& and ! as well) All these queries can be saved as Filter as well and will be available in PinballX This was the biggest change Scutters and I did. We also fixed some minor bugs, updated 2 core components (JSON and MEGA) and properly some stuff we forgot already. A big thanks thanks to Tom Speirs for adding extra features to PinballX And also a big thanks to Scutters, who is helping with code and ideas to make DBM everytime better have fun with it

Can you please post your pinballx.ini and the log.txt where you launch a fx3 table?

@Tom Speirs can you check this ? On my test PC I have the same behaviour. it's the Startup video that is rotated during desktop mode. When doing the same on cabinet, the video rotation is fine, but not sized to the screen (I used a 1920x1080 video on a 4k screen)

Added it to the debug list (so we won't forget it). Tom needs to check this part

Updated documentation to PBX version 5.83 Custom filters (INI files) can now also support AND(&) and NOT(!) in the string Combination of AND and OR is not allowed, but a NOT can always be in front of a wildcard (*) See examples in the documentation : The following will show all tables where Stern is in the search criteria *Stern The following will show all tables where Stern is NOT the search criteria !*Stern The following will show all tables where Stern AND Gottlieb is in the search criteria *Stern&*Gottlieb The following will show all tables where Stern OR Gottlieb is in the search criteria *Stern|*Gottlieb The following will show all tables where Stern AND Gottlieb are both NOT in the search criteria !*Stern&!*Gottlieb The following will show all tables where Stern OR Gottlieb are NOT in the search criteria (This would results in all tables, as you search on NOT Stern OR NOT Gottlieb) !*Stern|!*Gottlieb

Sounds like a plan ! Put your focus on vpe, that would make me (and a lot of other people) happy. Thanks freezy for your hard work and all your contribution to the vpinball community

Started this week that it gave a message that db was not working, but now completly offline ?

Can you also create a screenshot of perfmonitor (or taskmanager), with high cpu usage.

I think I had the same issue last year. Just with 1 table. Launching voa vpx only showed it on my real dmd, but launching it via pbx gave me an extra virtual screen. I cant recall which table it was, and can't recall aither what I did to avoid this.

@Tom Speirs Could it be added, that the systems 'Launch before' and the 'Launch After' scripts can be overruled per table ? Not all the settings, but maybe just the Enabled option ? I like to have a 1 system for VPX, but I have VPX systems, that needs a launch before and/or launch after scripts. I now have different systems and can combine them via groups, but that doesn't show nicely in the systems menu. If it could be that "Launch before" and "Launch After" can be overruled by the XML, so it can be set per table, that would make more sense. Not sure If I'm the only for this, but I have tables that requires pup packs (and those need extra start and stop scripts), and also for P-roc tables (at this moment just 1 table, and bit of waste to use a complete system for it) Thanks

Can you set the log file to nightmare logging (within the settings app) ? That should give the exact ffmpeg command that fails

On the video it looks like a lcd screen, not a real one

I dont have a solution, but instead of goin back, yiu can download the 10.7.4 x86 zip file. If yiu extract this to a differrent folder completely, and launch vpinball.exe, you actuallo load the complete 32 bit version (with vpinmame etc from your original folder) And to my opinion, if you have drops in fps by using 64 bit, just use 32 bit

Yeah ... restore point (or backup) is maybe better. I didnt registrated the 64 bit! Only copied the config files and downloaded the latest zip and extracted that. I should not go to the route to go in the registry. I did that for b2sserver, and still not working correctly (but more people has that issue)

Try running RegisterDirectOutputComObject.exe from your DOF 32 bit directory

I checked again, and indeed some stuff works better, and I needed to put on my glasses at 5:00 am to see the "Save and restart" option. Edited the first post. Strike through the issues that are fixed nice job Tom

Didn't you create a new folder, and put the 64 bit files in it? I also noticed in your log: Go to your 32bit dof folder and run the register app again. Check the plugin if that is fine. Edit: I'm more awake now. Your first screenshot shows that it cannot find a specific file. During initializing of PBX DOF can be found, but when using DOF, it is missing a component. Your 2nd screenshot, the message shows that it would like to load a dll thats not supported. Not sure, but think the dof plugin is 32 bit and if you like to talk with dof itseld, it needs a 32 bit as well

DOF for PBX still works. I left my 32bit version of DOF on the same location. Created a new folder for DOF64. Checking my dof plugin for PBX is still pointing to my old (32) bit location: log file shows it initialized : 06:00:33.28 22-3-2023: Loading PlugIns 06:00:33.44 22-3-2023: Loaded Plugin:"DirectOutput PinballX Plugin" Version 1.5 By Swisslizard (modified by Mike da Spike) 06:00:37.07 22-3-2023: PlugIn: "DirectOutput PinballX Plugin" Initialized OK 06:00:37.07 22-3-2023: Using Plugin System Version: 1,5 and dof log file shows : 23.03.22 06:00:58.326 Best match for THE GOONIES NEVER SAY DIE PINBALL is GOONIES, THE (goonies). Match Value: 1 23.03.22 06:00:58.326 Probably not 'PF Back PBX MX' set up (properly) for GOONIES, THE 23.03.22 06:00:58.326 Game selected The Goonies Never Say Die Pinball (Update sent for PinballXMX) and showing in PBX (5.80) Hope this helps

No problem Tom. It's quiet here as well, but dont have much energy to sit behind pc or cab. But I will look this week again and report back