Jump to content

panterapolnocy

Resident
  • Posts

    537
  • Joined

  • Last visited

Everything posted by panterapolnocy

  1. Lindens cannot share anything before the marketing team would. PPlus is aimed to be launched in the second part of May. No binding details about any benefits given, there are some suggestions See https://modemworld.me/2022/04/07/april-2022-web-user-group-summary-premium-plus/
  2. Teleport to a quiet region, for example https://maps.secondlife.com/secondlife/Loch Linden/ , clear your inventory cache, log out and log back in. Wait for around a minute and see if your items are back in place.
  3. Firestorm viewer does not have a dark mode option. Firestorm viewer has a set of skins. And the team is going to drop two of them if a new person that is willing to take care of them will not emerge. It is unfortunate that these problematic skins are the only ones that are the brighter ones, but this is the only way for the developers to stay sane. There is no fashion being pushed on anyone, no freedoms being taken. No politics being involved, not a conspiracy or a hidden agenda, no trends being applied. There is development time and resources being focused on different aspects of the viewer. I don't know if your OS has it, but Windows 10 and Windows 11 do support colour filters as an accessibility option, including "invert". I do have rather severe vision issues myself, which I'd rather not disclose here (but astigmatism is part of them), but when I wear my glasses I see everything mostly fine - dark letters on bright background or bright ones on the dark one like in Firestorm Gray skin - doesn't matter. I also keep proper lighting conditions in my room and do not stare at the screen for a few hours in a row. If in need I enlarge the font size in the viewer. I know my limitations. When my glasses were out of order once I didn't use my computer and just took a walk in the park instead. Again: I am aware that you'd like a light theme to stay in the viewer. Noted, understood. Answer: Right now it is not possible. Maybe it will be. Depends on the community. This is the fact. Posting a fourth post about mostly the same thing, a "dark mode as an option", won't help here. If you want to provide some help, then the best way to do that would be to learn how to modify viewer files (no one was born with these skills) and provide a new light scheme for any of the existing skins. Or to take care of StarLight skins, as a whole.
  4. float gTimerInterval = 7.7; // Experiment with this value, needs to be a bit shorter than the sound file (~ 8.0 - 8.1 s) integer gIsPlaying; integer gCurrentFragment; integer gSongLength; list gSong = [ "xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx", "xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx", "xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx", "xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx", "xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx", "xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx", "xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx", "xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx", "xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx", "xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx", "xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx", "xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx", "xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx" ]; setHoverText(string theText) { llSetText(theText, <1, 1, 1>, 0.5); } default { state_entry() { llOwnerSay("Loading..."); llStopSound(); setHoverText(""); gSongLength = llGetListLength(gSong); llPreloadSound(llList2String(gSong, 0)); llOwnerSay("Ready."); } touch_start(integer total_number) { if (llDetectedKey(0) == llGetOwner()) { gIsPlaying = !gIsPlaying; llSetSoundQueueing(TRUE); if (gIsPlaying) { setHoverText("Fragment 1/" + (string)gSongLength + "..."); llOwnerSay("Playing."); gCurrentFragment = 0; llSetTimerEvent(gTimerInterval); llPlaySound(llList2String(gSong, 0), 1); llPreloadSound(llList2String(gSong, 1)); return; } llSetTimerEvent(0); llStopSound(); setHoverText(""); llOwnerSay("Stopped."); } } timer() { ++gCurrentFragment; if (gCurrentFragment >= gSongLength) { gCurrentFragment = 0; } integer preloadIndex = gCurrentFragment + 1; if (preloadIndex >= gSongLength) { preloadIndex = 0; } setHoverText("Fragment " + (string)(gCurrentFragment + 1) + "/" + (string)gSongLength + "..."); llPlaySound(llList2String(gSong, gCurrentFragment), 1); llPreloadSound(llList2String(gSong, preloadIndex)); llSetTimerEvent(gTimerInterval); } on_rez(integer sp) { llResetScript(); } }
  5. I believe that https://wiki.secondlife.com/wiki/LlSetSoundQueueing can work just fine with a proper timer() set to 70-80% of sound samples length, sometimes up to 40 of them in a row (tested by creating a music box for a friend, with a lullaby song).
  6. Please check the @KT Kingsley's answer: As for this.. Mirrors code worked without any issues on my old laptop with GT520M card and 8GB RAM, with several surfaces acting as mirrors (and works even better nowadays with RTX 3060; Patch may be outdated for SLV, but is still being updated internally for FS). The main (if not the only) reason why the Lab didn't implement mirrors was the fact that the code didn't work in ALM mode (deferred rendering) - and they didn't have time and/or resources to forge anything out from the initial patch provided by Zi. However, as you may see in the Inara's article there is some interest again from the Lab's side to talk about this feature and maybe something will be done with it.
  7. There will be some changes because Firestorm team does care about problem reports. Maybe just not enormous, but who knows. Changing hex values is not a big deal (but takes time and a lot of testing regardless), but the team thought about retiring this set of skins, and was trying to patch/save it at the same time, for a far longer amount of time - it's not a decision that was taken over one single night. Everything has its limits... StarLight skins have more problems than just a different colour scheme - like compatibility issues with the main skin, that usually emerge after every bigger code merge - and there is no dedicated person in the team to track or fix them. They're structurally different enough from the main skin that you just cannot copy and paste some solutions, you need to create dedicated code just for StarLight skins. An alternative may eventually emerge, however, as... the Vintage skin is still maintained by the team. See https://jira.firestormviewer.org/browse/FIRE-31478 - note that no comment has been made on this suggestion for now. No decisions, no dates. That said, if anyone would like to pick the gauntlet and continue to maintain StarLight skins (as indefinitely as possible) - he or she is more than welcomed to do so. If no one will - FS will lose StarLight and StarLight CUI. This is not about forcing fashion on anyone, but about technical difficulties. Does anyone complain that an old operating system is not getting any official updates, drivers or upgrades anymore? No, because human resources were shifted to newer solutions and the first thing you get after contacting a helpline is "please update your OS". You'd get that reaction even with Linux if you'd like to get help while using an ancient kernel that no one has time and energy to patch anymore.
  8. I will just leave this here... not getting into the antivirus discussion myself. ~
  9. You need to decide for yourself if they're more or less meaningful. Complexity is a general value reported to the simulator by all viewers present in the vicinity, calculated based on a fixed formula. Performance floater is measuring how hard it is for your computer to render everything around - that's why distance, LOD and graphic settings matter - and the results will generally differ between two different (more/less powerful, different settings etc.) machines. See: https://beqsother.blogspot.com/2021/09/find-me-some-body-to-lovebenchmarking.html https://beqsother.blogspot.com/2021/11/i-dont-wanna-mesh-with-nobody.html https://beqsother.blogspot.com/2021/12/upgraders-of-lost-arc.html https://beqsother.blogspot.com/2022/03/how-to-use-new-firestorm-performance.html
  10. Join this group inworld and state your questions in group chat. Please note that Firestorm project does not give support for compiling the viewer on your own - this group is created by coding enthusiasts.
  11. Hm. I guess that you'll need to try to update again when the new version will emerge. The current newest version (https://releasenotes.secondlife.com/viewer/6.5.3.568554.html) was released at February 28, but this fix ("360 Snapshot tool fails to save file to computer", on "DRTVWR-540-maint" branch) was pushed to the code repository at 2nd of March, two days later. You may eventually try to use the maintenance version of the viewer in order to check if the issue is fixed there for you (and it actually may be: "Urgent Fixes - The 360 snapshot capture works again.", see this bug report as well) - but you do this at your own risk.
  12. All you need to do is to click on the "create" button (preferably with "max quality" being checked above said button), then on the "save" one. A file picker window should open, allowing you to save the file in a selected destination directory. If the file was not created, depending on your operating system or antivirus application, check if the viewer has permission to save to that directory (some operating systems / AVs deny saving to some locations because of ransomware protection mechanisms). You may also want to update your viewer or try a different directory, away from the user folders - for example in c:/My360Snaps.
  13. 1) 32 bit version of the viewer WILL crash much more often than the 64 bit one because of the memory limitations. 2) For the 64 bit version: Make sure that you perform a full CLEAN install of the viewer, step by step: https://wiki.firestormviewer.org/fs_clean_install And don't forget to whitelist your viewer installation as well, as cache/settings folders: https://wiki.firestormviewer.org/antivirus_whitelisting
  14. It may be a bit silly, but I cannot get rid of this - at least for me - Sprigatito earworm, for a few days now.
  15. Today I decided to sprinkle myself with a bit of retrowave glitter. A small and colourful treat, as an opposite to the gray real life. Pictures were taken in Backdrop City.
  16. https://wiki.firestormviewer.org/fs_stored_passwords#failed_to_decode_login_credentials https://en.wikipedia.org/wiki/KeePassXC
  17. I believe that this is the case in this topic. As far as I know there is no setting in the viewer to change that. In Firestorm that behavior was specifically changed in the code itself, so landmarks are saved into the Landmarks folder (commit here), while Second Life viewer still saves into Favorites (see this one).
  18. Replace this: setGlossColor(vector color) //Function With this: setGlossColor(vector theColor) //Function And then in your function use "theColor" in your llSetLinkPrimitiveParamsFast().
  19. For me NFTs are like sticky notes on a board. You see a car on the street you like and place a sticker on said board saying "that car is mine now". You own the sticker, yes. But not the car itself. The sticker is absolutely worthless. You show your board to everyone in the world and say "I own this" and everyone will agree... that you own the sticky note only. Let's say that you own the car and you have that sticker on your board. You want to sell the car to another person and as proof you want to give them the sticker. What would they say? That it's worthless, and they want actual ownership transfer regulated by law, signing an actual contract, passing registration etc. You want to "mint" the car, make something that is based on it, and call it your own (not make the picture of the car and play with it, but let's say replace wheels and spoiler, remove the original logo and branding, then call it PopBlenderCar). Well, personally I haven't heard about any car manufacturer officially allowing derivative work based on their cars. Usually, if you "remix, transform, or build upon the material" you are sued for copyright infringement, unless a license clearly states otherwise. Also the "NFT can be shared across platforms and applications in the real world" argument. Great. I will give you a red cube in Second Life. Or a green one. Or even blue. As a no-copy, I will even delete the original, so you will have the only existing copy of it (that's actually an NFT object within the grid itself already, but let's continue). Now, import it to Call of Duty, Undertale, River Raid or Microsoft Flight Simulator and make sure that it has exactly the same properties and possibilities as it has in Second Life, including 3D manipulation, ability to be hollowed, twisted, recolored, with its own prim inventory etc. Not possible? "But I have an image of it and I can import it everywhere, therefore the cube is NFT". No, it's not. It's just an image and proves nothing. The cube stays in the Second Life simulator environment, on Linden Lab / OpenSim servers. --- There ARE some good applications of NFT, but are not really necessary. For example, a lottery tickets system - you can get a digital NFT-ticket and wait for the results of the lottery. But when the winner is revealed, you don't own his/her prize, just the digital NFT-ticket which lost its "probability" value, but in theory can be kept and in a decade or two have some historical value. But why use NFT for that, when you can just utilize a regular paper ticket, or a digital payment confirmation from a bank or payment processor like PayPal? "Privacy" is not really an option, as blockchain will point at you as the owner of NFT... that's one of its basic functions, after all.
  20. I'm not sure about other TPVs, but in Firestorm the "Web" tab does expose the homepage URL at the very top. Clicking on the "load" button fetches contents of the page directly into the profile window. Interestingly, it has a different capitalization than the Lab's native web profile that is changing everything into lower case. Ticket could be useful. As a workaround I'd suggest to use a service like TinyUrl, for example: https://tinyurl.com/frankie-palmero-actor-flickr
  21. Without complicating it with the usage of strided lists, just as an example... Try to put this in the listen event instead of the ifs. integer pos = llListFindList(colorsNames, (list)msg); if (~pos) { setGlossColor(llList2Vector(colorsList, pos)); } And add this at the top. list colorsNames = ["Black", "Violet"];
  22. If that would be true, then we wouldn't start Firestorm support group(s) believing that we just don't need one. It's no secret that Firestorm codebase is based upon Lab's, like most TPV codebases, and that it lags a bit behind it due to some internal reasons - like health, free time or bugs that surface for FS during testing (yes, we do test stuff) and do not show up for the LL's viewer due to sheer level of complication, dependencies and options the FS viewer have and is loved for. Don't forget that FS supports Linux as well, better or worse, so the project has one more platform to care about. Oh, and OpenSim as well. ~ The lone fact that Firestorm has more options automatically makes it slower than the official LL one, which doesn't have as many functionalities under the hood as FS. Linden Lab is hammering out the proper shape out of their Viewer Performance Improvements Project viewer, but it will take some time before it will go public. You know, there was a reason why FS 6.4.21 was clearing the cache on first boot. I hope that you documented - with logs, facts and in a replicable way - the issues you've mentioned on the Firestorm JIRA bug reporting system in order for devs to be able to check them, fix them and give an answer - and not just "spread the word" on the forums. If not, then that would be nice! You cannot deny the fact that there are a handful of creators that do ask people to pull LOD up to 4.0 or higher. Or that some users try to run ultra graphics on built in Intel cards. No one said that Firestorm is perfect - if such a thing happened, please quote it - every single case is different and needs an individual approach, but it's not the viewer to blame and bash every single time. Again, that's why FS has support division, JIRA etc. You cannot compare apples and oranges directly, LL's and FS. That is what is done all the time, even in this very forum post. It's no secret that older machines run less demanding programs visibly better. Nonetheless, Second Life is built in a way that can cause any machine to crawl, regardless of the viewer. Please publish your tests and methods, in an extensive and detailed way - I'm interested in seeing the results. Don't forget to check if all settings are the same - water, occlusion, DoF, shadows, LOD, draw distance, impostors etc. - same as conditions - time of the day, avatars amount, location, cache being full or not, applied EEP. They can be analysed, issues targeted down and fixes applied. Win for everyone. ~ +1.
  23. Good luck and prosperity in the incoming Year of the Tiger. 新年快乐. And so... today I will be tiger-plushie-fied all around.
×
×
  • Create New...