Devlog KAG Build 2151 - Minor Tweaks, Knight Hitting Fixes, Exploits Patched

Hey Folks

Minor Release, just a few fixes and additions. Should be out in the next 30min or so.

I'm pushing this out in a relative hurry to revert to old behaviour for knight attacking - the new code allows attacking through doors in some instances, and the old code is more conservative, so I'm going with that. We'll look at a more robust solution soon.

There's also a fix for a TDM exploit, an added scripting constant, more modder-friendly collapse behaviour and a fix for the radius being reported incorrectly for non-circular shapes. It's still an approximation, but it's now a correct approximation instead of twice what it should be.

Also: your votes have been noticed - we'll be looking at the PixelOffset issues next

Have Fun,
Max

Full Changelog:

Code:

[added] air count is copied when changing class
[fixed?] modding-unfriendly isTileSolid was used for collapse block solidity testing.
[fixed] approximate radius for polygon shapes was twice what it should be
[added] Maths::Pi constant (how were we missing this??)
[fixed] more dirt vulns on pressurecooker (people amaze me)
[reverted] to old knightlogic to patch hitting issues

 

In some circumstances, maybe? Not 100% what you're asking. It's back as it was before the last build. @Fuzzle has done some work on better code based off that previous one, but it's quite a complicated problem to solve. I don't have any more time to burn on it this week (again, I'm not meant to be "on KAG" this week) and next week I'm going to be looking at those pixeloffset issues.

This is my experience in KAG all day every day lol - as I said in the maps feedback thread I can't imagine why anyone would deliberately stalemate themselves but whatever, should be fixed.

 

Awesome! You could have put some lanterns in there though or waited til day time, haha :D
Really glad to see it getting use, it makes it worth working on modding related features.

Sidenote: are those classic-style doors?

 

To continue the discussion from the previous build thread:

This is a video of me, only holding jump. No other keys are being pressed. It's ridiculously infuriating. It's on an Official US CTF, where I have <100 ping.

Spoiler: Video

Link: https://youtu.be/XBxlUkIq3iM

This was probably the only time I've had it happen so consistently (on every jump). I guess my ping at the time was a little bit jumpy (flashing between 33 and 66).

 

I don't think this is related to ping except when you're building. Next time it happens can you check your framerate and net graph please (holes in netgraph hint either bad connection on your end or skipping frames on the server). I've got a feeling this can be a symptom of bad perf on you or the server's side (i'll look into why tomorrow).

 

Sounds like it'd be the server or client hitting some CPU limit in that case? The delta calculations are pretty expensive. I dunno how much overhead syncing the mechanism stuff adds but it's probably not super trivial. I haven't seen "landsharking" on that map myself though, even on a full server :/

Lots of things have changed to work around wily TDM players.

 

It certainly seems like if perf drops below some threshold the physics steps become larger - I've got no idea where that happens because the physics code is a big pile of bandaids :) I'd have to go searching.

Though, if you check out twitter I've also had it at 30fps on localhost when something else is jammed into the terrain, so there might be some global data sharing issue on top of just bigger physics steps.

 

Has uncapped framerate now been capped at your refresh rate? I used to get >100fps but now only get 60fps.

 

That's what vsync does.