Map UV makes mapped images blurry #31868

New Issue

Chris Want · 2012-06-19T01:26:29+02:00

Chris Want commented

2012-06-19 01:26:29 +02:00

%%%Hi there,

I've attached a file to this bug report with a compositor setup that uses a MapUV node.

When I press F12 to render the composite image, the output from MapUV look unnecessarily blurry to me. The border of the UV mapped areas looks a bit odd too.

Cheers,
Chris
%%%

%%%Hi there, I've attached a file to this bug report with a compositor setup that uses a MapUV node. When I press F12 to render the composite image, the output from MapUV look unnecessarily blurry to me. The border of the UV mapped areas looks a bit odd too. Cheers, Chris %%%

Chris Want commented

2012-06-19 01:26:29 +02:00

Changed status to: 'Open'

Jeroen Bakker commented

2012-06-19 09:40:53 +02:00

%%%Hi Chris!

Same result as blender 2.63a. What exactly is the bug? or is this more a feature request?

Best regards,
Jeroen%%%

%%%Hi Chris! Same result as blender 2.63a. What exactly is the bug? or is this more a feature request? Best regards, Jeroen%%%

Chris Want commented

2012-06-19 17:39:13 +02:00

%%%Hi Jeroen,

Thanks for responding!

I would say that the bug here is that the resulting image
looks so bad that it's unusable.

For comparison, I've attached a second file that compares
the output from a transform node with the output from MapUV
(press F12 to render). It's my contention that the output from
the transform node is the correct result, and that the MapUV
output is the wrong result. These two nodes should be
performing similar operations to get their results, so should
look roughly the same.

I will probably end up using the transform node instead of
the MapUV node in the project I'm working on, so for me
this isn't a showstopper. It's a pity though, since the MapUV
node allows you the convenience of placing an inset image
using geometry in object space.

Best regards,
Chris
%%%

%%%Hi Jeroen, Thanks for responding! I would say that the bug here is that the resulting image looks so bad that it's unusable. For comparison, I've attached a second file that compares the output from a transform node with the output from MapUV (press F12 to render). It's my contention that the output from the transform node is the correct result, and that the MapUV output is the wrong result. These two nodes should be performing similar operations to get their results, so should look roughly the same. I will probably end up using the transform node instead of the MapUV node in the project I'm working on, so for me this isn't a showstopper. It's a pity though, since the MapUV node allows you the convenience of placing an inset image using geometry in object space. Best regards, Chris %%%

Sergey Sharybin commented

2012-06-20 20:55:04 +02:00

%%%Since it's not a regression and it behaves in the same way since 2.50alpha0 i'd call this thing to be improved, not a bug.

Added to our TODO list: http://wiki.blender.org/index.php/Dev:2.5/Source/Development/Todo/Tools#Compositing%%%

%%%Since it's not a regression and it behaves in the same way since 2.50alpha0 i'd call this thing to be improved, not a bug. Added to our TODO list: http://wiki.blender.org/index.php/Dev:2.5/Source/Development/Todo/Tools#Compositing%%%

Sergey Sharybin commented

2012-06-20 20:55:04 +02:00

Changed status from 'Open' to: 'Archived'

Sergey Sharybin closed this issue

2012-06-20 20:55:04 +02:00

Sign in to join this conversation.

No Label

Download

What's New

Blender Studio

Manual

Developers Blog

Documentation

Benchmark

Blender Conference

Development Fund

One-time Donations

Map UV makes mapped images blurry #31868