MageUK

Alright, I'll make sure to set an exception on my browser. Glad to know I'm not being diverted elsewhere, and that we're securing the login step a bit better now. Thank you for confirming this for me. :thumbsup: You shouldn't have to set an exception, it's a valid certificate. Perhaps you visited the login page while we were still messing with the configuration. At the top it shows up as unsigned. Not sure if it's a bug or not. I'll check with other browsers. That's just Chrome telling you there's insecure items on the page. In this case, it's the advert, I'll see if I can turn the advert off for the login page. I've tried both Firefox 7 and 8, and it's trusted on both of them. Firefox 4... well, I think there's a line commented in the server config (the chain file) that needs to be uncommented, so I'll sort that out. Again, that's the advert, the stylesheets etc. are fine. Same as to essiw.

Alright, I'll make sure to set an exception on my browser. Glad to know I'm not being diverted elsewhere, and that we're securing the login step a bit better now. Thank you for confirming this for me. :thumbsup: You shouldn't have to set an exception, it's a valid certificate. Perhaps you visited the login page while we were still messing with the configuration.

This. It's so that if you get banned for something later you can't claim it's because you had the mod who sent you your warning ignored and thus couldn't see it.

They are probably deleting the conversation before you get chance to view it.

What specific item are you wanting information for? We do store that data but we don't provide it as an attempt to cut down on the amount of data that flash is required to deal with after it's been fed to it. I know this is an old topic and you probably won't answer, but whatever. :P

Any chance we could ask our representative (Peter, right?) who's already got an account over there to take this up with IPB instead? My e-mail bin is buried in spam rather badly still, even though I'm trying to climb out of that, and I can't just go wandering around making accounts on the web. :oops: ~D. V. "Too buried in spam to do it myself..." Devnull (p.s.: Have a laugh, if you must... but I don't feel like being buried in spam is that funny...) IPS have made it clear that the Photos/Avatars will be merging into one and that they won't be changing this behaviour in the future unless there's a huge majority of outcry against it.

In that case try disabling JavaScript. With it disabled, a "Go" button will appear next to the skin chooser.

Fixed. Looks like it was part of a topic which got split or something. Anyway, the post didn't get marked as being the topic root, so the forum didn't know it was supposed to allow the editing of the title when editing that post.

Realistically we can't (shouldn't, and thus won't) "repair" forum topics while the forum is running. Given the amount of posts, this would be the equivalent of the post rebuild we did when we first moved to IPB, which took 3-4 days. Also, we can't easily differentiate between which line breaks should be there and which shouldn't. In summary, we're not going to be automatically "repairing" old posts.

This issue has now been resolved. :)

They're not actually supposed to do much unless you're listening to true 5.1 content.

Onboard sound is very good these days and will beat most older soundcards. What you're actually looking for here is a sound card with software that allows you to set the rear speakers to be front speakers, which is not something that you're supposed to do and thus I doubt there will be many manufacturers who include that "feature".

Well, I see what you're trying to do now, and I'm 99% sure you can no longer do it at all. Older drivers are unlikely to work, especially if you're on Windows 7 x64. In fact, not just unlikely, with x86 XP drivers won't work full stop, they'd have to be x64 drivers, and usually only Vista or above works. However, look at the advanced settings in the top right, I think there's something that allowed you to turn on "jack detection" or something to enable that popup, but I'm not sure.

When I say rear I'm not referring to the rear of the computer, I'm referring to the actual jack on the motherboard that's solely intended for rear speakers. Your screenshot of your Realtek panel shows it's detected input in the green jack on the rear, which is the headphone/stereo speaker jack. Also your speakers can't possibly be working properly in 5.1 mode with only a single analogue jack which is perhaps why they didn't sound that great on the proper setting?

It's entirely probable that the Realtek drivers are now updated enough to not allow you to select rear speakers for that jack, since you're not supposed to do that. I would suggest if you want the rear speakers option, you plug into the rear speaker jack, not the headphone jack, however I highly doubt the sound will actually be better when set that way as "rear speakers" are a subset of a surround sound system, which presumably you don't have.

Yes Jagex now includes unranked stats exp/levels in the high scores lite feed.

We're still working on it but we hope it is improving things, it should get even faster in the next week or so as we make some more optimisations to it.

Fixed. They were missed as we've been changing web servers.

I see the future, and it contains bans. :rolleyes:

