UEGitPlugin VS PBCharacterMovement

Git LFS does have a concept of locks which is supported by the UE git plugin with the caveat that the one bundled in the engine is somewhat older (so you would need to grab v2 of the plugin this way).

I'm a solo dev. This past summer I took a little time and set up a small Gitea server on a Raspberry Pi with a 1tb USB SSD, partially to see if I could but also to get some kind of version control up, as I didn't really want to pay for it if I didn't need to. It mostly works fantastically. This required the use of this UE4Git plugin.

Let me make the case that it's definitely not just nostalgia - or, at least, that Quake style movement didn't fade away because of any objective, rational process.

One of the exasperating consequences of the rise of game engines has been that you have games shipping that have more and more of their game design inherited from their game engines.

On some level this makes sense - games are just massively complicated, and so if you already have working, tested code, it's often quite tempting to just go with what already works (and not spend time really internalizing how working things work) and then focus on figuring out the particular things you are adding from that baseline.

As just such an example, when I was working on Activision's Soldier of Fortune, we largely inherited Quake 2's movement code, and most of it was left untouched by the time we shipped. At some point, midway through development, inspired by Thief, I stayed late one night with a co-worker, and I added in leaning around corners to the player controls. I don't remember the particulars of that process, but (obviously) I had to make tons of aesthetic choices while doing that, because I was writing it from scratch. But the base movement we could inherit.

If you go back and look at first person games from the late 90's, their aesthetic choices about basic player movement are all different in subtle ways. That makes sense, because most studios were writing their own bespoke engines at the time, and there was vastly less code sharing. So people were writing code because there was no particular alternative, and so they were making tons and tons of aesthetics choices whether they wanted to or not. Lots of those choices weren't always great, but they were often particular.

It's clear at this point that lots and lots of FPS games just inherit Unreal Engines movement. Not because it's great, but because it comes with Unreal and it's a default. To me, there's something very specific about the way friction works with player movement in Unreal that feels very ... sticky? ... compared to Quake Engine games. Players come to a stop when input is released in a way that feels like being in glue - again, at least to me. There's more subtle gliding around in Quake. As far as I can tell, the difference rarely effects game play in most games. But it does change how it feels aesthetically to play moment by moment.

Anyway, this topic feels intensely path dependent to me. Unreal's movement is the default because Unreal is the default engine (in a lot of contexts), but it didn't become the default because of anything specific about its player movement code. Those aesthetic decisions were just along for the ride, so to speak. Or at least, that's my sense.

Interestingly, I found a github project a while ago that tried to reverse engineer Quake / Source's movement and put it into Unreal Engine 4. No idea how successful the project is, but I suspect it might be an interesting resource for seeing what's different between the two: https://github.com/ProjectBorealis/PBCharacterMovement

I've never come across surfing in anything but Source engine games. There is however an open-source recreation of the Source movement system which allows for surfing, it's available here: https://github.com/ProjectBorealis/PBCharacterMovement

it should be possible, given the Project Borealis folk ported HL2 movement to Unreal (https://github.com/ProjectBorealis/PBCharacterMovement), but it definitely isn't easy (and not present in TSPUD), i'll give you that

For instance my custom movement component is based off of this one https://github.com/ProjectBorealis/PBCharacterMovement which allows for automatic bunnyhopping, better air control, surfing and sliding along the ground. The drawback is that it wasn’t built with multiplayer in mind and stutters when you try to walk when simulating poor network conditions.

Judging by the issue thread re: 4.26 support, the devs are pretty open to PRs that extend support.

hi, i have just started helping a friend with his project. i wanted to use project borealis' movement plugin (github link), which isn't compiled for the version we are using, 4.27. recompiling it via the prompt that pops up when opening the project did not work, and trying to recompile it via RunUAT.bat led to a lot of errors shown below

There are a few projects that have open source modules that implement various systems (https://github.com/alanedwardes/Estranged.Core, https://github.com/ProjectBorealis/PBCharacterMovement/, https://github.com/sinbad/SPUD) that you could use to get an idea re: how people organize their stuff.

(Source code: https://github.com/ProjectBorealis/PBCharacterMovement)