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 donating by either clicking this text or the Patreon link on the right.

Patreon

Carny_Priest

Elite Member
  • Posts

    916
  • Joined

  • Last visited

  • Days Won

    19

Everything posted by Carny_Priest

  1. db2s file names match the table file names? In your xml file are the hidebackglass tags set to False? You said many tables don't show backglasses in PinballX. But does that mean that some do show backglasses? Is there some difference that you can identify between tables where the backglass works and the tables where the backglass doesn't work?
  2. Just making sure, when you refer to B2S, you mean directB2S? Or are you talking about the older B2S executables such as Rosve's tables? If directB2S, then the file name should be identical to the table file name. PinballX leverages the command line parameters that VP supports. It launches the VP editor and automatically plays the table whose script in turn calls B2S.server which displays the backglass associated with the table. The one whose file name is identical to the table's file name. Sent from my iPad using Tapatalk
  3. Doesn't look like OBS Studio has support for designating different profiles to run. Then you would have to have multiple installations to manage simultaneous captures. I would not have much of an issue doing that for myself, but it's not a solution suitable to publish I think. Appears to be a low priority for the developers, as well: https://obsproject.com/forum/threads/are-they-any-shortcut-parameters.33385/#post-153345 The older classic version of OBS can load multiple instances with different profiles, but again, my playfield capture was black using Win10. So, going back to 0.657 is a no go. It would be possible to swap out ffmpeg with OBS Studio for the playfield capture engine and keep ffmpeg for backglass and DMD, but I'm not sure that I can get the output synchronized. At least not easily. That may not matter to most users anyway, so if people want to see it published then that's fine.
  4. The author has generated a bunch of media for MAME (vertical games):
  5. Thanks, TerryRed. I can confirm that OBS Studio 0.13.2 captures FP+BAM in Windows 10, so I am back in business. My script was only using OBS to capture the playfield and FFMPEG gdigrab for the other screens. Output videos were not quite synchronized. I'll see if I can just use OBS Studio for all screens and see if that's better. I'm not sure why you are doing multiple installations of OBS Studio. Can't you just run multiple instances from a single installation and designate the profiles that you want to use to capture different screens? Notes: OBS Studio added a lossless capture option as preset, but it appears to be just dumping uncompressed audio and video streams to an avi container. Even though I have an SSD, it's just a little much. I'm getting a lot of dropped frames. If you go deeper into the settings, it is still possible to setup a lossless compressed video capture via x264. Audio capture would then be lossy, but can still be done with HQ. I don't use audio in my previews anyway, so I simply disable the audio capture source. The advanced settings have an option for full color range which is good since in my experience partial color ranges seem to produce washed out reds/oranges. The LAV filters can handle full color range output where other codecs may not support it. I use DSR and downscale the playfield resolution. Right now, I have set up the capture at the increased resolution and scale down the output to 1920x1080. Still looks good. Capturing at 30 fps. I still have a transcode step where I rotate the output for display in PinballX and do some modest compression to get the file size down to around 10Mb. I'll work on updating the script this weekend. I've got a backlog of FP preview videos to create.
  6. Where tables appear in the PinballX menu is dependent on the entry in the description tag. The media files can be "linked" using either the description or the game name tags. Usually everything works fine if your media files are named the same as the description tag. Where the link is not matching correctly because the names are similar, I then rename the media files to match the game name tag and make sure that the name is unique enough not to cause a mismatch. There's more flexibility here. You can use anything you want in the game name tag and the table should still show up in the correct order as long as the description tag is correct. You just have to be sure that your table file name is also the same as the game name tag (has to be the same as the game name tag in order for PinballX to launch the table).
  7. Yes, you can edit Visual Pinball.xml manually. Media files are not deleted just because you edit the xml manually or using Game Manager or anything else. If you want to fix file matching for those problem tables like Fire! and Firepower, do the following: Leave Firepower as-is. For your example, Fire!, the description tag should remain Fire! (Williams 1987). The game name tag should be Hose (Williams 1987) or whatever you want. All your media files should match the game name tag. For example, wheel should be "Hose (Williams 1987).png", audio file should be "Hose (Williams 1987).mp3". Also, the table file name should also match the name tag, such as "Hose (Williams 1987).vpt". Just some selective editing of the xml and renaming a few media files only for your tables where there is a problem with file matching. Pretty easy.
  8. Has PinballX ever behaved correctly on your system when you have it start with Windows boot-up? Does it work if you log off of your user account and log back in? It looks like you get a five second delay for PinballX to start-up. I'm thinking that your system may require a longer delay. I don't think that there is a way to change this in PinballX, but you might be able to use a batch file or Task Scheduler or something.
  9. I tend to turn off File Matching because of mismatches. I think I'm better off manually renaming, especially if there a lot of tables. Seems like it would really be preferable where there are different versions of the same table to list in the xml.
  10. Well, you are going to have to be more specific. What big problems are you having after renaming? What, specifically, needs to be fixed? Need some detailed feedback if you ever expect to see any improvements in the program. XML tag and file name matching is not perfect, but I've been able to work around my issues. Of course, I tend to keep one version of a table and I use the table names in IPDB.org as the value for my description tag.
  11. Perhaps there is still some confusion with similarly named games. Programmatically, it might have been better to use IPDB numbers instead of table names but users even keep multiple versions of the same table (Night mod, Day mod, PM5, Color Mod, Toy mod, etc.). In any case, if you are using Game Manager to import your media it sounds like you will have to take the extra step of verifying media for tables with similar names and do some manual renaming as described above. Myself, I don't use the Game Manager. I edit my databases with Notepad and generate most of my own media. Everything else, I just download directly from the FTP or elsewhere so that I can check them out before I copy over to the PinballX\media folders. Hope this helps you at least work around some of the issues you are experiencing.
  12. You have System_2 assigned to "Pinball Arcade" and it is enabled. It uses the NukePA launcher. You also have the Pinball X built in support for "PinballArcade" enabled. If you have an xml database set up for both systems then Pinball X will display all of the games in your main wheel. Pick one system and disable the other. You would do this using the Settings Wizard and not Game Manager.
  13. Can you attach your log.txt and PinballX.ini files?
  14. Yes. It's even perhaps a bit too big and the image projecting on the playfield makes messages displayed on the bottom of the screen a little hard to read. Using native DMD resolution scaled times 2 with the backglass screen set to a supported resolution 1152 x 864. In other words, it is close to edge-to-edge.
  15. Hmm, don't know. You might try walking back some of the video rendering options in FP. If you set Texture Filtering to Trilinear then based on my experience you definitely need to switch to Bilinear. Try using Medium (Default) preset or using a lower resolution just to test. If you are using Aero try turning it off. Or if you are not using Aero then try turning it on.
  16. Yes, that'll happen. You'll have to do some selective renaming of files to avoid having the system get confused by similarly spelled description tags. Example: Rename the GAME NAME element in the xml, so that the spelling is no longer similar, such as "aPlayboy stern 2002". Then rename your vpt and media files to aPlayboy stern 2002.???. You description tag can remain Playboy stern 2002 and it will be located in the correct place on your wheel when you are running PinballX. Correct media will be displayed because of matching game name elements.
  17. Is the game running correctly when you run from the FP editor outside of PinballX?
  18. According to the ini you have Quit (PinballX) and Exit Emulator both set to Escape. My suggestion would be for you to change Exit Emulator to a different key. I use Q. Then you would need to remember to click on Q to exit FP back to PinballX instead of Esc. Note: I know that Q is supposed to bring up the BAM menu, but I always configure FP outside of PinballX. It's just been a habit for me to assign Q to 'quit'.
  19. Not sure. Have you tried setting hidedmd=False in your database.xml[Game Manager]?
  20. Find your PinballX/Databases/MAME/MAME.xml file. Make a copy of the file. Call it Arcade.xml. Go back to your MAME.xml and edit it. Clear all games and leave only the following two lines as the content of MAME.xml:
  21. Start by reading some documentation. Section 5.5 http://www.gameex.info/forums/topic/13736-pinballx-documentation/#entry137121 We'd still need your Pinballx.ini and your log.txt to give you any real help. http://www.gameex.info/forums/topic/6451-guide-how-to-ask-for-help/
  22. It's been a few years. At one point, I had set up a multi-monitor mame system with vertical games playing on a portrait oriented monitor and horizontal games playing on my old multi-sync CRT. I believe I had set up a separate ini for vertical games. That is, any games MAME classified as vertical in the source code would be configured using vertical.ini instead of the default mame.ini. You would define which screen to display on within the "PER-WINDOW VIDEO OPTIONS" section. You would need to know how Windows identifies your backglass screen. A quick way is too see what monitor is defined for your backbox in Future Pinball Preferences -> Video / Rendering Options. For me it is \\.\DISPLAY1 \\.\DISPLAY1 would be the entry for screen instead of auto I think, anyway. Like I said, it's been a while. Got my answers on Google like everybody else.
  23. I don't see anything in your Visual Pinball.xml. You have other systems that feed into your main menu wheel. I'd look for errors in your other xml files. Look around games that start with "Tr"
  24. Give us those and your Visual Pinball.xml file
  25. Here's some documentation. http://www.gameex.info/forums/index.php?/topic/13736-PinballX-Documentation/page__view__findpost__p__137121 Not entirely up-to-date, but the bits for managing subgroups (secondary wheels) should still be useful info.
×
×
  • Create New...