Incorrect color unit.
Галиев Рустем 5 years ago • updated by anonymous 5 years ago • 11
Windows 10 64 bit, 8 Gm RAM, Intel(R) Core(TM) I7-4500 CPU1.80 GHz 2.40GHz GPU: AMD Radeon R7 M265, Intel(R) HD Graphics Family. Version game fresh.
The unit (Necromancer) is indicated in purple. But it belongs to me, my color is green.
Watch the video. This often happens.
War for the Overworld Launcher Log.txt
Customer support service by UserEcho
by looking at the code, this _should_ not be possible under no circumstances.
Do you have any idea how we could reproduce this issue?
1. Map of 125 to 125 with the presence of water, impassable rocks and lava.
2. Many creatures on the map. 4 Underlords.
3. FPS below 25.
The result: I was recently in another time his eyes saw the yellow unit in the torture purple Underlord, changed affiliation. But remained yellow! I.e., after the torture of being unable to leave the old color, this is a CONSTANT problem I have.
And one more observation. When I load the save with this problem - the color units are already correct.
If it happens, it's probably - logical, right?
I just played the map, created recently, after the patch 1.6.4.
Incorrect color unit does not occur immediately. Perhaps, after treatment of creatures (torture).
Found me and AI.
I took conversation by torture into account, but there is code which should handle that case correctly.
It would be interesting to know how to trigger this problem in a reproducable manner.
Otherwise I tap in the dark, because the code at least looks like it should work in all cases.
Helps the availability of this map for you (published by the Steam, as a private map - you'll see her?). Or you can copy the map from a savegame?
This would only help, if using this map guarentees that the issue occurs so we can debug it.
Listen, if you do not reproduce, then there is some difference between the game between me and you. Maybe on my notebook the game has access to less video memory? Maybe Russian localization affects it? I'm ready to give access to my laptop through a teamviewer, we can agree on what time.
Unfortunately after reviewing this issue with the Code Team today this issue is not going to see a fix within the remaining development of WFTO. There's a number of reasons for this but primarily it's simply a matter of resources spent vs value of fix, we're not entirely sure as to the cause of this issue but one thing is sure; the issue is deeply ingrained and to resolve it would require considerable resources that unfortunately will not be available to us moving forwards compared to spending our resources on other higher priority issues or new features.
We didn't want to leave this in limbo so as such we're now going to close this ticket as not fixable.
We know it's not desirable for issues like these to remain in game and we want to always endeavor to ensure that player experience is the best it can be. But realistically there are some issues which we won't be able to address so we want to ensure that expectations from our community align with that.
Thanks for the report and I apologize that we will not be fixing this issue. Please feel free to get in touch if you have questions.