Jump to content
Forums

Hyptronic

Members
  • Content Count

    28
  • Joined

  • Last visited

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

  1. On songshu theres bunch of crafting things to 'find out' which gives 1.5k xp per thing afaik...
  2. nope still running 1000 132 10054 5-8 times on a daily basis...
  3. that doesnt do much to 90% users affected by 1000 132 10054...
  4. Some of us are fighting with a plague called error 1000 132 10054 since launch, and they (CS) still insist its user/client fault, even when shown all ports opened, ISPs logs that everything is clear on their end, pingplotter and everything... They have serious network problems which they aint addressing since launch... Some of us already gave up on finding a fix when nothing helps to fix something that is not on your end...
  5. ...Whos bright idea was to make client shut down upon dc...
  6. After fighting with error 1000 132 10054 since launch ( like every 3rd loading screen error pops), and support telling us its our ISP fault (which isnt cause people from germany are rerouted via UK, packetloss happens on server ping pre Frankfut etc etc, its like they've blocked range of IPs towards them and we can go fk ourselfs...) their almost whole network system and routings are bugged as fk, you clearly expect way too much from them... Its always easier to say 'it's not our fault, its yours'....
  7. there is no fix... nothing you can do but wait till (and if) ncsoft fix it...
  8. Its BnSs error that they've blocked some range of IPs thus you get 100% packet loss (most likely on server just before frankfurt one)...
  9. Embrace that error cause it will be the bane of your playtime in BnS... No fix as of yet...
  10. @Ralfyork Right click, properties, check read only
  11. gl doing that in cross server dungeons...
  12. That is sooo not true, LOL well sorta... we've tested bunch of stuff on 1000/132/10054 error, nothing can be done untill ncsoft resolves their routing issues theres a blocked range of ips on their route just before ping reaches frankfurt... Error 3000 132 10060 -> is simple dc caused by dropped connection Error 1000 132 10054 -> is blocked route thus dropped packets For others cant be sure just yet, never had any besides those 2
  13. Its a routing issue, not process one... And no, its not fixed...
  14. Just a daily reminder that his error still plagues crapton of users (without being their fault or their ISPs too)... Trully yours, Hyptronic...
×
×
  • Create New...