v1.19i[rc]

Just updated. Anything new besides the standard 1. Crash fixes & 2. Memory leak fixes? 

6,976 views 9 replies
Reply #1 Top

hopefully, they'll fix some of the graphical glitching too

Reply #2 Top

Well the dupiclate hero bug is back I have 2 Rilis 1 in my party, and anuther in a city I married 1 on them. thay seem to level spratly so thay have seprate tags but have the same in game name stats and model.

Reply #3 Top

The starting farm is mislabeled as an ancient battlefield; I can't improve it.  Cloth map shows it as a farm, though. 

Reply #4 Top

Winnihym, you can't select it if you click again when the battelfield is highlighted? Somethimes when both item exist on the same square only the resources shows, but when you select it, its always the quest related item that is selected first.

 

I had a out of memory when I was typing a new designed unit name, is there a memory leak when we edit text field in game??

Game crash less then before at least but they need to improve the memory issue still.

Reply #5 Top

To Winnihym, move your character or champion onto the resource and they will automatically pick up the midnight stone, then you can select the resource.

Reply #6 Top

I've seen a lot of duplicate heroes in this build also.

Reply #7 Top

I don't think the game does anything to avoid having duplicate heroes. It just randomly rolls. 

Reply #8 Top

Quoting Trojasmic, reply 1
hopefully, they'll fix some of the graphical glitching too
End of Trojasmic's quote

yes, 1.19i includes a fix for the quality/quantity icons on the train unit window, as well as a fix for the unit gfx making a ghost unit on the map after unstationing multiple units from a city.

 

 

Reply #9 Top

Quoting CodeCritter, reply 8

Quoting Trojasmic, reply 1hopefully, they'll fix some of the graphical glitching too
yes, 1.19i includes a fix for the quality/quantity icons on the train unit window,
 
End of CodeCritter's quote

Well in that case I'm going to have to make another bug report, because it was back in my game and I just assumed it wasn't fixed yet.