Description

Title:	Flex Settings - "Save, Load, Reset"
Category:	Workflow
Status:	Considered
Priority:
Posted By:	michaelwbell ( Michael Wentworth-Bell )
Date Created:	16 December 2015
Description:	This is another low priority request. I think users would love the ability to have preset management in the flex settings. Options at the bottom of the modifier panel to 'save', 'load' and even 'reset' the settings. If a user wants to simulate a fluid they need to tweak the particle radius, substeps, fluid rest, etc to get the settings for the particular scene scale they may be working with. if they could instead simply load their favourite fluid preset, they'd save a lot of time. Also, I find that as a new user to Lucid, I am tweaking the Flex settings and reach a point where the simulation looks quite terrible, and i'm not sure exactly why. I have to open another instance of Max in order to fill out the default 'flex settings' and the simulation works again. For this reason, it would be great to have a 'reset' option to reset the settings to their defaults.

Follow Ups

4 January 2016 #7396
michaelwbell	Hi Marsel, Will this make the Lucid 1.0 release? Now that there are even more simulation settings exposed under the Flex settings object, it would be great to be able to save/load/reset the settings for different scenarios. Michael Wentworth-Bell -- Test system for Lucid: i7-4790k GTX 780 6GB 32GB Ram Windows 7 Pro 3ds Max 2016 EXT2 -- Portfolio - http://thelode.com.au Facebook - https://www.facebook.com/DigitalLode
4 January 2016 #7398
EPHERE	Indeed, I am still thinking on how to handle this best. On the "already possible" end of the spectrum you can save out the Flex settings object by itself into a separate scene and then merge it into another scene to preserve the settings. Maybe this can be automated to make it more user-friendly. Another approach which can be tried is actually creating/saving some preset file in a text/xml format. This would likely be more involved. Marsel Khadiyev (Software Developer, EPHERE Inc.)
4 January 2016 #7399
michaelwbell	Oh coool! That's great, thanks for pointing that out - the save selected/merge option is very handy. I definitely think the text/xml would be the way to go. -Don't have to worry about .max version numbers (2016 "flex settings" not opening in 2013, etc) -Dont' have to worry about other junk/settings that would be saved/merged into a scene (Layers, etc) -Easy to share presets with the community -Easy for people to edit the presets in a text editor I've tested out the merge option and it is a fine workaround for now. I see issues when having - for example - 1< flex settings objects in the scene. In this case the user has merged in the Flex Settings and clicked 'Auto rename". Now there's multiple flex settings objects. The user can click the "Show Lucid Flex Settings" button on the Lucid toolbar to identify which settings are being used (i'm assuming), and they can delete the ones they do not want. Overall though, it is messy. But again, a good workaround if it's not possible to have xml presets in version 1. Michael Wentworth-Bell -- Test system for Lucid: i7-4790k GTX 780 6GB 32GB Ram Windows 7 Pro 3ds Max 2016 EXT2 -- Portfolio - http://thelode.com.au Facebook - https://www.facebook.com/DigitalLode
5 January 2016 #7401
EPHERE	Glad to hear that it is working for now as a workaround. There should be only one Flex settings object, at least only one will be picked up by Lucid. I want to find if we can reuse some of the preset code from Ornatrix for the XML based preset solution, though it might have to wait for a 1.x release. Marsel Khadiyev (Software Developer, EPHERE Inc.)