Empires on UE4 (A collaborative project)

Okay, SVN is up.

http://kylegar.net/svn/empires2editor/

You need a username/password to contribute to this. Send me a PM to request one.

 

I had a question, are you going to create a map editor when the game is released?

For people who don't or can't spend the money for UE4?

 

I don't know yet. Right now, I have no choice but to force you guys to pay for a license. If I release a game, I might be able to discuss something with Epic to release a copy of the Editor with some features removed, but honestly I have no fucking clue if that will ever happen.

 

Using SVN in the editor

First, click this button



Second: Select "Subversion"



URL is http://kylegar.net/svn/empires2editor/

Username is whatever username you gave me.

Tags is "tags"

Password is whatever password you gave me.

When you are editing an asset, Right click on it, Check-out that asset.

IMPORTANT SUPER IMPORTANT When you save the asset, Make damn fucking sure you right click on it and check it back in. If you are editing multiple assets, go to File->Submit to Source Control to group check in assets.

If you forget, none of us can edit the file until you check it in. This is why it's important.

 

I wont stop you.

 

Shouldn't you be able to find that in the terms of use of either Unreal or the stuff you are buying? If not, ask the creator.

 

I just had a problem with the built in Subversion, but my solution might save you some headache. It seems that the internal SVN isn't that good in syncing up folders. So you might have to submit folders manually with Tortoise SVN. I also encountered that problem with moving/deleting files. Just keep that in mind.

 

Yeah. I can't sync the binaries from inside the editor either.

 

I figured out how to do console vars!

This was like 3 weeks of casual searching on how to do this. There is literally 0 documentation on this shit and it's hidden away in the Hardware abstraction layer.

 

I'm adding Muzzleflashes. Right now it's using an explosion particle effect (which is fucking hilarious) but I discovered that remote clients don't play fire effects, so I gotta figure that out.

 

So, I redid the way weapons attach to the character, that way we don't need to create custom hands for every model.



Lookin pretty sexy, if I do say so myself.

Ingame, however, since the pistol isn't a skeletal mesh (and the FP model doesn't have the gun removed), it's kinda broken. You walk around with a gun on top of your head that explodes every time you shoot. It's pretty funny. I'll fix it tomorrow when firewarrior gets on and can poke at his export settings.

 

btw, this happened while progressing to the above picture:



The explosion muzzle flash came out of his crotch area. It was pretty funny.

 

That has nothing to do with my export settings. The bones are simply not there yet. (At least for the pistol, the ones for the first person arms where missing on import entirely) You still need to tell me where the gun attaches now. (the bone name I imagine)

That's a really good candidate for documentation as it affects 2 different people/teams and I don't want to have to ask you about every single detail in it.

 

The root bone of the pistol attaches to the socket defined in the 3rd/1st person model. The socket is set up in the editor (parented to a bone, just a flat offset position/rotation from the given bone) by right clicking on the bone and selecting 'Create new socket here'. There is a field in the weapon (called 'Weapon Attach Socket') that you can type in the name of the socket you gave it. This will let us set up multiple different sockets if we need them.

I have it set up right now, so you can take a look how I did it. I created a socket named "WeaponAttach" parented to the Right Hand ("r_hand" iirc). Also, you should check out the project before we get around to fixing it. Nothing like a mystical floating set of arms pointing the wrong direction exploding every time you fire. Today was a pretty hilarious day.

 

Heh neat. That's a lot easier to do than the bone merging in Source. I kinda guessed that's what sockets are for, but have not tried it out yet. That should also let me easily implement weapon attachments.

 

I am extremely tempted to advise you go the Goat Simulator route with this thing and just leave in anything that doesn't crash the game.

 

I lost it.