Toggle Visibility for component is broken.

Development Rendering
, , , ,
1

Here is the BP section

http://puu.sh/nWcSh/cc7e7f5b1d.jpg

Result using toggle (breakpoint after the function):

http://puu.sh/nWdvm/423549bb6a.jpg

Result using Set Visibility:

http://puu.sh/nWdBm/2a6536deb1.jpg

Not a big deal really, just figured might as well report it. I was goofing around with some random stuff anyway :smiley:
I haven’t tried it for any other mesh, and to be honest it seemed to work just fine pre 10.4. And I just could have some weird one-off super obscure problem that makes this happen.

2

Hi ,

Unfortunately I have not been able to reproduce this on my end. Toggle visibility seems to be acting as I’d expect.

  • Does this occur in a clean, blank project with no additional content or is it limited to one project?
  • Is this limited to one type of actor?
  • What steps can I take to reproduce this on my end?
3

I’m unable to reproduce it myself on a blank project. I did some testing, on different actors, everything seems to work fine.

I suspect this has to do with the death logic I have set up for the actor. On Destroy I remove the visibility. It used to work with Toggle just fine, then I added a particle (default sparks from the engine) component to the Ball and attached a collider in order to get events from it. Since then Toggle didn’t work.

I suspect it’s some weird isolated case and don’t think it will happen to anyone else. I reported this in case you guys get some other similar reports and needed an extra scenario.

In the end it might just be that I’m blind and have a problem with the BP logic somewhere, but it did seem strange that it works fine with Set Visibility and not with Toggle.

Sorry for wasting your time man, that’s as much info as I can give you, I really don’t know how this happened. Should I delete the report?

4

Hi ,

It isn’t a problem at all. I’d certainly rather a report be here so that if other individuals are experiencing the same error, we can try to track down a potential bug. I’ll mark this as answered for now for tracking purposes. If you find the error and steps to recreate it, post here and I’ll be happy to take another look!