lets see if it is a bit more clear here
https://youtu.be/EAobUHJ5s30

i did more tests on a 3dsmax, importing from file import does not read the uvs, but importing object by object creating the primitive (alembic can be created as a primitive like a cube, click alembic on prim select the path the object click on the scene) it does read the uvs, also created rotated 90º but that its a max thing ^^
So it seem that yep the uvs are there, didn't try to export and import alembic on max to max, to check if its a soft thing or an alembic thing

also notice that to repeat the test from step one, at least in windows blender needs to be restarted or do a Ctrl+n to work a new file, directly reloading the file leaves a greyish mesh, not a white one as in step one.

Not a developer, but need to add more info,

i have a question about that, since the GP stroke sculpt can only be done under Stroke editing, is there a way to block other shortcuts that are unused? is not posible to select any uv island or move them or rotate them (G,R,S) anyways if the Gpencil Stroke editing its active
Other possibility( this is always as a user point of view) is to disable E as a quick short cut to sculpt or add a conditional key stroke at least in the uv image editor. Using pie menu D+E works fine, its not as practical as E but at least is there.

humm i wasn't aware of that.
If that's the case, sorry, my bad

ok
is this mailing list the place to raise the topic? ------> bf-translations-dev@blender.org ?

sorry i made a mistake on the version number, the last one i tested from builder that fails its
39ae324

Step to reproduce the error:
1-

to sum up, this termator thing affects reflections, refractions, bump maps or ¿can we call it shading distortion? and also shadows(actually shading not shadows per se)?
it seems to be a really big stuff not only a few things, basically affects every possible material that we could create exept volumetrics, emmit or non distorted shaders on high poly count models.
It could be possible to add some experimental feature at least to have a possibility to do a workaround using experimental stuff? or this will mess with some core functionality?
(yes i know this is not the place for feature request, im trying to understand how deep this problem is)

i didn't realized but yes i got the same on the consol
https://www.youtube.com/watch?v=1IxKx--qzc0&feature

~, ~ dyslexia and short sighted sorry, the working and double check build its Hash: 5c8fc8e

sorry the working version build was Hash: 5c8tc8e

after two more hours testing, i had reduce the sample file down to a single case

thanks for testing
i just downloaded both 32 and 64 version of the las build blender-2.74-3bffcc6 for windows, both still crash the same way, actually now also crash rendering using the button in the interface(but using the interface its a really random crash), so the deal must be among the object and the armature, removing the armature worked really well for me in my tests, maybe its on the material, i leave the material because removing it didn`t fully stabilized the render but made the crashes more random.

""Light Groups
In the Material buttons (F5) Shading panel, you can indicate a Group of Lamp Objects to be used as light for rendering, instead of the usual visible Lamps. This actually enables per-Material lighting (independent of which Object has the Material, or whether the Lamps are in visible layer).
If you don't want Lamps from a Light Group to work on the other Objects, just move them to an invisible layer.""

ok i fell a bit dumb because its weird but it works as it use to worked on blender 2.49 just cheked, sorry

just came up with a different situation but same bug,
on the step 1-fille above.
2-create a lamp
3-Ctrl+G to add the lamp to a group
4-F6 to access last operator options
5-change the name of the group
6-Accept the change using the key intro on the keyboard
7-switch to the original scene, just as the undo

Thanks
i imagine something like that could be happening, the work around was to copy the points from the vse the ones im interested on, to a new grease pencil data block and that work, but it took a wile to figure it out ^ -^,

the "Intro" submit the report before finish it.
2- hover on the right monitor (the vse) and select using A (that should work)
3- hit A again to deselect
4-try on the right monitor(the vse) to select a grease pencil point using Right click.
5- look at the crash.

this bug was reproduced under a linux system. . . y forgot to ask for info about that system, but at least i know its posible to repeat it outside windows

someting i realized, at the moment of testing if you are using windows, hide the bottom desktop tasks bar or move it to a second monitor, the bar makes the blender window a bit smaller and the test file no longer works.
Again seem extremly difficult to get the angle, but i accidentally trash several textures because of this before realizing what was happening.

tested using e2c412f and it seem to be working fine, no crashes.
thanks for cheking

im just a user, but that happened to me when i didn't fully uncompress the .zip file of a portable build.

enzyme69, do you mean this?

@mont thanks for the tip about "---" ill take didn't know about it ^^, and also for the fix, ill test it as soon as i get a new version from builder or graphic all.

by the way, an off topic
don't know way that "2-start any render" its bold and bigger and i cant edit my reports, the site doesn't allow me

for some reason i cant edit the info
this is the image reference file
http://www.pasteall.org/pic/68254

Fixed File, but it seams that is the same with geometry or no the parent crashes the file, unfortunately i could not reproduce the error outside this mesh.
http://www.pasteall.org/blend/26006

geometry its missing but still crashes, just with the empty reference objects parented

I just download the file at home, it seams to be that the sample file has some linked geometry that its at the server at the office, ill fix the sample file on Thursday.
my bad sorry