Agar Lifeafter Tidak Lag
What if I told you that you can get less lag in seconds, with a few simple clicks?No, this ain't a scam, but like some infomercials, it's completely risk-free. Y'see, I love 'smart' defaults because they help give us a better experience out of the box, whether we're new to Second Life or doing a fresh install. But I keep coming across Resis who, despite having a fat broadband connection, feel 'laggy' because they didn't know they could up their Maximum Bandwidth.GOOD GOSH.
SPREAD THE WORD:One of the not-so-bright defaults, as (the Internet never forgets), is the default Maximum Bandwidth setting. It defaults to 500 kbps, which makes no sense because HELLO WE'RE NOT ON DIAL-UP ANYMORE.But srsly, like Geordi La Forge said on Reading Rainbow, you don't have to take my word for it. Try it yourself. Go to Me menu Preferences.
In PREFERENCES window, click Setup tab. Move Maximum bandwidth slider all the way to the right. Yeah, crank that baby!(Supposedly years ago, setting your Max. Bandwidth too high would result in bad packet loss and overall decreased performance, but tell me if you still notice that.
It may not even be true anymore.)Links to followup on:.(so you can see the STATISTICS BAR in the video)., which you should vote for if you care. And see my comment in there, more history. I voted and commented on this, but I do have a question. I noticed your frames per second didn't change with the slider pushed to the limit. I DID see the world rez a lot faster, and I DID see your bandwidth climb measureably. But I always notice with lag, my FPS drops drastically, hovering below 10, and when I'm not lagging much, my FPS is around mid 20's.
If changing the bandwidth isn't affecting the FPS, how is this helping with lag? Perhaps I need a smack for missing something. My apologies. But I am curious. What I'm getting at is this:would you try to drive 250 miles per hour on a twisty little country road and expect to be able to do so without problems?If you set the maximum bandwidth too high you get into all kind of trouble as well, this time from loosing packets instead of having to wait for them too long.Here's what you do to find the right setting:. take your webbrowser, go to. slide the little rectangle on the world map over california.
select a server in San Francisco. run the test. convert the result to kilobit per second (for example, I get 13.75 MBit/s. That is 13750 kilobit/second). Use that as the maximum, after considering other uses of your bandwidth. For example, If you habitually log in to SL with more than one computer and avatar at the same time, you have to split the bandwidth. FPS is not the same as lag, although people often use them interchangably which leads to tons of confusion.in the past, there were various bugs that caused your client to choke if you set the bandwidth too high.
I believe this also just recently occurred again when the HTTP texture fetching was first added. What torley is saying is that these issues have all been resolved and there is no reason to cap your bandwidth setting any longer - unless you're sharing your wire with another user or you don't have an unlimited data plan.lance's 'advice' is outdated and telling people to still do this is counter-productive. If you set it to max and experience a problem, a new JIRA needs to be opened for it. I would like to point out to all the people saying this will increase their bill, that this is false. The bill you get is based on bandwidth used, or in simpler terms, how much data you transferred. The Bandwidth setting in the viewer sets how much data per second is transferred.
If you have to download 1000 textures, you have to download 1000 textures, regardless of the speed, and the amount of data transferred remains the same.They are named the same, but are different things altogether. Bandwidth slider = speed. Billable Bandwidth = volume of data.Your bill will be the same, no matter how high or low you set the bandwidth slider, as it affects transfer rate, not transfer volume.
The viewer bandwidth setting just throttles how fast the data transfers, in effect how long it will take to transfer these 1000 textures. It doesn't somehow make these 1000 textures equal more data, which is what you are billed for.The only possible factor that could affect your bill is that you can now do.more. in the same amount of time, as you're not standing around waiting for textures to load. I'm pretty sure, setting the bandwidth to the maximum has no effect whatsoever on your packet loss or 'lag'. Unless the viewer does something really stupid the bandwidth setting only throttles when you go lower than your can take. But if you go above it, you will simply be limited by your own connection. It's like saying that building a 6 lane motorway creates traffic jams with the same amount of cars on it (your connection's max bandwidth) as on a single lane country road.
I fail to see where maximum bandwidth could hurt your connection speed at all. I'd appreciate a technical, well researched explanation.
@Ewer, what you are missing is that complaining about lag is like going to your doctor and saying you hurt, but being unable to say whether it's your head, stomach or feet that hurt (as I recall, it was Torley who first came up with that analogy). How can your doctor help you? Lag has 3 main components - client (the SL viewer), network and server (the sim you are in).If the server is lagged out by too many avatars, crashed physical vehicles or scripts, then you will experience server lag; time dilation lower than 1.00 and the walking through jello effect.If there's something wrong with your network connection (high time to communicate, known as ping time, or high packet loss, meaning some communications don't get through) then you will experience network lag. You hit the keyboard, your avatar does nothing for a while. Also if your network connection is too slow (twisty lane instead of 6 lane highway) then it will take longer for stuff to rez.
You will tp somewhere and it will be bare land for a long time, and then the scene will build slowly.I have to say what I do is exactly the same as Lance Corrimal describes. It works, maybe it's conservative.Finally, client lag can still strike in a sim that is running fine with a good network connection. Set graphics to ultra, draw distance to max and stand inside a megayacht built out of megaprims and sculpties.
If your graphics card is a few years old, your client FPS will plummet.The easy way to see the cause of the lag is the lag meter, which gives you red yellow and green for each of these 3 factors.The more detailed way is the stats floater (control shift 1) which will show you what's wrong with the client frame rate, network connection or sim. The sim aims to run at 45 fps, which means it has to be able to draw each frame in a bit over 22ms. If script time or physics time are approaching that figure, then the sim has no choice but to slow down. I've noticed the clients (1.23, most TPVs, and my most recent shot at 2.x) all seem to keep your bandwidth setting, as far as the slider goes, but it doesn't actually seem to know it. Much like a badly installed toilet, you have to 'jiggle the handle,' so to speak, by opening the preferences, grabbing the slider, and increasing or decreasing it a bit, then applying. I notice an INSTANT, dramatic increase in loading every time, as if the viewer didn't realize the setting had been changed until then (even if it was showing my chosen setting). Here's what you do to find the right setting:.
take your webbrowser, go to. slide the little rectangle on the world map over california. select a server in San Francisco.That's actually very helpful advice, thanks Lance. I just wonder if this apply for SL.
I just tried as you said and my bandwidth to California is worse. Somewhat about 3-5Mb/s. I did this 10Mb/s thing anyway and figured that's working very well.
No performance decrease, no packet loss, steady FPS and surprisingly even more bandwidth as expected (up to 8Mb/s). Well, of course! Most SL content is hosted somewhere else by Amazon S3 and some LL facilities on Mars. On second thought, why should a limit apply for SL anyway, if it's not an issue with server side bandwidth anymore? I mean, none of my other web applications need speed limits either but what's with all this 'STICK AT 500kb/s' talk in earlier days?? PLUS Thank you Torley for your comments. I have a question though.
Last night I opened all my performance meters and teleported around to test things out at these settings. Everything worked great, I did not lose any packets, the sky did not fall and nothing terrible happened.but! My frame rate was very low and changing Graphic Settings from Ultra even all the way to Low did not seem to improve this and it seemed to be true for 2 or 3 different locations that I tried.
Agar Lifeafter Tidak Lag Video
I found a chart for Typical Frame Rate Performance by Graphics Card at My card was not listed but similar cards showed better frame rates then I was getting. Any ideas of what I might be doing wrong?