How do you get to edit table to make adjustments? Every time I just try to edit it crashes. Thanks!
So, here's what you need to know as well as why the issue is occuring. Hopefully this information will help everyone use this knowledge to apply to other situations in the future that might involve the same settings or concepts even if you can't just step by step follow this same procedure.
First off this isn't a "fix" to your system, but rather a workaround to deal with a flaw elsewhere (re: human litography if you get my jist).
32-bit applications (like the current vpx executable) have a memory limit. So even if your system has 64 gigabytes of ram, the VPX app can still run out of memory and will, as a result, crash. When you go to open VPX, a file-> open dialogue will appear. The box that people are being told to uncheck literally just determines whether this file-> open dialogue box appears on launch. It won't fix anything else to uncheck that box. Determining whether this initial file open displays when launching the VPX exe directly is ALL that that option does. It will have a negligible draw on performance otherwise. That being said, the file-> open box that opens on launch won't just "open" the table, but will immediately attempt to play the table after it loads into memory. Since you most likely are either directly launching a table or want to get into VPX to open a table and edit it (Without playing it first), it is a good idea to disable that by going to preferences -> ui/editor and de-selecting the last check box (right above grid size).
In this case, because of file limitations of 32-bit applications that this table doesn't conform to, the table will most likely crash on most systems WHILE loading into memory. (It may work for some, and for me does work inconsistently, but when it does load takes up essentially all of the memory available to a 32 bit application so appears to be right on the edge which is a bad place to be-- especially when it's for no percievable benefit to do so).
So then, you need to click cancel to that file->open dialogue box. Now you can edit certain settings which aren't going to be table specific and are universal to VPX as a whole. You're going to set the max texture dimensions to a limit so that the few assets on this table that require a massive amount of system memory at full size don't cause the table to crash. However, you won't always want this setting applied because there are tables that may have larger sized assets which collectively don't exceed the 32-bit application memory limit even though they're larger than the 3072 setting you're about to apply. So, rather than limit the fidelity of all tables, we'll just temporarily use this setting to fix the actual problem and then turn it back on because all other table creators ensure that their table will consistently load on any system at all while the unlimited setting is selected (I actually did have luck getting it to load about 50% of the time// I suspect this is right at the line of the limitation and has at least something to do with quirks in how vpx addresses memory ).
Now you can use file->open to open the table and then use the table -> image manager and click raw size to sort by largest images. Export those, resize quickly to 50% of each dimension, and "re-import from" the updated images. Now you can play the game without reducing the quality for the rest of your collection. I was able to get this working by just taking the top 7 graphics by size (the 10k x 10k nonsense ones) and resizing them to 2500 x 2500. I'm sure I could have gone bigger, I just went with the quick and dirty, I know this will work re-size given that they won't even display at even 2500 x 2500 regardless.
Steps:
- Open VPX directly (not a table file)
- If you have file open dialogue enabled on launch, click cancel.
- Set your graphics settings temporarily down (Preferences -> Video Graphics Options -> Max Texture Dimensions ->3072; this isn't because your system is low-end... it's only needed on this table)
- Now file->open the table and wait for it to load; don't click anywhere as it's still going to be a bit finnicky on the load most likely even on a performant system
- Click table -> image manager, click raw size a few times until the larger images are listed at the top
- 1 by 1 click export. Resize image with your favorite image editor. Here you have a choice of spending a few hundred bucks on an adobe license or you could probably get by with the free install of open source application GIMP (seeing as how this is just light graphics work)
- For each of the seven largest assets, click reimport from. If you just click import it will "add" an image asset rather than replacing the oversized images with your newly sized images!
TA-DA! You've caused 0 impact to percievable fidelity and now have a working table.