Jump to content
SpesoftPinballXConvert-It

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

scutters

Elite Member
 View Profile  See their activity

  • Posts

    2122

  • Joined

  • Last visited

  • Days Won

    190

 Content Type 

Everything posted by scutters

  1. scutters
    Was that using your PinballX install or your Fathers? (it may be configured differently) Please also attach your PinballX.ini file
  2. scutters
    Damn. Running low on ideas now! If you have Task Manager open on the backglass monitor (with stay on top set from system tray icon right click), on the CPU performance tab showing all processors (right click to change graph view) what does that show during the load, anything staying at 100%? Also what is your PinballX startup program pvpeh.exe doing, could that be a factor? (probably unlikely unless recently added) Edit - Also check your launch audio file first. Just remembered a previous issue with slow loading of a table due to a very long launch audio file (try to stick to a few seconds long)
  3. scutters
    Focus from the cmd line isn't an issue for that test, the thing that counts is how long it takes - and that was the same as from VPX, and a lot quicker than from PinballX for you (which uses the same command). It's not the DOF plugin so it must be something else, but not sure what. Have you added a new loading video for Dark Chaos?, maybe a large file there could impact performance enough to cause an issue if it was on the edge of maxing out before during loading. Might be worth trying a loading image rather than a video just to test.
  4. scutters
    It takes about 30 seconds to load for me from PinballX 6.87 and from VPX. log.txt @DJO Maverick Can you try opening a command prompt and seeing how long that takes to open the table for you? "C:\Visual Pinball\VPinballX_GL64.exe" /play -"C:\Visual Pinball\Tables\Dark Chaos (Original 2025).vpx" It might be worth disabling the DirectOutput PinballX Plugin in PinballX to see if that is causing an issue somehow as that is a difference in our PinballX configs. Not sure what else to suggest, but the load time in the log was definitely abysmal!
  5. scutters
    Please attach your PinballX config\pinballx.ini and log\log.txt files (after attempting to launch a table). I suspect it'll be something wrong in your launch parameters, but do the tables work when launched directly from visual pinball?
  6. scutters
    Thanks Tom. v6.87 still closing process well for me with 10.7 & 10.8 I didn't need to add or tweak the new ini key value, but just to be clear.. The new WaitForEditorClose key currently has to be added to the ini manually (i.e. not via Setttings)? When/if it is added, does it affect all Visual Pinball systems (i.e. those under 'custom systems' set to type 'Visual Pinball' as well as the standard inbuild Visual Pinball system)?
  7. scutters
    Thanks Tom, that's fixed the mismatch in exit times / killing between 10.7 and 10.8. All exited quickly now for me (on that non pup table) log685 test ver 10.7.txt log685 test ver 10.8 GL.txt log685 test ver 10.8 DX.txt
  8. scutters
    Hi Tom, previously i was unaffected by the slow/kill exit so i hadn't stayed on top of testing the new releases but it appears i now see the slow / killed process exit issue on releases after 6.81 (consistent on every exit). Nothing fancy with the table in the testing, no pup pack etc. log681.txt log682.txt log683.txt log684.txt log685.txt But, that's all using VPX 10.7 (some tables still need to). If i switch the system to use VPX 10.8 GL or DX versions 6.85 exits quickly with no kill log685 10.8 GL.txt log685 10.8 DX.txt Window titles are the same except the version number in use (10.7.4 shows as 10.7.3) and the log shows it finds the editor window in the slow exits as well so don't think it's that. It looks like VPX 10.7 and 10.8 just handle close requests very differently and the older method was great for 10.7 (and 10.8 for me), but the new method works for 10.8 only?
  9. scutters
    Good job Tom. All still working great for me (no idea why i didn't have the issues others noted). Bit cheeky, but while the exit code is still fresh in your head is there any chance you could look at this feature request. Basically, if possible, show the exit image immediately on the playfield when 'exit system control pressed' is logged while the exit takes place (just to avoid the two or three secs of black screen).
  10. scutters
    Wallace and Gromit using @endeemillr's backglass (right click and save as until pack updated)
  11. scutters
    I've had a look at this now, and i'm afraid the answer is a No from me (sorry!). Technically i could do it (with a lot of work), but i now realise it would make processing of images a lot slower too. This is because each frame is built using cached data of the original source image (and then maths is performed to plot new points of each pixel based on rotation, frame number values etc). To include a full wrap of the source image (not repeating the same image on the front and reverse of the ball) i'd need to alter the source image to take into account the frame number for each frame (for the wrapping), which in turn would mean that the caching wouldn't be valid and the app would need to loop through the pixels of every frame instead (which is a lot of pixels when producing multi frame apngs - and it'd be very slow) Basically, i just don't think the benefits of the option would outweigh the disadvantages. Hope that makes sense!
  12. scutters
    They should always be disabled if you have selected to use the DBM recorder option in settings (instead of DBM using the native PinballX recording functions) From the manual; DBM recording When using DBM recording (see Settings: Media Recording) , the options to create video, backglass , DMD videos and Topper videos are not able to be modified. This is because it will use the options you have selected in the Media recording tab. Including the screens you selected under Images! (See section 5.3.5 of the the documentation installed with Database Manager for more information)
  13. scutters
    Ahh, two GPU's!.. yes i think that is probably the cause in the mix up of numbers in recording. Different apps get different numbers from different places. What PinballX thinks the numbers are is probably different to those that ffmpeg uses. You might be able to adjust the primary GPU in BIOS somewhere to address the priority order - but not everyone is comfortable changing BIOS so don't even think about doing it if you're not (and as it sounds like DBM recording is [mainly] working for you anyway lets try and fix that instead) As well as the files @Mike_da_Spike requested can you also confirm if the 'Test' button in DBM recording settings shows the correct area for the DMD or is that cut off too?
  14. scutters
    Would it be possible? - Yes But not easily, it would need quite a big rewrite as i made an assumption early on in the development that having the full logo visible in the first frame would be preferred (and the 'reverse' side graphics were added later building into that same original design). I do have a concern that adding the 2:1 image for different font and rear images as an option might complicate the UI even more, but i'll have a look (with no promises!!!)
  15. scutters
    @piggei It looks like your monitor numbers are messed up (it happens!). You might be better off clearing some registry keys so that PinballX and Windows monitor ids get re-aligned (you may need to reconfigure PinballX after) See this post for details Windows Display Properties "Identify" numbers are incorrect – DisplayLink Support, reboot after deleting the registry keys to force windows to rediscover the connected monitors.
  16. scutters
    For whatever reason i didn't see 'process killed' issue and got consistent clean closes... so my tests may not be relevant, but here's my logs just launching and exiting the same table with different versions; log666.txt log672.txt logTest1.txt logTest2.txt (test 1 is the first version, 2 is the 2nd) All my exits were clean and took around 2.75 secs (from exit press to backglass created log entries). One thing i noticed was that the first test version appeared not to get the high score data.
  17. scutters
    Attachment in first post updated to V2.1.0 The mad Dutchman (aka @Mike_da_Spike) updates - Updated to .Net 4.8 and changed so it can launch a pinemhi challenge table in a different PinballX system (working path, executable and parameters should be exactly the same. Table path can be different). Enables you to split VP tables into different PinballX systems and still have a single challenge table entry in one system to launch the challenges with tables in other systems.
  18. scutters
    Bit more of a soak test today.. and all ok!
  19. scutters
    Thanks for the help Tom. In the end i found a code fix, issue was with showing the player window. Did update to FW 4.8 as well though. Attachment in first post updated to V2.2.0
  20. scutters
    Just tried 6.64 and good news, launched about 20 tables and all exited back to PinballX ok. The issue with 6.63 seemed random on when the issue would occur with table exit, so there is a chance i may have just got lucky with my 6.64 tests.. can we give it a few days before closing this issue off
  21. scutters
    Similar issue with 6.63 to 6.62, 1st table exited ok, 2nd exited but PinballX was not responding after that. log.txt (sorry forgot to disable plugins this time - but think i've fixed the media player plugin issue which caused a hang on PinballX startup)
  22. scutters
    Sorry, different issue with 6.62. Table launches ok and PinballX is still running, press exit and table closes ok but PinballX does not return (gets left 'not responding') log.txt
  23. scutters
    Getting issues with PinballX 6.61 hanging on the first table loaded, the table will continue to load but PinballX has died or is hanging in the background. Last line in the log is always the table launch parameters. Thought it might be plugin related so disabled all those and still have the issue. log.txtPinballX.ini I get the following in Event Viewer; EventViewerCrash.txt
  24. scutters
    Thanks Tom, appreciated. No luck changing bass.dll, but installed with win 8 compatibility and the plugin works. Pretty sure i need a code update at my end, leave it with me.
  25. scutters
    The plugin uses WMP Legacy so i don't think it's that. It's the plugin .net FW code somewhere that doesn't like the .net 8 owner or something, probably just one obscure .net function call. Just got to refresh my memory on how the code works for it again now, it's been a while..
×
×
  • Create New...