spring 95 + BA 7.84 and video memory - Page 2

spring 95 + BA 7.84 and video memory

Discuss your problems with the latest release of the engine here. Problems with games, maps or other utilities belong in their respective forums.

Moderator: Moderators

User avatar
Silentwings
Posts: 3720
Joined: 25 Oct 2008, 00:23

Re: spring 95 + BA 7.84 and video memory

Post by Silentwings »

As far as I know, in most cases this is connected to lua memory usage and its only a few cases where it isnt. So I suspect more than one bug here.
User avatar
nixtux
TechA Developer
Posts: 100
Joined: 01 Mar 2009, 15:36

Re: spring 95 + BA 7.84 and video memory

Post by nixtux »

Neonstorm there is if you have a semi recent NVIDIA gpu use
watch nvidia-smi
For me and my 9800gfx I just get basic usage but iirc more recent gpu get a more detailed output
User avatar
jamerlan
Balanced Annihilation Developer
Posts: 683
Joined: 20 Oct 2009, 13:04

Re: spring 95 + BA 7.84 and video memory

Post by jamerlan »

I tryed to use gDebugger :-) but it crashes on start for me. Even amd version of gdebugger had the same crash.

But actually Beherith helped me :-)
He suggested to set these options:
AllowDeferredMapRendering = 0
AllowDeferredModelRendering = 0

and I got -200mb to video memory usage (like 700mb with antialiasing set to 4 + enabled LuaShaders support + Bump Mapped water etc). That works for me!

Only BAR uses these features. So I will enable them when I will decide to play BAR or when I will buy better Video card.

Thanks Beherith!
luckywaldo7
Posts: 1398
Joined: 17 Sep 2008, 04:36

Re: spring 95 + BA 7.84 and video memory

Post by luckywaldo7 »

That is still kind of odd; I am playing with a 560 Ti on Kubuntu and I have no troubles playing at max settings including all deferred rendering enabled.
Kloot
Spring Developer
Posts: 1867
Joined: 08 Oct 2006, 16:58

Re: spring 95 + BA 7.84 and video memory

Post by Kloot »

The amount of GPU memory used by AllowDeferred*Rendering largely depends on screen resolution. If both are enabled, the total footprint in bytes minus driver overhead is 2 * (6 * sx * sy * 4) which yields 80MB at 1680x1050.

A "Dell U2713H" monitor has a native resolution of 2560x1440, so the raw footprint there would be 168MB when running Spring in fullscreen mode. Subtracting that and other known vidmem consumers still leaves a rather large chunk unaccounted for.
Post Reply

Return to “Help & Bugs”