Announcement

**voytov** · 01-03-2011, 01:31 AM

Re: osx: UV doesnt work

.. Try to change "Material">"Texture">"Image settings">"Filter" which is probably ="Summed Area" to ="None"
It helped in my case.

**FB3000** · 01-03-2011, 02:00 AM

Re: osx: UV doesnt work

thanks voyotov but changing filter also didnt helped

**tinmanjuggernaut** · 01-03-2011, 02:43 AM

Re: osx: UV doesnt work

what about on a smaller, simpler scene to test?

What are the uv maps on that floor? Half of it is textured.

**FB3000** · 01-03-2011, 03:14 AM

Re: osx: UV doesnt work

1. simple scne with a plane - works but blender refereshes uv changes after second render try:
http://dl.dropbox.com/u/19725436/vb_bugs/UV_test.blend

2. not working example - uv made the same way as in 1. but still it doesnt use uv.
http://dl.dropbox.com/u/19725436/vb_bugs/noUV.blend

**bdancer** · 01-03-2011, 08:06 AM

Re: osx: UV doesnt work

Btw, it also doesn't work in Internal, so report a bug to Blender Bug Tracker.

**tinmanjuggernaut** · 01-03-2011, 02:31 PM

Re: osx: UV doesnt work

Originally posted by FB3000

1. simple scne with a plane - works but blender refereshes uv changes after second render try:

I added colormap as my image and rendered several times accurately, whether I export and render, or just rendered, uv map was accurate (and stayed put, see below). Upon loading the only things I changed are: detect vray, replace jpg with colormap jpg, tab out of edit mode (so uv map sticks), reduce resolution, then export and render. Nothing unusual on console.

Originally posted by FB3000

2. not working example - uv made the same way as in 1. but still it doesnt use uv.

How did you create your uvs? The UV map does look really messed up. When I look at the uv map editor, when I zoom in with my mouse wheel or out, the uv map jumps around with each click, or even disappears! Even if I delete the uvmap and recreate it it's still messed up. Also the uvmap through the camera is not accurate to vray. This is with your file, but my build.

Your nouv blender file is 7.5mb for a few cameras, a sun and some objects. I wonder if your default blender scene is corrupt.

I can create a uvmap on my default file and it stays put when I zoom in or out in the uv editor. Also what I see in the camera is updated in realtime, and is reflected in vray output. Attached is a simple file for your to play with.

Is this with your 64-bit build? Or do you see the same thing on one of bdancer's builds?

Cory

Attached Files

coryuv.7z (101.9 KB, 110 views)

**FB3000** · 01-03-2011, 02:53 PM

Re: osx: UV doesnt work

Thank Cory,
about 1.I reported that already to bug tracker here:
http://projects.blender.org/tracker/?fu ... group_id=9
- so it looks that this is some memory issue.

about 2.
Fisrt of all this is scene that was previously bigger - I deleted everything from it that wasnt important for that case. Even now 3 simple things have 7mb. I dont know if it is the reason but i suppose that it has something to do with this shity 2.5 pack images system.
Like U said UV editor is almost useless
- the view is jumping,
- unwraped mesh or cursor dissapers
- cursor is scaling with texture: http://dl.dropbox.com/u/19725436/vb_bug ... cursor.png

I created it like that:
- added plane, moved vertices
- added material
- added texture
- added image in tex tab
- selected object and went into edit mode
- U > project from view
- in uv image editor selected from rollup menu proper image
- in tex tab > selected UV mapping and proper layer

i tried vray and internal but blender behaves the same way.
Yes, this is on my 64bit build, but i tested the files also on older one build with the same result.

**FB3000** · 06-03-2011, 11:33 AM

Re: osx: UV doesnt work

Comment By: Ton Roosendaal (ton)
Date: 2011-03-06 19:17

Message:
Hi Paul.

I accidentally tested the wrong file... there was a UV.blend on my desktop too

Error is confirmed, but the UV Image editor is totally corrupted. It behaves very bad, which points at some memory corruption.
Loading this file with option "No UI" makes it behave OK again.

There's always a minor risk involved with compiling svn and using it... not to mention that building a stable blender is also not trivial always.
My suggestion is to warn the person who made this build to check on his compile settings. Doing clean builds is always advised. Applying patches is risky, and playing with optimize settings is even more.