0.71#72 Garrisoning, ungarrisoning, or switching between visiting & garrisoned hero, causes all other heroes on the Adventure Map to lose their preset paths : [forum.vcmi.eu/t/vcmi-0-71-bug-seeking-thread/143/65)
Artifact debuff minimums should be 0 for Attack & Defense and 1 for Power & Knowledge
#90 - Right-click on a hero on Adventure Map opens the info box always in the upper left side of the hero. That creates an issue when we scroll the map as such that our hero is close to the upper and/or left edge of the client interface. In that case parts of the info are not visible anymore (if the hero is really in the upper left corner, you see nothing of it):
In H3 the info box was first of all opening as centered above the hero. That’s not really an issue, as I kinda like it to still see the hero when the info box opens next to him. But in H3, if the hero was next to the edge of the interface, the position of the info box was adjusting to the edge of the screen so that we can see it completely.
Rather non-issue. It would be troublesome to fix. Console shouldn’t be closed manually if you don’t want cause crash.
Fixed.
Fixed.
Not implemented.
I can’t reproduce it with 0.72. Either has been fixed or it’s platform-specific issue.
Duplicate to #48
Resource-giving artifacts crashes on new turn have been fixed. I’m not sure if it will fix also the pick-up crashes but it’s possible. (There was really ugly bug with artifacts in 0.71b).
Scholar info was corrupted on the saving, fixed.
Fixed.
Fixed.
Missing projectile graphic.
Who knows what is the name of Storm Elemental projectile?
Should be fixed.
Not reproducible.
Not reproducible / probably fixed.
I’ll leave it as it is, I agree we can consider this as not-a-bug.
Duplicate to… never mind, I can’t find it
Current behavior was simpler to implement (and gives all needed possibilities). Will be fixed later.
I can reproduce. Linux’ libc has a built-in memory allocator detector. In that case it found a double free.
The problem is actually with the tavern. When right clicking on a hero, CHeroWindow::setHero is called and curHero is set. When the button is released, the hero window closes, but CHeroWindow::quit is not called, so curHero is not reset to NULL, and then bad things happen.
That’s also causing the crash when buying a ballista.
It seems to me that is cprgtix.def the same as for Titan, i compared both in game (if my eyes are fast enough) and rechecked in h3sprute.lod for projectile defs, but there is probability about 1% that i missed that stormelemental’s def
Indeed. Thanks for clear description, that explains everything.
When hero artifacts set is changed (eg. because of picking arts from the map or buying war machines / spellbook) VCMI checks if herowindow is opened (and needs updating) by checking if curHero is set.
So we have crash if we have opened hero window preview with r-click and then buy / pick up artifacts. Workaround to prevent the crash is to open hero window in the conventional way.
I finished checking all the bugs in this thread, and they are all either fixed (= not reproducible anymore in 0.73) or reported in SourceForge or newer bug threads. Well, except for this one, which I added only now in SF:
To clarify when the bug occurs, I added also in SF that it’s only in case of loading a saved game (which makes it easily reproducible, also in 0.73).
And with this I’ve finished the checking of all bugs reported before VCMI 0.72 (from the “Main bug thread” until the “0.71b - development version” here). They are all:
either fixed (= not reproducible anymore in 0.72d/0.73, at least on my machine)
This means as of now we can easily trace all un-resolved bugs by checking only two locations:
→ SourceForge : for older bugs (0.6x-0.71b)
→ Tow’s opening post in the thread of the newest VCMI release : for newer bugs (0.72-…), plus of course the bugs reported in that thread.
So as long as the devs will continue to find the current system most efficient, there should be no need of logging bugs in SF anymore. Unless of course the programmers will find it convenient to log there bugs encountered in dev. versions not released on the forum.