AWS Thinkbox Discussion Forums

Force Redraw

Deprecated Frost MX 1.0 Beta Bug Reports
#1

Ver 1.1.1 still, so apologies if this has been addressed, but when unchecking “Enable in Viewport” the mesh disappears instantly (good), but when I recheck it, I’m required to force an update, or tick the timeslider once to redraw. Can you throw a force redraw on that check enabled?

#2

I have seen this recently, it still happens in the current version.

#3

Thank you for your report!

Do you have Viewport Update “When Frost Changes” off?

Do you notice this when you are using some particular particle source, for example, when loading particle files directly using Frost?

#4

“When Frost Changes” is enabled. Currently I’m experiencing it using a PRT Loader.

#5

I will have to check when I get home, it was late last night, I only had a “huh” moment. I can’t recall the setting.

#6

Also Paul, is it a feature that “Enable in Viewport” is animateable? I accidently create a key for it and was scratching my head why my mesh was disappearing halfway through the animation. I know it was my idiocy, but didn’t expect that it could be animated.

#7

No, that is not intended :open_mouth: Thank you for mentioning it.

I was unable to reproduce this issue. If you have a scene file in which this happens consistently, could you please send it to us? You can send us files using our ticket system.

#8

I found the source of the redraw failure. I have a feeling this will be taken care of as a biproduct of you removing the enableViewportMesh from being animateable, but these are the steps right now to repro

  1. Create a Box; Create Frost. Add Box as Frost source.
  2. Toggle Enable in Viewport. This turns on and off as expected.
  3. Open track view, assign a Boolean control to the Frost.enableViewportMesh track.
  4. Toggle Enable in Viewport. The frost mesh hides correctly, but will not display back on until forced by a other methods.

I was seeing this because as I mentioned, I accidently had animated the control, which automatically assigned the boolean control. And even after deleting the keys, the controller remained causing this failure.

#9

Thank you! I should have realized those were related.

#10

I about forgot.

Sorry for the detour, it happended when I repathed a PRT loader.

It was my bad, I did not have “when particles change” enabled

#11

Thank you for the follow-up!

I intend to make those parameters non-animatable, but I don’t think we will have a chance to fix this before the next release.

Privacy | Site terms | Cookie preferences