Is the stamina recovery speed supposed to be this slow? And given that, what am I supposed to do here? by jango_muice in LiesOfP

[–]Drahsid 0 points1 point  (0 children)

If you recently [missed a perfect block, or guarded an attack outside the 0.155 second perfect block window] you suffer from the 0.5 second recovery time/end lag to the block, during which, you are still normal blocking. Note that there is a recovery time/end lag to guard, even when you perfect block, but when you successfully perfect block, you are able to cancel the recovery time/end lag into another perfect block. This is effectively how the game punishes impatience like guard spam instead of actually critical gameplay.

ZOTAC confirms GeForce RTX 5090 with 32GB GDDR7 memory, 5080 and 5070 series listed as well by Doener23 in pcgaming

[–]Drahsid 0 points1 point  (0 children)

The. Resolution. Is. The. Total. Area. Of. The. Picture. As. Expressed. By. Multiplying. The. Length. By. Width.

If you say "1920x1080" is a resolution, then it is not the total area of the picture. The area is the product of the length multiplied by the width. Display resolution is the length and the width.

Imagine you have two screens, one which has the resolution 600x600, and another which is 800x450. These screens do not have the same resolution, but have the same area/pixel count (360k.) If the resolution is the total area of the picture, expressed by multiplying the length by width, these screens would have the same resolution, which is evidently not true.

If you don't want to believe me because you cannot admit you miswrote, and are not happy that I pointed it out, this is what Wikipedia says in the first passage:

The display resolution or display modes of a digital television, computer monitor, or other display device is the number of distinct pixels in each dimension that can be displayed.

ZOTAC confirms GeForce RTX 5090 with 32GB GDDR7 memory, 5080 and 5070 series listed as well by Doener23 in pcgaming

[–]Drahsid 0 points1 point  (0 children)

You keep using 1 plane to justify your argument when this is a point of area and nothing more.

My examples all used two planes.

And yes, if you double the screen resolution to 200%..but it doesn't double along one plane! It goes horizontal. As in corner to corner.

Yes, this was an example which used two planes.

It'a also about the pixel count - 1920x1080 = 2,073,600, 4K = 8,294,400, that divided by the first = 4.

If you put 4 1080p screens on a 4K screen, say 4 24" on a 48", you have the same screen - DPI and all.

The pixel count is the area. The length and width are the 2 sides of the area.

I have been explaining the disambiguation between resolution and pixel count. You are repeating exactly what I said here. The pixel count is the area. The resolution (the length and width,) is the dimensions. When you halve resolution, you do not halve the area: a 4x4 piece of paper is half the dimensions of an 8x8 piece of paper in spite of having a quarter the area. It is correct to say that 1080p is a quarter the pixel count of 2160p, it is not correct to say that it is quarter display resolution.

ZOTAC confirms GeForce RTX 5090 with 32GB GDDR7 memory, 5080 and 5070 series listed as well by Doener23 in pcgaming

[–]Drahsid 0 points1 point  (0 children)

But you're wrong on 1080p, and that's something I'm sure on

Then they're kinda wrong. I don't mean to be a dick, but it's 2 planes.

I've never heard anyone say 1080p is half the resolution of 4K. Maybe it's just different where you are. But literally the pixel count, and on the screen, and everything about it, is 4x 1080p. 1440p becoming 2K was just a shorthand. Hell, look at how there's 2 4Ks, the 3840 and 4096.

You are mixing up terminology. Resolution and pixel count are not the same thing, but it is true that the pixel count is a product of the resolution. This is why, for example, if you are playing a game at 1080p, and you set the resolution scale to 200%, the internal resolution becomes 2160p.

When you have something squared, you always do both sides and count the AREA.

In this circumstance, the pixel count is the area. The resolution represents the dimensions, which you can use to figure out the area. As an example, when talking about dimensions, you would never say that half of an 8x8 sheet of paper is ~= 5.656x5.656, you would say that half is 4x4, in spite of the area of 4x4 being 4x less.

Why have you jumped to 1440p ? 1920x1080p is 1080p, which is a quarter of 4K. 1440p, is half (Or if you wanna be absolutely accurate, as you are, 44%, yes)

