Page MenuHome

[BI] 2.77 World texture has no reaction to parented camera rotation
Closed, ResolvedPublic


System Information
Windows 7 x64, Phenom II, 8GB, Radeon R9 270 (Driver Packaging Version 15.30.1025-151117a-296575C)

Blender Version
Broken: 2.77-rc2 , 2.77 02cabda (dev build
Worked: 2.76b (f337fea) and all earlier

Short description of error
rendered by BI camera fly in rotation, objects are rotated as they must, but worldmap background stay still and has no move with all

Not so short description of error
Then you use Blender internal render (not cycles - no no) , has where world texture image with Equirectangular mapping (maybe not only that i think) and Camera attached to something what has rotation ("animated" calling be?)
--> background world texture on rendered image will no has an any transformation as it rendered with simple still background cropped picture with view-mapping or some of it/

Then camera is disattached from parent is seems working right (has visual difference in angles with displayed in viewport, but for me it is not critical now )

Exact steps for others to reproduce the error

  1. open attached scene
  2. call render image by some standard way. wait for it stop eat CPU
  3. scratch time slider some over random frame with meaning change of camera angle (seen it on viewport)
  4. change Slot if render result fom 2 to some different
  5. Render again and wait it
  6. swap around render slots and watch - objects are rotated but background is still the same, if you repeat all steps in older builds background would be correctly transformed by rotation

*i'm not brain damaged, just bad knowledge of language, sorry

Event Timeline

Vik (V) updated the task description. (Show Details)Mar 11 2016, 1:39 AM
Vik (V) set Type to Bug.
Vik (V) added a subscriber: Vik (V).
Vik (V) created this task.
Vik (V) raised the priority of this task from to Needs Triage by Developer.

I can confirm this here.
(win10 64bits)

Campbell Barton (campbellbarton) triaged this task as Confirmed, Medium priority.

Confirmed, rB53711020396a706418ebf3f24065b9c26eae5b06 caused this.

However 2.76b behavior doesn't match Cycles or new viewport code.

Have a fix which beings this in line with Cycles/Viewport, but investigating D1729 - to see why this change was made.