{{
`${userDetail.user.displayName}${userDetail.user.cachedBungieGlobalDisplayNameCode ? `#${standardizeBungieGlobalCode(userDetail.user.cachedBungieGlobalDisplayNameCode)}` : ""}`}}
{{getUserClans()}}
5/25/2017 4:20:03 PM
15
I've seen numerous reports from others that when they leave the match after the final kill, it's being recorded as a loss. I can't view your video right now. Did your party leader initiate orbit after the final kill? If so, you might just want to wait for the rewards screen.
English
-
Edited by ness 33rd: 5/25/2017 5:13:48 PMNope, to make matters worse, we did not back out. We let the match fully complete, and when our ToO card came up at the end of the game, we noticed we didn't get a win for it (we also didn't get a loss at this time). Then after flying back out to orbit, we noticed we had gotten a loss instead. The video covers this entirely, so when you get a chance to view it... you'll see what I mean.
-
Watched your video twice to be sure… The only thing I noticed out of the ordinary is that the audio and video was interrupted in between the times when you first check your passage and the next time you checked your passage. That looks like a poorly edited and spliced video to me and proof of nothing. If we could pull up your stats, then there would be a little more to back it up, but anybody could've edited that video, and if it was done that way, whoever edited it did a very poor job.
-
Agreed wholeheartedly this is a spliced film
-
Yep. I would've blamed the interruption in the video on my crappy Internet, but it was fixed today, after much educating had to be done over the phone and in person with the tech that came out to fix it. What a PITA that was!
-
I just upgraded to the best modem money can buy right now (SB8200) the other day with Cox. So I know your pain. It literally took 6 hours for them to figure out how to get it initialized because they said, "It's too highly advanced". WTH LOL
-
I'll have to look into an SB 8200. I got stuck with an SB 6190 before it was known the Puma 6 chipset was faulty. The messed up thing was I ended up purchasing that modem because my ISP said my current modem was bad during a time they had an outage. Nothing was wrong with the old modem, they just couldn't ping it, well duh! Their service was down.
-
The 8200 got me a 25 ms drop in ping and 35 ms drop in jitter ... and that is coming from the 6190. It also has had me peaking in the 350 Mbps range
-
Lol. I was trying to show the tech that came out the results that I was getting for packet loss on DSLreports.com Well, not only was it apparent he didn't know what I meant by packet loss, but he said "you don't even have DSL, so why are you using that?".
-
I think I would have told him to get out of my house at that given moment and tell them to send a competent tech out. Ended up I walked Tier 3 support through provisioning the modem on their system (which I never used but found out it is an archaic Unix system) ... just blew my mind and the guy was like, "Maybe you should have my job with how you do this!" Nope, nope nope nope nope ^1000000
-
My ISP recently changed flags, and their level III tech-support is not available to their customers anymore. The last guy that came out at least knew his stuff, and I had talked to level III over the phone in advance. The tech that came out this time ended up talking to his regional IT manager over the phone. I overheard some of the conversation, and I believed they made a change to my provisioning. The tech also installed a new line, and an upstream signal amplifier. I'm not sure what actually fixed it, but I'm guessing it was the provisioning, because my signal strength levels were fine before. I'm just glad to finally be able to pass a packet last test on DSL reports again. This crap had been going on for three weeks, and at times my upload bandwidth had dropped down to 0.1 Mbps. Even then, still green in crucible, lol.
-
Major problem I found out for my ISP (Cox) was the hub on site which sits on my property was installed in 1995 and never upgraded ... gee do you think that could cause problems?! LOL
-
That's a pretty good improvement, but not unexpected if you were switching from the 6190. So many of the gigabit modems that came out all had the same faulty chipset. https://www.google.com/amp/s/www.theregister.co.uk/AMP/2016/12/03/intel_puma_chipset_firmware_fix/ https://www.google.com/amp/s/www.theregister.co.uk/AMP/2017/04/11/intel_puma_6_arris/ I was an early adopter, and ended up with a $200 paperweight.
-
Yeah I am hoping it fixes my major problem. I had to reboot the modem EVERY TWO DAYS. It was highly annoying. I was getting IP fragmentation every time I didn't.
-
I probably reboot my modem that often just as a matter of practice. With the issues I've been having recently though, I would have to reboot it five or six times before it would connect to my ISP. So far, everything is working fine now. Considering the issues I've had over the years with various ISPs, and hoops I have to jump through to get them fixed, it wouldn't surprise me if many people have an ongoing issue that was left unresolved. Probably many of them don't even recognize they have a problem. At least that keeps us busy on the help forum.
-
That's just the way XBL spit out the video. I used the Upload Studio to simply cut out the first ~2 minutes of the video because I recorded 3 mins back just to get the whole process.
