Replies: 6 comments
-
|
This part of the log is fine , what i found at least with mine is with QTimeLine::start: already running warrning in my log which makes the launcher use a lot of cpu resources for nothing , and closing it after you are in the main menu , ive got a lot of frames back , almost twice in my case . I see you got the same warning also . And i wonder if this is wine related issue , because is connected with trying to run some kind of animation somewhere on the launcher constantly . |
Beta Was this translation helpful? Give feedback.
-
|
@Iliageorgiev well that's discussion not about QTimeLine warning, but about risk of getting banned. also that's kinda strange. file i/o operations should not take a lot of CPU, and launcher already closed (not rendering ui, just stays at ram) during gameplay. there are no QTimeLine warns during gameplay |
Beta Was this translation helpful? Give feedback.
-
|
@Iliageorgiev it also depends on your hardware and used wine/wrapper. also did you had that issue on windows? if yes - open new issue with detailed logs |
Beta Was this translation helpful? Give feedback.
-
|
The latest patch fixed it anyways . |
Beta Was this translation helpful? Give feedback.
-
|
Moved to discussion, as i feel this is a better place to report issues of bans. |
Beta Was this translation helpful? Give feedback.
-
|
i got a DMCA take down from some company on a other repo of mine. now i am a bit afraid that maybe strinova will get me ass. lets hope not. so far i have not heard any news about bans or wierd stuff. |
Beta Was this translation helpful? Give feedback.
Uh oh!
There was an error while loading. Please reload this page.
-
Found inside
LAUNCHER_FOLDER/log/*****.log, search forrisk statusmoved from #9
Beta Was this translation helpful? Give feedback.
All reactions