Bake Fail Part 1 – Fixing the cloud

This tutorial covers many of the most common fixes to the red cloud/Ruthed problem many face while in SecondLife. This topic is very expansive, so I’m going to break it up into several posts. It’s easier to digest for you, and easier to put together for me. Also, it keeps all the information from jumbling together too much. All the information used on this tutorial can also be found on the Firestorm wiki. To access the regions mentioned in the tutorial, please click one of the following links:

Hippo Hollow

Cyclops

bake-fail-part-1

New-to-Mac Users: How to Install Firestorm

This question came up in the English Firestorm support group tonight, so I figured I’d tutorial it! As markets change and more users are switching to Mac, installing a program from a DMG instead of a Setup.exe can be a little confusing for some. Hopefully, this tutorial makes it easier to install Firestorm and other programs that install from a DMG.

installing-FS

But I’m terrible at reading!

I have to say, this phrase probably gets my goat the most. Not just because it allows the sayer to be absolutely lazy when it comes to reading the wiki, but because they have to read the group text anyway. Group chat isn’t in voice, and it isn’t in pictures. It’s in text. This rant goes right along with the rant about not being a techno geek. Saying you’re horrible at reading is pretty absurd. Surely, you’ve learned at some point in your education how to cope with reading comprehension issues. Other than sheer laziness of the teacher, there’s no other way you could have graduated. Be that as it may, I actually have something positive to say on this matter.

 

Read slowly. Take it one line at a time.

If you happen to be one of those who say they can’t follow the wiki links because you’re horrible at reading, there is a solution. Take the page one line at a time, and reread it until the instructions make sense. Because you’re reading on a static web page, you can take as much time as you need to work through your problem. The text won’t leave you behind like the group chat will, and it also won’t get lagged out. There’s no need to feel rushed. Please feel free to work at your own pace. Doing so will actually help you figure out the problem and understand how the instructions lead you to the solution. You’ll be much less frustrated when you work at your own pace rather than feeling stressed to fix the problem NAO.

The fact something doesn’t work right is frustrating enough, and we all do understand that. That’s why we continually update the wiki with new information for common problems and even some not-so-common issues. It helps us help you help us all. When you read the wiki one line at a time, and work through the instructions at your own pace, you really do end up learning a little bit more about the viewer and may even have a solution for someone else with a similar problem. Plus, you know where to look when your friends have issues and can help walk them through it a little at a time as well.

 

If you don’t understand, just ask!

Contrary to popular belief, the support team doesn’t throw wiki links out for shits ‘n giggles. The wiki links are designed to offer each user a truckload of information in a single line of chat. This helps cut down on chat lag, but also eliminates huge wall ‘o texts. We also understand that not everyone learns at the same pace, and that not everyone will understand every line of instruction on the wiki. We’ve tried to word the information into an easily understood language for the least techy amongst us, but sometimes not even that is understood by all. If you don’t understand something, please don’t hesitate to ask in group. We’re here to help you learn, and you can’t learn if you don’t ask.

 

Go to class!

As a final word, don’t be afraid to attend the Firestorm classes. They’re held regularly, and offer a lot of information on the viewer in short, one hour chunks. There’s usually one or two support members present as well, and an open Q & A after the class for any and all questions you may have. These are very beneficial and 100% free for all users. Many of the users who attend them are very pleased to leave the class knowing a little bit more about how their viewer works, and they go on to help others who are having issues. As a support member, I also enjoy seeing who shows up to the classes. It’s great to see some of the users of this great viewer, and it’s always a pleasure to meet you in avatar. Come join us! We don’t bite. Well…I don’t bite very hard. I can’t speak for the rest of the team.

Whitelisting Firestorm and its plugins in Gatekeeper

For those of you wondering how to add programs as exceptions in the Mac OS X firewall, wonder no more! This tutorial will show you how to do just that very thing. Also, this tutorial walks you through being able to add package contents such as the SLPlugin and SLVoice assets from the app package into the firewall. It does get a little advanced for most users at the point where the plugins are added, but I tried to keep it simple enough for anyone to follow along and accomplish successfully.

whitelist-in-gatekeeper

F1, F1, F1!

F1. The universal function button for help. At least it was eons ago when I was just starting out on Windows 3.1 and then up through ME. I’m not sure when F1 got hidden under the fluff of online help guides in programs like Adobe Photoshop or Microsoft Office 2008 for Mac, but it’s not as prominently pushed these days. Either that, or I’m just not looking. Either way, F1 plays a HUGE role in the Firestorm viewer. It’s your direct link to lag-free help via the Firestorm wiki, and I must say, it’s a handy help tool to have.

I really can’t stress using the wiki enough. It has topics on every single question you could possibly imagine. And if it’s not there, well, we’ll get it there eventually. The in-world support groups are fantastic on days the Lagdra doesn’t decide to wreak Havok on us all, but there are days when it’s just so bad I find myself relogging several times just to get the group chat to open for me. That’s where F1 comes in handy. It’s your quick link to the biggest body of documentation on the viewer, and it comes to you with no chat lag.

Need to troubleshoot a bake fail? Press F1 then search for bake fail. You’ll find http://wiki.phoenixviewer.com/bake_fail just a few clicks away. Curious about everything the bridge adds to your viewer? Press F1, search for bridge and you get http://wiki.phoenixviewer.com/fs_bridge to peer over. There’s even a wiki about filing a jira on that bug you may have just found. That’s right here: http://wiki.phoenixviewer.com/file_a_jira . So you see, there’s a lot of info inside the wiki, and I haven’t even scratched the surface. More like poked it and made it annoyed at me.

Give F1 a press and see where the wiki takes you. 🙂

“I’m not a techno-geek!”

We’ve all heard it before a million times a day. We send a user to the Firestorm Wiki to troubleshoot a problem or learn how to use a feature and we hear “I can’t understand that because I’m not a techno-geek!” Wikis are, by their very nature, very wordy. What they aren’t, however, is hard to understand for most people. Some people simply do not want to even try to work through the wiki links they’re provided in chat and instead insist on having their hands held through the process.

Then, there are others still, who are more visual in learning. I happen to be a more visual learner myself, though you’d probably never have guessed that. I prefer pictures to words, as they tend to tell me more of what the heck I’m trying to do. Thus, I’ve decided to start this blog in hopes of educating a few more of the Firestorm users who say they can’t make heads or tails of the wiki.

I’ll be updating this periodically with visual tutorials to help guide you through the basic troubleshooting steps on the wiki. I can’t cover all OSes, as I don’t have them all and I won’t even try to have them all. But I will attempt to at least cover a couple of the more major ones, time permitting.