I’ve checked issues that I’ve reported for previous versions: #18 on 0.72c - After recruiting hero, on adventure map new hero is overlapped by town.
also tight formation in events-battles still present. (Loose formation needed)
ref.#05 - i’ve added the save, logs and screenshot
ref.#06 - saving setting for grids works only for games saved, if you start new map it’s also switch on. I’ve added info for this point in my previous post.
#15 Bug if you want to get into subterranean gate but hero movement is just finished. There apperes info “System message: Server encountered a problem: Hero don’t have any movement points left!”. Hero should be able to go through on the other side. Also “space” button doesn’t work. I’ve attached saved game if you need reproduce the bug.
Some battle functionalities which Zamolxis mentioned in 0.62c - development version are still not implemented, should be added to tracker ie. cerberi two heads attack, point #16.Area attacks. bug_hero movement finished.zip (208 KB)
[size=84]I’m not sure if missing features are to be added to the tracker as well (Tow/TowDragon pls confirm). But you can always add them to the Missing features & functionalities thread here on the forum. Though I guess things like multiple attacks for creatures are not a priority for the moment, as long as we still have bugs with normal attacks.[/size]
Testing and finding new bugs has definitely higher priority than moving existing ones from one place to another.
I’m disappointed with SF tracker (though it was rather Tow Dragon’s initiative, not mine), it consumes much more time than it saves. Maybe it would have sense if it was the only place of reporting bugs but IMHO forum is way more friendly place for it.
Nevertheless if someone has too much free time, feel free to add bugs from my post.
If noone does it, I’ll simply keep using my list for “tracking” 0.72+ bugs.
Okay, then I’ll focus more on testing, but still log some bugs every now and then. But for reporting - I’d prefer to start with the ones from 0.71(x) which are not yet fixed. Once I’m done with those - and after having worked a bit with SF - I’ll have a better idea if I want to go on logging bugs or just give up. I can see SF has its advantages. But if I’d be forced to choose, I’d also pick the forum any day, which is a way more flexible place to report/analyze issues.
Yes, indeed. I thought it could save us some time (assembla’s bug tracker worked well because it was the only place for bugs) but it actually doesn’t. I think sf bug tracker should be closed.
Just to make sure what you meant by “closing”, the existing reports will remain accessible right? I’m asking because there are about 30 valid bugs in there which are not in Tow’s list above, so without SF we’d have to dig in 6 different old threads to find them back.
#18 Splitting stack in meeting screen and between garrisoned heroes - if you want to separate one unit from one hero stack to another hero and you push “1”, there automatically apears quantity equal 2. (not big deal but irritating).
Everything is ok if you do it bettwen garrison and hero or from hero with one stack to another hero. img361.imageshack.us/img361/3440/splitingunitsgarrisoned.th.jpg
I suggest blocking the possibility of adding new bugs, although bugs already added should be visible. There is no point in using that tracker when it’s not the primary place for bug reports.
#19 Similar crash to crash #34 ver 072c. If hero is in windmill and you want to transfer creatures after meeting screen appears windmill screen and game crashes.
Attached saved game before the incident, you can reproduce the crash, and logs after crash.
#20 Bug - after you load saved game with hero in boat his is outside of the boat and can not move. (you can use the same attached saved game to reproduce the bug- hero Broghild)
#22 - The yellow & blue (when hover) glow animations for creatures in battle should not fade out completely. You can check it in H3: the active and the hovered creature have a yellow, respectively blue contour outline which glows, but never totally disappears.
#23 - Imps can fly to/through battle obstacles.
To reproduce use Lord Haart in the attached saved game to attack the Imps. And try to place your troops behind the obstacles.
#24 - Crash after clicking during the intro video (with the purpose of skipping to the Main Menu). Not sure if relevant, but the click was somewhere in the lower right part of the Client. I couldn’t reproduce it though. Please see the attached logs.
#25 - Crash when trying to retreat from battle (not reproducible - see logs):
#26 Flying creatures are flying through the other creatures on the battlefield (the graphics of the 2 creatures get mixed). In H3 they were always flying over the (graphics of the) passive creatures.
#27 Ballista cannot shoot if there’s an enemy creature next to it (maybe the same for Catapult). In H3 Ballista & Catapult were not losing their range abilities if an enemy was in the adjacent hex.
Only 1 Titan & 10 Storm E. reported, while you can already see 2 dead Titans in the background. In fact there were 3 Titans and 40 Storm E. that were killed.
You can reproduce all 3 bugs by attacking the Archangels at South-West with Sir Mullich in the map attached. And I’ve also added logs for #28 if necessary. just testing.h3m (4.83 KB) 090801 - Wrong Battle Casualties.zip (3.9 KB)
It was not used as place for reporting bugs but for arranging roadmap and as remainder for some “to be solved later” issues. But even in that form it proved to be needless.
Hmm… if someone wants add some of the old bugs to the tracker I won’t have anything against. It’s easier for me to track bugs when they are in the tracker. It’s only not worth of our (or our testers’) time. But if someone has it…
Let it be.
Duplicate to that one, fixed.
Fixed.
As for the smpeg crashes (on entering town screen / battle screen / battle result window), please check if problem is still present in 0.73 (I’ve used different version of smpeg that reportedly has some fixes).
Probably fixed (as redundant clicks are now ignored).
I can see SF has its advantages. But if I’d be forced to choose, I’d also pick the forum any day, which is a way more flexible place to report/analyze issues.
