0001092: Camera+object motion blur behaves wrong

(0003133)
Lord Crc (administrator)
2011-08-02 14:49
edited on: 2011-08-02 15:06

This seems to be an exporter issue.

LuxBlend uses normalized time it seems (0.0 to 1.0) when exporting the MotionInstance, while it should write it in "absolute time", usually shutteropen to shutterclose which is 0.0 and 0.25 in this case.

This can be verified by changing the line to

MotionInstance "Sphere" 0.0 0.25 "Sphere_motion"

which will make the sphere stationary.

(0003428)
SATtva (developer)
2012-06-13 09:48

Lord Crc, it seems MB is broken (maybe due to the latest motion block changes). Once again, when i try to make camera and an object to move in sync (without parent relations), an object blurs out.

(0003437)
Lord Crc (administrator)
2012-06-15 16:21

Ah, forgot to test that when I rewrote the code, will check it out shortly.

(0003438)
Lord Crc (administrator)
2012-06-15 16:22

Can I use the attached blend file to reproduce it?

(0003439)
SATtva (developer)
2012-06-15 22:29

I've added a new test scene made with Blender 2.63. The other file was from 2.49, so i'm not sure whether it's usable anymore.

(0003443)
Lord Crc (administrator)
2012-06-30 17:43

I think the problem here is that you've set the exposure mode to "absolute", while you most likely want it to be "normalized" or "degrees".

(0003444)
Lord Crc (administrator)
2012-06-30 19:02

I've changed the layout and description a bit on the exposure mode fields, hopefully it should be slightly more obvious which mode is active.

(0003446)
SATtva (developer)
2012-06-30 22:35

I don't really get why it doesn't work with "absolute". I use this mode all the time as it allows to set the camera exposure more precisely.

(0003447)
Lord Crc (administrator)
2012-06-30 22:51

It works just fine here, it's just that the exposure time you've set (1 second) is so long compared to the time the object moves (the frame time, ie 1/25fps = 0.04 seconds) that it looks as if the object is stationary. Reduce shutter close time to something reasonable, or change the fps, and you're off.

(0003448)
SATtva (developer)
2012-06-30 22:57
edited on: 2012-06-30 22:58

Ah, i get it now, thanks!

(0003453)
J the Ninja (developer)
2012-06-30 23:32

So is this issue fixed? The 2.63 file seems to work correctly for me.

(0003455)
SATtva (developer)
2012-06-30 23:43

Same here, i'm closing it.

Issue History
Date Modified	Username	Field	Change
2011-06-07 08:55	SATtva	New Issue
2011-06-07 08:55	SATtva	File Added: MB.blend
2011-07-28 07:44	SATtva	Target Version	=> 1.0
2011-08-02 14:49	Lord Crc	Note Added: 0003133
2011-08-02 14:51	Lord Crc	Category	Core => LuxBlend
2011-08-02 15:06	Lord Crc	Note Edited: 0003133	View Revisions
2011-08-08 08:38	SATtva	Relationship added	related to 0001130
2012-06-13 09:48	SATtva	Note Added: 0003428
2012-06-15 16:21	Lord Crc	Assigned To	=> Lord Crc
2012-06-15 16:21	Lord Crc	Status	new => assigned
2012-06-15 16:21	Lord Crc	Note Added: 0003437
2012-06-15 16:22	Lord Crc	Note Added: 0003438
2012-06-15 22:27	SATtva	File Added: MB-2.63.blend
2012-06-15 22:29	SATtva	Note Added: 0003439
2012-06-30 17:43	Lord Crc	Note Added: 0003443
2012-06-30 19:02	Lord Crc	Note Added: 0003444
2012-06-30 22:35	SATtva	Note Added: 0003446
2012-06-30 22:51	Lord Crc	Note Added: 0003447
2012-06-30 22:57	SATtva	Note Added: 0003448
2012-06-30 22:58	SATtva	Note Edited: 0003448	View Revisions
2012-06-30 23:32	J the Ninja	Note Added: 0003453
2012-06-30 23:43	SATtva	Note Added: 0003455
2012-06-30 23:43	SATtva	Status	assigned => resolved
2012-06-30 23:43	SATtva	Fixed in Version	=> 1.0
2012-06-30 23:43	SATtva	Resolution	open => fixed
2012-08-21 06:54	jeanphi	Fixed in Version	1.0 => 1.0RC4
2012-09-11 06:10	jeanphi	Status	resolved => closed

Notes
(0003133) Lord Crc (administrator) 2011-08-02 14:49 edited on: 2011-08-02 15:06	This seems to be an exporter issue. LuxBlend uses normalized time it seems (0.0 to 1.0) when exporting the MotionInstance, while it should write it in "absolute time", usually shutteropen to shutterclose which is 0.0 and 0.25 in this case. This can be verified by changing the line to MotionInstance "Sphere" 0.0 0.25 "Sphere_motion" which will make the sphere stationary.

(0003428) SATtva (developer) 2012-06-13 09:48	Lord Crc, it seems MB is broken (maybe due to the latest motion block changes). Once again, when i try to make camera and an object to move in sync (without parent relations), an object blurs out.

(0003437) Lord Crc (administrator) 2012-06-15 16:21	Ah, forgot to test that when I rewrote the code, will check it out shortly.

(0003438) Lord Crc (administrator) 2012-06-15 16:22	Can I use the attached blend file to reproduce it?

(0003439) SATtva (developer) 2012-06-15 22:29	I've added a new test scene made with Blender 2.63. The other file was from 2.49, so i'm not sure whether it's usable anymore.

(0003443) Lord Crc (administrator) 2012-06-30 17:43	I think the problem here is that you've set the exposure mode to "absolute", while you most likely want it to be "normalized" or "degrees".

(0003444) Lord Crc (administrator) 2012-06-30 19:02	I've changed the layout and description a bit on the exposure mode fields, hopefully it should be slightly more obvious which mode is active.

(0003446) SATtva (developer) 2012-06-30 22:35	I don't really get why it doesn't work with "absolute". I use this mode all the time as it allows to set the camera exposure more precisely.

(0003447) Lord Crc (administrator) 2012-06-30 22:51	It works just fine here, it's just that the exposure time you've set (1 second) is so long compared to the time the object moves (the frame time, ie 1/25fps = 0.04 seconds) that it looks as if the object is stationary. Reduce shutter close time to something reasonable, or change the fps, and you're off.

(0003448) SATtva (developer) 2012-06-30 22:57 edited on: 2012-06-30 22:58	Ah, i get it now, thanks!

(0003453) J the Ninja (developer) 2012-06-30 23:32	So is this issue fixed? The 2.63 file seems to work correctly for me.

(0003455) SATtva (developer) 2012-06-30 23:43	Same here, i'm closing it.