panterapolnocy

Since open source doesn't count here... I'm a web developer in the paid RL, working in a small company - doing not very interesting stuff for a regular mortal, I'd guess. Server maintenance (yay for PuTTY), PostgreSQL/MySQL databases, PHP, XML, APIs; HTML/CSS/JS/AJAX etc. on frontend as well. Sometimes things even don't blow up.

Make sure that you are not using any customized Personal Lighting and that you also have ticked the Top menu -> World -> Environment -> Use Shared Environment.

Well then. I guess that the app didn't exactly find the face. I've tried at least! I've chosen the "Witch Doctor" song from the list of available titles, by Cartoons.

Hello, First of all, none of the viewers that are listed in the official Third Party Viewer directory should harm your machine - which means that Firestorm (and Black Dragon) will run just fine and if you see any alerts coming from Windows/Defender, then it must be because of the lack of code signing - that is to be expected. In case of doubt, please see https://wiki.firestormviewer.org/is_my_viewer_safe As for Black Dragon's avatar imposters / detecting avatar complexity functionalities - I'd take a peek in its preferences, into the Display tab, and look for appropriate settings to change the limits.

A soundtrack from one of the most favourite games of mine.

Click on the "customize" button to customize your day cycle and see when sun is rising and when is setting down - this should give you an idea and potential place to modify everything to your liking.

I've set my own home parcel like that - 24 hour clock, matching current EU time (GMT + 1/2)... so when it's dark behind the window in RL, it's also dark for me in SL. Open the Environment tab in About Land window and set the "Day Length (hours)" to 24, then manipulate the "Day Offset (hours)" slider until the "Apparent Time of Day" below matches the desired real life time.

Hola. Intente seguir los consejos y sugerencias que se mencionan en esta página: https://translate.google.com/translate?sl=en&tl=es&u=https://wiki.firestormviewer.org/fs_missing_inventory

A lazy afternoon and evening after an eventful day at remote work. Fluffy carpet, a tandem of comfortable sweatpants and shirt with ThunderCats logo, an off-screen mug of cocoa and quiet tunes humming from radio - that's how I roll and look today. ~

... did you try to follow https://www.tenforums.com/tutorials/103965-set-preferred-gpu-apps-windows-10-a.html and tell Windows to use your AMD for the installed viewer?

If the general tips do not work, then I'd personally start to look around system logs ( https://www.windowscentral.com/how-use-event-viewer-windows-10 ) and viewer logs ( see https://wiki.firestormviewer.org/file_a_jira#how_to_give_us_your_logs ). The fact, that all three mentioned world viewers are producing the same slowdown (and they didn't change, the error appeared "suddenly") means that there is something wrong with the OS itself - or the drivers. Both log locations may help to determine what it is exactly. Maybe it's power saving mode in the computer as well... it's a long shot, but check if here https://www.tenforums.com/tutorials/103965-set-preferred-gpu-apps-windows-10-a.html viewers are in high performance mode.

Not the "usual" music today.

It may be a silly idea, but try to run the viewer with administrator privileges. Also, a question is - do you try to start the viewer on your main or secondary monitor?

I just tell them that I keep my friends list as tidy as possible - and that's actually a friends list, not just a buddy list; That I add people to it after a year or two of constant talking when I trust them enough. The best part is... I'm actually not lying - I do the same thing in social media as well. ~

Try to experiment with these. Again - coded dry, and no whiles(). integer gChannel = -943; string gDamageMessage = "PlasmaG"; list gExplode = ["ex1", "ex2", "ex3", "ex4"]; default { on_rez(integer vIntFound) { llSetMemoryLimit(llGetUsedMemory() + 5120); llTriggerSound(llList2String(llListRandomize(gExplode, 1), 0), 1.0); llSleep(0.2); llRegionSay(gChannel, gDamageMessage); llSetAlpha(0.0, ALL_SIDES); llSleep(3); llDie(); } } integer gChannel = -943; string gDamageMessage = "PlasmaG"; string gDamageDistance = 10; default { state_entry() { llListen(gChannel, "", NULL_KEY, ""); llSetMemoryLimit(llGetUsedMemory() + 10240); } listen(integer channel, string name, key id, string message) { if (message == gDamageMessage) { vector pos = llList2Vector(llGetObjectDetails(id, [OBJECT_POS]), 0); float dist = llVecDist(pos, llGetPos()); if (dist < gDamageDistance) { llSay(0, "Damage registered from '" + name + "'."); } } } on_rez(integer start_param) { llResetScript(); } }

Try this one - written dry and without testing if it compiles inworld, but should work. You don't need llSensorRepeat since you're using llDie right after the sensor ends its work, llSensor is sufficient. Remember, that sensor functions can only get up to 16 items max, which may be not enough and prevent from registering damage; It would be better if your grenade would do llRegionSay only and then just llDie after few seconds - and the items/receivers themselves would do the llVecDist calculation instead. This would also cut out the slow sensor call. Or... since your grenade is scanning within 10m, you could just use llWhisper for it and start simple listeners in receivers without any calculations, as whispering has 10m range. list explode = ["ex1", "ex2", "ex3", "ex4"]; default { on_rez(integer vIntFound) { llTriggerSound(llList2String(llListRandomize(explode, 1), 0), 1.0); llSleep(0.2); llSensor("", "", ACTIVE | AGENT, 10, PI); } sensor(integer vIntFound) { vector currentPos = llGetPos(); while(vIntFound--) { key itemFound = llDetectedKey(vIntFound) llOwnerSay("Index: " + (string)vIntFound); llOwnerSay("id: " + (string)itemFound); vector pos = llDetectedPos(vIntFound); float dist = llVecDist(pos, currentPos); if (dist < 10) { llRegionSayTo(itemFound, -943, "PlasmaG"); } } llDie(); } no_sensor() { llDie(); } }

As far as I know, the "buttons" (which should be labelled as "interface" really) does share the on/off state for all UI actions - buttons, opening/closing windows, region restart sound etc. and the incoming IM sound. Try to untick it and see if the viewer makes the desired sound.

This is one of these rare occurrences when clearing your cache should help. Please take a look at https://status.secondlifegrid.net/incidents/vqbm8q3tg98r

@Natthan Bailycheck the freshdesk link provided by @LittleMe Jewell that leads to creating a support ticket - it allows you to send one as a guest (without logging in) - you can input any e-mail there. Just make sure you describe your issue properly, maybe even send a link to this very forum thread.

I'd personally suggest trying a different web browser (Chrome/Firefox/Edge etc.) from the one that you normally use, preferably without any ad-blocking addons, as some important scripts may get killed by such.

I'd only like to point out, that the "Windows Graphics Driver version" is just a hardcoded string and it really doesn't matter - what does matter is the numbers behind the colon sign. It's the "graphics driver that Windows is currently using" - can be ATI/AMD/NVIDIA/anything. Your computer is using ATI Radeon RX 580. Remember, that Second Life is heavily bound to CPU, at least by most of the viewers - try to kill some processes in the background.

Please try to manually delete cache, as per https://wiki.firestormviewer.org/fs_startup_issues in the "Firestorm Freezes on 'Initializing VFS" - maybe it would help. Then you can follow rest of the suggestions visible there.

Firestorm does still work with Windows 7. In fact - I'm running it all the time, at least for the time being, until I get a machine with something newer on board. Sylviaangel, don't forget to whitelist Firestorm in your antivirus ( https://wiki.firestormviewer.org/antivirus_whitelisting + https://wiki.firestormviewer.org/is_my_viewer_safe ), because if nothing has changed viewer-wise, then the inability to launch it must be caused by some external software.