Feedback XMage Version 1.4.42 (January 2020) #6169
Labels
Comments
JayDi85
changed the title
|
Not sure if this is the best place to report bugs for THB, I write it just in case:
|
|
Fixed. |
Fixed. |
|
This ends up not happening every time. But still at least 50% chance of the cards not sticking after escaping them. |
|
Hopeful Idolon isn't triggering when an opponents creature dies with you enchantment on them. |
|
Looks like Hateful Eidolon is also not triggering off opponent's creatures with auras on them, likely for the same reason(s) |
|
Looks like there may be an issue with Dream Trawler. My last opponent stated they were unable to activate its "Discard a card:" ability. |
|
Tectonic Giant triggered ability is not working |
|
|
There is a bug with Exitrpate. You are not allowed to pick the chosen card from your opponents hand. I don't know if the same problem exists for surgical extraction. Hope this is the right place to report this. |
|
Medomai's Prophecy - Chapter 4 trigger may be bugged. Expected Result Actual Result |
|
Lagonna-Band Storyteller - Enter trigger occurs, asks you to select an enchantment, after selection it asks if you would like to put it on top etc. Selecting "Yes" resulted in no life gained and the enchantment stayed in the graveyard. |
|
XMage doesn't let me cast Rise to Glory when I just have a creature in my graveyard. It seems to be requiring both a creature AND and aura (whereas the card allows one OR both). |
|
Agonizing remorse doesnt make you lose 1 life. |
Dilnu
added a commit
to Dilnu/mage
that referenced
this issue
Feb 1, 2020
|
The Network stack seems to be extremely slow:
|
|
@allentiak server/client startup related to OS's system file cache. As example: Windows will cache files from disk to memory and it will increase speed on next startup. If your system do not use cache (e.g. too slow on startup) then it can be low free memory in OS. P.S. Also first run after update can be slow -- it re-create cards database files from scratch ( P.P.S. In v1 (start of the january) were introduced extra data compression -- it increased CPU usage too. Maybe in next version it will be disabled again. |
|
@JayDi85 Thanks for the update! BTW: I know the first time is always the slowest one. However, the times I mentioned above are the normal ones (read: after recreating the DB). |
|
I'm researched logs at beta server (simple cloud server: 1 cpu, 2 GB, SSD disk) -- normal startup time is 20-30 seconds all the time (in December and January). Database create startup -- 1 minute. Try to check free memory available on your OS (I'm talking about system memory, not xmage's app memory settings). P.S. windows file cache have limits and can be overflowed on another app active disk usage. As example: if you run antivirus to check files on computer then it "eats" all files cache (after hours) and system will freezes on any disk operations until restart. KIS antivirus have that bug. |
|
On Tue, 4 Feb 2020 at 12:16, Oleg Agafonov ***@***.***> wrote:
Try to check free memory available on your OS (I'm talking about system memory, not xmage's app memory settings).
Do you mean from the Launcher's Java settings? My system has 16G of RAM...
|
|
Nope, I'm talking about OS free memory. Xmage server app works fine with default 500 MB for local games (you can change it by launcher settings -- same as client).
What can you try:
- restart computer;
- ensure that you have free system memory (2+ GB);
- run xmage server app multiple times to test startup time.
If your normal startup time will take minutes then something wrong with HDD (check it for errors) or antivirus/antimalware software (try to disable to check).
Also try to report slow startup logs here. It can be problem like proxy-network -- logs can show it (slow command).
|
|
Below are the startup logs. You will notice the difference in startup time. In the same machine, with the same config:
Startup log (1.4.42V0)Startup log (1.4.42V2)Startup log (1.4.42V3) |
|
Only for V2 the DB is recreated (but its startup is still fast). |
|
All logs and times are fine except last: 2+ minutes takes action to test is it another server runs on computer (server creates simple client connection and try to connect from it to server's address). So it's network or config settings problem:
|
|
Thanks for the comment, @JayDi85 ! Chances are, there was an old idling server/client around... I'll restart my computer, start the server and post the log again. |
77 tasks
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
CARDS
v0 (on 10.01.2020)
v0 (on 12.01.2020)
v0 (on 16.01.2020)
v1-beta on 12.01.2020
v1-beta on 15.01.2020
v1 on 18.01.2020
v2 on 24.01.2020
v2 (on 01.02.2020)
OTHER
v0 (on 12.01.2020)
v1 (on 18.01.2020)
v2 on 24.01.2020
v2 on 01.02.2020
The text was updated successfully, but these errors were encountered: