Yeap , you’re right other time they were moving, so this wasn’t reproducible, but that time enemy skeletons were staying for about 3 rounds “in the wall” not going to gate
and about #34 - it was for ai creatures and on 16001200 so probably related to “slowdowns” because later I had morale on my troops on 800600
As for catapult it’s not a bug - it has it’s move but it’s invisible. (as I wrote it’s animation is not yet supported) The only noticable effect may be wall damaging (if it is lucky enough to hit)
Any log messages before? Do you have graphics for the queue (included in the apckage)?
A lot of errors would seem to spring from different resolutions. IIRC there is bits and pieces of code that assumes 800x600 instead of calculating positions from the current resolution.
Fixed, but perhaps not pixel-perfect. Spell effect positions in general should be more accurate (at least in 800x600).
Also, a bug: #41 - Underground cartographer should only reveal the underground ground, even when placed at the surface. Same thing for surface cartographer (they’re treated as the same object, I reckon). I had first thought it was supposed to be this way myself, but apparently not. Maybe it was in RoE?
Sea cartographers also reveal sea at both levels. Not sure if this is already so, my test map is a bit strange and I haven’t had the time to fix it.
Well, I did it so that Cartographer reveals the land of type where it’s placed. The problem is these objects have no subtypes, but only different graphics, so indeed are handled as one.
Not having different subtypes does make it awkward I’m sure, but there must have been something in the standard H3 code to handle them. Perhaps a subtype or something could be added to VCMI so you can differentiate as well?
To keep full compatibility with all existing H3 maps, Cartographers would need to work the same way: i.e., surface Cartographers reveal all terrains that aren’t subterranean or water, subterranean Cartographers reveal only subterranean, and water Cartographers reveal only water.
Personally, I think they should have made the land Cartographers reveal the shroud based strictly on layer (surface or underground) except for water which would be revealed by the water Cartographer.
Even better would be if each Cartographer could be edited in the map editor with a checkbox for Surface, Underground, and each Terrain type, so you could have them reveal whatever you wanted. (BTW, are there any plans to make a VCMI map editor at some point in the future?)
Guys, I just tested it in WoG and underground cartographer doesn’t reveal any terrain AT ALL, no matter where it is, while the others reveal land or sea on both levels. Makes little sense to me.
It does. the underground Cartographer reveals all subterranean type terrain (whether on surface or underground) and ignores all other terrain.
After reading your message I created a quick WoG 3.58 test map just now and verified it.
But you’re right that it doesn’t make a lot of sense the way they did it (basing it on terrain types only). Which is why I said to keep full compatibility with existing maps you’d need to do it the same way, but I wished they had done it a more sensible way.
Great. It’s good to hear that you would like to have one (I’ll take that to mean you may work on one at a much later date. ) And of course, the engine is of prime importance, because without the engine, nothing else will go very far.
I think the advantage of a new map editor (at some point after the engine’s completed) is that it can provide a degree of easy modding to the game (on a map level) that almost anyone can do. For example, a simple addition might be setting the value of treasure chests, sea chests and similar objects in the map editor. A more complex addition might allow certain bonuses or abilities to be given to artifacts without the need for scripting.
I’m probably writing this in the wrong thread, and I suspect serious consideration of a map editor is a year or more away, but I just wanted to share my thoughts as they occurred.
#43 - If possible, correct (no plural) handling of single creatures in info boxes & subtitles.
In the screenshot above, the message says correctly “Archangels, Sorceresses and Pikeman”, however under creature icon we have “1 Pikemen”.
[size=75]
No problem. The map editor will probably be a whole big chapter later on in the development of this project, which will get its own thread once the devs start working on it. I’ll take care then to scan the forum for all related suggestions from the past (like yours above), and log them all in there. ;)[/size]
[size=92]I have a small question about the google spreadsheet (not sure if this is the best place, but I guess it’s as good as anywhere else:) :
Some objects appear in there twice (i.e.: Garrison, Magic Plains). Is that just by mistake, or there is a reason for it (like for example an enhanced version of the same object either introduced by WoG, or simply planned for VCMI)?[/size]
[quote=“Zamolxis”]
Some objects appear in there twice (i.e.: Garrison, Magic Plains). Is that just by mistake, or there is a reason for it (like for example an enhanced version of the same object either introduced by WoG, or simply planned for VCMI)?[/quote]
Some variations of a certain object may have a different ID. In the case with garrisons, ID 33 is used for horizontal and the diagonal one and ID 219 for the vertical ones. It’s good you brought that up, since I had only implemented right-click info for the ones with ID 33 and is fixed now.
@Boulie: Are you sure it’s when you press NEW GAME? I do have the same issues, however not when I click on NEW GAME, but afterwards, in the New Game menu, when I click SINGLE SCENARIO.
If that is the case, then this was already reported on Mantis as #77 & #79. If that is the case, please confirm, as there’s no need to create dupes. Otherwise let me know and I’ll log this one as well. Thanks!
Meanwhile I also completed moving all unresolved bugs from this thread to Mantis (based on the list created by Tow in the 0.74 thread and some further tests of my own). If anyone believes something was left out (still reproducible in 0.74 and not logged in Mantis), please advise. We’ll check with the devs if it’s fixed in SVN, or else we’ll log it. Cheers all!