Launch Editor, open Edit->Project Settings window.
Go to Engine->Collision->Preset section.
Add a new custom collision profile or edit a previously added custom profile and change ObjectType and Collision Responses from their default values. e.g.
Press Accept button to close Add/Edit Profile dialog.
Press Set As Default button to save changes to DefaultEngine.ini, if you check .ini you’ll see your changes have indeed been saved.
Select custom profile you just created or edited and press Edit button, note that your previous changes to ObjectType and Collision Responses have been discarded. e.g.
I can confirm that this has been fixed in our internal build, and will likely be working as expected in 4.3. I do not have a confirmed date for 4.3 yet, but it should be coming very soon.
As of 4.3 preview; settings do persist. How ever they only ever write to user Engine.ini file. project settings window states that settings will be saved into defaults that is currently incorrect. save to default button is greyed out so you can’t set it yourself. I had to copy and paste them into defaults in order to get change into our depot.
This needs just a little more of that elbow grease.
Thanks for update. Currently, settings are being saved to Project in \Saved\Config\Windows\Engine.ini. This is default for that project, and it is set automatically (no need to Set as Default). If you need these Object Channels, Trace Channels, and Presets transferred to another project, you should be able to Export them and Import them into other project without any problems.
We don’t have any settings that transfer between projects, though you can set defaults way you mentioned if you need to create many projects with same settings, by copying them into actual engine defaults rather than Project defaults. I don’t believe Set as Default button is actually doing anything at moment, though I’m looking into that now.
This particular issue seems to permeate everything in project settings that are under a section that has “These settings are always saved in default configuration file, which is currently writeable”.
Input mapping changes do not seem to go into Config\DefaultInput.ini either.
Unless we’re supposed to be checking in \Saved\Config dir?
This issue is in both 4.2.1 and 4.3.0-preview on windows
Sorry for delay in response. What that post suggests is that putting Saved\Config in your depot would change all personal settings for everyone, and anytime anybody made a change and checked it in, it would change it for everyone. For now, copying and pasting into defaults might be your best solution.
It does seem odd that collision channels and other settings like that would be considered personal settings. I’m going to look into this a bit further and, if we’re not missing anything, put in a feature request for developers. Thanks for your patience!
