Page MenuHome

Grid mesh with x/y_subdivisions = 1762, 896 creates broken UV map
Closed, ResolvedPublic

Description

System Information
Operating system: Windows 10 Home, Ubuntu 18.04
Graphics card: builtin Intel GPU on Windows, Nvidia 1050 Ti on Ubuntu

Blender Version2.80 (sub 75), branch: master, commit date: 2019-07-29 14:47, hash: f6cb5f54494e
Works: recent development versions for 2.81

Short description of error

Grid mesh with subdivisions produce incorrect UV maps, depending on the number of subdivisions

Exact steps for others to reproduce the error
See the following script. Doing it manually gives identical results. Didn't find a pattern. Tried developer build from today and yesterday, those work as expected, i.e. produce a UV pattern like in "Correct" for all number pairs that I tried.

import bpy
w=1762
h=896
bpy.ops.mesh.primitive_grid_add(x_subdivisions=w, y_subdivisions=h, size=1.0, enter_editmode=False, location=(0,0,0))
grid=bpy.context.active_object
grid.name="Kaputt2"

w=1763
h=896
bpy.ops.mesh.primitive_grid_add(x_subdivisions=w, y_subdivisions=h, size=1.0, enter_editmode=False, location=(0,0,0))
grid=bpy.context.active_object
grid.name="Correct"

Event Timeline

William Reynish (billreynish) lowered the priority of this task from 90 to 30.Aug 6 2019, 3:09 PM

This should be fixed already. Can you try the latest build on builder.blender.org? Thanks

Well, I already did, see "Works: recent development versions for 2.81" and "Tried developer build from today and yesterday, those work as expected, i.e. produce a UV pattern like in "Correct" for all number pairs that I tried." above.

I wrote a bug report because the behaviour looks somewhat random and because I did't find an earlier report, so it might show up in later builds, again, because it seems, well, random. Given that we will have to wait for an 2.81 release, it would be beneficial to know about possible workarounds. If it is indeed already fixed, it might be possible to deduce that from the actual fix.

William Reynish (billreynish) changed the task status from Unknown Status to Resolved.EditedAug 6 2019, 5:43 PM

If it works in the latest builds, it is resolved. If this is important, you could just use a newer build rather than 2.80