Only found out now after finishing the game - some things are bound to FPS and don't behave as they should on high frame rates. Extremely important for 2 things:

1) Bosses that passively regenerate health. I initially thought it was intended, but no. Had to resort to cheese tactics to beat those bosses, only to find out that they had 4x the intended regeneration rate, as I played the game in 240 FPS. Locking to 60 makes it normal and the bosses become somewhat normally killable. So for these boss fights, make sure to lock FPS to 60. The rest of the game, you can play mostly with unlocked FPS if:

2) You are fine with buggy knockback physics. There are a couple enemies which have knockback to their attack, mostly bosses again and golems. With unlocked FPS, it can sometimes bug out and a knockback which should deal only a little damage to you will instagib you because the physics are yet again confused by the frame rate and the damage is dealt to you like 50 times instantly.

3) A minor thing, but some sounds can get spammed multiple times in a row with too high FPS. Like arrows or bolts hitting things, rain, campfire sound, weapons and items dropping to the ground etc. Dropped items can also fall through the ground if they are on a too steep hill because the FPS is too high and the collision detection code can't keep up.

Would have been really nice to know this BEFORE finishing the game.... Oh well, at least a warning for others. Other than the 3 things mentioned above, the game played fine at 240 FPS.

Nice list and yes Indeed locking a game at 60fps, is what anyone should do to all games from this era, modern gamers need to realize that high refresh rate monitors, was not a thing back then, afaik at that time the max a monitor ever went, was 100hz (could be wrong thou...) and that was in the days of CRT's and even then, afaik that was very rare, most CRT's I knew where 60hz, 75hz or 85hz. When TFT's, plasma and LED monitors came about, the norm became 60hz (60fps), and this, was for a very long time, so many old games, until more or less 2007/8, are mostly coded to 60hz (a few do support 120hz but is always a gamble) and a few that got directly converted from old consoles, got even coded to 30hz (30fps), thou fortunately this ones are a minority but is good to know they exist.

So the main rules of thumb when playing such old games and having issues, is do this, one lock frame rate to 60hz and in rare cases even 30hz and two, set CPU affinity for the game executable, to a single core.
The last one alone, solves many problems in old games, specially with physics, like collision detection failing for example and causing a bunch of bugs like scripting bugs, like some trigger doesn't fire because the physics fail to detect the player inside the trigger, so a mission bugs out and totally breaks the game.
Yes this is not cool, because we all want to use our latest and greatest hardware to play our games, but this is the nature of the thing, this old games were not made with modern hardware in mind (people are not witches...) so things end not working has expected in more modern hardware. When it evolves, changes and things get removed because they got deprecated, the probability past games will break is mostly certain.
And this will be true to current games in few decades.

Definitely. The thing with Gothic though, is that it seems perfectly fine at first glance. The game is perfectly playable and the things the high framerate causes are very specific, which you might not even realize are happening.

In most cases, you can tell straight away if a game falls apart at high frame rates. But here, I only looked into after having nearly finished the game and wondering, what the intended "strategy" for the auto-heal bosses was. Which was when I found some mention of this on the internet.