Posts from HoMM3 HD is a mod (add-on) for the game Heroes of Might and Magic 3.

It's not just you who reported the issue with settings being reset, so we'll continue to investigate and figure it out. The bug with the kingdom overview will be fixed in the next version. You mentioned that you can't load password-protected saves in HotS. You need to select the correct colors using checkboxes – it's not very obvious, but that's how it works for now.

I also experienced settings being reset in one of the latest versions. The solution was simple: configure the map, select the castles, return to the map configuration, choose the desired settings, and start the generation without switching to the castle selection. The problem only occurred during the first generation; in the second and subsequent attempts, you could start the generation from the castle selection window.

No idea what they decided to do with the replayable quick battles; I don't feel like reading through a ton of text, but if they're going to implement it, they should also introduce another feature from Warlords/Towns: resetting mana before the quick battle. I still shudder when I remember the AI's love for summoning elementals in battles against weak neutral creatures.

experience, experience... awesome... :smile52:
but first, it would be good to fix the bug with earth magic (absolutely all the most important spells in it are broken, and in water magic - it's empty :mad:)
and I'm tired of playing when I'm just 1 gem short of building angels on day 117, I heard there's a solution...

but if you implement it, you should also introduce another feature from Warlords/Towns: mana reset before quick cast.

I can't say for sure which version I have, but quick cast doesn't use spells at all.

This isn't a bug; it's just poorly designed. This feature also makes it difficult to "remember" the game and hinders both the player loading the game and the opponent if there's been a long break in the game.

If you load a save in HD+ (let's say a game with a 10-minute timer) and immediately switch to the castle window, the timer will reset after the opponent joins. In my case, it reset to unlimited time, while my opponent's game time continued to run normally. + It can be fixed by selecting a different save, and then selecting the last save again. The timer is restored.

Lider1, I keep looking at the logs and realize that most of the bugs you report have already been fixed. In the post with the two crash logs, there is definitely a bug in the mod. But the last two are bugs in the game.

HD+ = 0 in the last two logs, so the crashes don't surprise me.
You should at least study the structure of the crash log, since your game crashes so often. And you shouldn't be surprised by crashes without HD+, some errors are caught and fixed by the mod "on the fly", so there may not even be an exact cause for the bug, just an underdeveloped exception, for example.

You should be more mindful of Bari's time and filter the logs yourself. ;)

Lider1, I've looked through the logs again and again, and I realize that most of the bugs you report have already been fixed.

Hmm... I don't understand? If they're fixed, why do they still appear?

HD+ > = 0 in the last two logs, so I'm not surprised by the crashes.

Are you saying that critical bugs in the regular version aren't fixed automatically?

And you shouldn't be surprised by crashes without HD+, some errors are caught and fixed by a mod "on the fly," so there might not even be a specific cause for the bug, just an underdeveloped exception, for example.

But why doesn't it crash as often in the regular version? And what guarantee is there that it won't be "just an underdeveloped exception" in the HD+ version? And does that mean I can't play the regular version at all now?

You should at least study the structure of the crash log, since the game crashes so often for you.

Maybe I should learn assembly language too? :D Since my game crashes so often.

You should be more considerate of Bari's time.

Well, I personally don't have anywhere to rush, and I think Baratorch doesn't either. And I'm not pressuring anyone. If they have the time/desire, they'll do it; if not, they won't. I'm just reporting what happened. But I can slow down if there are too many reports and they're not that needed (or useless), because I'm starting to feel like Genghis Khan myself :D :D :D In my opinion, they're for a good cause, but who knows.
But your phrase

And you shouldn't be surprised by crashes without HD+

somehow really confused me.

and I filtered the logs myself. ;)

Well, you said it. Good job. How can I filter them if I don't know anything about debuggers and the like, I only know that they exist. I'm not a developer, I'm a player.

But, I hope you want to be not just a player, but also a helpful tester, because you've sent 90% of the logs in this thread. ;-)

Now, to the point: disabling HD+ does not fix bugs. None, not even critical ones (although, in my opinion, this is unfair, and I may be misinforming the public). Therefore, crashes will likely still occur and may even happen quite frequently. There is a solution: play with HD+, and if that's not possible, don't complain. Because I'm sure that a significant number of logs contain errors that have already been fixed or at least recorded so as not to cause the game to crash.

In reality, there's nothing complicated about the structure of the crash log; you just need to read a little about what's written. Ignore anything unclear.

Now, about the structure of the crash log.
Actually, the first block after the description is the mod version. If the mod version is older than the latest one, you shouldn't send the log. This is logical.

The next block is the time of the crash. Well, everything seems clear here.

The Exception block is the most important one; it contains the module in which the error occurred and, directly, the address of that error.

In most cases, the most important information in it is the first two lines.
Module – the component of the mod (or the game, in the case of an executable file – *.exe) in which the error occurred. It should be noted that the following may appear here:

• mp3dec.asi or mss32.dll – a crash due to outdated SoD music libraries. Fixed by HDmod, the parameter in the ini file < NewerSoundLibraries > = 1. It is enabled by default, so such crashes should not occur.
• heroes3.exe (or any other executable file that was launched using the mod) – a crash due to a SoD bug or incorrect modifications (this is unlikely if you don't modify the game code yourself). If the *.exe file has not been modified, you should send the crash log if HD+ is enabled, as you may have discovered an original game bug.
• binkw32.dll or smackw32.dll – a crash due to video, most likely due to bugs in the vid file (this is unlikely if you don't mess with things you shouldn't :-)).
• patcher_x86.dll – a crash, usually, immediately when the game starts, due to incorrect installation of modifications. If no dll modifications were loaded (if you don't know how to do this, the probability of this is quite small), you should send the crash log itself, as well as patcher_x86 dump.txt and patcher_x86 log.txt, which are created in the root folder of the game, in the same place as the crash log.
• _HD3_.dll – a crash due to an error in the HDmod algorithm. This means that an error or oversight was made somewhere in the code of the mod (not the game). In addition to the crash log itself, you should send patcher_x86 dump.txt and patcher_x86 log.txt
• kernel32.dll – God forbid you encounter this, as this is one of the most unpleasant cases of a game crash, related to memory allocation or deallocation.

The second line of the block is the address where the error was detected. This information will only be useful for the developer, so we won't pay attention to it.

The Call Stack block captures the calls to the address specified in the previous block and, so to speak, related addresses. Any program, any code consists of functions that are intertwined with each other. Therefore, if one fails, it will drag several others with it. The Call Stack helps track the root cause of the game crash (if there is no one at the address specified in the previous block). In principle, this is the result of a breakpoint, a crash specifically triggered at a certain point to capture calls to it or to the function containing it. Oh yes, this information is only for the developer.

I decided to explain the blocks that won't be useful for the user later, so I'll skip some.

The Main INI block is actually your ini file. Sometimes, it helps to identify or build a hypothesis about the cause of the crash. For example, in your crash log, I saw a line in it that says that HD+ is disabled. From this, I made the above conclusion.

The Some ingame values block allows you to find out additional information about the circumstances of the crash, for example, in the case of map errors (a city turns gray, let's say), the developer will see the map name, the active player at the time of the crash, and so on in this log (it's basically all written in English, so if you want, you can translate it), which may theoretically help.

That's all. If you study the structure of the crash log and some of the circumstances of crashes, the number of crash logs you send, Lider1, will probably decrease significantly. Play with HD+ and a normal version of Heroes. )

Vaflya, you are wrong. I hasten to dispel your misconception so as not to mislead others.

1. Critical bugs in the original game (leading to crashes and not affecting gameplay) are fixed by the main HD module; it will do this even if all HD options are disabled. (For example, the bug with rumors in the tavern causing random crashes, crashes in the city screen when clicking on the city icon in the list during the opponent's turn if they don't have that many cities yet, crashes in artifact merchants if there are empty slots between artifacts in the backpack, crashes if random creatures are assigned to a random hero in the editor, ...)

2. The NewerSoundLibraries option, which is enabled by default in HD, is specifically responsible for fixing critical errors when playing music in the original game (i.e., the errors are fixed by default).

3. A separate module, working independently of others, is responsible for automatically fixing map errors, such as duplicates, overlaps, etc., and is activated by the AutofixMap option (and deactivated by it as well). The AutofixMap option is always enabled by default in HD 3.x; if you want to disable it, you can always do so.

4. Only some critical errors (leading to crashes or freezes) in the original game are fixed by HD+, specifically those that affect gameplay: AI with an alliance of angels and neutral creatures in the army, casting the 'clone' spell, AI freezing (infinite turn). (all 3 for now)

5. If the module with the error is not _HD3_.dll, it does not mean that the cause of the error is not in HD. Moreover, if all of the above fixes are enabled, then the cause of the crash is 99.9% an HD error. (it is also true that HD sometimes exploits an original bug that is not exploited by the original game itself; such bugs are very difficult to catch, but ultimately the cause of the crash is still HD, because it does not exist in the original game.)

**

The main suspect for the source of the latest errors in the game (resetting RMG settings, timer, and crashes) is the 'fix' for desynchronization of new game settings among players in a network game, which is activated along with the TournamentExtensions option. In the next version, I hope to fix all this. But it may be necessary to sacrifice the fix for desynchronization in order to do so.

Well, I warned that I might be wrong, and I don't fully understand how it works, but now people will know better.

I scrolled through the last 8 pages and couldn't find how to enable the display of monster turns on the battlefield. Version 3.20. HD+ is enabled, of course. And what are "stretch filter" and "renderer"? Maybe I should remove them and move them somewhere else?

I've scrolled through the last 8 pages and couldn't find how to enable the display of the movement range of units on the battlefield. Version 3.20. HD+ is enabled, of course. What are "stretch filter" and "renderer"? Maybe they can be removed or moved somewhere else?

Without considering the units already in position - Ctrl + hovering the cursor over the desired unit, with consideration - using Shift.
In general, when playing a hotseat game with two players, the shadow of the cursor, indicating where they will move, was displayed incorrectly for two-square units, showing the cell to the left. Also, I often can't open the stack window to see how many turns are left for slow/haste. The question mark is there, but it's no longer clickable. Nothing happens when I click it. Also, a request to add gems for the Nagabanka. And in the last generation, strangely enough, a "Vog" object appeared - a pyramid with golems. That was surprising. I tested the Nagabankas (just in case, considering the generation issues). I entered "nwczion" to build everything - when switching to the Castle of the Flux, it consistently crashes. I'm not sure what exactly causes it, so here's the log (it might not be related to the cheat). When launching not through the launcher, everything is normal. However, it's not launched through Heroes3.exe itself, but through Heroes3HD.exe, created back in version 2.96, if I'm not mistaken. It also works normally through h3wog.exe, without crashing. The last two crashes in the log relate to this problem.

Vaflya, thanks for the technical details. You’ve shed some light on what each component does. But as you can see, critical errors are also fixed automatically in the New Dawn.

There is a solution: play with HD+, or, if that’s not possible, don’t complain.

I think this is not an option! If an error occurs for me, it means it will occur for someone else as well. And simply giving up on playing the game on “pure” New Dawn is not a solution, IMHO.

If you study the structure of the crash log and some of the circumstances of the crashes, I think the number of crash logs you send, Lider1, will noticeably decrease.

What was meant by the highlighted text? Well, I opened a text document and checked to see if the error addresses were repeated. What’s next? The mod version is always the latest.

Play with HD+ and a normal version of Heroes.

What does “normal version” imply? Does it include New Dawn+?