5 replies to this topic

[GeeMo]

Sorry, doing this kinda backwards. I started with Future Pinball to experiment. Do you close the VPX editor down and reopen it before a new table is loaded? That is a must in FP thinking memory leaks. Don't see mention of this where you simply close the file only and open another table in the running editor. Testing, it seems to load new tables fine without bombing the app first. 

 

I found different executables in the file structure that launch different versions of VPX. One launches 10.7.4 and the other 'X64' launches 10.8.0. Do you guys use both for older/newer tables? I've used the 10.8 version thinking backwards compatible. Seems to work with no 'old version' prompts with newer games. Why retain two flavors in the files? 

[hmueck]

With VPX it's normally not necessary to close the editor between tables. Yes, sometimes something can go wrong and you have to restart VPX, but that's the exception.

 

10.7.4 is the latest "stable" version. 10.8 is in beta testing. That's why there are usually multiple versions in the folder.

[kiwi]

The frontends restart the VP app every time a new table is loaded, to avoid memory leaks.

 

The tables with the ROM are the most delicate ones because the VPinMame is also involved.

A typical problem that can occur after opening multiple tables is the lack of ROM sounds.

 

If I load a huge table, and then when I load a second one the crash is almost guaranteed.

[GeeMo]

Thanks guys, that's answers (most) of my top puzzlements.

 

Still looking at ROM interactions. Seems newer tables are requiring 10.8. Okay, different flavors for Devs and tables but seeing some tables also requiring VpinMame change to 3.6. Have seen some strange stuff like a giant ball size in Bad Cats (VPW) ver., or other oddities with tables. Seeing they need the 3.6. The steps to upgrade VpinMame files also lead to DMD X64 patching as described in Github docs. Are these 'upgrades' backward compatible or inviting bugs? 

 

Thinking many upgrade the whole enchilada with 10.8 VPX ver., VpinMame to 3,6X, and/or required Freeezy/DMD files. I don't use DOF. This is a simple two-monitor cabinet. Hoping to play new and older gen tables. Seems like the ROM interaction is a big deal. Mismatched versions or the wrong Mame engine with everything else patched could be the issue I'm chasing with newer tables.  

[htamas]

I'm currently running pretty much everything with the 64-bit latest VPX 10.8 release candidate (RC3), VPinMAME 3.6-929 (take sc for DMD colorization) and latest Freezy DMD, FlexDMD without any problem.

[anthias]

Some vp9 tables have graphical glitches if you don't close the editor and open a fresh one, but I've not seen the same in vpx.