"Some objects were not built correctly" repeating error

[Coastalvis]

So when rendering in realtime using 3dsmax 2022 and Fstorm (Im sure it applies to any real-time render) If you adjust a setting and go above your max renderable items you get a " Some objects were not built correctly" Error which just constantly pops up every time you press the ok button. There is no way to get out of this loop! And it is VERY frustrating that something like this is still in the plugin. Can you add a do not show again button or some basic fix for this? Its been in the software for many years and is a real pain.

[Michal Karmazín]

Hi,

Well, that‘s because some limit has been reached (and it’s preventing the system from any potential performance issues), but if preferred, all limits (Distribution > Max. Density, Display > Max Items/Faces) can be disabled by setting the value to zero.". Also, it's possible to set them by using Maxscript in the following way:

$.maxdensity = 0
$.vmaxitems = 0
$.rmaxitems = 0
$.maxfaces = 0

I hope that helps.

Best regards,

[Coastalvis]

Thanks for the info/command lines to work around it. But my real issue is that can FP not just display the warning once and then not render the scatter items? I have to alt+f4 and kill 3dsmax to get out of this situation a lot of the time unless I sit there for 20 minutes and hit the ok and close buttons on the render window repeatedly! When you have a deadline this kind of thing is unbearable and should not be in the software. As mentioned just display the message once and then kill the scatter in the render. Its ridiculous 3d artists have to put up with this kind of stuff in a "professional tool/plugin" im loosing work because I have to hard kill 3dsmax when it happens.

[iToo]

This specific error is shown all times because is critical, and should not be ignored.
There are other warnings messages which include the "don't show again" option.

Usually this message is triggered when one of the Forest object could not be built at render.
You can see more information about the error selecting the FP object, and clicking the 'Statistic' button at the General rollup.

Theorically there is not any reason why you want to continue rendering, if one or more objects are 'broken'. In all cases you will get a wrong render.

Anyway, the dialog message is shown only when using 3DS Max on interactive mode, not in unattended render modes (as Backburner or others), to not stop the rendering queue.

[Coastalvis]

I don't really find your answer helpful, to be honest. What was your point? I can read the message, Do you think its necessary for that dialogue box to pop up a 1000 times in an infinite loop for the user to know there's a problem?

-Why do you need to read that message 1000+ times before the window closes?,
-Did you even read my previous reply?
-In regards to " Anyway, the dialog message is shown only when using 3DS Max on interactive mode, not in unattended render modes" !
Most professional Artists use "interactive mode" in their render engines when working on their scenes. Most 3d artists have moved on and use interactive render modes. If your plugin is not optimized for this you really need to speak to some artists to find out what features they need.

The fact an itoo dialogue box constantly pops up in an infinite loop making 3dsmax unresponsive is really not acceptable. We only need to know we have exceeded the threshold once where we can then close the render window and adjust the settings. Or keep the interactive render session going and adjust the setting. This is a janky bug that needs to be fixed. I won't hold my breath though seems itoo are lazy and don't listen to their users from what I can see on this forum.

[iToo]

You're right. Reading your posts again, i see we didn't understand well the problem. I apologize for that.

This message should appear only once time, when renderer stops, not multiple times.
This seems a specific issue with FStorm and Interactive Renderer. I just tested with V-Ray and Corona IPR and it doesn't happen (the message is not even shown).
We'll check what is happening with FStorm and will try to fix it.

-In regards to " Anyway, the dialog message is shown only when using 3DS Max on interactive mode, not in unattended render modes" !
Most professional Artists use "interactive mode" in their render engines when working on their scenes. Most 3d artists have moved on and use interactive render modes. If your plugin is not optimized for this you really need to speak to some artists to find out what features they need.

Sorry, another misunderstanding on our part. I mean 'interactive mode', as when 3DS Max is running by an human operator, not in render queues as Backburner.
I just noticed FStorm names their IPR as "interactive mode", the same term i used but for other purpose.

We'll take a look to this for our next update.

[iToo]

As we though, this is a problem exclusively with FStorm. More specifically, when using Interactive Render and 'real time geometry update' is enabled.
With this configuration, when Forest doesn't return any item, it seems that FStorm calls continuously to Forest, entering in a loop with the warning message.

FStorm team is checking it. Unfortunately we cannot stop the render process from our side.
Even if we disable the popup message completely, that doesn't solve the problem of the calling loop to Forest.

Anyway, in next Forest update we'll add the posibility to disable this specific popup with General->Settings->'Disable Popups'.
Another option is to disable 'real time geometry update'. According to our tests, problem doesn't happen when this option is off.

I hope that helps until there is a complete fix.