Chaos Corona Forum
Chaos Corona for 3ds Max => [Max] Bug Reporting => Topic started by: Basshunter on 2022-06-20, 17:27:05
-
I don't recall this happening in previous versions. So for example, if I move a chair to another corner of the room, IR will remain completely noisy as long as the left mouse button is pressed, even if I'm not moving the object anymore. Only after releasing the button, the image starts to show up.
From my perspective, IP should update right after we stop moving an object and not wait for the mouse button to be released.
I'm on Max 2022.1 update and CoronaCorona 9 (DailyBuild June 9, 2022).
-
Hi,
I'll look into this one.
Rowan
(Report ID=918291061)
-
Hi,
I can't reproduce this one in the latest daily build (v9 2022-08-02)
Could you give it a go and let me know if you still experience this behaviour.
Rowan
-
Hello, it is Nazar from the Corona support team. Do you have any updates here? Are you still facing this issue?
-
I don't recall this happening in previous versions.
I don't recall that it ever has been differently :)
Good Luck
-
We were no longer able to reproduce this. If anyone observes this, please report to us.
-
Reproduced, but happens only when rendering from a camera. Moving back. :)
(Internal ID=1117269106)
-
Update:
- the issue is IR refreshing infinitely when moving/rotating/scaling objects (so that it always stays in the "pixelated" mode)
- the issue happens when rendering from a Corona Camera
- the issue does not happen when rendering from a perspective view
Our dev team checked the behavior, but unfortunately it's completely outside of our control:
We update the IR based on messages that we get from 3ds Max, the parameters we get there are very brief. It is sometimes impossible to get any useful information from them. It gets the modified node (the modified object, not the camera), so we can't tell why it happens only when we are rendering from the camera. Also there is nothing like "before" and "after" state which we could compare to see if something really changed.
This is something that can't be fixed on our side. We just get from Max the information that the object is still moving, while it is not.
We may try looking into it again at some point, but the most likely scenario is that we just have to consider it a limitation.
-
Our dev team checked the behavior, but unfortunately it's completely outside of our control:
We update the IR based on messages that we get from 3ds Max, the parameters we get there are very brief. It is sometimes impossible to get any useful information from them. It gets the modified node (the modified object, not the camera), so we can't tell why it happens only when we are rendering from the camera. Also there is nothing like "before" and "after" state which we could compare to see if something really changed.
This is something that can't be fixed on our side. We just get from Max the information that the object is still moving, while it is not.
We may try looking into it again at some point, but the most likely scenario is that we just have to consider it a limitation.
How is it that V-Ray doesn't have this problem but you do?
-
I guess IR works different in V-Ray than in Corona. But maybe we can improve this. I will be sure to let you know if I learn anything new.
-
Thank you