Jump to content

KT Kingsley

Resident
  • Content Count

    298
  • Joined

  • Last visited

Community Reputation

253 Excellent

About KT Kingsley

  • Rank
    Advanced Member

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

  1. Also the suitcase icon at the bottom left of the inventory window.
  2. I can't find any links myself now, and I can't remember where I thought I'd seen it before, but the dates for some of the drivers on 3DConnexion's driver archive page do go back a few years so it might be worth trying some of the older ones.
  3. Preferences/Network & Files/Directories/Conversation logs and transcript locations/Open will open the folder you want. Then open the sub-folder with the name of the avatar you were using when you were chatting. You should find the file of your chat there, named after the person you were chatting with. Ctrl+P to open the Preferences floater. I'm not sure if the files use the display name or the username, though.
  4. I've stuck with the SpaceNavigator driver version 6.18.0, the next update to which started inserting very irritating and intrusive dialog boxes whenever I activated it. I didn't see that version available on the 3D Connexion website (I didn't look very hard) but I do see it on some driver archive sites, which I'd be very wary of without a proper health check. Maybe reverting to the driver version that came on the installation disk might work better for you. I seem to remember that worked fine for me with SL and Blender.
  5. Remember that scripts use alpha, opacity, measured 0.0 – 1.0, while in the build floater it's transparency, measured 0% – 100%. So, different scales and measured the other way around.
  6. I don't find my SpaceNavigator helpful in build mode, when I usually really don't want to spin what I'm working on around. I find it a bit meh as an avatar controller, probably because I've not practiced enough to develop the lightness of touch and the precision it seems to need. But in flycam mode it's a really nice accessory to have, whether building, photographing or touring. Where it really comes into its own is in Blender (and, presumably, any other 3D modelling program). I'd happily continue to use SL without it, but I'd find using Blender with just the keyboard and the mouse a bit of a pain.
  7. Try replacing the 0.05, 1.0, with 0.5, 0.5,. I've no idea how the parameters are supposed to work with scaling, but those numbers seem to zoom in to 2x and back to 1x.
  8. Does using the Esc key get you back to the correct angle?
  9. You've overdone the ORs. Specifically, you should separate PSYS_PART_FLAGS from the ORed flags with a comma, and also separate PSYS_SRC_PATTERN from PSYS_SRC_PATTERN_EXPLODE with a comma. llParticleSystem( [ PSYS_PART_FLAGS,PSYS_PART_EMISSIVE_MASK| PSYS_PART_INTERP_COLOR_MASK|PSYS_PART_INTERP_SCALE_MASK, PSYS_SRC_PATTERN,PSYS_SRC_PATTERN_EXPLODE ,PSYS_SRC_BURST_RADIUS, 2.1 ,PSYS_PART_START_COLOR, <0.0, 1.0, 0.0> ,PSYS_PART_END_COLOR, <0.0, 0.6, 0.3> ,PSYS_PART_START_ALPHA, 1.0 ,PSYS_PART_END_ALPHA, 0.0 ,PSYS_PART_START_SCALE, <0.5, 0.5, 0.0> ,PSYS_PART_END_SCALE, <0.5, 0.5, 0.0> ,PSYS_SRC_TEXTURE, "407dfddc-ede1-4fe2-92a8-0176283aed58" ,PSYS_PART_START_GLOW, 0.5 ,PSYS_PART_END_GLOW, 0.3 ,PSYS_SRC_MAX_AGE, 0.0 ,PSYS_PART_MAX_AGE, 5.5 ,PSYS_SRC_BURST_RATE, 4.0 ,PSYS_SRC_BURST_PART_COUNT, 80 ,PSYS_SRC_BURST_SPEED_MIN, 0.01 ,PSYS_SRC_BURST_SPEED_MAX, 0.03 ] );
  10. The PSYS_PART_FLAGS are bitfield values (that is they are a set if individual one bit flags in a single integer), so they need to be ORed together using the bitwise OR operator "|" to make that integer. I think what's happening here is immediately following PSYS_PART_FLAGS you have the integer PSYS_PART_EMISSIVE_MASK which is taken to be the entirety of the flags, and following this you have PSYS_PART_INTERP_COLOR_MASK which has the same value (1) as PSYS_PART_START_COLOR, so the compiler then looks for a vector but finds PSYS_PART_INTERP_SCALE_MASK which is an integer.
  11. Not status. Prims. The buildings and landscaping for a Linden home do not count as part of the parcel's land impact, so you get the whole allocation to play with. Which is a considerable boon, as usually the buildings on a parcel take up a considerable portion of the allowance.
  12. Well, that was quick. Immediately after posting I remembered PRIM_SCRIPTED_SIT_ONLY and llSetLinkPrimitiveParams. Set that to FALSE and bingo! I can't think of any way that flag got set in the first place, though.
  13. I think the server forum is the right place for this… Just now, for the first time ever, and without any action by me, a couple of links with their own sit targets and set to sit on click, have started returning the "No suitable surface to sit on" message, whether directly clicked-to-sit or right-clicked and sit selected from the menu. It's true that neither does have an obvious sitting surface, but they did work properly before. The items, both meshes, are linked to a larger linkset that has a mesh as its root, and includes an assortment of prims and meshes. I've reset the scripts, but to no effect. Is this a known issue? Has anyone else experienced it, and, if so, have they found a cure? Or is it Jira time? Any other suggestions?
  14. There was a third party website that did let you send an IM to a user in SL. I can't remember any details. It wasn't anything to do with Linden Lab, though. The website communicated with an in-world server that would send the actual IM. If I remember correctly anyone wanting to use it first had to click on the in-world server and set up a password so that they could be authenticated when they went to the website. If this isn't functioning any more, I guess it's because the people who ran it stopped supporting it. If the website still exists but doesn't work it's likely that it's the in-world server that's not working, maybe because the people who owned it decided to stop paying for the land on which it once existed.
  15. llGetObjectDetails (http://wiki.secondlife.com/wiki/LlGetObjectDetails) allows you to ask for OBJECT_LAST_OWNER_ID. If that doesn't match the required ID you can then delete the object. ETA: Doh! But I don't think that'll work for objects in inventory?
×
×
  • Create New...