Switching to "Textured solid" and "GLSL" view will cause the FPS drop to 0 (was fine in 2.69) #39395

New Issue

Lino Thomas · 2014-03-24T19:15:46+01:00

Lino Thomas commented

2014-03-24 19:15:46 +01:00

System Information
Win 7 64 bit
GF GTX470
6GB RAM
Intel Xeon w3520 @3ghz

Blender Version
Broken: 2.70 official build Hash: 19e627c
Worked: 2.69 official build

Switching to textured solid or GLSL with a 4k Texture will cause the framerate to drop massively to 0fps.

I started working on this scene in 2.69 and i dont had any issues with the framerate.

Download the file. I packed the used textures in the Blend, so watch out for the downloadsize.
If you have to: unpack the Textures
Just change in the "n" toolshelf the shading to "textured solid"
You will now see the textured ship, but in this situation i get around 0.2 FPS.
My graphiccard and cpu are around 25% usage when this happends, no intersting memoryspike or similiar to see. Maybe Blender is waiting for a thread to finish to draw the next frame?
Sadly this bug is pretty bad to work with, as i use atlastextures for my assets, so texturing without seeing the texture (because its to slow) doesnt work.

If you need more information on this issue, i will try to deliver as much as i can to solve this issue.

Tested on two Pcs (both intel cpus [i7 920/xeon w3520] and nvidia cards [gtx 470/ 460] latest drivers) happend on both of them.

Save file (65mb!)
https://www.dropbox.com/s/g56zshqt0l8kj6t/twitch_jet_01_bug.blend

**System Information** Win 7 64 bit GF GTX470 6GB RAM Intel Xeon w3520 @3ghz **Blender Version** Broken: 2.70 official build Hash: 19e627c Worked: 2.69 official build Switching to textured solid or GLSL with a 4k Texture will cause the framerate to drop massively to 0fps. I started working on this scene in 2.69 and i dont had any issues with the framerate. Download the file. I packed the used textures in the Blend, so watch out for the downloadsize. If you have to: unpack the Textures Just change in the "n" toolshelf the shading to "textured solid" You will now see the textured ship, but in this situation i get around 0.2 FPS. My graphiccard and cpu are around 25% usage when this happends, no intersting memoryspike or similiar to see. Maybe Blender is waiting for a thread to finish to draw the next frame? Sadly this bug is pretty bad to work with, as i use atlastextures for my assets, so texturing without seeing the texture (because its to slow) doesnt work. If you need more information on this issue, i will try to deliver as much as i can to solve this issue. Tested on two Pcs (both intel cpus [i7 920/xeon w3520] and nvidia cards [gtx 470/ 460] latest drivers) happend on both of them. Save file (65mb!) https://www.dropbox.com/s/g56zshqt0l8kj6t/twitch_jet_01_bug.blend

Lino Thomas commented

2014-03-24 19:15:46 +01:00

Changed status to: 'Open'

Lino Thomas commented

2014-03-24 19:15:46 +01:00

Added subscriber: @LinoThomas

blender-admin commented

2014-03-24 19:15:46 +01:00

#39396 was marked as duplicate of this issue

Sergey Sharybin commented

2014-03-25 06:56:14 +01:00

Added subscriber: @Sergey

Sergey Sharybin self-assigned this 2014-03-25 06:57:49 +01:00

Sergey Sharybin commented

2014-03-25 06:57:49 +01:00

This is likely because of cache limit being applied on the images. For now you can increase Memory Cache Limit in User Preferences ->System and i'll try to find a proper solution soon.