Killing floor sdk что это
Animated Trader, fire emmiter, smoke, sound, ammo / weapon spawns and more.
Path Node : Right-click, select path node.
Anything can be used for a door or mover. The only reason I started using money for a trader door was because it was basically door shaped. but with the name GunsForBucks it turned into a kind of signature thing quite by chance.
You select in the:
To set movement positions
Put door in closed position, right-click and select:
Now that you can find the parts, this section will help you put them together. The proper weld door message I just sort of stumbled on by accident, spent a lot of time trying to find a tutorial that had that. For these settings Right-click on it and select Properites.
To make the proper message come up as it does in the game, go to the bottom of the properties and type «USE or WELD» in for the message. You have to capitalize it exactly as shown or it just comes up with white text of what you typed instead of the standard game message.
To add sounds you must first find the sound in the browser and select it, then when you go to the sound tab on the door and hit «use» it will use the sound you have selected for that operation. The sound pitch can then be modified to fit the door movement in the doors settings.
Things that will move when you get close or an automatic elevator etc.
This is not the KFUseTrigger for weldable doors, this one works by proximity.
For helping bots pathing and access, normally needs to be blocked properly to keep players from using, cannot be set for zeds only.
It crashes easily if miss-clicks are made, undo is limited and unstable if you go too far, SAVE OFTEN. Sometimes issues come up that have easy work arounds, I noticed in a comment board thread about an issue that I had figured out but had not put in the guide. That is what this section will be used for.
Loss of view, SDK opens to white page
Your previously selected viewport configuration should be back to normal.
Terrain editor zoomed in:
Go to your KF/System folder and open your User.ini in there.
Search for the [WindowPositions] section and delete it completely, save afterwards.
Load up the SDK and everything should be in place as usually.
Killing floor sdk что это
Hiya, this guide provides tips, but it also serves as a pretty extensive tutorial nowadays.
I HATE KF SDK, I despise it, it’s awful but i’m here because I love KF. If that’s the case for you you’ll learn to despise KF SDK as well.
Ofc, there is at least a certain charm in this SDK because it’s based on UE 2.5 which just breathe’s simplicity.
Sure, the tools may not be intuitive for beginners, but with the help of guides you’ll at least realise they’re not hidden behind a million hotkeys or tabs. Unless you get inventive there’s usually 1 or 2 ways to do something, and that’s that.
Speaking of guides, this one is for making Killing Floor maps. This game is soo dead you’re prob here because you’re REALLY bored, or clicked one of my links to this guide, by mistake?! Meh, well have fun skimming through.
> If you JUST started with KF SDK and you don’t like my Basics section, here’s a video which isn’t terrible for noobs:
> If you’re only interested in SDK but don’t EVEN know how to open it yet, this guide would be better to start with:
https://steamcommunity.com/sharedfiles/filedetails/?id=117622426
Lastly, if you hate my guts feel free to only rely on some of my extensive references listed at the end of the guide. Otherwise let’s get started.
Once you’ve prepared a rough shape of section/s in your map (using cube builders, subtract and odd tools on the left side of your screen). 3 things that should get your attention are little icons near the top of your screen:
The Texture Browser contains almost every surface decoration used in other KF maps. just find the right one for your floor, wall or ceiling and apply it with a double click.
I wont go into depth myself but regarding supported textures, tranparency (alpha), and whatever, reference dis:
https://docs.unrealengine.com/udk/Two/UnrealTexturing.html
Finally, we have the Static Mesh Browser. To sum up, SM (static meshes) are your archived, and hopefully optimised shapes. Doors, tricycles, radioactive mushrooms and dosh for instance.
Alternatively, using stock map folders, you can take almost any SM from a KF map and use it, rescale and re-purpose to decorate your own.
It relies entirely on radical ideas and improvisations but also takes way less time then designing your own anyway so feel free to reference this spreadsheet I put together:
https://docs.google.com/spreadsheets/d/1zW2LIq6_G7Rr4sPQtuJSu5IBzRdkLbyEhBFvm-zutlM/edit?usp=sharing
If you want to help add to the SM spreadsheet feel free to join the Siren Torturers discord and inquire about it there because they helped format it and stuff.
Stock KF map resources look better, and always will be yours for the taking. Just don’t forget to add your own original touches to your map.
Do rely on the games resources as much as possible tho, static meshes and textures form kf maps, If you have those moments when you’re not feeling very creative, it even helps to look at the available static meshes at your disposal, other projects, other maps, other games and whatever is around you as inspiration. Ideas come to me randomly, and I could only properly work with them once I knew how to work with SDK
Don’t forget Search Engines have an infinite supply of reference images too :DD
So, there’s something you need to realise about how KF SDK works:
The build button at the top right of your screen, re-builds the whole map every time you ask it too, following the set of guidelines you give it.
Well Duh. But this includes every brush you’ve ever added or subtracted. Go into wireframe by clicking the hollow cube icon above your 3D viewport and you’ll even observe any old brushes you may have ‘added’ over.
So to sum up, you can use a «brush» that applies an effect and continues to persist even after you add or remove space with more brushes. Like a skeleton of sorts. Not to mention how the editor builds them in the order you applied the brushes. Now onto the juicy parts!
UE light-ray tracing is pretty bad (more like Realllllly bad) but if build lighting ends up compressing one of your lights way too much, just add more xD. I’ve seen other mappers stack multiple lights directly on top of each other, even with different colours. And official maps tend to spread multiple tiny light sources out to highlight certain spots and add to the atmosphere.
You may notice properties for effects like torchflicker or phase but don’t touch them; they shouldn’t really exist.
Where you’ll find em: somewhere in actor class browser xd
—————————————————————————————————
In KFO-Foundry they use scripted triggers to activate/spawn a headlight corona Actor based on an Event usually triggered after the bonus objective is satisfied.
Learn how to do that and your imagination is the only limit from there. 😛
I kinda wanna recreate the stereotypical parking lot one day, flip a switch and all the lights turn on with loud sound effects in a desolate room, row by row. But I guess the shadows would be ♥♥♥♥♥.
—————————————————————————————————
So, bumping against meshes or invisible walls that prevents players from breaking your map, and jumping out of bounds. This can be a minor thing to worry about. But it’s also essential to a player’s in-game experience so don’t be fooled into ignoring it.
But, what if you want to block off an area to players but not zeds? What if the collision on a static mesh just doesn’t cut it? We can’t just have people going where-ever they want. Specimen pathfinding in KF1 is already bad enough without players jumping across rooftops or wandering into their spawn points! So this is when you want collision volumes.
It’s important to recognise where you use these. Usually you should place a static mesh or platform of some kind to seemingly ‘block’ off the player. But extend NonZero Collision much higher up then someone can be expected to jump.
Otherwise i’d walk up to a perfectly normal piece of ground and hit an invisible wall, get frustrated, cornered by zeds and killed. Don’t. Break. Immersion.
So without further ado:
Yup, those are what you want. If you’re familiar with the cube, cylinder builders and brushes then all you need is to mould the shape of collision you want, and instead of hitting subtract, look further down for a transulcent blue cube tool and Rick it.
This should bring up plenty of options but for this section so i’ll just highlight these two:
If you want an example of how you shouldn’t misuse these volumes if you can avoid it, Check out KF-Stronghold in SDK.
Whereas not using them enough generally turns into something like this:
When adding terrain to a map first thing you want to do is follow this here URL:
https://docs.unrealengine.com/udk/Two/CreatingTerrain.html
It’s explained in that URL that you should leave properties of the new layer as default but one thing that KF REALLY loves to do is set «U scale» and «V scale» to 0 by default when you make the new layer
^This is the scale of your repeating texture applied to terrain so it should absolutely NOT be set to 0. Otherwise your terrain will work but it will appear invisible D:
If you follow that advice your terrain will work and appear in the map. Now you can start playing with the terrain tools explained here:
https://docs.unrealengine.com/udk/Two/EditingTerrainMaps.html
^
Additional Notes
I usually use paint brush (followed by smoothing) because it’s easiest to use, set strength to a little under 50, ctrl + m1 to paint mountains/hills, ctrl + m2 to carve into the terrain and create valleys.
This is when you should be practicing with terrain shapes and My God I hate it, it’s always laggy for me when I use it 🙁
And finally! After you’re happy with your terrain shape, you can apply different texture layers that blend into each other by looking at this link:
https://docs.unrealengine.com/udk/Two/EditingTerrainLayers.html
As you can see I rely on UDK Two Site Map a lot, because it’s usually accurate to KF SDK.
When getting terrain to work your TerrainZone setting in Zone Info actor should always be set to True like this:
If your terrain is built, you’ve followed those previous steps, and it still remains invisible. Go into your terrain tool, select your layer under the layers tab, select ‘paint’, and paint the texture of your layer onto the terrain with ctrl + m1
I’ll keep this section brief, using the actor browser, you can select an assortment of triggers to use. Just bear in mind that not all of them will necessarily work in every possible way. Some may even be obsolete! Experiment with 1 at a time, for different purposes.
Now that that’s over, triggers are blatantly simple, go into actor class browser > trigger. And you’ll find an assortment. I like things simple, so the ones I’ve stuck too (and coincidentally most KF mappers have used) so far are:
actor class browser > trigger > trigger > KFProxyTrigger
actor class browser > trigger > Use Trigger > KFUseTrigger
Usage:
① Place it where convenient, if it’s a KFUseTrigger, I place them centrally in the door and a ProxyTrigger would be on or next to something important in your level.
② Go into properties > Events, name the event of the trigger something simple and explanatory that you won’t repeat (‘Door1A’ for example).
③ Make your trigger actually do something by giving your lucky chosen actor or mover a Tag of the same name (‘Door1A’).
④ You’re done. This can be used to play sound effects, activate a scripted trigger, complete/activate objectives and it even works for movers with the corresponding Tag.
Side Note: plenty of actors like movers can trigger events as they do their thing (look into sections of their properties), if I went into all of them it would be a pretty extensive and boring guide but just understand they work the same way. The trick is using them to link to different tags and cause «events» in a variety of different ways.
e.g. a given alarm sound effect event, triggered by a door opening.
SideSideNote: If there was a third trigger I’d like to learn how to use someday it would be the shoot trigger. It does work (KFO-RE-Mansion and KFO-WestLondon use one) but it looks finnicky so good luck.
Add some commands into a chain of ‘actions’ to get ST’s to interact or do anything you want around players mid-game. I’ll outline the important commands you can practice with:
Once you’re really confident with using ST’s you can check out my KFO-BossArenaNerf map and see if you understand everything going on there, (I gotta advertise my own stuffs at some point) lol.
See if you can notice some aspects where I ♥♥♥♥♥♥ up as well, I could fix it but that would require effort so. xD.
First, highlight the mesh you want in the mesh browser, then click a tool below subtract, which appears blue and rectangular with 4 arrows sticking out as shown in this Really Intimidating link.
(Oh and if you Rick, you get to choose between advanced mover types).
Great, now SDK has inserted a perfectly normal looking mesh somewhere in the middle of where you last left your red, active brush.
Well, Rick in the corners, the central parts of corridors and insert path node. Done, ez, gg.
And of course, sometimes, such as in the case of my KFO-BossArenaNerf map, you might feel that even though zeds fall off platforms occasionally, and you’ve done your best to give them a clear route. Bad KF pathing can make a map fun. Who doesn’t want to see a menacing Patriarch charge at you, only to fall off a plank mere inches from your face?
If you’re here because your imagination sucks I pity you, there’s no helping you, clear off.
Aww jk
level design is an art. If you think your map naturally looks like trash don’t despair. It’s a learning process. And, mine always look like trash because I haven’t released anything to a wide public audience, I don’t get enough feedback! But I hope the feeling will fade with time lol.
What’s the point in making maps if you can’t have a little FUN. Easter eggs are a great way to encourage players to look around and appreciate the decorations in your map.
For instance take KF-SawnOfTheDead:
It plays on everyone’s mutual hate of sirens and does so using stock decorations provided to pretty much everyone. So no extra downloads required, nothing eccentric or complicated, and it should all be optimised 😀
If you’re reading this you’re insane, and you should know you’re in for a world of pain. I’ll try ease your suffering:
Tip:
Objective Mode is a series of triggers and events that you set up yourself, just like story mode, but a wee bit more flexible and with a FuNkY agro system. So plan what you want to do, then figure out how to get it to work. Which actor is the cause of an event, when to trigger it, what does the trigger do?
https://imgur.com/deoKkg8
^
The mother of KFO. Say Hello to the KFStoryObjective actor, you may hate it some days but it’s your friend. In its properties the 3 most important headers are Objective_Actions, Objective_Conditions and Objective_Events.
I need to test this myself but I think setting progress importance: critical, on an objective condition makes it so if that critical condition is satisfied at any point, the map moves on to the next objective.
It’s also worth noting that a team wipe is always a wipe, it’s built in, end of. You don’t need to add it to failure conditions so alternate routes for your objectives is possible.
I’ve never ever done this myself so please ignore me if you have someone else more qualified to ask. But If anyone came here interested in porting maps I recently discovered that UE includes a polygon limit when importing maps lol
65535 of them to be exact. So at the very least all the BSP in your map shouldn’t exceed that.
And ofc you can check out this TWI forum post: [forums.tripwireinteractive.com]
The process of porting games can vary a lot depending what game it is and what engine it supports. Preferably games that have a Modding kit supported like an SDK, hammer, etc.
In a short summary, for Dungeon Defenders, I grab all the assets related to the map I want to work with in DD’s DDDK and move them into a custom new package. Moving assets instead of copying will auto assign MATs directory references to the new package. Just do NOT save the package changes from the games default upk packages. In this case, Dungeon Defenders is built off of a older version of UDK (UE3). So it does make things a bit easier in terms of grabbing similar MATs/Textures/upk’s, but not much different in terms of procedures and porting. Make sure you categorize everything you’re grabbing, because you’ll lose progress real quick if you do not.
Now, since KF2 is built off of a newer and heavily modified version of UE3, it would be simple to just grab the packages and just load them into KF2 right? Well, if it were only that easily, but sadly it’s not. KF2 SDK will crash with a crap ton of errors because of many possibly issues. Some of these issues include UPK version structure, Old mesh renders, bad MAT structure, Custom Assets specified to game only, ParticleFX Crashes due to custom FX, and many more issues I can’t remember off the top of my head. Also, DD’s DDDK is very unstable as of the build you get from it now. How does one get around these issues? The methods I came up with are a lot to explain, but the most common reason for a crash is an old mesh render. This involves you having to extract the upk file raw and gathering the pskx file. Grab that, and import it to a 3D program like 3DS Max with ActorX plugin. Export it as FBX file type with version 2014/2015 for KF2 SDK (VERY IMPORTANT) or it will crash. If you would like to know more of these methods, just message me or I might just post here accordingly XD. I might make a tutorial some day in the future maybe (Ideas!).
But yeah, once you have all the stuff you want into a package, then you can start building your map slowly. Export from DD’s DDDK selected meshes into a t3d file for it to auto place for you the exact mesh placement in the world and import with KF2 SDK. If it crashes, it’s one of the meshes most likely. This is why I do several meshes at a time instead of just getting ALL meshes in the world. And you’ll just simply crash the SDK due to too much memory allocation. Once you placed all the meshes from DDDK, then you proceed to build the rest of the required assets like Lighting, Pathing, Volumes, etc. Porting is by no means easy. Takes a ton of patience and determination, but it’s rewarding in the end!
Walltext! 😀
To summarise this dude is telling you need 3DS Max or a similar crappy alternative (like Milkshape). [www.milkshape3d.com]
It requires converting meshes to different file types (.FBX for KF2), and due to memory limits and possible conversion errors, it should be done in little groups of meshes as opposed to all of them in one batch.
Then you need to rebuild the map with your resources, and cross-reference it, possibly import the old textures too, etc.
What you choose to do with this info is up to you. 😛
If you still have questions related specifically with porting to KF2, feel free to nag someone on this discord: https://discord.gg/rzNpaD3
I won’t testify to how alive it is (by your time of reading) but it’s a group of KF2 modders who exist to provide help and some of them do have experience porting a lot of maps so that could work for you. gl hf
Testing is Hella Important, if you release a map you haven’t tested, it’s garbage. 100%
If testing in game is 50% better then testing via SDK, then server testing (in private servers ideally) would be 300% better. Should you know how to set up a local dedicated server, go for that. Learn how port forwarding works, whatever. If you have friends, nag them and test together! They’ll grow to hate you. Muahahaha.
Feel free to comment if you have any more relevant errors or bugs to report, or rate me nicely if you like my style.
//ProTip//: The description during upload has a character limit, but if you edit description in steam workshop, post-upload, you won’t be restricted to nearly the same degree, and can format your upload in FancY ways like a CooL Kid.
If you tick every tag when uploading something simple to the workshop, you definitely Stink. Tags are there to make the workshop easier to navigate. But for KF they’re essentially pointless now. There’s no-one to moderate lying tags so everyone stinks, no-one can be bothered looking at the workshop, and meh, it definitely won’t help your workshop views in the long run.
It does help me but I would also hate to think the effort in this guide went mostly to waste given the late release, in a dwindling community. So do feel free to check on it whenever you want and give any support or constructive feedback in the comments section.
So why are you still here? Weirdo
Well I may as well give one more link, here’s a video of a KF Speedmapper?, in a timelapse:
See if you can spot out some of the features you may have learned in your time, or how you can simplify and improve on some of his building methods.
It’s a great example of what you could do during the pre-building (planning) stage so that your map doesn’t end of looking like total crap, although my plans are usually just scribbles. Catch you later 😀
That’s all of my references excusing steam guides lol. Have fun!
