shadows dropping the frame-rate based on camera distance #34757

Closed
opened 2013-03-24 17:07:25 +01:00 by Chris Smith · 2 comments

Category: Rendering

%%%I think Ive found a bug with the shadows dropping the frame-rate based on camera distance.
It happens only when the game engine is started with shadow maps close to the camera.

in my scene i get about 200 frames with my amd 7950 however when this oddity kicks in it goes and locks down to around 30 and the rasterizer hits 30ms.
if the game engine is started while still viewing the same set of shadows but with a larger distance between the shadows and the active camera the frame rate starts with over 200 fps again.

Another thing that i found odd is that if i start the game engine a fare distance away from the shadow mapping and then go look up really close with the game still running no frame-rate drop will occur. And I say up close not really that close maybe about 3 to 4 blender units viewing distance away and it will start to happen.

In the blend Ive uploaded to make it more apparent Ive made the objects quite high-poly just to show the drop in frame-rate better,
as it seems like its dependent on how close the object is to the light that's casting the shadows.

And also in the blend its set to camera 1 up close to the shadows where the frame-rate drop happens with game-start, and you can then change to camera 2 with numpad 2 to then see the frame-rate rise again (fingers crossed) and you can also then go back to camera one with numpad 1 with no longer a drop in frames.

Took three screen grabs to show what happens clearly, probably best to check those out first.

few other things ive tested

happens with sun lamp shadowshappens with spot light shadows
happens with simple and variance type shadowmappinghappens with 64bit&32bit blender 2.66a
//Same thing happens in blender and in blenderplayer

it just happens ^_^

Cpu intel 3570k
Gpu amd 7950
OS Windows 7 sp1 64bit
blender version 2.66a

%%%

**Category**: Rendering %%%I think Ive found a bug with the shadows dropping the frame-rate based on camera distance. It happens only when the game engine is started with shadow maps close to the camera. in my scene i get about 200 frames with my amd 7950 however when this oddity kicks in it goes and locks down to around 30 and the rasterizer hits 30ms. if the game engine is started while still viewing the same set of shadows but with a larger distance between the shadows and the active camera the frame rate starts with over 200 fps again. Another thing that i found odd is that if i start the game engine a fare distance away from the shadow mapping and then go look up really close with the game still running no frame-rate drop will occur. And I say up close not really that close maybe about 3 to 4 blender units viewing distance away and it will start to happen. In the blend Ive uploaded to make it more apparent Ive made the objects quite high-poly just to show the drop in frame-rate better, as it seems like its dependent on how close the object is to the light that's casting the shadows. And also in the blend its set to camera 1 up close to the shadows where the frame-rate drop happens with game-start, and you can then change to camera 2 with numpad 2 to then see the frame-rate rise again (fingers crossed) and you can also then go back to camera one with numpad 1 with no longer a drop in frames. Took three screen grabs to show what happens clearly, probably best to check those out first. few other things ive tested *happens with sun lamp shadows*happens with spot light shadows *happens with simple and variance type shadowmapping*happens with 64bit&32bit blender 2.66a //Same thing happens in blender and in blenderplayer it just happens ^_^ Cpu intel 3570k Gpu amd 7950 OS Windows 7 sp1 64bit blender version 2.66a %%%
Author

Changed status to: 'Open'

Changed status to: 'Open'
Member

Changed status from 'Open' to: 'Archived'

Changed status from 'Open' to: 'Archived'
Aaron Carlisle self-assigned this 2019-06-29 02:12:11 +02:00
Sign in to join this conversation.
No Label
Interest
Alembic
Interest
Animation & Rigging
Interest
Asset Browser
Interest
Asset Browser Project Overview
Interest
Audio
Interest
Automated Testing
Interest
Blender Asset Bundle
Interest
BlendFile
Interest
Collada
Interest
Compatibility
Interest
Compositing
Interest
Core
Interest
Cycles
Interest
Dependency Graph
Interest
Development Management
Interest
EEVEE
Interest
EEVEE & Viewport
Interest
Freestyle
Interest
Geometry Nodes
Interest
Grease Pencil
Interest
ID Management
Interest
Images & Movies
Interest
Import Export
Interest
Line Art
Interest
Masking
Interest
Metal
Interest
Modeling
Interest
Modifiers
Interest
Motion Tracking
Interest
Nodes & Physics
Interest
OpenGL
Interest
Overlay
Interest
Overrides
Interest
Performance
Interest
Physics
Interest
Pipeline, Assets & IO
Interest
Platforms, Builds & Tests
Interest
Python API
Interest
Render & Cycles
Interest
Render Pipeline
Interest
Sculpt, Paint & Texture
Interest
Text Editor
Interest
Translations
Interest
Triaging
Interest
Undo
Interest
USD
Interest
User Interface
Interest
UV Editing
Interest
VFX & Video
Interest
Video Sequencer
Interest
Virtual Reality
Interest
Vulkan
Interest
Wayland
Interest
Workbench
Interest: X11
Legacy
Blender 2.8 Project
Legacy
Milestone 1: Basic, Local Asset Browser
Legacy
OpenGL Error
Meta
Good First Issue
Meta
Papercut
Meta
Retrospective
Meta
Security
Module
Animation & Rigging
Module
Core
Module
Development Management
Module
EEVEE & Viewport
Module
Grease Pencil
Module
Modeling
Module
Nodes & Physics
Module
Pipeline, Assets & IO
Module
Platforms, Builds & Tests
Module
Python API
Module
Render & Cycles
Module
Sculpt, Paint & Texture
Module
Triaging
Module
User Interface
Module
VFX & Video
Platform
FreeBSD
Platform
Linux
Platform
macOS
Platform
Windows
Priority
High
Priority
Low
Priority
Normal
Priority
Unbreak Now!
Status
Archived
Status
Confirmed
Status
Duplicate
Status
Needs Info from Developers
Status
Needs Information from User
Status
Needs Triage
Status
Resolved
Type
Bug
Type
Design
Type
Known Issue
Type
Patch
Type
Report
Type
To Do
No Milestone
No project
No Assignees
2 Participants
Notifications
Due Date
The due date is invalid or out of range. Please use the format 'yyyy-mm-dd'.

No due date set.

Dependencies

No dependencies set.

Reference: blender/blender#34757
No description provided.