Śląskie, PolandFirst patch:
- Fix for respawning inside of Cruxfirth before completing The Lice Slough, plus moving Cuff Arrow just in case you had already done this.
F?
The one in DX guide outdated - the autosplitter linked in that guide is deprecated at this point. Use the one that can be automatically download from LiveSplit when you type in the name of the game.
I don't mind. The only thing I am opposed to are using Macros, so essentially complex sequences of buttons, often with delay in between - cause that's going near TAS territory, but rebinding is fine for me.
Short for me: Rebinding keys to mouse - Yes Key macros - No
You should join Deus Ex speedrunning Discord - post it there. Not many runners actively check Speedrun.com forums.
If you mean, "Why aren't there more Revision runs?" - probably because it's not an interesting or fun run due to the changes Revision makes to pretty much patch everything as it goes.
One thing that bothers me is once again a limitation of speedrun.com itself.
In other Hitman leaderboards, it was quite common for Any% and Easy runs with worse times than SA or Hard difficulty runs to be submitted and listed as WR, while in reality, it's SA runs that should be automatically listed in Any% category (or Any% Hard runs to be listed in Any% Easy) as WRs.
Basically, a category and sub-category dependency would be nice, where it would not be required to duplicate entries to prevent "lazy" runs that don't beat requirements from higher difficulties or more difficulty categories from being listed as WRs.
Could you set https://www.speedrun.com/hitman_3_category_extensions/ as a category extension of https://www.speedrun.com/hitman_3
solderq35 asked me about it and thanks.
At this point, it will literally create an empty leaderboard. So it's pointless...
If by that, you mean "should be such a mess ass "Predator: Concrete Jungle" leaderboard" - no.
If more people submit runs from consoles, yeah, I am willing to separate those, but with a single run from consoles on the entire leaderboard, there really isn't much point.
I agree. I think even old doc had some SO runs. But would like to hear what others think.
-- EDIT -- Added 2 variables for 2 levels where SO makes a difference.
I've put in baldnate in charge of the leaderboard. He is far better knowledge about the game and if he has trouble keeping up, he can set up new moderators as well. I'm gone from here, cause having just started a full-time job, I really don't have time (or energy) to moderate so many leaderboards.
That's the thing - they are not specified and I'd want someone who knows the game to take over moderating the leaderboard. Dosbox for me is a nightmare to deal with in general and I know that at least some games can pretty much take any kind of cycle value and run fine, but I have no idea how is it with original Syndicate.
I honestly have no idea how to approach the differences between PC and console.
In fact, with "Absolution" it is even worse, because not only you have huge differences between PCs and consoles (not to mention differences between consoles themselves), Absolution has such a buggy engine, that you can observe huge differences between load times on the same PC, which was the main reason why I even wrote load remover for "Absolution", as I was getting sick of runners losing up to 25s, cause for whatever reason the loading took longer.
And then of course you have controller limitations etc. so it's even worse. So essentially - I have no idea how to solve it in a way that makes sense. I guess technically there are enough runs on consoles nowadays, you could separate console from PC for the full-game leaderboard, but that is not the case for ILs.
Not very keen on that idea of killing everyone on the map in a stealth game - doesn't sound at all interesting or fast. But if you can figure out the exact numbers of NPCs on the map and others would be willing to try it - maybe I could add it as misc category.
As in the title.
We actually do know about one end level mission crash case, which we speculated to be related to newspaper screens and limited to Nvidia graphics cards (Heinki when playing the game casually on - I believe - GTX 1080 Ti experienced it, as well as Kotti on then - I believe - GTX 970). However, I don't think we ever found a solution - the problems just seemed to have stopped and that was it.
However, it might be that our assumption is wrong and this issue is specific to some Windows version or some windows upgrade or something. All I can recommend is to try and update drivers to the newest version and make sure no settings are enforced from the graphics card panel (like Anti-aliasing, Anisotropic filtering, etc.)
If that doesn't help - you might want to try running the game over DXVK (DirectX to Vulkan Wrapper) assuming your GPU allows for Vulkan rendering. That wrapper recently not only was making wonders for Linux gaming but it was also solving many graphical glitches for DirectX9 and DirectX 10 games. Sadly it has some downsides like it doesn't allow for Steam overlay to work, some games exhibit some performance issues with it and of course, you need to use window capture in OBS for it.
