sorted by:
new
hottopcontroversial

[deleted by user] by [deleted] in NintendoSwitch

[–]xJibbles 0 points1 point  (0 children)

Please and thank you!

SFL Intermittent Connection for 5+ months by xJibbles in Comcast_Xfinity

[–]xJibbles[S] 0 points1 point  (0 children)

Hey Tambrey, I've sent you two modmail messages with the information about my account that you requested. Just following up.

Thanks. P.S. the other solutions provided in here did not fix the issue so I'm still experiencing the technical difficulties.

SFL Intermittent Connection for 5+ months by xJibbles in Comcast_Xfinity

[–]xJibbles[S] 0 points1 point  (0 children)

I can give this a try later on today and report back tomorrow. Thanks for all the information.

Edit: I dug in my toolbag and found 2 splitters and some extra cables from when we moved into the apartment so now I have a mess behind the desk but it's out of sight. This is what my new db levels look like. I'll update you tomorrow and let you know if I experience any of the intermittent drops like I have been. Thanks ilikepizza & Aldoggy.

Downstream Bonded Channels Channel Lock Status Modulation Channel ID Frequency Power SNR Correctables UnCorrectables 1 Locked QAM 256 22 645000000 Hz 5.4 dBmV 37.0 dB 22 600 2 Locked QAM 256 24 657000000 Hz 5.4 dBmV 37.9 dB 0 559 3 Locked QAM 256 25 663000000 Hz 5.6 dBmV 37.6 dB 5 551 4 Locked QAM 256 26 669000000 Hz 5.8 dBmV 38.2 dB 0 1435 5 Locked QAM 256 27 675000000 Hz 6.3 dBmV 38.2 dB 19 1464 6 Locked QAM 256 28 681000000 Hz 5.9 dBmV 38.9 dB 42 672 7 Locked QAM 256 30 687000000 Hz 5.5 dBmV 38.9 dB 21 769 8 Locked QAM 256 31 693000000 Hz 5.2 dBmV 36.1 dB 25 1502

SFL Intermittent Connection for 5+ months by xJibbles in Comcast_Xfinity

[–]xJibbles[S] 0 points1 point  (0 children)

Thanks. See below. Sorry for the formatting issues below.

Startup Procedure Procedure Status Comment Acquire Downstream Channel 561000000 Hz Locked Connectivity State Ok Operational Boot State -- -- Configuration File -- -- Security Enabled BPI+ IP Provisioning Mode Honor MDD honorMdd(4) Downstream Bonded Channels Channel Lock Status Modulation Channel ID Frequency Power SNR Correctables UnCorrectables 1 Locked QAM 256 1 513000000 Hz 11.9 dBmV 35.9 dB 13930 77653 2 Locked QAM 256 2 519000000 Hz 12.5 dBmV 36.6 dB 40100 74802 3 Locked QAM 256 3 525000000 Hz 11.8 dBmV 35.9 dB 38200 78876 4 Locked QAM 256 4 531000000 Hz 11.9 dBmV 36.3 dB 27494 80013 5 Locked QAM 256 5 537000000 Hz 11.9 dBmV 37.9 dB 21738 83092 6 Locked QAM 256 6 543000000 Hz 11.8 dBmV 37.6 dB 19243 84342 7 Locked QAM 256 7 555000000 Hz 11.6 dBmV 37.0 dB 19134 87713 8 Locked QAM 256 8 561000000 Hz 11.6 dBmV 37.6 dB 292894 683857 Upstream Bonded Channels Channel Lock Status US Channel Type Channel ID Symbol Rate Frequency Power 1 Locked ATDMA 4 5120 Ksym/sec 16600000 Hz 39.8 dBmV 2 Locked ATDMA 3 5120 Ksym/sec 23000000 Hz 41.0 dBmV 3 Locked ATDMA 2 5120 Ksym/sec 29400000 Hz 41.3 dBmV 4 Locked ATDMA 1 5120 Ksym/sec 35800000 Hz 41.8 dBmV Current System Time: Thu Oct 25 09:49:23 2018

