Any way of suppressing hair and fur warnings when using DR?

[Jpjapers]

If youre rendering H&F using DR and youre using a somewhat high poly growth mesh you get a warning on every single DR node that has to be manually clicked in order to begin rendering.
Its really annoying. Is there anyone who might have a fix or workaround for this?

Thanks

[aaouviz]

Just out of interest, what are you creating the H+F with? Or do you mean the H+F corona material?

[Jpjapers]

Just out of interest, what are you creating the H+F with? Or do you mean the H+F corona material?

3DS Max built-in hair and fur.

[Jpjapers]

Still looking for a way around this if anyone has any ideas.

[maru]

We need more details. What exact warning do you mean? Why is it always popping up?

[Jpjapers]

We need more details. What exact warning do you mean? Why is it always popping up?

Ive attached a screenshot of the dialog.
This dialog gets suppressed during DR as a service, but it means the render doesnt start (i guess because you cant click ok)
If you run DR as the executable, this will appear and halt scene parsing until you click OK. This happens with every render using hair and fur, every time.
If you cancel your render before youve clicked OK, and then click OK, DR is stuck 'waiting for render start' and wont take another job until you close and reopen DR.

I guess it appears because it believes my computer is going to s**t itself when trying to scatter H&F but that might have been the case in like 2009 or whenever H&F was last updated. Today im dealing with a sub 1000 poly object that causes this error so its nothing to worry about.

[maru]

I don't think this message is related to Corona in any way. It's probably a 3ds Max thing. I will make sure.
Update: yep, it's not in our code.

[Jpjapers]

I don't think this message is related to Corona in any way. It's probably a 3ds Max thing. I will make sure.
Update: yep, it's not in our code.

I understand its not in your code. But running DR as a service manages to suppress this dialog. Can it not just be made to dismiss it entirely?

[Frood]

It's another bad habit from the you-know-who-company, ignoring quiet/network mode and the corresponding bug reports. Look here for example:

https://forums.autodesk.com/t5/3ds-max-forum/urgent-hair-amp-fur-warnings-on-render-farm/td-p/4101171

"they" seem not to care about this since at least 10 years. Corona team can do nothing about this I fear, they break their own standards/guidelines in familiar manner and ignorance.


Good Luck

[Jpjapers]

It's another bad habit from the you-know-who-company, ignoring quiet/network mode and the corresponding bug reports. Look here for example:

https://forums.autodesk.com/t5/3ds-max-forum/urgent-hair-amp-fur-warnings-on-render-farm/td-p/4101171

"they" seem not to care about this since at least 10 years. Corona team can do nothing about this I fear, they break their own standards/guidelines in familiar manner and ignorance.


Good Luck

Oh the fact that running DR as a service suppresses the warning isnt anything to do with DR server telling max not to throw warnings but more about how running as a service deals with dialogs?

[Frood]

Yes (right way to answer a oder-question) or No (wrong way but more common :)

The suppressed UI (+warning messages in this case) are a result of running DrServer + Max as another user/service. In older windows versions, there was an option to allow UI interaction with services (you could even see the framebuffer working) but MS kicked that option due to security reasons for Win10. And even then, you would have to remote desktop through all your clients at every job and click that shit away. It's "just" another nasty Max bug which was not addressed since... it exists it seems.


Good Luck

[Jpjapers]

Yes (right way to answer a oder-question) or No (wrong way but more common :)

The suppressed UI (+warning messages in this case) are a result of running DrServer + Max as another user/service. In older windows versions, there was an option to allow UI interaction with services (you could even see the framebuffer working) but MS kicked that option due to security reasons for Win10. And even then, you would have to remote desktop through all your clients at every job and click that shit away. It's "just" another nasty Max bug which was not addressed since... it exists it seems.


Good Luck

Ahhh i see right apologies i assumed the suppression was DR server doing its thing. I can see why this cant be solved by the team then. No problem!

[Frood]

i assumed the suppression was DR server doing its thing

Yes, also. It starts the job with quiet:true, which should be enough - but not for "them". The only thing Corona team can do is to stick a thorn in the a*** of responsible people. It would be a one line check if quiet mode is active and not to issue that damn message if in quiet mode. But someone would have to touch 10 years old code. They rather throw some new stuff into max instead of fixing this.


Good Luck