I'm not sure what you think by 'load 3 different cubemap' since they depending from player camera perspective..anyway here is case..
when you do this before main loop
tex1=CreateTexture(32,32,1+128+256)
tex2=CreateTexture(32,32,1+128+256)
tex3=CreateTexture(32,32,1+128+256)
frame is instantly killed even if I updating only 2 of them..
now, if I delete any of previous cubemaps and leave things like this before main loop
tex1=CreateTexture(512,512,1+128+256)
tex2=CreateTexture(512,512,1+128+256)
and updating both cubemaps within main loop, frame rate is excellent..
my question how come? In the last case I'm updating two 512x512 cubemaps what cousing bigger VRAM usage, but frame rate is excellent...in the first case I'm also updating just 2 of 3 cubemaps and much more smaller, but FPS is horrible..only difference is that I create one cubemap texture more before main loop, but I didnt update it in main loop...and for three 32x32 cubemaps, memory usage is smaller than for two 512x512 and at same time its faster than case with 32x32...I'm confused..whats happening ??
when you do this before main loop
tex1=CreateTexture(32,32,1+128+256)
tex2=CreateTexture(32,32,1+128+256)
tex3=CreateTexture(32,32,1+128+256)
frame is instantly killed even if I updating only 2 of them..
now, if I delete any of previous cubemaps and leave things like this before main loop
tex1=CreateTexture(512,512,1+128+256)
tex2=CreateTexture(512,512,1+128+256)
and updating both cubemaps within main loop, frame rate is excellent..
my question how come? In the last case I'm updating two 512x512 cubemaps what cousing bigger VRAM usage, but frame rate is excellent...in the first case I'm also updating just 2 of 3 cubemaps and much more smaller, but FPS is horrible..only difference is that I create one cubemap texture more before main loop, but I didnt update it in main loop...and for three 32x32 cubemaps, memory usage is smaller than for two 512x512 and at same time its faster than case with 32x32...I'm confused..whats happening ??