Pretty much self explanatory. I found this out while trying to change a ParticleEmitter’s LightEmission from 0 to 1.
Can you give more info than that? I’m changing tons of properties atm and this hasn’t happened for me.
https://i.gyazo.com/8d161fc0ffb996fdcb80f623fbbd1b1d.mp4
Absolutely unacceptable…
I think it’s only happening with certain properties like TextStrokeTransprency.
Yeah so far it’s only float properties that crash for me
Same problem here. I was trying out the new water properties and it crashed whenever I tried editing a float property.
Just checked and it does seem to only happen with floats.
LMAO wtf… How does stuff like even happen? This is ridiculously unacceptable…
I think it has to do with the implementation of the new Transparency sliding bar
(as shown here x.com)
I can’t reproduce this for any float property, what kind of values are you submitting to which properties?
EDIT: ah, wait, I’ve had Studio open for hours, probably missing a version.
Studio didn’t update in the past couple of hours / days. It must have been a flag that was switched on.
1 Like
This should be fixed shortly.
4 Likes
Good thing 
I think this new slider is the reason. On the values I DON’T crash on, I get this:
Btw, if any of you Studio modders want that slider on other properties (i.e. Camera’s FieldOfView edit: won’t work on FoV – maybe the properties which can use the slider are hardcoded into the executable), you can go into your reflectionmetadata.xml and add
<double name="UIMinimum">0</double>
<double name="UIMaximum">1</double>inside the Properties tag alongside Name/summary. Ctrl+F UIMinimum/Maximum if you need to see an example. Modify the UIMinimum and UIMaximum values to constrain the slider. The opposite is also true – if you don’t like the slider for certain properties (or all of them), you can remove it in reflectiondata.xml and you won’t get it for the properties you removed it from.
This topic was automatically closed 14 days after the last reply. New replies are no longer allowed.