Annoying feature/bug?

Sorry to litter up the forums with a question like this but I couldn’t find anything about it anywhere online…

So… I have made some shaders that use time to essentially animate themselves. Whenever I attach them to a material, and then a sprite in the engine, I can see them moving in the editor as expected. Almost everybody at my studio can see them the way that I see them… But, there are a few people who cannot see the shaders move unless they click and hold the right mouse button or the middle mouse button to turn on the panning feature.

One of them is using a Mac one of them is using windows both of them have the same problem. I just opened up a project on my MacBook today (I usually work on my PC) this is the first time I’ve tried to use one of these shaders in the editor on my MacBook I believe… And I’m getting the same issue. Unless I click and hold the right mouse button the shader doesn’t move or update in the scene. (I don’t have a middle mouse button on MacBook)

Is this a bug? Or is it a feature that I can turn on/off somewhere? It’s nearly impossible to edit/adjust shader material properties in the inspector without being able to see their changes real time… and we can’t hold the mouse button in the viewport and change property values in the inspector at the same time…

If you need an example of what I’m talking about, imagine this… You make a Shader that essentially scrolls your UV coordinates on the Y axis continuously based on time… So, as long as the texture itself has its wrap mood set to repeat, you should see that texture scrolling up or down endlessly in the viewport… but, for those of us affected by this bug/hidden feature, that texture will not scroll unless we are holding down a mouse button in the viewport that enables panning (middle/right mouse button) when we let go of the button, the image goes back to being static…

Again, it doesn’t do this on my PC and it doesn’t do this for the majority of people working on our games at the studio… So far I only know of three people experiencing the issue. Two are on a Mac and one is on a windows Desktop PC.

The reason is that our editor doesn’t run scene if there is no modification or no executing components, for the sake of performance.
If you want to force the editor to run the shader, you can attach a component with executeInEditMode.

So, out of curiosity… why is it that some people’s editor is running the shader and some aren’t? We are all working on the same project using the same editor version? Thank you for your response btw! :slight_smile:

If you move the viewport in the scene view (dragging, pinch or other actions), it will run the engine, then you will see it taken effect