dimitrius154

Once the next iteration is released< the problem should be resolved. The expected time of release is the end of March. Hmm, should I make it the 01.04.2023 release, or should I not?)

Indeed, that way the un-zipped package takes approximately half the original space. Supposedly without affecting the original quality.

That's correct for the "miniobj" and "physx" subfolders, the rest are altered.

Somehow 1-bit alpha gets messed up. Updated. Let's try again.

Could you, please, take a look at https://drive.google.com/file/d/1jOsXS4JJQEycX8jnlrAZJH8r04t3Iuia/view?usp=sharing ? Point is, Sacred 2 memory management is very particular as to how much is taken by textures. It should never be more then 390 - 400 MB, otherwise the game starts to stutter.

@VishankaAbout the Beautification Mod - is there any specific visible effect from saving as DXT5, instead of DXT1?

@FlixTurns out, the coldown + regeneration time description part had been erroneously made invisible back in 2018.

Hmm, the timer must be off.

Definitely, looks like I forgot to do it myself.

@FlixIt's definitely about s2logic.dll. Will take some time to figure out.

Hmm, try replacing global.res with the one from v15.

I'd say it should be a "hidden" property, like those special weapon mechanics in Sacred1. The way it works is quite shoddy, basically, a state flag is being set, that's checked upon animation selection. Definitely not intended. May I see a sample of the original outlook? No, itemnames addresses NameGen.dll. Although, perhaps, changes chould be made to it, for the sake of consistency. It's definitely et_shieldblock. Damn those typos and the inferior keyboards!

Depends on the version of the game. The cookie-cut answer is {game_directory}\scripts\server. The true challenge is identifying the quest names. They are in German. I'd suggest the German->Russian Google Translate setup, since I'm reasonably certain the ru_RU localization had been made via direct German->Russian translation.

In quest.txt, not in a common readable form.

It's not an amulet, it's a mount ward. It only works, when you are riding a mount.

They are now obsolete. The vertex-animated models are clearly not well suited to the code-solution present and they take a lot of RAM. The developers have even mentioned that in one of the Inquisitor's quotes. I've taken effort to get rid of other similar issues(Seraphim skirts, Undead Legate cape, Undead Mage cape). Sure. I'm currently in a process of squishing an unfortunate bug regarding collecting loot while dismounted.

A typo, actually, NUMBERS_SKILP, instead of NUMBERS_SKILLP. Wonder if anyone produces quality keyboards anymore.

@FlixIt appears you've substituted QuestView.xml with your older version, which does not contain the necessary entries for "attrp", "skilp". Entries 1804406278 and 0431164270 also have to be present in global.res. The reason it even worked with the older sacred2.exe was that it contained erroneous pointers to those entries.

Yes, the classification bonus. While I expect some additional confirmation, it would seem the Light Range bonus was bugged in vanilla as well.

1) Technically possible, their droplists may yield an empty roll. 2) I'd say, it's a pesudo-randomization quirk, unless the same situation continues further ingame.

That would be weird. Maybe it's about the GME. I'd suggest trying the more basic installation approach.

@FlixLet's try this one, the entire system folder: https://drive.google.com/file/d/1MKeizcyQ4lU6m131gpczp_o_0svceNA7/view?usp=sharing

@FlixHmm, we definitely need one more rig. Can anyone else confirm that same behaviour? @Androdion, perhaps?

Hmm, D2F v14 definitley launches for me. have you tries a shortcut with -nocpubinding -skipopenal flags?

It took me 35 minutes for this boss to die. Looks like it still regenerates somehow.