Chaos Corona 13 for 3ds Max Daily Builds Discussion
You can grab the latest build from: [Daily Builds Changelog](https://forum.corona-renderer.com/ Chaos Corona 13 for 3ds Max - Daily Builds Changelog )
Will we have live link in this version in chaos vantage?
I made clean install for this daily build.
Unfortunately in scenes made back in Corona 10 still crushes when starting IR…
Edit:
Guys i am sorry, that’s actually forest pack that doesnt work well with new Corona…
Could you please send us a sample of such a problematic scene at https://support.chaos.com/hc/en-us/requests/new
We are using the newest available versions of Forest and RailClone, in our internal scenes and user scenes, and we could not reproduce any crashes so far.
Hi,
When is the bug going to get sorted where the Chaos scatter toolbar doesn’t show up when using small icon toolbar in 3dsmax. This is a long awaited fix we have been waiting for.
Thank you.
This is already fixed internally and will be included in the upcoming Corona 12 Hotfix 1.
Please please pretty please could we finally get a toon outline shader? Or even just expand coronawire to include a profiles mode (like sketchup profiles) without needing to outline every face?
At work currently to produce elevations with just the profiles outlined and not every polygon we are relying on a free third party exporter to export to sketchup and then produce them in there. If corona had the ability to render outlines it would have saved me genuinely weeks of work in the last two months.
It has been requested since 2014 for the exact same purpose and theres a TON of support for it every time someone posts about it. I dont think ive seen many people asking for ink and paint style shading. Just this outlines feature.
I imagine youll say you cant make any commitments to features etc etc and to post it in the feature requests etc which is fine. But toon outlines have been requested since the beta days and are consistently requested still and are one of the most backed and popular requests every time its mentioned. So if you could consider this for v13 it would make lots of your core user base very happy.
Thank you for the update and releasing the fix for it in the HF 1. It has been long waited.
+1 million
Hello, are you planning to enable ‘history autosaving for sequences and for slaves during distributed rendering’ again in a future hotfix? I’ve been using this as a way to save the full CXR file since there is no other way to do it.
Can you explain why exactly you would like to autosave history items when using DR? What’s your workflow?
Quote from tooltip “Render History and A/B Comparison”:
“If enabled, a new item will be automatically added to the render history in the Corona VFB after each render ends (both IR and Production). This feature is automatically disabled when rendering sequences, and also for nodes during distributed rendering.”
This is another feature Corona team managed to turn into some broken mystery, needing a diagram to look at when trying to use it. And it feels like decisions are made to work around design flaws rather than solving the issue itself.
- IR results have never ever been saved to history in any Corona version so far. It was even considered as a bug in some daily when it happens - I remember reporting this, and some famous developer who is unfortunately out of duty atm. confirmed it as a bug. If (this==kindof NewFeature): the result does not get saved into history by pressing “stop” if using IR which is the “stop and save the results so far” button in contrast to “cancel”, so it SHOULD be saved in history when pressing “Stop”. It only gets saved if IR “Max passes” is set explicitly by the user - and has been reached.
AND it only happens if having “Time Output” to “Single”?! Who on earth should be able to understand and remember all this? If I just want to IR a frame and would like to have a history item from it, I have to change my scene setup, really? Btw: IR stop condition still defaults to 0, meaning “rendering forever”, so you usually do not get a history item using IR anyway (a shame to have it at 0 by default nowadays btw.).
- Do not even try to be smarter as the user. If I render a sequence, say frame 0 to 20, every 5th frame, I want to have exactly this in the history if I have enabled “autosave” - independently of having DR activated or not. DR on/off should never ever make any difference while using any feature anyway. Of course DR slaves should not write history items locally, they should never EVER write anything to production files. I’ve been fighting a lot to just have slaves not to overwrite light cache files - hard to believe that it took almost a decade to get that destructive behavior removed. Slaves should just deliver data to the master and never touch any production file, no need to stress that in a tooltip.
Good Luck
Am i missing something here? But surely the answer is “for the exact same reasons as when not using DR”
Agree 100%. But it seems they just don’t care what customers are asking for for almost a decade. Corpo behaviour at its finest, thanks to Chaos I guess.
Hmm, I don’t understand the strong reaction regarding the history autosaving. Let me try to explain what the original issue was and how we ended with the current solution:
First of all, there was a long and thorough discussion before making any decisions. The discussion involved the devs, support, and QA.
The issue was that while rendering in “silent” mode (no UI, no VFB, for example distributed rendering) with the history autosaving enabled, a pop-up message could appear when the HDD size / number of snapshots limit is reached, asking the user whether to delete the history snapshots or not, and this would halt rendering. So theoretically you could start rendering in the evening and wake up to see only 10% of your animation rendered.
We were considering either ignoring the popup in silent mode or disabling the history autosave in this case. The thing is, we could not think of any scenario where a user would like to use silent rendering and sequence rendering and use the history autosave. We assumed that you either set your main output file or you use the “regular autosave” (not history autosave) for this. It can also store images on render end, and you can set the limit to 0, and it saves to CXR format.
Here are my requests/questions:
Please explain why exactly you need the history autosave here and the “regular” autosave is not enough for you. What is your exact workflow, what you are achieving thanks to using the history autosave?
And what exactly is that reason? Can you please provide a use case? Why not use the “regular” autosave instead of the history autosave?
This is simply not true and this case has nothing to do with Chaos (as in: the whole company, or other people than the Corona team). Please check this article: Renderer for architectural visualization - Corona | Chaos
“Which does not mean we always get it right (we don’t, whether that’s in picking features, or estimating how long things take). What we can say is this though – even when we get it wrong, our heart was in the right place!”
"The article mentions how important user feedback is, so here’s how you can become part of the process! Keep up-to-date with the Changelogs in the daily builds sections of the forum:
Corona for 3ds Max Daily Builds
Corona for Cinema 4D Daily Builds
The Changelog posts in those sections detail what is in each daily build, giving you a chance to test new features well before release. Then you can give us your feedback in the discussion/reporting threads there too, where we welcome suggestions for those new features, as well as any reports of problems using them."
Please note that:
- Saying “this feature is a broken mystery” will help literally nobody. You should instead explain what exactly is wrong and how we can improve it.
- Saying “surely the answer is “for the exact same reasons as when not using DR”” will help literally nobody. We need to know what exactly you mean by “the same reasons”.
I was more so getting at the fact that whether it’s a DR render or single workstation render shouldn’t make a difference as to whether a certain feature works or not. Most of us use DR simply to get faster renders, so if something works when doing a local render, you’d assume it would work when bringing DR into play, because you’re not changing anything workflow wise other than wanting to get a faster render by adding more processors into the mix.
Also, I thought the OP of that comment had already given his reasons “I’ve been using this as a way to save the full CXR file since there is no other way to do it.”
As I understand it, this feature worked previously but the functionality has since been changed. Was the change documented/announced anywhere or was it another under the hood change that users weren’t notified about? Because that’s happened before and I remember users weren’t too happy then.
Also if you’re basically saying “you don’t need this feature” which is certainly what it sounds like. Then why does it/did it even exist as an option in the first place?
Ultimately the users determine how they use the product and if the option is there, chances are someone will find a reason to use it.
Also I wasn’t try to be confrontational/unhelpful in any way. Frood actually beat me to it when they said “DR on/off should never ever make any difference while using any feature anyway.” That’s all I was getting at
We understand what you would like. But we do not understand why. None of the replies so far explains why you are asking for this. The only valid answer would be explaining to us what exactly you are doing with the history autosave feature, not just saying that you are using it.
As I understand it, this feature worked previously but the functionality has since been changed. Was the change documented/announced anywhere or was it another under the hood change that users weren’t notified about? Because that’s happened before and I remember users weren’t too happy then.
It was announced in the V13 and V12 HF1 changelog.
Also if you’re basically saying “you don’t need this feature” which is certainly what it sounds like. Then why does it/did it even exist as an option in the first place?
Nobody is saying that, I am just trying to understand you (and failing so far). I also do not understand why you can’t use the regular VFB autosave feature for this (not the history autosave).
Ultimately the users determine how they use the product and if the option is there, chances are someone will find a reason to use it.
Of course, and we need to know that reason if we made a mistake and should revert some behavior. We do not understand the reason so far.
Let’s be clear. I don’t personally use this feature. I was simply confused as to why DR would make any difference to the OP’s reasons (whatever they are) whatsoever. That’s it. Nothing more.
One thing that does frustrate me sometimes with this forum, is simple questions being answered with questions and requests to justify your reasonings. So perhaps it just got my back up a little bit and I replied with a reactionary response.