Jump to content

Displaying inworld textures using shared media.


Innula Zenovka
 Share

You are about to reply to a thread that has been inactive for 471 days.

Please take a moment to consider if this thread is worth bumping.

Recommended Posts

Specifically, if I want to display an image that exists as a texture in-world using shared media do I have to upload a copy to a hosting service like gyazo and reference that in the <img> tag, or can I use the inworld uuid?   

I think I have to upload it but I'm just wondering if there's another way to do it.

  • Like 1
Link to comment
Share on other sites

It's possible, but the web interface textures get retrieved as a funky lowish resolution of 256x192.

The relevant (X)HTML is

"<img src=\"http://secondlife.com/app/image/"+(string)UUID+"/1\"/>"

for example https://picture-service.secondlife.com/b2d5eb75-b4bf-7763-28dc-d46a03f8e992/256x192.jpg

(for the curious, it seems plugging any other resolution into the above redirect URL does not work.)

Edited by Quistess Alpha
  • Thanks 3
Link to comment
Share on other sites

If you only want the image on the face of a prim, set the url of the media directly to the image URL, set the media scaling to 256x192, vertical texture scale to .75 and vertical offset to .875 (easier to do via build menu than via script).

But at that point, you might as well just set the face as a regular texture.

  • Thanks 2
Link to comment
Share on other sites

32 minutes ago, Quistess Alpha said:

If you only want the image on the face of a prim, set the url of the media directly to the image URL, set the media scaling to 256x192, vertical texture scale to .75 and vertical offset to .875 (easier to do via build menu than via script).

But at that point, you might as well just set the face as a regular texture.

Unless there's some use-case where it's easier / fits the workflow better to change the image URL than it is to use llSetLinkPrimitiveParamsFast(), etc...?

Link to comment
Share on other sites

Just now, Love Zhaoying said:

Unless there's some use-case where it's easier / fits the workflow better to change the image URL than it is to use llSetLinkPrimitiveParamsFast(), etc...?

Yeah, if you're mixing non-SL images with SL ones, I could see that being useful, as long as you know the resolution of all the non-SL images and can figure out a general formula for the vertical texture offset and scaling. or perhaps alternating showing an image with displaying some other kind of media (allowing the back image to remain a "you do not have media enabled" texture).

Tangentially relevant: it would only be able to receive clicks on that face if ctrl+clicked in a not-firestorm viewer (or firestorm with an obscure option enabled) or if the image was displayed through a simple page hosted on the prim via the image tag and a link.

  • Like 1
Link to comment
Share on other sites

You are about to reply to a thread that has been inactive for 471 days.

Please take a moment to consider if this thread is worth bumping.

Please sign in to comment

You will be able to leave a comment after signing in



Sign In Now
 Share

×
×
  • Create New...