Effects only display after render all ?

[gerry]

4.1.13. Windows.

It appears that I can only see the results of an effect (new dropped to grid or changes to an existing one ) in the House preview window (or model window) after I click Render All.

Tried on individual models as well as at the group level and different effects eg text , single strand and butterfly

Has there been a  recent change/option that would explain this ?
 

[JonB256]

How long did you wait? It isn't always instantaneous. 

[gerry]

For me at least , it definitely appears as an issue after I installed 4.1.13. Even say 30/60 secs later it does not show up. None of them , till I click render all. Existing seq or new sequence.

I re-installed 4.1.12 and it is fine - instantaneous like before

Will wait to see if anyone else has the same problem and will work with 4.1.12 till then.

[kevinp]

I too noticed this on Saturday when I was using the Morph effect under 4.1.13 (Mac OS X).  I could only get the live preview to render after saving or rendering all.  I was about to post/report that issue Saturday night, but just called it a night instead.  That was Saturday, now on Sunday, I was having no issues.  And this morning I just tried it again and I'm getting instant updates in the preview window.

[RGBNoob]

I have the same issue. Even my AC models won't update most of the time until I hit the render button.

[JonB256]

Try reinstalling that same version again. That has sometimes helped me.
(ps, mine is updating - Windows 8 )
What platform are you using - always helpful to mention.

[RGBNoob]

Windows 7.  I'll try a reinstall later today. Thanks.

[Gilrock]

I thought I noticed the same thing yesterday.  I'll have to review what went into this build to see if anything could have affected that behavior.

[ronald]

I'm having the same issue. Both on a win 7 and win 8 machine

Sent from my SCH-I545 using Tapatalk

[RGBNoob]

Would I need to do an uninstall first before reinstalling or can I just reinstall over my current installation?

[Gilrock]

You can reinstall directly over the current installation but it's not going to fix this issue.  We have an idea what might have caused it.  There was new logic to put a mutex around rendering to an element to prevent lockups and crashes and that object might not be working well on windows.  It appears to work fine on a mac.

[RGBNoob]

You can reinstall directly over the current installation but it's not going to fix this issue.  We have an idea what might have caused it.  There was new logic to put a mutex around rendering to an element to prevent lockups and crashes and that object might not be working well on windows.  It appears to work fine on a mac.

Thanks.

[gerry]

We have an idea what might have caused it.  There was new logic to put a mutex around rendering to an element to prevent lockups and crashes and that object might not be working well on windows.  It appears to work fine on a mac.

Thanks Gil. 

[dkulp]

You can reinstall directly over the current installation but it's not going to fix this issue.  We have an idea what might have caused it.  There was new logic to put a mutex around rendering to an element to prevent lockups and crashes and that object might not be working well on windows.  It appears to work fine on a mac.

Well, to be completely honest, after looking through the code, in this specific case I think it's a bit simpler and it's something that keeps biting me:  C++ calls default constructors for object member variables, but doesn't do anything about primitives.   I'm SOOO used to Java (my day job) where everything is always guaranteed to be 0 for all the primitives I keep forgetting I need to explicitly set them to 0 in C++.