👍🏻

Thank you Cleetus, yes the only issue seems to be the json file limit when saving.

You can assign a single vertex a selection name and animate it for all axis. Instead of setting the position via script, you would translate the target position to a local animation value for the axis. You would need to name all the vertices you want to move anyway in order to know which is which in script. So the step from doing that to just giving it animations is quite small.

I don't think, because you're talking about the fact that we can do an animation with this ticket? If that's the case, we always stay limited, some vertices need to be in specific places calculated on the moment T, and the fact of creating animations prevents you from having precise things because it's pre-defined. (Correct me if I'm wrong, and you weren't thinking about that)

Can't you just use model.cfg animations for this?

Fixed in an offline environment in 1.05 Experimental.

Sorry to come back here again, but in 1.05 this actually hide correctly fire geometry component, but not hiding geometry component.

yeah after testing a bunch, it's only an issue when writing to a file beyond 64kb in length. Following the code, it seems that the limit may actually be in the way that it takes the data into a single string.

I also noticed that the ItemPreviewWidget behaves the same, you can see in the above screenshot

A multimap is not a solution to this issue, @Jacob_Mango. I don't need an array of values to one key, and the way the multimap serializes is absolute cancer without making them into a template class. Also, there is still a 64kb limit on JsonSerializer stuff, so yeah....

Try multiMap 3_Game\DayZ\tools\tools.c

Having the exact same issue in 1.04 stable

@Geez Any chance for this, or can it be closed? Thank you for taking a look.

Fixed in 1.04.(something)

That's actually should be done, if I want to add a new option into the game, I need to mod the EDayZProfilesOptions enum, instead, overwriting where it's used.