I'm glad the app is helpful to you,
tho, I'm pretty sure a model with no uv's would not load in any Away version
higher than 3.0 of the engine with no errors.
If the model is the same as before, you probably have loaded it into another
editor and exported it again, and the VT tag got somehow lost in the process.
Or you did use an older version of the engine
From 2.0 till 3.0, the obj parser was checking on missing uv's, and was adding
new ones to prevent this crash.
As many older exporters didn't care about generating uv's.
Here's the baby that made you a happy man :)
private function checkUV(id:int, uv:UV = null):UV
{
if(uv == null){
switch(id){
case 1:
return new UV(0, 1);
break;
case 2:
return new UV(.5, 0);
break;
case 3:
return new UV(1, 1);
}
}
return uv;
}
We've decided from 3.0 that we needed to be more strict (checks are expensive)
and that it's your responsability to generate models for the Away requirements.
That's also why this kind of features (correction tools in general) are found
in Prefab, where parsing performance is not important.
Fabrice
On Feb 10, 2011, at 4:55 PM, GenericDev wrote:
> OK.... the model (as above) does work in Prefab as is, and the
> exported version of the model from Prefab loads OK in Away. The
> exporter adds a (white) texture, as well as normals and uvs, which as
> John mentioned may be why it now works.
>
> Seems a bit peculiar that it worked fine in previous versions of Away,
> but not in the latest. But Prefab is a suitable workaround. Thanks.
>
> On Feb 10, 2:56 pm, Fabrice3D <[email protected]> wrote:
>> no. In Away valid uv definition has always been a requirement for a render.
>> not having a texture is something else. Prefab or Away will then applied
>> default ones (colormaterial in case of Away, BitmapMaterial +white map for
>> Prefab).
>>
>> Fabrice
>>
>> On Feb 10, 2011, at 3:13 PM, GenericDev wrote:
>>
>>
>>
>>
>>
>>
>>
>>> Hmm, is that a new change to Obj? It worked fine without textures and
>>> associated coordinates before.
>>
>>> On Feb 10, 1:56 pm, Fabrice3D <[email protected]> wrote:
>>>> and so, Prefab would have warned you about missing uv's data...
>>
>>>> Fabrice
>>
>>>> On Feb 10, 2011, at 1:27 PM, John Brookes wrote:
>>
>>>>> I think its because you dont have any UV data.
>>
>>>>> Just dropped your file into maya, and mapped some UVs and it worked in
>>>>> away.
>>
>>>>> ps it loads in prefab fine.
>>>>> Update your version of air, then you can use prefab.
