Blocks in Model seem to disappear when zooming in or out

Hey there,

since a few days i'm using MATLAB 2012b (previously 2007b). I've updated all the models via the slupdate function and my models work fine! (Results are as they should be)

Only thing is, whenever i start to zoom in or out of the model it seems that the blocks within the model disappear. Knowing where the different blocks or subsystems are i can even open them by double klicking (and actually see the content of the subsystem) and return back to the previous level with esc and see an "empty" model. This might happen at a zoom level of 120% then zooming in i can see the model again, zooming out and it happens at 100%, just randomly. So it's not a problem of a certain zoom level. This is very annoying. Any ideas what might be the problem?

Regards Frank

[Ryan G]

What operating system and what types of blocks are disappearing (sounds like all of them)?

This sounds like it could be a real problem for you and I would recommend contacting technical support for such a serious issue which can only be seen while Simulink is in use.

Answer 1

[Babak]

I think you are panning and zooming. The blocks don't disappear. They are there but you need to scroll all the way up to see them.

[Frank]

Unfortunately it's not a panning and zooming issue. It also happens when you press the space bar, which is supposed to zoom in and center the model to a level to get an overview of your model.

Answer 2

[Frank]

Back to the question of the OS: I'm using Win XP SP3 MATLAB 2012b 32bit

I figured it just happens after i get one of those Errors when using to many scopes in the model and you get this "failed to set IDBits". Basically you can solve that issue by changing the renderer of the scope. But it seems that it's messin' up the Simulink rendering.

[Ryan G]

Could be a memory issue if you have a really big model and/or are storing lots of data.

Even though it is supported for that setup, the fact is you are limited to <3gigs of RAM and every release of MATLAB is likely to take up a little bit more system resources for new features. So if you run the same model in 2 different versions, you may hit a limitation that was not there on a previous version, especially in 32-bit windows. However, this is all a conjecture.

What happens when you open the model fresh? What happens if you don't perform SLUPDATE?

[Frank]

Looks like a memory Problem. I got a quite big model and alot of data. In the befinning everything seems to be fine. after some simulations and changes it's messed up again. Well and without slupdate the model is not running due to some blocks that changed within simulink (as expected)

[Ryan G]

Sorry to hear you're hitting the memory barrier. There are some tricks you could try to employ that may help, but realistically you should work towards getting up to a 64-bit machine for a long-term solution.