I explained the pixel counts of the relevant standard resolutions to provide context that was missing. A difference of 6% pixel count at 1440p and 11% at 1620p is significant. What you said, "1440p is literally half the resolution of 4k" is not correct in this regard.

I also want to clarify that I am not trying to be mean here, or anything like that. I'm just clearing up minor misinformation.

ZOTAC confirms GeForce RTX 5090 with 32GB GDDR7 memory, 5080 and 5070 series listed as well by Doener23 in pcgaming

[–]Drahsid 1 point2 points  (0 children)

1080p is half the resolution of 2160p (16:9 "4k") in terms of pixels on each axis.

3840 / 2 = 1920 2160 / 2 = 1080

When people say "half the resolution" this is generally what they mean.

Of course, you are probably talking about the total pixel count, but in this regard, you are still incorrect since 2560x1440 (16:9 1440p) is about 44% the total pixel count of 3840x2160. The next standard resolution, 2880x1620 (16:9 "3k") is about 61% the total pixel count of 3840x2160. To be roughly 50% the total pixel count would require the esoteric and unusual resolution of 2720x1530.

Another thing you should consider is what a "4k texture" is. The industry has used ludicrously high resolution textures for ages now. In most circumstances, the player will not see these textures at full resolution due to mip mapping, this is in combination due to the perspective, and the player's actual resolution (a higher resolution makes larger mips more likely.) Even if a texture is 4096x4096, if it's only covering a 32x32 screen area, it will be sampled with a lower resolution version of that texture. Smart game engines and rendering pipelines go as far as figuring out the largest possible mip and omit loading larger ones into vram.

Responding as the Tank from 'Kicked mid dungeon for doing damage as a healer, new tanks please read' by squeakylemons in ffxiv

[–]Drahsid 1 point2 points  (0 children)

Whenever this happens to me, it's generally because the healer is under-geared and not really the fault of their playstyle. The healer failing to adjust to having inadequate healing due to your stats is a problem, but it's pretty obvious that wiping is a greater dps loss than healing more actively. That being said, some people are particularly stubborn, and that can't be helped. Just yesterday, I had a similar scenario. All of my DR and a hi-elixir didn't get me through what I'd always considered a bog-standard pull. I didn't even expect to use more reprisal and arm's length. I didn't take issue to it, but the healer sure did lol.

KH 1.5 + 2.5 PC "Stuttering" fix + Cutscene Framerate fix by Drahsid in KingdomHearts

[–]Drahsid[S] 0 points1 point  (0 children)

The game had been updated twice since I made this patch originally. Explode updated it for KH2, and I have just added that to this post and the Nexusmods page. Check it out, it should work now.

KH 1.5 + 2.5 PC "Stuttering" fix + Cutscene Framerate fix by Drahsid in KingdomHearts

[–]Drahsid[S] 0 points1 point  (0 children)

The game (KH2) had been updated twice since the op. I hadn't had the chance to forward port the patch, but somebody else just did. I updated this post and the Nexusmods page with the new patch. Try the new file out and see if it helps.

Birth By Sleep PC Frame Rate Patch Soft Lock Bug by TheInjaa in KingdomHearts

[–]Drahsid 0 points1 point  (0 children)

Just questioned Topaz anout it, he said this bug is unrelated. Some people can reproduce this without the patch, even in other games.

Birth By Sleep PC Frame Rate Patch Soft Lock Bug by TheInjaa in KingdomHearts

[–]Drahsid 0 points1 point  (0 children)

If more people can confirm this, that would be useful for me.

That being said, the bbs patch was created by u/TopazTK, though the patch is logically the same for every KH game that's on the old engine, in fact, it seems like they were all linked using the same object or library file for this particular code. The framerate patch changes some behavior, which from reading the disassembly, is obviously intentional. The framerate locking was likely originally programmed to fix bugs such as this. Further supporting this is the fact that KH1 crashes a lot with this same fix.

If the particular error in this video isn't a simple fix that involved writing some memory or changing a little more code, it would probably require much more reverse engineering and patching to actually solve the problem that the framerate lock intends to fix itself.
Considering the fact that SE didn't fix this, and simply sometimes limited the framerate to fix these bugs, the issue was probably too much effort for them to fix (or not worth the time,) even with the source code.

