14 replies to this topic

[whynotpizza]

See below.

 

I get this error on some tables which previously worked just fine on x86 using 10.7.2, but now that I upgraded to 10.8.0 I see this warning on some tables.

 

Can we just disable this warning? If so I couldn't find the switch. Especially when just running the table, not modifying it?

 

Or should I just make the leap and run ALL my tables using X64 instead? If I do that I run the risk of older tables not working right on X64 (or maybe not)

 

--

WARNING!   WARNING!   WARNING!   WARNING!

 

Not all images were loaded, likely due to low memory.

Please use the 64-bit version of the application.

 

DO NOT SAVE THIS FILE OR YOU MAY LOOSE DATA!

 

Affected Files:

---

[Tesla]

I start VPX v10.8.0 with C:\VPX80\VPinballX.exe ... mainly because that is how the Desktop Shortcut was created.

Also, the name of my Pinball-Y EXE-file starter (and is now again).

 

I've never seen that message.

 

But seems to me it's telling you what it thinks is wrong.

If this is a healthy 16gb Windows computer, then maybe a VPX software component mismatch is the problem? 

[whynotpizza]

CPU is Intel i5-4690K 3.5Ghz

MEM is 16GB

OS is Win7 Enterprise

STORAGE is SanDisk SDSSDH3 1 TB

GRAPHICS is NVIDIA GeForce GTX 1050Ti

POWER is 2 x 750W to drive PC and Toys

 

This looks like a dialog added along the way to Visual Pinball and its a valid warning I suspect. 

 

I just wish it was suppressed when calling VPX engine in "play" mode. 

[Tesla]

CPU is Intel i5-4690K 3.5Ghz

MEM is 16GB

OS is Win7 Enterprise

STORAGE is SanDisk SDSSDH3 1 TB

GRAPHICS is NVIDIA GeForce GTX 1050Ti

POWER is 2 x 750W to drive PC and Toys

 

 

 

Glaring issue with this config is Windows-7. Surely, it's 64-bit but still ... like 3 versions behind ... you are in the Windows realm of 2009-2014.

 

You don't have something weird set in Windows do you ?

- like virtual-memory completely disabled

- running i5 as Over-Clocked

- something with i5 core affinity

 

Hardware wise ... Providing your main Playfield monitor is 1080p you should be OK.

But at 1440p, you might get near the edge with only a Intel-i5 . Also, that GTX-1050-Ti is pretty slow (now-where near even a GTX-1070).

[deadmanworking]

The upgraded versions of the tables are using too much memory for the 32bit version, as the message says, just use the 64bit version

[Thalamus]

Deanmanwalking is correct. 10.8 is newer than 10.7.2 and I'm quite sure that the reason for these warnings is that 10.8 actually DO warn you about something that was ignored before. It is mostly a warning for those those that might actually edit the table, but, also giving you a clear warning saying there is a high chance that what you author intended to work, might not be. It is quite a long time ago since 64bit was unstable and not recommended. Nowadays it is the other way around.

[Tesla]

The upgraded versions of the tables are using too much memory for the 32bit version, as the message says, just use the 64bit version

 

Possibly.

 

But the windows WoW64 traditionally takes care of that ... and the Windows gaming developers (as a whole) have been releasing video-games and simulations that use crazy-high amounts of memory (on top of what the Windows-OS uses itself). 

[deadmanworking]

 

The upgraded versions of the tables are using too much memory for the 32bit version, as the message says, just use the 64bit version

 

Possibly.

 

But the windows WoW64 traditionally takes care of that ... and the Windows gaming developers (as a whole) have been releasing video-games and simulations that use crazy-high amounts of memory (on top of what the Windows-OS uses itself). 

 

 

Not "possibly" - 32bit cannot address more than 4 GB and if the software hits that ceiling (due to new lightning and rendering features in 10.8) you get that error message, simple as that

[Itchigo]

 

CPU is Intel i5-4690K 3.5Ghz

MEM is 16GB

OS is Win7 Enterprise

STORAGE is SanDisk SDSSDH3 1 TB

GRAPHICS is NVIDIA GeForce GTX 1050Ti

POWER is 2 x 750W to drive PC and Toys

 

 

 

Glaring issue with this config is Windows-7. Surely, it's 64-bit but still ... like 3 versions behind ... you are in the Windows realm of 2009-2014.

 

My Windows7 (Ultimate) cab has been working for the last 12 years. Unless it's a 64 bit vs 32 bit thing. Just because it's not supported doesn't mean it stops working. It may or may not be enough to run everything, but I can't speak to this particular error. The pc I'm on now is older than his (I-5 2400k, but I don't run tables on it).

Edited by Itchigo, 09 February 2026 - 07:21 PM.

[Tesla]

 

 

The upgraded versions of the tables are using too much memory for the 32bit version, as the message says, just use the 64bit version

 

