RuntimeError: Texture too large((350,2074) maximum supported by graphics card is 2048?

Asked by Viswanathan R

Hi,
  I am using the xibo client 1.2.2a in ubuntu 10.04. It was run perfectly. Few days ago, i was start to run my client, it throws Runtime error texture too large. But, I checked the site.cfg. It contains width=1024 and height = 768. I don't know where the player takes the size as 350,2074.
  Please suggest me whether it is a graphics card issue or some other problems.

Question information

Language:
English Edit question
Status:
Answered
For:
Xibo Edit question
Assignee:
No assignee Edit question
Last query:
Last reply:
Revision history for this message
Alex Harrington (alexharrington) said :
#1

It'll be that your layout has exhausted the texture.memory.on your graphics card. By default we scale the images to the correct size before using them as textures so either you changed that setting, or you need to use less images, or you need a better graphics card with more texture memory.

What card are you using?

Revision history for this message
Viswanathan R (rvisu87) said :
#2

My system configuration is

Intel Atom Dual Core D525 Processor and board with Inbuilt Graphics NM10 Express Chipset.

Revision history for this message
Viswanathan R (rvisu87) said :
#3

I just removed the cache.xml file in data folder when "RuntimeError: Texture too large((350,2074) maximum supported by graphics card is 2048" occurred. After, deleting the cache.xml file the client run perfectly without error.
Is their any relationship is available between this runtime error and cache.xml file. If not, how did run the client after remove only cache.xml file?

Revision history for this message
Alex Harrington (alexharrington) said :
#4

There's no relationship between the two. The image you were trying to load isn't on the layout any longer.

Alex

Revision history for this message
Viswanathan R (rvisu87) said :
#5

Sorry,I need more clarification,I can agree there is no relationship between those, but how its run if am suppose to remove the cache.xml file.

Revision history for this message
Alex Harrington (alexharrington) said :
#6

I don't know. If you can give me logs showing before and after then maybe we could see.

My guess is either:

1. Whatever layout contained that image isn't scheduled anymore and removing cache.xml and restarting the client caused it not to be loaded anymore and so no problem.

2. You had a corrupt downloaded image with a corrupt checksum in cache.xml and removing that caused a fresh copy to be downloaded from the server - but that's so unfeasible it's almost impossible. It would require the server to generate an invalid checksum the corrupt the data it sent to the server such that the checksum done client end then matched.

Please keep in mind the Linux client is a beta application.

Alex

Revision history for this message
Viswanathan R (rvisu87) said :
#7

thanks,

Can you help with this problem?

Provide an answer of your own, or ask Viswanathan R for more information if necessary.

To post a message you must log in.