PRIM_MEDIA_FIRST_CLICK_INTERACT settings are not working correctly [INVALID]
closed
Tapple Gao
I made a mistake, and there is no bug. On my test prim, I had 2 media faces set. One had PRIM_MEDIA_FIRST_CLICK_INTERACT set to TRUE, and on the other face, PRIM_MEDIA_FIRST_CLICK_INTERACT was FALSE. I was testing the FALSE face in world and the TRUE face in the hud. The reproduction is invalid and there is no bug
--------------
Rez a prim on the ground, and put this script in it:
init() {
llOwnerSay((string)llSetPrimMediaParams(4, [
PRIM_MEDIA_HOME_URL, "https://secondlife.com/destinations",
PRIM_MEDIA_FIRST_CLICK_INTERACT, TRUE,
PRIM_MEDIA_AUTO_PLAY, TRUE
]));
}
default {
state_entry() { init(); }
on_rez(integer param) { init(); }
}
- Open the script window
- Set Me > Preferences > Sound & Media > Media first-interact to "Landowner Objects" (this is the default)
- Close preferences
- Wait for the media to start playing. Click the prim until it does play
- Click the home button to show the secondlife destination guide
- Click the script window
- Click one of the pictures in the destination guide ONCE
Expected: the prim should navigate to that place in the destination guide, because
- PRIM_MEDIA_FIRST_CLICK_INTERACT is TRUE
- Media first-interact is "Owned Objects" or above
Actual: The media face gains focus, but nothing else happens
Now pick up the prim and attach it to hud center. Repeat the above steps:
- Wait for the media to start playing. Click the prim until it does play
- Click the script window
- Click one of the pictures in the destination guide ONCE
This time, the media correctly navigates to the new page
Log In
Dan Linden
marked this post as
closed
Dan Linden
Thank you for the update, Tapple! Issue closed.
Tapple Gao
I tested this in 3 viewers, and all have the same bug:
- Second Life Project Lua Editor 26.1.1.24528939506 (64bit)
- Alchemy Test 26.2.0.62422 (64bit)
- Firestorm 7.2.2 (79439) Nov 7 2025 16:03:06 (64bit / AVX2) (Firestorm-Releasex64)
All tested on Fedora Linux 44
Hecklezz Resident
Tapple Gao The firestorm version you tested on is quite old at this point, can you test it on our latest 7.2.4?
Tapple Gao
Hecklezz Resident May as well. I thought I'd test on that old firestorm to see if it had been around a while, as my other 2 viewers are up to the minute github HEAD builds
- The bug also occurs on Firestorm 7.2.4 (80712) Jun 1 2026 11:53:51 (64bit / AVX2) (Firestorm-Releasex64)