Has anyone encountered this issue? In Designer, the image displays correctly, but in the client launcher, it appears as an (X) icon. When I close the client, one image disappears, and a different image from another page also shows up as an (X) icon. I’ve tried deleting the .ignition folder to refresh the cache, but the problem still persists.
I have also checked the logs and I can't see any messages that pertains to having an error loading an image.
I’d appreciate any help you can provide.
Thanks!
I can imagine three possible culprits off the top of my head:
• A binding on the image path that is overwriting what's saved in the designer.
• The image path is pointed at a local file that the client's computer simply doesn't have access to.
• The client's computer is pointed at a different gateway than the designer, and the image hasn't been imported to the other gateway.
2 Likes
Hi,
Thank you for your response.
• A binding on the image path that is overwriting what's saved in the designer.
- here is how it looks on the graphics designer, the image is just linked to the path on the image management
and here is how it looks on the client:
• The image path is pointed at a local file that the client's computer simply doesn't have access to.
I can clearly access the images without any access rights issue because all the images came from the same path and most of the images are showing and some are missing when being viewed on the client.
• The client's computer is pointed at a different gateway than the designer, and the image hasn't been imported to the other gateway.
There's only 1 gateway for this setup.
Perhaps rule out the file system by importing the image using the image management tool, and then, use the path provided by the tool [right click-->Copy Path].
1 Like
I’ve identified the issue causing the images to break. It turns out that the Client Memory was set to only 256MB, which isn’t enough for the project I’m running. This limitation significantly slows down the client, affecting image loading and caching.
At peak usage, the project consumes 246/256MB of memory.
To resolve this, I adjusted the memory allocation from 256MB to 1024MB. If you’re running your client through a shortcut, you’ll need to delete the existing shortcut and create a new shortcut and it will automatically load up the project along with the updated memory settings.
1 Like
