Spot lights: Spot Shape Size incorrect from 2.70 to 2.69 #40367

Closed
opened 2014-05-26 19:17:04 +02:00 by Sam Vila · 9 comments

System Information
Windows 8

Blender Version
2.70 official release and 2.69 official release.

Short description of error

Exact steps for others to reproduce the error
Basically if you have a spot light with a shape size of 106° for example in 2.70 and you save that file and you open that file in a previous version (2.69 for example) you get a value of 1.85° instead of the original 106°.

It's very easy to reproduce this problem but I don't know if it's part of the breaking compatibility plan of if it's a bug.

**System Information** Windows 8 **Blender Version** 2.70 official release and 2.69 official release. **Short description of error** **Exact steps for others to reproduce the error** Basically if you have a spot light with a shape size of 106° for example in 2.70 and you save that file and you open that file in a previous version (2.69 for example) you get a value of 1.85° instead of the original 106°. It's very easy to reproduce this problem but I don't know if it's part of the breaking compatibility plan of if it's a bug.
Author

Changed status to: 'Open'

Changed status to: 'Open'
Author

Added subscriber: @samvila

Added subscriber: @samvila

Changed status from 'Open' to: 'Archived'

Changed status from 'Open' to: 'Archived'
Bastien Montagne self-assigned this 2014-05-26 21:21:47 +02:00

Please have a look at the release notes before reporting a bug, this is none, but a mere forward compatibility breaking due to internal cleanup (values moved from degrees to radians).

Please have a look at the release notes before reporting a bug, this is none, but a mere forward compatibility breaking due to internal cleanup (values moved from degrees to radians).
Author

OK, excuse me if I don't read all the releases notes, that's why in my description I said that I was not sure. I'm not a developer and sometimes is hard to keep track to all the changes in Blender. I don't know why but every time I report a problem I feel like I'm going to get hit by a bus with the feedback from the developers. Not all blender users are blender developers.

OK, excuse me if I don't read all the releases notes, that's why in my description I said that I was not sure. I'm not a developer and sometimes is hard to keep track to all the changes in Blender. I don't know why but every time I report a problem I feel like I'm going to get hit by a bus with the feedback from the developers. Not all blender users are blender developers.

I’m sorry if I’m a bit harsh sometimes, but you report one bug, so taking the five minutes needed to skim the release notes about compatibility issues (those have their own section even, and google can also help) is not a great deal for you, while as developers, we have to check tens of bugs everyday, and even simply closing invalid ones takes a few minutes as well!

Serious, well made and tested/checked reports are great value for us. False reports esp. when info about it is very easily accessible are waste of our time.

I’m sorry if I’m a bit harsh sometimes, but you report **one** bug, so taking the five minutes needed to skim the release notes about compatibility issues (those have their own section even, and google can also help) is not a great deal for you, while as developers, we have to check tens of bugs everyday, and even simply closing invalid ones takes a few minutes as well! Serious, well made and tested/checked reports are great value for us. False reports esp. when info about it is very easily accessible are waste of our time.
Author

I'm also wasting my time in creating these reports, sometimes they are bugs and sometimes not. If you think users are creating reports because they are bored you are wrong, if I create a report is because I don't have all the information of knowledge of I'm not up to date with all the changes that happens in Blender everyday. I think I mention you previously this and I will do it again for the last time, I'm very tired to be treated like this (especially from you) every time I report a bug so I think I'm not going to waste more of your time or my time in these reports, not going to report anything else about blender bugs.

Is funny to hear Ton and other developers asking for help in catching bugs when you get so much heat every time you try to be helpful. Good luck.

I'm also wasting my time in creating these reports, sometimes they are bugs and sometimes not. If you think users are creating reports because they are bored you are wrong, if I create a report is because I don't have all the information of knowledge of I'm not up to date with all the changes that happens in Blender everyday. I think I mention you previously this and I will do it again for the last time, I'm very tired to be treated like this (especially from you) every time I report a bug so I think I'm not going to waste more of your time or my time in these reports, not going to report anything else about blender bugs. Is funny to hear Ton and other developers asking for help in catching bugs when you get so much heat every time you try to be helpful. Good luck.

Added subscriber: @ThomasDinges

Added subscriber: @ThomasDinges

@samvila: I think monts first response here was very polite. You said that you are unsure whether this is a bug or not. Mont answered this question, but also gave you a hint to the release logs. See it as additional info, not as a attack. :)

@samvila: I think monts first response here was very polite. You said that you are unsure whether this is a bug or not. Mont answered this question, but also gave you a hint to the release logs. See it as additional info, not as a attack. :)
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
3 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#40367
No description provided.