--- Operating System, Graphics card ---
winxp 32 bits, G41
--- Blender version with error, and version that worked ---
blender-2.67-r56922-win32 from the buildbot is affected
blender 2.67 stable release works without a problem with this.
--- Short description of error ---
Shading is going very wrong in recent buildbot in the 3D view with an edge split modifier
--- Steps for others to reproduce the error (preferably based on attached .blend file) ---
- use r56922 , default factory setting
- load the attached blend (Load UI disabled or enabled it does not make a difference)
- zoom on the model and rotate around to see the shading horrible from attached picture
in the stable 2.67 release doing the same will show the model having a correct and expected shading
Description
Event Timeline
Good news, that reported shading problem does not exist for the just released stable Blender 2.67a, so at least it's not one of the fixes from between 2.67 and 2.67a that created this shading bug but something else that didn't made it in the 2.67a release.
Next time, try irc.freenode.net #blendercoders for example! Daily builds can always have issues...
Do not understand why the bug-report was closed. This bug still exists in the latest builds.
Sanc: the tracker is for bugs in our releases first, we do releases very often for that reason.
Issues in current development builds we accept too, but it's just a good idea if you check with others (developers) if this is a temporary build issue or something to report.
I will reopen report, with clear title.
Thank you for the reply, i wasn't aware of the "releases first" priority for the bug tracker.
Maybe this is something that should be added in the bug report guideline (with a mention of the irc to report for daily buildbot new bugs) that are displayed when you click on the "Submit New".
mistake in own optimization r56649, fixed r56993.
@Ton, I'd prefer these bugs get reported in the tracker, it means I can check on them when I have time.
Maybe a timezone issue but IRC is very active around 8-10pm for me, which is normally not a time I want to start investigating new reports.