Possibly.

 

But the windows WoW64 traditionally takes care of that ... and the Windows gaming developers (as a whole) have been releasing video-games and simulations that use crazy-high amounts of memory (on top of what the Windows-OS uses itself). 

 

 

Not "possibly" - 32bit cannot address more than 4 GB and if the software hits that ceiling (due to new lightning and rendering features in 10.8) you get that error message, simple as that

 

 

Interesting.

 

So, when I use C:\VPX80\VPinballX.exe on my cabinet, that is just Direct-X 32-bit ? 

I get this error on some tables which previously worked just fine on x86 using 10.7.2, but now that I upgraded to 10.8.0 I see this warning on some tables.

 

--

WARNING!   WARNING!   WARNING!   WARNING!

 

Not all images were loaded, likely due to low memory.

Please use the 64-bit version of the application.

 

DO NOT SAVE THIS FILE OR YOU MAY LOOSE DATA!

 

Affected Files:

---

 

Can you give me a couple of example VPX tables that always give you this message?

[fhjui]

There's a lot of confusion here regarding the error messages, which confuses me and doesn't fit together.

I have checked all the vpx-files of 32bit, 64bit, 10.7 and 10.8 versions.

This warning exists only for the x64-DirectX and the x64-GL versions, not in the 32bit-versions. The hint "Please use the 64-bit version of the application" doesn't exist in the source code of vpx 10.8

And in addition thats  illogical because 10.8 is a 64bit program and wouldn't hint to use a 64bit prog.

 

Tesla's approach is correct. Which table causes this error. ?

If you run explicitly vpx10.8, load the table and run it. Does the same error then occur?

Your warning messags do not fit to the 32bit version

 

Then some remarks to the max. amount of RAM 32bit-windows can address:

32bit software or OS can, theoretically, address a maximum of 4GB of RAM. But that is not correct concerning windows. It divides the memory into 2 GB for kernel space and 2 GB for use space. As a result, the program can only use 2GB.

There is "4GB-patch" from MS available which can shift the memory limit to 1:3 instead of 2:2. (Physical Address Extension, PAE-patch) Then 32bit-programms can use 3GB instead of 2GB. This is independent of whether the PC has 16GB of RAM or more.

Edited by fhjui, 09 February 2026 - 08:38 PM.

[deadmanworking]

 

 

 

The upgraded versions of the tables are using too much memory for the 32bit version, as the message says, just use the 64bit version

 

Possibly.

 

But the windows WoW64 traditionally takes care of that ... and the Windows gaming developers (as a whole) have been releasing video-games and simulations that use crazy-high amounts of memory (on top of what the Windows-OS uses itself). 

 

 

Not "possibly" - 32bit cannot address more than 4 GB and if the software hits that ceiling (due to new lightning and rendering features in 10.8) you get that error message, simple as that

 

 

Interesting.

 

So, when I use C:\VPX80\VPinballX.exe on my cabinet, that is just Direct-X 32-bit ? 

 

Yes, if you didn't rename the applications that is 32bit, you can check by opening the program and choosing Help > About

[whynotpizza]

Here are three tables I see this problem.

 

In each case, I opened the table and recorded the MEM usage from task manager.

 

x86 = WARNING

 

VPinballX.exe *32 = 3.110 GB -- Pirates Life 2.1b -Under a Black Flag

VPinballX.exe *32 = 3.084 GB -- The Blizzard of Ozz

VPinballX.exe *32 = 2.054 GB -- Dragonfist (Stern 1981)

 

x64 = OK

 

VPinballX64.exe   = 3.821 GB -- Pirates Life 2.1b -Under a Black Flag

VPinballX64.exe   = 3.392 GB -- The Blizzard of Ozz

VPinballX64.exe   = 2.865 GB -- Dragonfist (Stern 1981)

[Tesla]

Yes, if you didn't rename the applications that is 32bit, you can check by opening the program and choosing Help > About

 

 

I have my cabinet sorta-apart at the moment ...

I looked in the supplied doc folder, but didn't really see it.

 

Is this correct ?

 

VPX 8.0 for Windows (VPX v10.8.0)

 

VPinballX.exe             32bit   Direct-X

VPinballX64.exe         64bit   Direct-X

 

VPinballX_GL.exe      32bit   Open-GL

VPinballX_GL64.exe  64bit   Open-GL

Edited by Tesla, 10 February 2026 - 04:24 AM.

[fhjui]

@Tesla: yes, your version list is correct. I have downloaded the 10.8 version from github and checked it.

There I have seen, that I have misinterpreted the first post of whynotpizza. I had referred to the warning message to version 10.7. But its included in all 32bit 10.8.

For me, the case is clear. These tables run only with 64bit vpx.

With a front-end like PinUpSystem, it's not difficult to start tables with different VPX versions via the game manager.