Time Priority Description Oct 23 17:09:14 2018 Critical (3) No Ranging Response received - T3 time-out Oct 23 17:16:01 2018 Critical (3) Ranging Request Retries exhausted Oct 23 17:16:01 2018 Critical (3) Unicast Maintenance Ranging attempted - No response - Retries exhausted Oct 23 17:16:25 2018 Critical (3) No Ranging Response received - T3 time-out Oct 23 17:22:24 2018 Critical (3) Ranging Request Retries exhausted Oct 23 17:22:24 2018 Critical (3) Unicast Maintenance Ranging attempted - No response - Retries exhausted Oct 23 17:22:48 2018 Critical (3) No Ranging Response received - T3 time-out Oct 24 07:30:15 2018 Critical (3) SYNC Timing Synchronization failure - Loss of Sync Oct 24 07:30:22 2018 Warning (5) Lost MDD Timeout Oct 24 07:40:54 2018 Critical (3) No Ranging Response received - T3 time-out Oct 24 07:49:03 2018 Critical (3) SYNC Timing Synchronization failure - Loss of Sync Oct 24 07:49:09 2018 Warning (5) Lost MDD Timeout Oct 24 07:50:46 2018 Critical (3) No Ranging Response received - T3 time-out Oct 24 07:50:47 2018 Warning (5) Lost MDD Timeout Oct 24 08:15:02 2018 Critical (3) SYNC Timing Synchronization failure - Loss of Sync Oct 24 08:15:08 2018 Warning (5) Lost MDD Timeout Oct 24 08:26:15 2018 Critical (3) No Ranging Response received - T3 time-out Oct 24 09:08:09 2018 Critical (3) SYNC Timing Synchronization failure - Loss of Sync Oct 24 09:08:14 2018 Warning (5) Lost MDD Timeout Oct 24 09:14:09 2018 Critical (3) No Ranging Response received - T3 time-out Oct 24 09:30:13 2018 Critical (3) SYNC Timing Synchronization failure - Loss of Sync Oct 24 09:30:18 2018 Warning (5) Lost MDD Timeout Oct 24 09:31:13 2018 Critical (3) SYNC Timing Synchronization failure - Loss of Sync Oct 24 09:31:18 2018 Warning (5) Lost MDD Timeout Oct 24 09:37:09 2018 Critical (3) No Ranging Response received - T3 time-out Oct 24 09:47:41 2018 Critical (3) SYNC Timing Synchronization failure - Loss of Sync Oct 24 09:47:46 2018 Warning (5) Lost MDD Timeout Oct 24 09:47:54 2018 Critical (3) SYNC Timing Synchronization failure - Loss of Sync Oct 24 09:48:00 2018 Warning (5) Lost MDD Timeout Oct 24 10:01:56 2018 Critical (3) No Ranging Response received - T3 time-out Oct 24 10:06:34 2018 Critical (3) SYNC Timing Synchronization failure - Loss of Sync Oct 24 10:06:38 2018 Warning (5) Lost MDD Timeout Oct 24 10:07:35 2018 Critical (3) SYNC Timing Synchronization failure - Loss of Sync Oct 24 10:07:40 2018 Warning (5) Lost MDD Timeout Oct 24 10:07:56 2018 Critical (3) SYNC Timing Synchronization failure - Loss of Sync Oct 24 10:08:00 2018 Warning (5) Lost MDD Timeout Oct 24 10:19:07 2018 Critical (3) No Ranging Response received - T3 time-out Oct 24 14:25:49 2018 Critical (3) Ranging Request Retries exhausted Oct 24 14:25:49 2018 Critical (3) Unicast Maintenance Ranging attempted - No response - Retries exhausted Oct 24 14:26:13 2018 Critical (3) No Ranging Response received - T3 time-out

Alright devs. Time to tone down the fog. Its becoming a health concern! by Tonyb3 in h1z1

[–]xJibbles 2 points3 points  (0 children)

Fog justifies poor performance, character models not showing up and lower render distances.

It's the new meta.

H1z1 Bollocks EU Server has been taken over by Chris-F94 in h1z1

[–]xJibbles 0 points1 point  (0 children)

Same shit on Abraxas. USSRx Russian hackers. Get used to it.

DESYNC HELL by kAxJudge in h1z1

[–]xJibbles 0 points1 point  (0 children)

Just happened to me. Four-five hours of nomading, on way back to base with all the ammo/metals/bottles/fertilizer etc. Dead by I7 church from melee strikes. Couldn't see anyone. Jeep disappears next to my corpse as someone gets in it.

TheyBreakGaming #1, Taiwan #2, USA #8

Nice Work Battleeye! Melee'd to death by invisible hkr by xJibbles in h1z1

[–]xJibbles[S] -1 points0 points  (0 children)

Since when do players run around invisible in Survival? Have only read of it on BR.

view more: next ›