ACAD LT 2023 Visibility not updated after making changes to dynamic block

[humdec]

This looks like a bug in ACAD LT 2023 with blocks with multiple visibility states. After making changes to one of the visibility states and closing the dynamic block, the changes won't update. This varies from new items put in the block, or moved, stretched, rotated existing ones, etc. 
For example, a new window block is placed on Visibility State A. When closing the block editor, and setting the block Visibility State to "A" the new window won't show. In some cases a window from other state will be visible. Reopening the and reselecting items to be OFF or ON won't help. What helps in many cases is copying the new window to the side, then moving the previews window somewhere else randomly. Then closing the block will show the previous window in the right place, but not the new one. The new one is off. Reopening the block in block editor, deleting the first window and moving the second one to its right place finally does the trick. However this happens a lot and it is silly and time consuming to be fixing every item that way, to the point that we are considering not to use Visibility States any more.

Is there a fix for this?

[ntclmain]

Did you try the command: BATTMAN, choose your block then click SYNC ?

*
By the way, the question seems not relate to .NET customization

[humdec]

BATTMAN is for attributes only.

and oops, I didn't even notice I was in the wrong forum

[ntclmain]

BATTMAN\SYNC can "repair" some problems with attributes position in Dynamic block
*

Anyway, if BATTMAN \SYNC does not work in your case, then the last command I can think about is RESETBLOCK

[pendean]

Your block in a container file would help others help you too... .

[humdec]

We have no attributes in the blocks.

RESETBLOCK does help, thanks! However, after doing that, and changing the block visibility state to a state that has similar problems, we have to do RESET it again. Then going back to the original state that was already RESET, shows incorrectly, having us to do RESET again on a state that was already RESET. And this is random, sometimes going back the problem will not recur, sometimes it will. I am attaching one of the blocks.

[humdec]

here is one of the blocks

[architecturalgroupiiihd]

UPDATE.- Resetblock command is not helping anymore, when used, it set the block to its first visibility state. Then the problem reoccurs. After not seeing more replies, I guess this is officially a bug in the product. We are no longer using visibility states in dynamic blocks, nor can recommend it at this point.

[pendean]

---

@architecturalgroupiiihd wrote:

UPDATE.- Resetblock command is not helping anymore, when used, it set the block to its first visibility state. Then the problem reoccurs. After not seeing more replies, I guess this is officially a bug in the product. We are no longer using visibility states in dynamic blocks, nor can recommend it at this point.

---

Open a support case with Autodesk if you are on subscription to seek out Autodesk Support's help: https://knowledge.autodesk.com/customer-service/account-management/users-software/support-options/we...

[dmahoneyHALT6]

I know this is  2 years old at this point, but I ran into this issue today and found a way to fix it.  I just needed to go into block editor and move the visibility up and then down again, closing out of visibility states each time I moved one.  Then closed out of block editor with changes.  This seemed to trigger a reset in the visibility states and allowed it to function properly again.