FOSS gamedev and creative worlds

I've done "enable_texture_atlas = false" but i'm still getting

A bunch of time, what gives?

I don't think that has to do with the texture atlas. Minetest doesn't free all the video memory until it quits; I get this error when I start a new game many times without quitting Minetest completely. Are you doing that, or using a ton of mods, high-res textures, or have little video memory?

Menche wrote:I don't think that has to do with the texture atlas. Minetest doesn't free all the video memory until it quits; I get this error when I start a new game many times without quitting Minetest completely. Are you doing that, or using a ton of mods, high-res textures, or have little video memory?

I'm using a ton of mods, with a gig of video memory, it's not using it all up because i can run minecraft on top of it, it's just not utilizing my memory, is there a way to assign more opengl memory?

Now i got a traceback:

assigning more memory doesnt fix the leak, youre just filling up more of it and might cause other applications to suffer, possibly the whole system as is the case with my older P4.

So what? You're saying that minetest has an ultimate memory limit even though i have more than enough left to play an entirely different game?

It doesn't look like that traceback has anything to do with being unable to bind textures, that looks like a different bug (probably a block being freed twice somewhere?). But if you're getting texture binding errors, that doesn't necessarily mean that there is no free memory on your video card. It just means that the driver is unable to allocate a contiguous block of memory of the size you need. So, for all intents and purposes, you are using it all up. Get a better video card, or be easier on the one you have.

Orby wrote:It doesn't look like that traceback has anything to do with being unable to bind textures, that looks like a different bug (probably a block being freed twice somewhere?). But if you're getting texture binding errors, that doesn't necessarily mean that there is no free memory on your video card. It just means that the driver is unable to allocate a contiguous block of memory of the size you need. So, for all intents and purposes, you are using it all up. Get a better video card, or be easier on the one you have.

I have a superclocked gt430, it's probably linux' shitty drivers

jordan4ibanez wrote:

Orby wrote:It doesn't look like that traceback has anything to do with being unable to bind textures, that looks like a different bug (probably a block being freed twice somewhere?). But if you're getting texture binding errors, that doesn't necessarily mean that there is no free memory on your video card. It just means that the driver is unable to allocate a contiguous block of memory of the size you need. So, for all intents and purposes, you are using it all up. Get a better video card, or be easier on the one you have.

I have a superclocked gt430, it's probably linux' shitty drivers

Are you using the proper nvidia drivers or the shitty nouveau ones (in which case, yes you are screwed)?

Orby wrote:

jordan4ibanez wrote:

Orby wrote:It doesn't look like that traceback has anything to do with being unable to bind textures, that looks like a different bug (probably a block being freed twice somewhere?). But if you're getting texture binding errors, that doesn't necessarily mean that there is no free memory on your video card. It just means that the driver is unable to allocate a contiguous block of memory of the size you need. So, for all intents and purposes, you are using it all up. Get a better video card, or be easier on the one you have.

I have a superclocked gt430, it's probably linux' shitty drivers

Are you using the proper nvidia drivers or the shitty nouveau ones (in which case, yes you are screwed)?

I'm using the proprietary drivers, which still sucks

jordan4ibanez wrote:

Orby wrote:

jordan4ibanez wrote:I have a superclocked gt430, it's probably linux' shitty drivers

Are you using the proper nvidia drivers or the shitty nouveau ones (in which case, yes you are screwed)?

I'm using the proprietary drivers, which still sucks

I don't think the nvidia binary drivers suck at all. I find them to be quite reliable.

Orby wrote:

jordan4ibanez wrote:

Orby wrote:
Are you using the proper nvidia drivers or the shitty nouveau ones (in which case, yes you are screwed)?

I'm using the proprietary drivers, which still sucks

I don't think the nvidia binary drivers suck at all. I find them to be quite reliable.

Not when trying to play games, they're quite unstable in linux, very stable in windows, and exuberant in bsd

Orby wrote:

jordan4ibanez wrote:

Orby wrote:It doesn't look like that traceback has anything to do with being unable to bind textures, that looks like a different bug (probably a block being freed twice somewhere?). But if you're getting texture binding errors, that doesn't necessarily mean that there is no free memory on your video card. It just means that the driver is unable to allocate a contiguous block of memory of the size you need. So, for all intents and purposes, you are using it all up. Get a better video card, or be easier on the one you have.

I have a superclocked gt430, it's probably linux' shitty drivers

Are you using the proper nvidia drivers or the shitty nouveau ones (in which case, yes you are screwed)?

I used the nouveau drivers for a while, and minetest actually ran quite well with them.

jordan4ibanez wrote:

Orby wrote:

jordan4ibanez wrote:I'm using the proprietary drivers, which still sucks

I don't think the nvidia binary drivers suck at all. I find them to be quite reliable.

Not when trying to play games, they're quite unstable in linux, very stable in windows, and exuberant in bsd

Perhaps it would be more accurate to say that the binary nvidia drivers are the best video drivers under Linux (which, admittedly isn't saying much...)

Menche wrote:

Orby wrote:

jordan4ibanez wrote:I have a superclocked gt430, it's probably linux' shitty drivers

Are you using the proper nvidia drivers or the shitty nouveau ones (in which case, yes you are screwed)?

I used the nouveau drivers for a while, and minetest actually ran quite well with them.

I always got god awful framerates for everything when I ran the nouveau drivers. I haven't touched them in quite a few years, would be nice if they had improved.

it turns out it was the nvidia driver, it's poopoo

jordan4ibanez wrote:it turns out it was the nvidia driver, it's poopoo

Yes. What Ubuntu calls the "proprietary drivers" are indeed the binary nvidia drivers, but they're usually a couple minor releases behind. You should use the most recent drivers available through nvidia. I'm not sure why running out of vram means the driver is poopoo, but ok.

Menche wrote:Minetest doesn't free all the video memory until it quits;

But why? Can it be done or is it impossible?
I have it when starting many worlds without closing Minetest and I use the proprietary from ubuntu.

(for me) Its not the drivers causing the problems, but the game reacts differently depending on the driver.

P4 has new-ish nvidia card (new enough for binary drivers) and the video locks up when GL runs out.
amd-2x core uses radeonhd + catalyst and all textures go white when GL runs out without the lockup

This may fix some issues: https://github.com/celeron55/minetest/commit/41c00e87d42580881d8c7001f39014814e3b55f2