>> I tried doing myMaterial.texture=newpicture(64,64,32).
>
>That'll work if you watn your texture to be blank.
>
Blank would be a start. All I can get is nil.
>> I tried making a separate picture object p and doing myMaterial.texture=p.
>
>That should work fine to set the texture to p. Note that this statement
>generates a texture from the given picture; you can't subsequently modify p
>and expect the texture to reflect it.
>
>> Neither works. Texture comes back as nil.
>
>That's really odd! Yet you're able to load and display textured objects from
>files?
>
>> Also, the examples don't demonstrate making a material, so I've exhausted
>> all the obvious things to attempt.
>
>I'm quite sure that the Trimesh Explorer example *does* make a material; it
>also lets you paste in any picture to replace the texture of an existing
>material.
>
>Best,
>- Joe
Under what circumstances would texture always be nil, Joe?
Quesa Model Viewer works, so I know I'm ok in that respect. I'm running Quesa
1.7, if that's relavant.
Does the Trimesh Explorer example use the r3 features, or declares? Where can I
download it?
Thanks,
Daniel
_______________________________________________
Unsubscribe or switch delivery mode:
<http://www.realsoftware.com/support/listmanager/>
Search the archives of this list here:
<http://support.realsoftware.com/listarchives/lists.html>
|