Jump to content

Nofunawo

Resident
  • Posts

    64
  • Joined

  • Last visited

Everything posted by Nofunawo

  1. The original ZHAO-II has no "SitAnywhere" Option. I think you're talking about the ZHAO-II-MB or other extensions based on the zhao-II. Yes, the CTRL-ALT-S brings the Ava to Sit. But using the Stand button is one-click. Stopping the "SitAnywhere" also.
  2. Groundsits...yes, you can stuff the FS AO with groundsits and Ctrl-Alt-S lets you sit down. And before you ask: Hover, flying and...is also available.
  3. Maybe you inform yourself before judging. https://gyazo.com/da0f5fc45a6bf3e93e1d7e8d81bd12bf
  4. Ah, you don't like a FS...now I get it.
  5. You know that the viewer-side AO is an option? Why is an option useless? Cause you don't like it?
  6. The current FS Beta 7.1.10.75843 is not based on the DeltaFPS viewer. It is based on the Atlasaurus release. Just read the Beta NC: This beta aligns us with the LL release known as "Atlasaurus". It has a number of performance improvements to support lower end hardware, though I would note that this is not the final set of updates that we are expecting. A further viewer update dubbed "DeltaFPS" is currnetly being worked upon and we will of course incorporate those changes as they become stable and mature. FPS limit: There is also an option to limit FPS depending on the app in the NVIDIA settings - it will probably also be available for AMD...or Intel...
  7. Using a 2048x1024 texture doesn't make me crash on 6.6.17 - only using this texture in a group pic, does.
  8. AFAIK only Win is affected. Linux doesn't seem to have the issue. And it is only with 2048x1024 - as I stated before 2048x2048 is OK. And yes, I don't understand why someone puts a 2048 Texture in this tiny group pic field. I could give my opinion, but it would not be covered by nettiquete. But of course a black K on a white background needs 2048 pixels...
  9. Don't know. I didn't open one. I'm running fine with 7.1.9 and am not affected by the problem. my very selfish thoughts: Let one of the PBR refusers do it. But the FS team has already been informed about this and they have already mentioned it in the FS chat. I'm curious to see if 6.6.17 will be fixed after all or if they will stick to their word.
  10. Just did some tests with 6.6.17 (!) Group picture: 2048x2048 no crash 2048x1024 immediate crash I think anyone who tries can confirm.
  11. Yes, it is only for UDP and yes, UDP has nothing to do with textures and meshes. AND UDP is nowadays only a "side note" using SL...as most traffic (99,xx%) is not UDP anymore... BUT 🙂 (there is always a but) if your internet connection is very slow and/or you are using WIFI it still can be an issue. I personally run with 3000 since years, without any issues and it will also work fine for the most users - but saying it is irrelevant is not correct.
  12. Germany, Best in the last years was 5 working days (once). Standard: 7-8 days. Worst 13 days (the last time - a month ago). But at least it's getting more and more expensive 🙂
  13. O.K. first of all HE needs to install a 64bit version of the FS viewer.
  14. First of all she (I guess) needs to install a 64bit version of the FS Viewer.
  15. Yeah, one "problem" is the integrated GPU. You can try to set this option (see picture) to lower the VRAM usage (only 1GB available) But the real problem is that you use a 32bit Version of the viewer: Firestorm 6.6.17 (70368) Dec 10 2023 18:34:00 (32bit / SSE2) Which limits your memory usage. 12GB are available but can't be used with a 32bit version running. You Texture limit, for the "GPU" is set to 512MB´: Texture memory: 512 MB (1) which should be fine for the crappy Intel "GPU". You can try 768 but I don't think that will change much. One more not related to your problem.Your Disk cache: Max size 2048.0 MB (78.2% used) Viewer allows 10GB Disk Cache - if the space on your disk is not limited set the cache to 10GB.
  16. Yes, just a genius, with a black belt in reading, is able to find the older downloads:
  17. Interesting how many people here know what "THE SL" user wants and how SL should be. Didn't know I give them permission to talk for me. Must have missed the letter. Learned SL is something for masochists and freaks...for me SL is the thing that gives me space for my imagination and skills like no other. Some of which I learned the hard way over years of SL. Doing mesh, scripting...and now it's a wonderful playground full of possibilities. And now this world, which is still wonderful for me, has been updated and looks better than ever. Great. Do I have to get used to it? Yes. I'm happy to. Decent EEP, a bit of tweaking here, getting used to material textures...yay. Stuff to explore.
  18. Nofunawo

    AO Help

    Abranimations
  19. And that is my solution for the original question. There is neither a limit of 12 nor 24 as it uses numbers for the buttons. The "*List*" command prints all options to nearby chat - which is a quicker way to choose if there are many entries in the menu. integer chan; integer cHandle; integer chat_handler; integer chatchan; key id; integer idxMenu; list lTextures; string CurTex; integer NumTex; integer sum; texture_me() { CurTex = llList2String(lTextures,NumTex); llSetLinkTexture(LINK_SET,CurTex,ALL_SIDES); } buildMenu(key id) { llListenRemove(cHandle); chan = (integer)(llFrand(9999999) * -1); cHandle = llListen(chan, "", "", ""); list menu; integer i; string out = "\nTextures\n"; out+="\nCurrent Texture: "+CurTex+"\n"; string num; if(idxMenu > 0) menu += ["<<PREV"]; else menu += ["*List*"]; if(idxMenu*10+9 < sum - 1) menu += ["NEXT>>"]; for(i=idxMenu*10; (i <= idxMenu*10+9) && (i <= sum - 1);i++) { num = (string)(i+1); out += "\n"+num+": "+llList2String(lTextures,i); menu += [num]; } llSetTimerEvent(30); llDialog(id, out, menu, chan); } listing() { llOwnerSay("Chat command will work for 60 seconds:"); llSetTimerEvent(60); llListenRemove(chat_handler); chatchan = (integer)llFrand(60000) + 12345; chat_handler = llListen(chatchan,"","",""); string titel; integer c; string output; string object=llGetObjectName(); while (c < sum) { titel = llList2String(lTextures,c); output = "[secondlife:///app/chat/"+(string)chatchan+"/"+(string)c+"/ "+titel+"]"; integer d = c+1; llSetObjectName("# "+(string)d); llOwnerSay(output); llSetObjectName(object); c++; } } init() { sum = llGetInventoryNumber(0); integer i; string name; lTextures = []; for(i=0; i<sum; i++) { name = llGetInventoryName(0, i); lTextures += [name]; } } default { state_entry() { init(); } timer() { llSetTimerEvent(0); llOwnerSay("Menu/Chat timed out - Touch again"); llListenRemove(cHandle); llListenRemove(chat_handler); } changed(integer chg) { if(chg & CHANGED_INVENTORY) { llOwnerSay("Hello "+llKey2Name(llGetOwner())+", change detected - will reset"); init(); } } touch_start(integer touchme) { idxMenu = 0; buildMenu(llGetOwner()); } listen(integer channel, string name, key id, string message) { llListenRemove(cHandle); if (message == "*List*") { listing(); } else if (message == "NEXT>>") { idxMenu++; buildMenu(id); } else if (message == "<<PREV") { idxMenu--; buildMenu(id); } else if (channel == chan) { NumTex = (integer)message - 1; if (NumTex >= 0) { texture_me(); } } else if (channel == chatchan) { NumTex = (integer)message; texture_me(); } } }
  20. if (action == "zoom") { vector agentSize = llGetAgentSize(keyid); if (agentSize == ZERO_VECTOR) { llOwnerSay("Zoom in " + cbcAgentProfile(keyid) + " not possible. Most likely the Avatar left the Region"); return; } list details = llGetObjectDetails(keyid, [OBJECT_POS, OBJECT_ROT]); vector tPos = llList2Vector (details, 0); rotation tRot = llList2Rot (details, 1); llClearCameraParams(); llSetCameraParams ([ CAMERA_ACTIVE, TRUE, CAMERA_FOCUS, tPos, CAMERA_FOCUS_LOCKED, TRUE, CAMERA_POSITION, tPos + (camera_offset * tRot), CAMERA_POSITION_LOCKED, TRUE ]); llSetTimerEvent(1); } The timer aks again for pos & rot and sets camera focus & position. It is not smooth but it fulfills its purpose 🙂 camera_offset is a defined vector to show the ava in full size and not the belly only...
×
×
  • Create New...