funkyman

I figured that's why you rolled back versions. I've been testing/running on the "2.64 leak patch" you sent me (everyday since then) and it's been working great, no issues. However, I'm only using Visual Pinball 9/10 tables. I wonder if it's because of the Video Card / DirectX combo or just lucky since I didn't try anything fancy Either way, thanks for the work you put in!

No problem, not sure if it's helpful but I found this: http://www.vpforums.org/index.php?showtopic=31878 Seems like lowering the textures in Visual Pinball will do the trick! Good Luck, hopefully it's related!

Hey Topache, I'm actually running MJR's full expansion boards and his pinscape software without issue for quite awhile. It's odd that you're having issues with it, my guess is something else is conflicting. What are the fatal errors you're getting? it would help to know what they say, maybe screenshot them?

I'd have to agree! Nice!!! I've tested for over an hour with no crashes! Thanks for looking into this, It's odd but I'm guessing increasing the memory footprint since I was running at a high res cause this leak to be exposed! I'm just so happy I can now play in 4k without having to run a process scanner to relaunch if crashed!! Thanks Tom, you the man!

This time it happened a little sooner? Not sure if that helps! Thanks for working on this.

Hey Tom, Thanks for the update, I just dumped the exe into the usual location and ran it. I didn't notice a version change (still 2.64), but figured it didn't matter. yeah, still seems to crash after while. However, It seemed to take longer for it to happen this time. Here is the log: Looking at memory usage in windows system, it doesn't go above 6gb (out of 16). GPU memory doesn't seem to 2gb. I'm not even launching any tables, just opening the instruction cards!

Interesting, so it's not supposed to play unless a table sound isn't available? I guess I haven't seen this because I have table sounds for all my tables. What's odd is when exiting a table, and coming back to the front end, I'll hear the start up sound, but not the table sound (that worked prior to launching table). The table sounds don't start up again until flipping to another table. Then, of course, they play again when going back to the table that didn't play. Again, this isn't that big of a deal, I have way bigger problems that I'd like to eventually be fixed. I just wanted to know if this happens to others. Thanks!

Hey All, Now that @Tom Speirs fixed the startup sounds, has anyone else experienced this: PinballX Launches Default Start sound starts playing (I know this because I can hear a split second of it) Last selected table sound/music cuts in and plays instead, cutting off the start up sound. Also after exiting a table, and coming back I hear the startup sound play through to completion but the table sound doesn't play at all (this is an old issue, but still happens), until I switch tables via flipper. Then, after playing another table (could be same table again doesn't matter) once exiting, the start up sound doesn't play the rest of the session. Just curious if this is a common issue? It's not that big of a deal, but since the startup sounds were recently fixed I figured I should ask!

Thanks Outhere, I did update to the lastest version (2.64). However, still getting OOM in a bunch of situations. It's odd because I'm nowhere close to hitting a memory wall on GPU and system Mem. Guessing something else is going on! However, It's also apparent not a lot of people use 4k, but it's gaining popularity. The updated textures on the newer tables look amazing at 4k and it's tough to go back to 1080p. Fingers crossed Tom gets some 4k gear to test

Hey Tom, 2.62 fixes the exception handling again! Thanks and sorry it took a few days to post back. I have noticed I’m getting a lot more “out of memory” exceptions now. I can confirm the instruction card 4K bug I reported still happens but now it’s an OOM. Call stack looks similar to before (as you can see from my previous post). Here is with 2.62 I’ve pulled up memory for GPU and system but it doesn’t even come close to maxing out either. GPU (GTX1080) sits around 10% used and the system mem is around 30% in use at time of crash. Did anything change to your memory management system? My first thought is maybe memory fragmentation? but I’d have to differ to your knowledge about whichever system you use. Are you able to confirm if this OOM is shared or video ram? That might point to a clue. Thanks for your hard work as usual. Let me know the best way for me to contribute, even if it’s sending you callstscks and crash dump files.

Ah, well that would explain all the issues We need to get you some 4k gear! ...if you want, I can help you debug these 4k issues, that's literally what I do for a living! I have tried it, and I'm still crashing at the same places. However, the new version seems to have stripped out the callstack crash output in the log file. When I crash now (in 4k), by opening/closing the same instruction card multiple times, my log looks like this: I use to get: 15:17:18.5 2/3/2018: Started 15:17:28.1 2/3/2018: Error. Exiting 15:17:28.1 2/3/2018: Parameter is not valid. 15:17:28.1 2/3/2018: at System.Drawing.Bitmap..ctor(Int32 width, Int32 height, PixelFormat format) 15:17:28.1 2/3/2018: at System.Drawing.Bitmap..ctor(Int32 width, Int32 height) 15:17:28.1 2/3/2018: at Direct2D.Direct2d.Surface.a(Bitmap& A_0, Device& A_1) 15:17:28.1 2/3/2018: at Direct2D.Direct2d.Surface..ctor(Bitmap Image, Device Device) 15:17:28.1 2/3/2018: at PinballX.FrmMain.d(Boolean A_0) 15:17:28.1 2/3/2018: at PinballX.FrmMain.u() 15:17:28.1 2/3/2018: at PinballX.FrmMain.ap() 15:17:28.1 2/3/2018: at PinballX.FrmMain..ctor() 15:17:28.3 2/3/2018: Disposing Plugins 15:17:28.3 2/3/2018: Showing Taskbar 15:17:28.3 2/3/2018: Unhiding Mouse Cursor You can see the date is from the previous version, but you get the idea. Maybe this was by choice, but it certainly helped me isolate the issue and compare my crashes to other users. Thanks Tom!

Hey Tom, Great work, thanks for doing what you do!! Any chance the new version fixes some of the 4k issues? Like, instructions card crash: ...or the crash when exiting back from a table? Thanks for all your hard work! ...also let me know if you'd like to me to test anything, I'd be more than happy to be a guinea pig for testing fixes/features If I have to become a lifetime member to do it, I'd be glad to be able to help! Thanks!

Glad you got it working! So you forget a quote (") for passing the /play command for Visual Pinball X? Did you use the VPX default settings in the "other" section? Reason I ask, is that I just used that and didn't need to change any other settings and it worked fine. If you feel like it, you could also update the original post title with a "(Resolved)" tag so if anyone else has this problem they can get a quick solution, thanks!

Ah, so that does make some sense, at least we figured out where the B2s loads. Did you check for multiple screenres.txt files, that's where the screen number is held for b2s, maybe since the launch folder is pinballx it's using a screenres.txt from that location instead of your tables folder. The other thing I should ask is are you running 2 (or 3) monitors? Also, you could download (if you haven't already) the ScreenResCheck.exe from the downloads section, that will create a screenres.txt file but ALSO it'll load test images to see if it works from there.

This is quite strange, sorry I didn't get back to you yesterday. PinballX doesn't really do much after it loads Visual Pinball, it's just blacking out the screens and waiting for the exit button to be pressed to resume focus and display the front end again. I'm not sure what could be causing B2S backglass to not display when launched with PinballX. This sounds like it's putting the backglass on a different monitor than expected, you're seeing the blacked out screen that pinballX put up after launching a table. Do you have DOF and do you get output from any toys? (this will tell us if b2s is running but you just can't see the image) You've checked that just double-clicking a .VPX table in your table folder that the back glass shows? Do you have multiple copies of ScreenRes.txt around? If you do, make sure they all have the correct monitor in them. I could see issues if that was the case, other than that my only suggestion would be to post a video of the problem. That might provide a clue as to what's going on.