Spect
5929
I’m still having issues logging into Farcry 4 on my PS4. Is this a Sony issue or is Ubi under attack too?
Timex
5930
The psn is currently getting fucked by the lizard squad douchebags.
Teiman
5931
apropox of packets of fun
$ traceroute xmas.futile.net
1 192.168.1.1 (192.168.1.1) 2.047 ms 1.005 ms 1.526 ms
2 10.215.0.1 (10.215.0.1) 11.609 ms 38.234 ms 12.482 ms
3 10.127.43.205 (10.127.43.205) 29.964 ms 12.066 ms 11.383 ms
4 ae-129-3515.edge6.london1.level3.net (4.69.166.73) 51.672 ms
ae-130-3516.edge6.london1.level3.net (4.69.166.77) 40.443 ms
ae-128-3514.edge6.london1.level3.net (4.69.166.69) 41.092 ms
5 ae-127-3513.edge6.london1.level3.net (4.69.166.65) 38.946 ms
ae-130-3516.edge6.london1.level3.net (4.69.166.77) 37.672 ms
ae-129-3515.edge6.london1.level3.net (4.69.166.73) 39.601 ms
6 high-speed.edge6.london1.level3.net (195.50.90.134) 43.862 ms
ae-129-3515.edge6.london1.level3.net (4.69.166.73) 45.192 ms
high-speed.edge6.london1.level3.net (195.50.90.134) 40.421 ms
7 xe-3-4.core00.sov.uk.hso-group.net (46.17.60.173) 42.889 ms 76.799 ms
high-speed.edge6.london1.level3.net (195.50.90.134) 38.835 ms
8 xe-3-4.core00.sov.uk.hso-group.net (46.17.60.173) 58.149 ms 46.017 ms 52.286 ms
9 xe-4-1.core00.hex.uk.hso-group.net (77.75.108.153) 78.805 ms 52.666 ms 41.767 ms
10 xe-4-1.core00.hex.uk.hso-group.net (77.75.108.153) 58.294 ms 42.880 ms
xe-4-4.core00.lhc.uk.hso-group.net (77.75.108.158) 50.641 ms
11 xe-4-4.core00.tut.uk.hso-group.net (77.75.108.156) 46.164 ms 49.637 ms
xe-4-4.core00.lhc.uk.hso-group.net (77.75.108.158) 51.798 ms
12 xe-4-4.core00.tut.uk.hso-group.net (77.75.108.156) 47.780 ms 49.572 ms
xe-4-1.core00.gs1.uk.hso-group.net (77.75.108.154) 74.591 ms
13 xe-4-1.core00.gs1.uk.hso-group.net (77.75.108.154) 100.256 ms
ae0-1203.edge00.sov.uk.hso-group.net (46.17.60.117) 52.132 ms
xe-4-1.core00.gs1.uk.hso-group.net (77.75.108.154) 47.760 ms
14 xoxoxoxoxoxo.ho.ho.ho.xoxoxoxoxoxo (93.89.84.75) 41.096 ms 43.102 ms 41.009 ms
15 ooooxooooooxooo.v.ooooooxooooxoooo (82.133.91.37) 44.174 ms
xoxoxoxoxoxo.ho.ho.ho.xoxoxoxoxoxo (93.89.84.75) 45.328 ms 43.032 ms
16 ooxoooooxooooo.mmm.ooooooooxxoooxo (82.133.91.18) 43.217 ms 47.695 ms 42.928 ms
17 ooxoooooxooooo.mmm.ooooooooxxoooxo (82.133.91.18) 42.494 ms 45.090 ms 42.250 ms
18 ooooxooxooox.rrrrrrr.ooooooxooooox (82.133.91.56) 52.965 ms
oooxoooooxooo.eeeee.oooxoooooxoooo (82.133.91.63) 46.127 ms
ooooxooxooox.rrrrrrr.ooooooxooooox (82.133.91.56) 43.579 ms
19 ooooxooxooox.rrrrrrr.ooooooxooooox (82.133.91.56) 41.836 ms
oxooooooxoo.rrrrrrrrr.oooxooooooxo (82.133.91.55) 44.653 ms 44.088 ms
20 oxooooooxoo.rrrrrrrrr.oooxooooooxo (82.133.91.55) 45.627 ms *
xoooxooooo.yyyyyyyyyyy.oooxooooxoo (82.133.91.58) 45.774 ms
21 xoooxooooo.yyyyyyyyyyy.oooxooooxoo (82.133.91.58) 42.460 ms
ooxoooooxooooo.ccc.ooooooooxoooxoo (82.133.91.96) 41.103 ms 60.498 ms
22 ooxoooooxooooo.ccc.ooooooooxoooxoo (82.133.91.96) 47.444 ms
oooooxooo.hhhhhhhhhhhhh.oxoooxoooo (82.133.91.23) 41.394 ms
ooxoooooxooooo.ccc.ooooooooxoooxoo (82.133.91.96) 44.668 ms
23 oooooxooo.hhhhhhhhhhhhh.oxoooxoooo (82.133.91.23) 42.521 ms 44.779 ms 53.028 ms
24 oxoooxo.iiiiiiiiiiiiiiiii.oooxooxo (82.133.91.60) 44.271 ms
ooxooxoo.rrrrrrrrrrrrrrr.ooxoooxoo (82.133.91.49) 43.424 ms 45.638 ms
25 oooxoo.sssssssssssssssssss.ooxoooo (82.133.91.42) 45.464 ms
oxoooxo.iiiiiiiiiiiiiiiii.oooxooxo (82.133.91.60) 42.962 ms
oooxoo.sssssssssssssssssss.ooxoooo (82.133.91.42) 41.097 ms
26 oooxoo.sssssssssssssssssss.ooxoooo (82.133.91.42) 42.343 ms
oooxoooxoooooo.ttt.ooooooooooooxoo (82.133.91.61) 46.630 ms
oooxoo.sssssssssssssssssss.ooxoooo (82.133.91.42) 41.160 ms
27 ooxoo.mmmmmmmmmmmmmmmmmmmmmm.oooxo (82.133.91.34) 56.657 ms 42.746 ms 42.645 ms
28 xxoo.aaaaaaaaaaaaaaaaaaaaaaaa.oxoo (82.133.91.80) 52.879 ms 41.811 ms 42.236 ms
29 xxoo.aaaaaaaaaaaaaaaaaaaaaaaa.oxoo (82.133.91.80) 48.965 ms 52.155 ms 44.464 ms
30 oxo.ssssssssssssssssssssssssss.ooo (82.133.91.40) 48.386 ms
ooxooooooooooo.xxx.oooooooooooooxo (82.133.91.35) 52.818 ms
oxo.ssssssssssssssssssssssssss.ooo (82.133.91.40) 43.869 ms
31 oxoooooooooooo.xxx.ooooooooooooxxo (82.133.91.10) 53.791 ms
ooxooooooooooo.xxx.oooooooooooooxo (82.133.91.35) 45.399 ms 41.497 ms
32 oh.the.weather.outside.is.frightful (82.133.91.41) 54.638 ms 51.074 ms
oxoooooooooooo.xxx.ooooooooooooxxo (82.133.91.10) 61.669 ms
33 but.the.fire.is.so.delightful (82.133.91.19) 48.591 ms
oh.the.weather.outside.is.frightful (82.133.91.41) 47.148 ms 41.162 ms
34 but.the.fire.is.so.delightful (82.133.91.19) 44.970 ms 44.248 ms
and.since.weve.no.place.to.go (82.133.91.77) 46.177 ms
35 and.since.weve.no.place.to.go (82.133.91.77) 48.205 ms 46.530 ms 47.969 ms
36 let.it.snow.let.it.snow.let.it.snow (82.133.91.43) 41.546 ms 44.121 ms 45.122 ms
37 it.doesnt.show.signs.of.stopping (82.133.91.36) 43.631 ms 46.944 ms 41.926 ms
38 it.doesnt.show.signs.of.stopping (82.133.91.36) 44.709 ms
and.ive.bought.some.corn.for.popping (82.133.91.73) 49.879 ms 52.724 ms
39 the.lights.are.turned.way.down.low (82.133.91.76) 57.288 ms 44.007 ms 44.987 ms
40 the.lights.are.turned.way.down.low (82.133.91.76) 49.688 ms
let.it.snow.let.it.snow.let.it.snow (82.133.91.67) 41.057 ms
the.lights.are.turned.way.down.low (82.133.91.76) 54.389 ms
41 xxx (82.133.91.38) 44.441 ms 65.289 ms
let.it.snow.let.it.snow.let.it.snow (82.133.91.67) 44.322 ms
42 when.we.finally.kiss.good.night (82.133.91.62) 60.316 ms
xxx (82.133.91.38) 45.286 ms 47.364 ms
43 how.ill.hate.going.out.in.the.storm (82.133.91.45) 40.072 ms
when.we.finally.kiss.good.night (82.133.91.62) 44.378 ms 43.779 ms
44 but.if.youll.really.hold.me.tight (82.133.91.78) 42.848 ms 60.082 ms
how.ill.hate.going.out.in.the.storm (82.133.91.45) 45.146 ms
45 but.if.youll.really.hold.me.tight (82.133.91.78) 43.900 ms
all.the.way.home.ill.be.warm (82.133.91.17) 41.735 ms
but.if.youll.really.hold.me.tight (82.133.91.78) 79.177 ms
46 xxx (82.133.91.70) 43.703 ms
all.the.way.home.ill.be.warm (82.133.91.17) 60.384 ms
xxx (82.133.91.70) 52.321 ms
47 xxx (82.133.91.70) 57.258 ms
the.fire.is.slowly.dying (82.133.91.95) 53.839 ms
xxx (82.133.91.70) 59.063 ms
48 and.my.dear.were.still.goodbying (82.133.91.57) 41.294 ms 44.190 ms
the.fire.is.slowly.dying (82.133.91.95) 41.152 ms
49 but.as.long.as.you.love.me.so (82.133.91.31) 63.004 ms
and.my.dear.were.still.goodbying (82.133.91.57) 56.008 ms
but.as.long.as.you.love.me.so (82.133.91.31) 44.476 ms
50 let.it.snow.let.it.snow.let.it.snow (82.133.91.53) 45.012 ms
but.as.long.as.you.love.me.so (82.133.91.31) 44.439 ms
let.it.snow.let.it.snow.let.it.snow (82.133.91.53) 49.788 ms
51 let.it.snow.let.it.snow.let.it.snow (82.133.91.53) 52.569 ms
ooo (82.133.91.94) 42.096 ms 42.902 ms
52 ooo (82.133.91.94) 41.822 ms 47.656 ms
ho.ho.ho.are.we.having.fun.yet (82.133.91.64) 41.738 ms
53 ho.ho.ho.are.we.having.fun.yet (82.133.91.64) 43.959 ms
m.e.r.r.y.c.h.r.i.s.t.m.a.s (82.133.91.86) 41.709 ms
ho.ho.ho.are.we.having.fun.yet (82.133.91.64) 56.767 ms
54 ooo (82.133.91.15) 46.806 ms 44.977 ms
m.e.r.r.y.c.h.r.i.s.t.m.a.s (82.133.91.86) 55.519 ms
55 dashing.through.the.snow (82.133.91.14) 42.032 ms 41.686 ms 41.645 ms
56 in.a.one-horse.open.sleigh (82.133.91.83) 46.812 ms
dashing.through.the.snow (82.133.91.14) 44.075 ms 55.257 ms
57 in.a.one-horse.open.sleigh (82.133.91.83) 45.977 ms
over.the.fields.we.go (82.133.91.27) 41.518 ms
in.a.one-horse.open.sleigh (82.133.91.83) 75.220 ms
58 laughing.all.the.way (82.133.91.71) 54.308 ms 43.193 ms
over.the.fields.we.go (82.133.91.27) 41.884 ms
59 laughing.all.the.way (82.133.91.71) 49.507 ms
bells.on.bobtail.ring (82.133.91.79) 46.606 ms
laughing.all.the.way (82.133.91.71) 40.981 ms
60 bells.on.bobtail.ring (82.133.91.79) 43.888 ms
making.spirits.bright (82.133.91.75) 51.290 ms
bells.on.bobtail.ring (82.133.91.79) 49.930 ms
61 making.spirits.bright (82.133.91.75) 54.533 ms 48.092 ms 44.524 ms
62 what.fun.it.is.to.ride.and.sing (82.133.91.82) 42.635 ms 44.790 ms
a.sleighing.song.tonight (82.133.91.98) 51.768 ms
63 ooo (82.133.91.29) 43.519 ms 53.451 ms 43.350 ms
64 ooo (82.133.91.29) 40.855 ms 45.596 ms 43.136 ms
Happy Xmax!
I gotta tell you, even without the Lizard Squad shenanigans, the day one experience with a new console is pretty terrible. It’s been about 12 hours of downloading and setup. Haven’t even played a game yet.
How do you know you weren’t affected by it? My Day One experience a few months ago was maybe 60 minutes, probably less. They did this just so you could have a shitty Day One experience. So what are you going to do about it?
— Alan
Timex
5934
Yeah, when i originally got my ps4 back in September i was playing destiny within an hour.
I suspect your day one experience is being ruined by the lizard squad douche bags.
Update : My issue is resolved. Oddly, the day one experience in terms of setting up and configuring the Xbox One was painless. Since we got started early, before the Lizard Squad bullshit, it took maybe 90 minutes or so to get my son’s Live account active and all the updates and content downloaded to the new Xbox One. Once we had that squared away, he loaded and patched Destiny, which was also fairly painless. The only real glitch was with the account security I mentioned upthread (not being able to make purchases).
As I suspected, the fix was for me to login to my Live account and change the Xbox One settings on his account to allow purchases same as the settings for the 360. Logging into my account was impossible yesterday, and I’m not sure that was a Lizard Squad thing so much as a Microsoft thing since we could login to my son’s Live account just fine during the same period mine seemed to be borked. In the end, patience won the day, as I tried again this morning as was able to login as myself and change the security settings to allow him to purchase things (like $5 money-grab premium upgrade fee for Minecraft).
I still think the system is needlessly complex, and it’s fairly ridiculous to not carry over the same account security settings from the 360 setup when someone logs into an Xbox One with their existing account. I suppose the bright side is that it’s not PSN, which was still offline this morning.
Maybe, although I still suspect it would’ve been just as painful, if shorter.
Connect Xbox One.
Update.
Reboot.
Update.
Sign in.
Update.
Reboot.
Sign in.
Enter code for AC: Unity that came with the game.
Download 50GB overnight. (No, my internet is not normally this slow, but I noticed that the 360 used to download at about the same rate anyway.)
Start AC Unity.
Update AC Unity.
Restart AC Unity.
Play for about two hours.
Kid puts in Halo: MCC disc.
Update 16GB.
About five hours later, play Halo MCC.
I spent about 4 hours helping mys sister get a WiiU set up for her kids on Christmas Eve. The user/mii/nintendo ID stuff can be pretty confusing and the WiiU asks you questions non-stop for like the first 90 minutes about a myriad things. I also spent a long time trying to get their stuff transferred from their old Wii to the new WiiU and eventually gave up after midnight because the Wii Shop would not stop glitching out when I tried to download the transfer utility on the Wii. Had to go back to finish that today.
Of course, they’re playing game no problem when I’ve had my new PS4 since Christmas morning and can’t play a single thing on it because all the games I have for it are digital purchases or PS Plus games. I have not been able to log in to even start downloading the games I want to play. It feels a lot like I didn’t get any present at all. The firmware installed incredibly fast without issue Christmas morning so I’m good to go on 2.03. But all I can do is play music from a USB hard drive or watch Blu-ray movies. At least the controller is shiny and fun to hold.
Malderi
5938
Does anyone use the 3D capabilities of the system? From what I can gather, no games support it and 3D Blu-ray was only recently added. Are there any apps that support 3D streaming? Haven’t checked YouTube.
I honestly haven’t bothered, even with a nice new TV that supports 3D playback.
rowe33
5940
Netflix has a really small 3D section. I love watching the 3D blu-rays when I get the chance too.
Goddammit. When am I going to learn?
The Xbox One we got for Christmas has the dreaded loud grinding noise issue. Put a disc in that thing, and it sounds like a belt sander. So now we have to ship it off to Microsoft and wait for them to either fix it or replace it.
When are you going to learn what? That some electronic devices are duds?
I don’t know how widespread that particular issue is. I’m sure they’re all be others. But I’m on several forae and that’s not something I had heard about from One owners.
Sucks though. The One and its drive are whisper quiet for me
Or maybe you have learned that you are unlucky with new toys?
Wendelius
I think his point was that Microsoft has a bit of a bad reputation in the console hardware arena, post the Red Ring of Death issues with the original 360’s. While you can expect some defects with any product, that went way beyond that. IIRC there were design issues with heat dissipation, not just manufacturing problems.
Maybe it’s more of a general “Always wait for a later hardware revision” comment. I was tempted this Christmas, but Phantom Dust remains the only thing I’m jonesing for, so I decided to hold off for a slim version. That policy has never let me down.
Well, except for losing out on backwards compatibility with the PS3. But that original MSRP was nuts, so I guess it all evens out.
stusser
5945
The real lesson to be learned here is to buy stuff at Costco so you can easily exchange it, even years later.
You probably got your xbone for a much better deal, like $350 with a bunch of games. So you accepted the risk buying there rather than a place with easy exchanges. Odds are you’d come out OK, but the dice came up snake eyes. It happens.
This. I had two defective 360’s. One was the launch Red Ring of Death. The other was just a general drive failure. Both were fixed quickly enough - although the initial RRoD happened before the policy was set, so there was some fighting with support to get it resolved - but I should’ve learned my lesson about Microsoft’s console hardware. Unfortunately, my wife and kids really wanted the Xbox despite my trying to talk them into the PS4 instead. For the kids it was “all our friends are on Xbox” and for my wife it was the fact that she hates the PS4 controller and interface.
I read the reports of the grinding noise issue*, but I had hoped the manufacturing defect had run its course by the time the Assassins Creed bundles came out for Christmas. Apparently not.
*You may not have heard of it Wendelius, but it’s common enough that MS has a support policy for it specifically. It’s well-known and was reported at a lot of outlets.
There were definitely issues with the 360. Which is why MS overdesigned the XBox One and made it bigger with an external PSU, to be safe when it comes to heat and its dissipation. It’s a bigger console, but it doesn’t get as hot or generally as noisy as the PS4 (obviously this grindy problem expected).
So I was a bit curious to know whether the “When am I going to learn?” had anything to do with that. Because MS certainly did learn and has released a console which, initial software issues aside, is solid, IMO. So the lesson shouldn’t be: I should have learned that MS still makes unreliable consoles (at least not anymore than any other electronics manufacturer, it seems to me).
I don’t doubt that there will be other XBox Ones with issues out there (as shown by what Telefrog has found casting the net wider). My sample of known owners is small and unrepresentative in the grand scheme of things. Maybe somewhere between 100 and 200. But the grindy drive issue hasn’t come up in that set yet. A large proportion of those same people knew first hand what a red ring of death looked like. I did too.
Wendelius
Oh, by the way, Microsoft announced that the $349 bundle pricing will end on January 3rd. After that, they go back up to the regular $399 price.
…At least until Q4 2015.
