UV Project - Specified UV Map doesnt work properly #36759

New Issue

Carlo Andreacchio · 2013-09-18T06:21:01+02:00

Carlo Andreacchio commented

2013-09-18 06:21:01 +02:00

%%%--- Operating System, Graphics card ---
Windows 7, x64, gtx 580

- Blender version with error, and version that worked ---

tested with r60058M with both cycles & blender render

- Short description of error ---

UV Project onto a specific UV Map doesnt work properly... It is based on which item is selected in the object properties

- Steps for others to reproduce the error (preferably based on attached .blend file) ---

Open Attached blend file
go into rendered mode (material setup is of attribute uv2, so it should display the uv coordinates of uv2)
in mesh properties click on UVMap, then uv2
notice how the colours are changing
go into the modifier menu and notice that the uv map that should be effected by the uv project is uv2.. this should mean that whichever uv map you have selected shouldnt change the output of the attribute uv2...

%%%

%%%--- Operating System, Graphics card --- Windows 7, x64, gtx 580 - Blender version with error, and version that worked --- tested with r60058M with both cycles & blender render - Short description of error --- UV Project onto a specific UV Map doesnt work properly... It is based on which item is selected in the object properties - Steps for others to reproduce the error (preferably based on attached .blend file) --- 1. Open Attached blend file 2. go into rendered mode (material setup is of attribute uv2, so it should display the uv coordinates of uv2) 3. in mesh properties click on UVMap, then uv2 4. notice how the colours are changing 5. go into the modifier menu and notice that the uv map that should be effected by the uv project is uv2.. this should mean that whichever uv map you have selected shouldnt change the output of the attribute uv2... %%%

Carlo Andreacchio commented

2013-09-18 06:21:01 +02:00

Changed status to: 'Open'

Dalai Felinto commented

2013-09-18 14:37:52 +02:00

%%%I cannot reproduce the bug with your file and the version you mention. (OSX, ATI here - so using CPU rendering)
In fact your (4) doesn't happen here unless I remove 'uv2' from the modifier, or disable the modifier. Are you using CPU or GPU for your tests?

You mentioned the internal render engine as well. Can you provide a file where I can see the error in the render internal too?%%%

%%%I cannot reproduce the bug with your file and the version you mention. (OSX, ATI here - so using CPU rendering) In fact your (4) doesn't happen here unless I remove 'uv2' from the modifier, or disable the modifier. Are you using CPU or GPU for your tests? You mentioned the internal render engine as well. Can you provide a file where I can see the error in the render internal too?%%%

Brecht Van Lommel commented

2013-09-18 15:16:09 +02:00

%%%I can confirm the issue with 60205 on OS X, if you changing the active UV map will change the render, which it shouldn't.

It shouldn't matter if this is GPU render or blender internal, this looks like a modifier bug.%%%

%%%I can confirm the issue with 60205 on OS X, if you changing the active UV map will change the render, which it shouldn't. It shouldn't matter if this is GPU render or blender internal, this looks like a modifier bug.%%%

Bastien Montagne commented

2013-09-18 18:05:47 +02:00

%%%I can confirm the issue with the file you uploaded too (both internal and cycles). However, I cannot redo it from scratch, so I would be inclined to think that your file is somehow corrupted.

We need a way to reproduce the issue starting from default scene to be able to investigate this, imho.%%%

%%%I can confirm the issue with the file you uploaded too (both internal and cycles). However, I cannot redo it from scratch, so I would be inclined to think that your file is somehow corrupted. We need a way to reproduce the issue starting from default scene to be able to investigate this, imho.%%%

Brecht Van Lommel commented

2013-09-18 18:31:23 +02:00

%%%It's the MLOOP_UV and MTEXPOLY layer names that are out of sync. I'm not sure how that happens, but Campbell added a related fix a few days ago, maybe that should also fix up names.
https://projects.blender.org/scm/viewvc.php?view=rev&root=bf-blender&revision=60158%%%

%%%It's the MLOOP_UV and MTEXPOLY layer names that are out of sync. I'm not sure how that happens, but Campbell added a related fix a few days ago, maybe that should also fix up names. https://projects.blender.org/scm/viewvc.php?view=rev&root=bf-blender&revision=60158%%%

Carlo Andreacchio commented

2013-09-19 02:27:38 +02:00

%%%Updating to the latest build bot still returns the same error.

These steps I took to replicate it fully in a new blend file

delete everything in the scene
add mesh plane
scale plane to fit approx grid
add camera and move / rotate to position
on plane add two uv maps though mesh menu
rename maps to uv1 and uv2, in that order leaving uv2 selected and uv1 with render visibility on
split top view and bring up node editor up there
through node editor add new material
delete diffuse bsdf, add emission, and attirbute node, set attribute to uv2, vector output of attribute goes into emission
go into modifier menu, add uv project modifier
set camera to camera, uv map to uv2
toggle rendered mode
switch between selected uv maps in mesh menu
try applying scale to see if that does anything and then realise it doesnt

I have tried this in BI aswell, but same problem.

%%%

%%%Updating to the latest build bot still returns the same error. These steps I took to replicate it fully in a new blend file 1) delete everything in the scene 2) add mesh plane 3) scale plane to fit approx grid 4) add camera and move / rotate to position 5) on plane add two uv maps though mesh menu 6) rename maps to uv1 and uv2, in that order leaving uv2 selected and uv1 with render visibility on 7) split top view and bring up node editor up there 8) through node editor add new material 9) delete diffuse bsdf, add emission, and attirbute node, set attribute to uv2, vector output of attribute goes into emission 10) go into modifier menu, add uv project modifier 11) set camera to camera, uv map to uv2 12) toggle rendered mode 13) switch between selected uv maps in mesh menu 14) try applying scale to see if that does anything and then realise it doesnt I have tried this in BI aswell, but same problem. %%%

Carlo Andreacchio commented

2013-09-19 02:45:31 +02:00

%%%Here is an updated blend file which should work for both BI and Cycles... just toggle uvmap and uv2 as mentioned before.%%%

Bastien Montagne commented

2013-09-20 13:14:49 +02:00

%%%Fixed in r60260, thanks for the report. :)%%%

Bastien Montagne commented

2013-09-20 13:14:49 +02:00

Changed status from 'Open' to: 'Resolved'

Bastien Montagne closed this issue

2013-09-20 13:14:49 +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

UV Project - Specified UV Map doesnt work properly #36759