Сообщений в теме: Не синхронизируется персонаж Rift
1
Alchemist_s
Пользователь
Сообщений: 3
Регистрация: 24.03.2014
Отправлено: 06.04.2014, 5:23
Не синхронизируется персонаж Rift. Мало того при запущенном Magelo Sync загрузка локации при входе в игру доходит до 95% и виснет
Alchemist_s
Пользователь
Сообщений: 3
Регистрация: 24.03.2014
Отправлено: 07.04.2014, 14:27
[2014-04-07 21:27:32] Configuration initialisation
[2014-04-07 21:27:32] Could not find: magelo-i18n []
[2014-04-07 21:27:32] Using magelo-i18n[ru]
[2014-04-07 21:27:32] Using magelo-i18n[ru_RU]
[2014-04-07 21:27:32] Magelo Sync 4.4.1, Copyright (C) 2013 Magelo Limited
[2014-04-07 21:27:32] Windows 7 6.1 amd64
[2014-04-07 21:27:32] Java version 1.7.0_51
[2014-04-07 21:27:32] Europe/Helsinki, ru_RU, windows-1251
[2014-04-07 21:27:32]
[2014-04-07 21:27:32] Services initialisation ...
[2014-04-07 21:27:58] Automatic user authentification...
[2014-04-07 21:27:58] Game Slots : 3 free of 3
[2014-04-07 21:27:58] User : Alchemist_s (PREMIUM)
[2014-04-07 21:27:58] Starting services...
[2014-04-07 21:27:58] Starting service : Content Synchronizer
[2014-04-07 21:27:58] Starting service : Deadlock Hunter
[2014-04-07 21:27:59] Starting service : Game session seeker
[2014-04-07 21:28:00] New game session detected : rift.exe[4328]
[2014-04-07 21:28:01] RIFT: Monitor started
[2014-04-07 21:28:01] Starting game monitor : RIFT 1.1.64
[2014-04-07 21:28:02] [Char] Step 1
[2014-04-07 21:28:02] An error occured
java.lang.NullPointerException
at magelo.Rdq.Rg(Rdq.java:863)
at magelo.Rdq.i(Rdq.java:216)
at magelo.dt.a(dt.java:18)
at magelo.dt.run(dt.java:2)
at java.lang.Thread.run(Unknown Source)
[2014-04-07 21:28:03] An error occured
java.lang.NullPointerException
at magelo.Rdq.Rg(Rdq.java:863)
at magelo.Rdq.i(Rdq.java:216)
at magelo.dt.a(dt.java:18)
at magelo.dt.run(dt.java:2)
at java.lang.Thread.run(Unknown Source)
[2014-04-07 21:28:04] An error occured
java.lang.NullPointerException
at magelo.Rdq.Rg(Rdq.java:863)
at magelo.Rdq.i(Rdq.java:216)
at magelo.dt.a(dt.java:18)
at magelo.dt.run(dt.java:2)
at java.lang.Thread.run(Unknown Source)
[2014-04-07 21:28:05] An error occured
java.lang.NullPointerException
at magelo.Rdq.Rg(Rdq.java:863)
at magelo.Rdq.i(Rdq.java:216)
at magelo.dt.a(dt.java:18)
at magelo.dt.run(dt.java:2)
at java.lang.Thread.run(Unknown Source)
[2014-04-07 21:28:06] An error occured
java.lang.NullPointerException
at magelo.Rdq.Rg(Rdq.java:863)
at magelo.Rdq.i(Rdq.java:216)
at magelo.dt.a(dt.java:18)
at magelo.dt.run(dt.java:2)
at java.lang.Thread.run(Unknown Source)
[2014-04-07 21:28:07] An error occured
java.lang.NullPointerException
at magelo.Rdq.Rg(Rdq.java:863)
at magelo.Rdq.i(Rdq.java:216)
at magelo.dt.a(dt.java:18)
at magelo.dt.run(dt.java:2)
at java.lang.Thread.run(Unknown Source)
[2014-04-07 21:28:08] An error occured
java.lang.NullPointerException
at magelo.Rdq.Rg(Rdq.java:863)
at magelo.Rdq.i(Rdq.java:216)
at magelo.dt.a(dt.java:18)
at magelo.dt.run(dt.java:2)
at java.lang.Thread.run(Unknown Source)
[2014-04-07 21:28:09] An error occured
java.lang.NullPointerException
at magelo.Rdq.Rg(Rdq.java:863)
at magelo.Rdq.i(Rdq.java:216)
at magelo.dt.a(dt.java:18)
at magelo.dt.run(dt.java:2)
at java.lang.Thread.run(Unknown Source)
[2014-04-07 21:28:10] An error occured
java.lang.NullPointerException
at magelo.Rdq.Rg(Rdq.java:863)
at magelo.Rdq.i(Rdq.java:216)
at magelo.dt.a(dt.java:18)
at magelo.dt.run(dt.java:2)
at java.lang.Thread.run(Unknown Source)
[2014-04-07 21:28:11] An error occured
java.lang.NullPointerException
at magelo.Rdq.Rg(Rdq.java:863)
at magelo.Rdq.i(Rdq.java:216)
at magelo.dt.a(dt.java:18)
at magelo.dt.run(dt.java:2)
at java.lang.Thread.run(Unknown Source)
[2014-04-07 21:28:12] An error occured
java.lang.NullPointerException
at magelo.Rdq.Rg(Rdq.java:863)
at magelo.Rdq.i(Rdq.java:216)
at magelo.dt.a(dt.java:18)
at magelo.dt.run(dt.java:2)
at java.lang.Thread.run(Unknown Source)
loulina
Администратор
Сообщений: 4235
Регистрация: 08.02.2006
Отправлено: 28.04.2014, 6:10
Hi Alchemist_s
We fixed a problem with Magelo Sync a week or 2 ago and it should work correctly.
Let us know if you still have an issue. Thank you