It's showing the classic signs of a pretty common problem to do with the microwelds or the soldering, whatever you want to call it on the GPU. It often happens with cards that get very warm and as they get warm the solder heats up and then rapid cooling causes it to slowly crack over time which obviously causes components to lose contact with eachother. Given that the card is already 4 years old, it's obviously out of warranty. You can have a crack at fixing it yourself if you're daring enough. I've done it 3 or 4 times and had success once. Basically what you need to do is reflow the solder. You can try doing this yourself by: Remove all plastic components from the card (heatsink, any fans) Clean up any thermal paste which is on the card Remove the "backplate" (where the VGA/DVI connectors etc. are) Remove anything else that may melt at high temperatures Preheat an oven to approximately 385F, don't go any higher than this Suspend the card on 4 crunched up balls of foil on an oven proof tray (one ball on each corner) Place the card in the oven for no longer than 7-8 minutes Take the card out and wait for it to fully cool naturally, don't touch it or knock it Put it all back together Pray For your information, this is very likely to finish the card off, but it's worth a shot if you don't want to buy a new one. :P If you leave it too long, or if the temperature is a little too high etc., then components will drop off the card and you don't want that. And just as a disclaimer... I accept no responsibility for anything that happens as a result of you trying this, it's entirely at your own risk.

I considered it when Adventurer's Logs first came out (yes, I did notice that they show all stats), but the reason it wasn't done at the time was that the Adventurer's Log loading times were so sloooooow (like 3-4 seconds for a page load), which would have meant it took a while to grab stats initially, leading to users thinking things were broken and refreshing, causing more pings to be sent out to Adventurer's Logs trying to get stats etc. like an endless circle. If they've sped up however, I'll reconsider doing it. EDIT: Just checked and it's now significantly faster than it used to be.

Okay, I'm a little confused here. How did I end up with the FF2-based system having an image with non-accurate stats, and the FF3-based system having an image without any stats but "1"s, during that entire period? Did your server keep two different versions at the same time, or was there some kind of header that was sent with the image(s) originally, such that I couldn't bypass the cache on this system with a Ctrl-F5 even though I had also forced the cache to clear? :blink: ~D. V. "I'm totally confused here, sorry... Can you please help me make sense of what was happening?" Devnull That can't be anything but some sort of caching issue on your end, providing it was happening on exactly the same URL in both browsers. Here's a run down of the system and how it works: You request a signature. We check our database to see if we have your stats and how old the copy of those stats is. If the copy of the stats is older than 12 hours we request the stats from RS again and put them in our database. We check to see if the image you requested already exists on our server (same QP, pose, background etc.), and how old it is. If the image is newer than 12 hours, we serve you that cached image with headers in it stating when it expires (12 hours from creation). If the image is older than 12 hours, we create a new image, and put that in the cache directory, and serve you that, with headers stating when it expires (12 hours from creation). Stats can be updated without the image updating (say if you create a signature for the first time, we grab your stats then, you then create another signature 6 hours later, we still have your cached stats, the first image you made will update 6 hours before the second one does). But creating a new uncached image can use the new stats. Here's a scenario: You create a signature, so we grab your stats. 6 hours later you create a different signature (maybe change the background or something). You discard the first signature as you decide you don't like it, and decide to use the second one. 12 hours after the first one is created, your stats are due to update, but the server will see the image you're using (the second signature) as being only 6 hours old at that time, and as such, it won't update it; but at some point, when the image loads, the stats will update in our database. 6 hours later the second signature updates to use the new stats. If you change anything about the signature so it becomes an image we don't have cached, like change the background, pose, or number of quest points; it causes the image to be regenerated, but uses whatever stats we have in the database. So if 12 hours after you created the first signature (and thus 6 hours after the second) you make a third signature, that will have updated stats which are different from the second one you created. Yes, I know it's complicated, but normally I don't have to explain the system to users. :P

The signatures are only cached for 12 hours, along with your stats. What probably happened was that it just happened to fail to grab the stats when you generated the image, so the stats were set to 1 by default, then whenever you generated a signature from that point on it used those cached stats of all 1s until 12 hours later when it grabbed your stats again and this time was successful. The reason the signture will have looked fine when it had 43 QP on it was probably because we also cache the sig images themselves and that one was generated with working stats.

I'll submit a ticket to IPS regarding this and let them handle it.

Is it fixed now?