Page 4 of 4

Re: Indigo Renderer 4.0.38 Beta Release

Posted: Tue Jun 28, 2016 1:49 am
by Jay-ko
Something very annoying:
On this version, if I load a file through File-->Open, so the render start automaticaly.

And I have to wait before click on "pause".
And sometime I have to wait for a looong long time.


This is new, and particulary useless.

If you want to keep the sofware like that, please keep the choice open in the options!

Re: Indigo Renderer 4.0.38 Beta Release

Posted: Tue Jun 28, 2016 1:59 am
by OnoSendai
Jay-ko wrote:Something very annoying:
On this version, if I load a file through File-->Open, so the render start automaticaly.

And I have to wait before click on "pause".
And sometime I have to wait for a looong long time.


This is new, and particulary useless.

If you want to keep the sofware like that, please keep the choice open in the options!
FIle > Open doesn't start rendering here.

Re: Indigo Renderer 4.0.38 Beta Release

Posted: Tue Jun 28, 2016 6:29 am
by OriginalplanĀ®
OnoSendai wrote:
FIle > Open doesn't start rendering here.
Doesn't start rendering by me either.

Re: Indigo Renderer 4.0.38 Beta Release

Posted: Thu Jun 30, 2016 4:49 am
by dakiru
OriginalplanĀ® wrote:
OnoSendai wrote:
FIle > Open doesn't start rendering here.
Doesn't start rendering by me either.
Not for me either.

Re: Indigo Renderer 4.0.38 Beta Release

Posted: Fri Jul 29, 2016 7:39 pm
by Jay-ko
Thank you for your react.

So I removed the software and I re-installed it and now everything seem ok for that side.

Very bizarre!


I have a kind of side effect maybe, something new: (see picture below)


Then know that if I load an old igm file I have absolutly no problem.

Re: Indigo Renderer 4.0.38 Beta Release

Posted: Fri Jul 29, 2016 9:12 pm
by Oscar J
Jay-ko wrote:Thank you for your react.

So I removed the software and I re-installed it and now everything seem ok for that side.

Very bizarre!


I have a kind of side effect maybe, something new: (see picture below)


Then know that if I load an old igm file I have absolutly no problem.
This was fixed in later betas I think.