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

Patreon

If neither of those of work for you, you can donate any amount by clicking here.

qcol

Basic Member
  • Posts

    54
  • Joined

  • Last visited

Everything posted by qcol

  1. I'm sorry, of course correct <menu></menu> it's there. I made a mistake above. The MAME item is in the menu there even though it is empty
  2. I want my MAME games not to appear in the All Games list. They should be only available if you select them from the list. I did as shown in the PinballX_S2F_Documentation rev 1.3 (page 63). So I created files: MAME -- MAME.xml -- MAME-arcade.xml MAME.xml <mame> </mame> MAME-arcade.xml <menu> <game name="1941"> <description>1941: Counter Attack (Capcom 1990)</description> <rom></rom> <manufacturer>Capcom</manufacturer> <year>1990</year> <type></type> <hidedmd>True</hidedmd> <hidetopper>True</hidetopper> <hidebackglass>False</hidebackglass> <enabled>True</enabled> <rating>0</rating> </game> <game name="1942"> <description>1942 (Capcom 1984)</description> <rom></rom> <manufacturer>Capcom</manufacturer> <year>1984</year> <type></type> <hidedmd>True</hidedmd> <hidetopper>True</hidetopper> <hidebackglass>False</hidebackglass> <enabled>True</enabled> <rating>0</rating> </game> </menu> I don't know why, but both items appear on the list. Both MAME and MAME-arcade. Why does MAME appear when it is empty? If I delete MAME.xml - then neither one or the other item appears.
  3. I have a problem with files that have an apostrophe in their name. Game manager still detects them as new games because the previous name changes to "character entities". I'm removing the version with character entities but the problem returns (over and over again).
  4. I think the problem has been solved. Probably because of TeamViewer. Since I uninstalled it and replaced it with Anydesk, the problem has disappeared. The position of the VPX window is remembered and now it always starts from the Playfield screen. I will be watching, but it looks like it is already OK.
  5. I understand.... You confuse the day with the month https://en.wikipedia.org/wiki/Date_format_by_country
  6. I don't see anything strange here? https://time.is/pl/Poland
  7. Black background doesn't upset me so much (although it could display video there until the animated B2S window is loaded), the worst as the VPX window appears on the backglass instead of being hidden under the "loading" screen on the playfield. I know that this is not directly a PinballX problem (rather Windows) but I don't know why, the VPX window still returns to backglass None of you had a similar problem?
  8. log.txtPinballX.ini
  9. I don't know if it's a feature request. What does it look like in your case? Do you also have a black screen on the backglass while loading the game? Maybe everyone has it, but it only bothers me?
  10. I know this option, but it seems to me that running real backglass should turn off pinballx menu video. Leaving it in the background always unnecessarily loads the system.
  11. Hi When I run the table, on the playfield I have a beautiful loading image, but bad things happen on the backlass. The backglass gets black until the game is loaded, when it starts B2S. What to do to keep the backglass video until it is replaced by the B2S screen? Besides, the VPX window still runs on backglass, although I regularly drag it on playfield, it returns to backglass. Then it looks terrible on backglass when loading the game. What to do?
  12. qcol

    Recording problems

    Tables run on this configuration quite smoothly so for the recording itself I will not change the hardware, I prefer to arm myself with patience You're right, I've learned that it's better to record from the game manager because some tables don't react to the recording key during the game (in my case, e.g. Dr. Dude).
  13. qcol

    Recording problems

    Maybe it is not a rocket, but not 486 Intel(R) Pentium(R) CPU G4400 @ 3.30GHz, 3300 MHz / 8GB RAM / GeForce GTX 660, NVIDIA I wonder where this difference comes from at different tables.... It is possible that the dynamics of animation is important here (more details to compress?) Today it took 8 minutes to make a video for Monster Bash
  14. qcol

    Recording problems

    I still have a problem with recording (recording set to "GPU driver") It happens that recording works completely correctly: immediately after pressing the recording key the voice "capture start..." appears and after about 4 minutes the game returns to the menu with recorded playfield + backglass material. In the log file it is correctly recorded. But often (I can't find the rule) there are such cases: 1. recording key does not work at all, pressed several times - no reaction (no entries in the log file), need to exit and run table again 2. the key works but with a long delay, after pressing it there is no reaction, after waiting about a minute the voice "capture..." appears. (if pressed several times, the "capture video..." voices overlap) 3. only playfield is recorded: in this case, if I try to record the video a second time, sometimes after pressing the recording button it returns to the menu immediately (in the log file there is information that the playfield already exists). When repeat operation - everything is OK... backglass is recorded correctly. example (Exit System Control Pressed?? nothing was pressed ) 4. Sometimes it works but nightmarishly long, I don't know then whether to interrupt the action or wait (if other recordings are done in max 5 minutes)? Here is an example where it lasted 1/2h. Playfield = 30 minutes Backglass = 1 minute
  15. OK, thank you... I will try. It's not very troublesome because it happens only when you leave the game, I can live with it
  16. Hi Very often, when exit from any table to PinballX menu I get error: I didn't notice the same thing happens when I leave the table directly from VPX. VPX 10.6 beta rev 3660 32bit PinballX 3.34 32 bit What could be the reason?
  17. qcol

    Recording problems

    In fact, you are right! I should first look at ini and check if there is no such option. Thank you! Now the video generation time is reduced and acceptable. Thank you all for your help - the topic to close.
  18. qcol

    Recording problems

    And here was the problem! Thank you very much! Well, we have already clarified the first misunderstanding Step forward I was sure that the shortcut "grab videos" applies only to FFMPEG recording with a fixed recording time (e.g. 30 seconds). If you set up "Use GPU capture", I thought the start/stop shortcut would take effect from that moment. Forgive me, but the only documentation I found was this one, and it's probably from 2013 and there's nothing about video recording in it at all. The problem of long waiting time remained, however. As I read from the logs now, it works in such a way that PinballX still uses FFMPEG to rotate the video made by Geforce Experience. And that's what takes a very long time. Probably by the high resolution and not the newest GPU. And this is where the option of recording shorter than 30 seconds would be very useful. Personally, I would be satisfied with 10 seconds (which would mean about 3 times faster video processing).
  19. qcol

    Recording problems

    If the screen number does not have to be equal in Windows - OK, then I understand. However, with this setting where backglass is to the right of playfield, the offset is set to 2560 (playfield width). It works correctly for me, B2S Server displays everything correctly. Only if it was above Playfield it would have offset = 0? Isn't it?
  20. qcol

    Recording problems

    It is more strange to me that in PinballX I had to reverse the screen numbers. What in Windows is screen #1, in PinballX I had to set it as Display2 (and vice versa). Only with this setting it works properly for me.
  21. qcol

    Recording problems

    Yes. Playfield on the left, backglass on the right side. It was due to the fact that I also tried other front-ends.... in the documentation of one of them was written: I thought this was a general rule for every front-end with multi display set. Of course, if this would help in something, I can set it above playfield with no offset.
  22. qcol

    Recording problems

    OK, maybe I will try to explain it differently. I attached Geforce Experience settings and 2 ways to set PinballX and what happens when you press the defined F9 key. 1. Use GPU capture = No, Driver Record start/stop key empty, Driver Save Path empty. I start PinballX, then any game. Result of pressing F9 key: green icon informing me about start and end of recording. Video was recorded in the set path D:/PinballX Records. Playfield only. 2. Use GPU capture = Yes, Driver Record start/stop and Driver Save Path set as in Geforce Experience. I start PinballX, then any game. Result of pressing F9 key: green icon informing me about start and end of recording. Video was recorded in the set path D:/PinballX Records. Playfield only. Nothing else has happened. So I still don't understand this setting in PinballX if nothing else happens. Forgive my questions but I really miss the documentation with the description: what should this option give? What should be the effect of this option. Now that I can't see any difference in action, I just get lost.
  23. qcol

    Recording problems

    But Geforce Experience to record movies does not need to set anything in PinballX. If I set the recording folder in Geforce Experience and assign the start/stop recording hotkey, it works globally in Windows. Even if I do not set anything in PinballX, the recording this way will still work (starting the game with PinballX). Setting it the second time in PinballX doesn't give anything, hence my questions why to do it? Sorry, but probably I still don't understand something
  24. qcol

    Recording problems

    Why should there be a problem with GTX when Geforce Experience does it smoothly and immediately? Doesn't this mean that the problem lies somewhere else? The only problem with Geforce Experience is that it only records playfield, and in addition upside down (although I know how to deal with it).
×
×
  • Create New...