Incorrect UV Mapping in Preview #40462

New Issue

LS · 2014-06-02T03:10:49+02:00

LS commented

2014-06-02 03:10:49 +02:00

System Information
Windows 7 in Virtual Box

Blender Version
Broken: 2.70a (and also tested 2.66)

Short description of error
When importing from COLLADA file format the UV coordinates are mapped correctly on the texture, but displayed incorrectly in the preview window. Rendering the object works fine.
Image of the Error:
Sample COLLADA File: http://blackflux.com/dl/dragon.zip

Exact steps for others to reproduce the error

Opening new project in blender in virtual box windows 7 (without graphics support). I suspect that the non existing graphics support is the problem.
Import COLLADA file into project (see "dragon.zip")
Select texture manually if it's not mapped automatically
Error occurs (see sample image)

**System Information** Windows 7 in Virtual Box **Blender Version** Broken: 2.70a (and also tested 2.66) **Short description of error** When importing from COLLADA file format the UV coordinates are mapped correctly on the texture, but displayed incorrectly in the preview window. Rendering the object works fine. Image of the Error: ![umskupS.png](https://archive.blender.org/developer/F92335/umskupS.png) Sample COLLADA File: http://blackflux.com/dl/dragon.zip **Exact steps for others to reproduce the error** 1) Opening new project in blender in virtual box windows 7 (without graphics support). I suspect that the non existing graphics support is the problem. 2) Import COLLADA file into project (see "dragon.zip") 3) Select texture manually if it's not mapped automatically 3) Error occurs (see sample image)

LS commented

2014-06-02 03:10:49 +02:00

Changed status to: 'Open'

LS commented

2014-06-02 03:10:49 +02:00

Added subscriber: @vincent-6

Bastien Montagne commented

2014-06-02 14:06:05 +02:00

Changed status from 'Open' to: 'Archived'

Bastien Montagne closed this issue

2014-06-02 14:06:05 +02:00

Bastien Montagne self-assigned this 2014-06-02 14:06:05 +02:00

Bastien Montagne commented

2014-06-02 14:06:05 +02:00

We for sure can’t accept graphical-related bug reports from VM-ized OS! Even in plain classical ones, we already have a bunch of issues with drivers and GPUs, so in a virtualized ones…

Fazekas Laszlo commented

2014-06-02 14:28:02 +02:00

Added subscriber: @totoro-4

Fazekas Laszlo commented

2014-06-02 14:28:02 +02:00

I'm not sure what is incorrect. I got the same result under Linux x86 with NVidia 610 card and the rendering is similar to the preview. It's very similar to your picture but the colors are blurred on the preview and not big solid pixels. Maybe because you have software GL only and it works this way. The texture is very low resolution (4x10 pixels) so its pixels are quite visible without interpolation. The colors of the previewed big pixels are sampled with subpixel interpolation and that's why not the same as the colors on the texture. For example, the bottom corner on the dragon triangle is the topmost corner on the texture. You see a big orange pixel there as a mixture of the yellow and red pixels around the corner.

LS commented

2014-06-02 14:40:12 +02:00

So this seems to be a common bug on several systems. Just had another user describing it. Trying to get system specs.

@totoro-4: I totally forgot: For pixel accuracy rendering you need to disable mipmaps (file - > user preferences -> system). Can't edit the task unfortunately.

I think this is a valid problem and not just virtual specific. Please consider reopening! Thank you!

So this seems to be a common bug on several systems. Just had another user describing it. Trying to get system specs. @totoro-4: I totally forgot: For pixel accuracy rendering you need to disable mipmaps (file - > user preferences -> system). Can't edit the task unfortunately. I think this is a valid problem and not just virtual specific. Please consider reopening! Thank you!

Fazekas Laszlo commented

2014-06-02 14:46:45 +02:00

I can't confirm this, it is not a bug. What you see is only pixelated but basically the right mapping. It's because you don't have accelerated hardware GL on the virtual machine.

Bastien Montagne commented

2014-06-02 14:56:06 +02:00

dragon.zip (better to house this here)

Nope, definitively cannot reproduce either, what you describe is an issue with your VM-ized graphic system, afaict, probably a refresh issue of some kind…

Then, the BI render is always ugly, but that is to be expected imho, and indeed in 3DView to get sharp colors you need to disable all mipmap and aniso stuff, but there is no bug here, everything works as expected.

[dragon.zip](https://archive.blender.org/developer/F92349/dragon.zip) (better to house this here) Nope, definitively cannot reproduce either, what you describe is an issue with your VM-ized graphic system, afaict, probably a refresh issue of some kind… Then, the BI render is always ugly, but that is to be expected imho, and indeed in 3DView to get sharp colors you need to disable all mipmap and aniso stuff, but there is no bug here, everything works as expected.

LS commented

2014-06-02 17:10:17 +02:00

Thank you for your assistance! Seems reasonable not to debug VMs I guess.

I'll see if someone else with a proper graphics card can reproduce it, but for now let's keep it closed.

Thank you for your assistance! Seems reasonable not to debug VMs I guess. I'll see if someone else with a proper graphics card can reproduce it, but for now let's keep it closed.

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

Incorrect UV Mapping in Preview #40462