Page 2 of 2
Re: DAG zero
Posted: Mon Apr 08, 2019 12:06 am
by J'Kla
I am not concerned about the DAG message itself.
My issue is the reporting it is overwriting.
That and there is an Australian word with a different origin and I quote
The literal meaning is a dung-caked lock of wool around the hindquarters of a sheep
I know we should not be worried but it is untidy.

Re: DAG zero
Posted: Mon Apr 08, 2019 9:49 am
by Doobes
J'Kla wrote:My issue is the reporting it is overwriting.
As evidenced by the troubles you were having with journals recently, the export log Korman creates will sufficiently tell you what happened with the export, not the console window.
Again, I really wouldn't worry about it as it does not affect the Age export itself. It's one of those things our programmer friends can (if they choose to) clean up after adding more important things like particle emitters and custom GUI dialogs.

Re: DAG zero
Posted: Mon Apr 08, 2019 1:32 pm
by Deledrius
Tsar Hoikas wrote:In the meantime, if this is really bothering you, I suggest starting Blender with the new dependency graph by using the --enable-new-depsgraph argument.
Just add this to the shortcut with which you launch Blender and you'll never have to see that annoying message ever again!
Re: DAG zero
Posted: Tue Apr 09, 2019 1:29 am
by J'Kla
OK got it sorted added --enable-new-depsgraph no DAG message.
No Australian sheep were harmed in the reporting of this message.
Re: DAG zero
Posted: Tue Apr 09, 2019 2:44 am
by Deledrius