Dont really post much of project anywhere right now, I am hoping that soon I will be able to get a official forum post made once I have more content and mechanics in place as I will need to find people to help me test the multiplayer aspects as well.
but the past week as has been taking an old gun building system and totally revamping it so it more strait forward and can be used in a multiplayer game.
So for now the guns do randomizing and I only have the two different rifle classes in right now i get some more parts molded out for testing. The nest set will be needing to save and load the player weapon builds. Everything is still in temporary stage and will be replaced in the future.
=eP3j3MU9XP0
That answers one of the two questions I was going to have when I saw , my other question was are you going to make materiel react to on hit locations and have the effect ripple from there?
Probably not, at least not right now. I made for a friend to have as a prototype shield material, only spent a half hour or so on it from start to finish.
@albrechtmaler
OMG! I am watching only now and I am completely amazed, always loved castles and seeing made my jaw drop! Nice work
Are you planning to model all the interiors and “paint” them? I am really curious to know how you are going to work with those.
May I ask out of curiosity how much time did you put into project? Well I assure you it’s worth it!
Last but not least, given the results, what do you mean with
? Did you baked AO in Blender perhaps or is it something else entirely?
Thank you for showing us project! looking forward to hearing more about it
Hey guys, wanted to showcase a small teaser of my project I’m working on with one more person.
It’s still in alpha stage but we are doing pretty well thanks to Unreal Engine.
It’s not much but we always wanted to showcase something on forum after seeing so much of your amazing work.
Or really, I’ve been working on implementing a data-driven 1st & 3rd-person shooter weapon system. The general idea is that weapon logic, replication, etc. exists on the code side, and then there’s only a single blueprint for setting up defaults. Weapon data is built using datatables and CSV and loaded as needed, including doing things like loading the correct models, selecting animations, and scaling those animations based on the data. The goal is to allow a large number of weapons to be created without having to modify code or create blueprints for each one.
The below video shows working with the first two weapons in that spreadsheet pic, along with some camera transitioning stuff that I’ve also been working on.
?v=2C7KVBryxKI
I’ve also packaged a small project (~160 MB download) that includes a quick and dirty (and ugly) UI that allows weapon modification on the fly, if anyone wants to check out what I have so far. It’s using free assets from Epic, so please forgive any animations quirks and most weapons looking similar. Also, the UI part is a more limited version of what the spreadsheet-driven weapons currently support (mainly because I didn’t want to spend too much time on the UI), so I included a couple weapons on the character by default.