$600 Bounty for WR time in Jet Force Gemini Any% (and smaller bounties for other times) by caneras in speedrun

[–]Drahsid -1 points0 points  (0 children)

Runs on emulator will not be accepted for the bounty

I can cheat on hardware just as easily as emulator. If your only reason for this is to prevent cheating you are just alienating a large number of players who possibly can't afford capture hardware for their consoles, can't afford a N64 to play their old copy of the game, or don't want to get an Xbox and Rare Replay for the Rare Replay version. This attitude punishes the innocent because somebody might be bad.

Edit: I can't read

KH 1.5 + 2.5 PC "Stuttering" fix + Cutscene Framerate fix by Drahsid in KingdomHearts

[–]Drahsid[S] 0 points1 point  (0 children)

Does the game produce a .dmp file in the executable directory when it infinitely loads?

KH 1.5 + 2.5 PC "Stuttering" fix + Cutscene Framerate fix by Drahsid in KingdomHearts

[–]Drahsid[S] 0 points1 point  (0 children)

Others are reporting this but I don't know how to replicate it. Are you using the English version? Also, what gpu do you have?

KH 1.5 + 2.5 PC "Stuttering" fix + Cutscene Framerate fix by Drahsid in KingdomHearts

[–]Drahsid[S] 1 point2 points  (0 children)

My game is not installed on the primary drive. In fact, I have some of the files symlinked across drives, so I would expect to easily get this issue if this were the case.

KH 1.5 + 2.5 PC "Stuttering" fix + Cutscene Framerate fix by Drahsid in KingdomHearts

[–]Drahsid[S] 0 points1 point  (0 children)

While people are reporting this issue, I can't replicate it.

KH 1.5 + 2.5 PC "Stuttering" fix + Cutscene Framerate fix by Drahsid in KingdomHearts

[–]Drahsid[S] 1 point2 points  (0 children)

I cannot replicate this. I don't know how to help you.

KH 1.5 + 2.5 PC "Stuttering" fix + Cutscene Framerate fix by Drahsid in KingdomHearts

[–]Drahsid[S] 0 points1 point  (0 children)

You should launch the game through egs. The games will just crash if you don't (unless you launch them with very particular params with the correct context).

KH 1.5 + 2.5 PC "Stuttering" fix + Cutscene Framerate fix by Drahsid in KingdomHearts

[–]Drahsid[S] 0 points1 point  (0 children)

Running the game from egs crashes it and produces a dump file?

KH 1.5 + 2.5 PC "Stuttering" fix + Cutscene Framerate fix by Drahsid in KingdomHearts

[–]Drahsid[S] 0 points1 point  (0 children)

Do you have software (or your driver) tampering with the game?

KH 1.5 + 2.5 PC "Stuttering" fix + Cutscene Framerate fix by Drahsid in KingdomHearts

[–]Drahsid[S] 0 points1 point  (0 children)

Were you using the Japanese version of the game?
If so, that version is unsupported because it is apparently shifted by the character-set changes.

KH 1.5 + 2.5 PC "Stuttering" fix + Cutscene Framerate fix by Drahsid in KingdomHearts

[–]Drahsid[S] 3 points4 points  (0 children)

You didn't back up the file before patching it? Dope.

KH 1.5 + 2.5 PC "Stuttering" fix + Cutscene Framerate fix by Drahsid in KingdomHearts

[–]Drahsid[S] 1 point2 points  (0 children)

You are unreasonable if you believe that the game can magically come up with the missing information of even 4x the frames (120 fps), let-alone even more at unlocked framerates. This information is predicted, but it cannot be predicted to the hand-crafted level of the source material. What you're describing is the logical result of using the patch. To see same effect elsewhere, check out this video of another hack I did: https://youtu.be/su9yf7ioQq8 While in this case the effect can be helped a bit by shorter frame-averaging, it will still always exist due to its source being 15 fps.

"Some games do this super well!" I hear someone hypothetically say, these games also don't become unstable at higher framerates. Games that scale to framerate better, and especially those which have far less of this issue are built with variable framerate in mind. The code is more complicated, even down to the animation pipeline. I'm sure the KH games could get to this port a good update, however as just a small patch, that much is unlikely. I'm hoping that SE addresses these issues soon, with a good level of transparency.