Messages

31

[Max] Daily Builds / Re: Corona Renderer 6 for 3ds Max - Daily Builds Discussion

« on: 2020-04-24, 11:23:52 »

Uploaded scene via the provided link. Have not tested with Corona 6 latest builds.

It works fine here:
- Max 2020
- 16.04 V6 Corona daily
- TyFlow newest version (downloaded literally yesterday)

I rendered a few frames from the animation, no crashes.

Are You sure You are rendering the TYFlow, not the geometry generated . TYFlow has been disabled in rendering from object properties menu.
Tried once again with Corona V6 16.04 and latest TYFlow, but 3ds max 2018 - crashes persist.

32

[Max] Daily Builds / Re: Corona Renderer 6 for 3ds Max - Daily Builds Discussion

« on: 2020-04-24, 10:49:28 »

Hey all,

Has anyone had any success rendering motion blur with tyflow? I set up a basic flow with raindrops and it crashes max right after the scene parsing.

TY Flow motion blur does not work here as well - 3ds max 2018.4 +Corona 5.  Crashes on parsing. I had high hopes on Corona 6 daily builds that it solves this.
If recall accurately someone submitted similar issue  onto chaosgroup forum - there is something related with velocity of particles when using triangle mesh.

I decided to check if there is a workaround  for rendering just motion blur out of the particles generated with TY Flow.
With Vray Next a simple scene works fairly well. Same scene with Corona - crashes at parsing.

 "Export particles to objects" within TY flow seems to help rendering motion blur with Corona. Have not messed around with all the available options there, but at least it renders without crash.

Can you guys send any example scene? https://corona-renderer.com/upload
In my quick tests it worked fine, but it probably depends on what exactly you are motion-blurring.

Uploaded scene via the provided link. Have not tested with Corona 6 latest builds.

33

[Max] Daily Builds / Re: Corona Renderer 6 for 3ds Max - Daily Builds Discussion

« on: 2020-04-21, 20:58:09 »

TY Flow motion blur does not work here as well - 3ds max 2018.4 +Corona 5.  Crashes on parsing. I had high hopes on Corona 6 daily builds that it solves this.
If recall accurately someone submitted similar issue  onto chaosgroup forum - there is something related with velocity of particles when using triangle mesh.

I decided to check if there is a workaround  for rendering just motion blur out of the particles generated with TY Flow.
With Vray Next a simple scene works fairly well. Same scene with Corona - crashes at parsing.

 "Export particles to objects" within TY flow seems to help rendering motion blur with Corona. Have not messed around with all the available options there, but at least it renders without crash.

34

[Max] Tutorials & Guides / Re: 3ds max + Corona + Windows = Finally good performance

« on: 2020-04-13, 15:11:51 »

I would like to add few additional insights, although not specifically related to the "Defender" thing.
Still using one machine here, but noticed considerable decrease in performance and stability after several Windows 10 updates, which occurred around end of March.
It was mostly related to 3ds max instability, frequent freezes which eventually influenced Corona experience.
Made investigation as read a post somewhere that the following windows 10 updates "B4535996, KB4540673 and KB4551762" can cause some serious trouble.
Happened to have had  installed the latter and after removing it - back to normal.

Completely support the idea that we need to organize a windows 10/3ds max file or note where to put most common software related stuff that might be the real culprit behind some of the issues people are experiencing.
I am personally working from a network and almost every single file becomes  quite slow at certain point. Trying to avoid keeping multiple 3ds max instances opened as well, but... avoiding is not a solution. :)
Still using 3ds max 2018.3 but it is bit sluggish in UI, bit slow and more unstable than 3ds max 2018. Tempted to try most recent versions, but really do not want to go down the rabbit hole.

35

Gallery / Re: contemporary cabin - oslo, norway

« on: 2020-04-02, 18:49:07 »

Looks pretty awesome!

What's your experience with megascans? 
For some reason I can not get good looking shaders when using their 3d scans and the 4k resolution maps. Almost same applies to 4k textures for surfaces.
The tree and stone You have used look with quite good resolution....

Unfortunately by default Quixel just charges You without giving You the options to change your subscriptions plan.
After officially proclaimed free use with Unreal and the increased points and upped resolution, my account was charged without access to any of the new conditions. I hear others have experienced the same.... Really unprofessional, but still counting artistic souls.

36

[Max] I need help! / Re: Yet Another Parsing topic

« on: 2020-02-28, 12:05:18 »

Hi,

Thanks rowmanns  for the suggestions. Will see if latest v6 builds will help. Barely find any free time to delve into testing new software currently.

I have managed to reduce parsing at half. Switching all RC objects visiblity to point clouds and limitting FP scatter area  in half, resulted in much better handling of the scene.
Same scene, same file - from 10 min to 5 min.
Initially I though the issue could be due to motion blur present in scene.
Will keep posting observations.

37

[Max] I need help! / Re: Yet Another Parsing topic

« on: 2020-02-26, 14:45:30 »

Latest officially realeased from Corona team - v5, the
Updated windows 10 to latest available builds.
Hardware is already old one, but super stable overall - xeon v4, with sufficient RAM installed.
Latest FP and RC.
I have few cars moving within scene, and rendering motion blur. Also active displacement and using the 2.5D one at 2 px. Autobump disabled.
Cars are using path constraint.

Transforming vertices with or without FP - takes 10 min.

Despite the latest updates with RC, I think  that have to change habits and stop using it for a while, until find proper solution.
Will try to collapse geometry, especially the one using splines for clipping and will post results.

38

[Max] I need help! / Yet Another Parsing topic

« on: 2020-02-26, 01:30:45 »

Hi all,

I have recently updated all itoo plugins, alongside with latest service pack available for 3ds max 2018.
Interactive becomes slower with every single project, no matter the scale. I can narrow the culprits down to Railclone and Forest pack.
Parsing takes 10+ min and literally makes unusable. That of course applies when scene is prepared (modelling done).

I have recently discovered that using many RailClone objects with clipping splines slows down considerably the 3ds max scene - saving, opening and parsing.
The only workaround is to convert to poly  objects once they have  been generated with RC. It is not applicable to many of the projects due to never ending comments, hence I am looking desperately to solution or workflow that limits these excessive parsing times.

By the time writing this post, I have the 3ds max file open with a project. Parsing- 15 min. Swtiching from corona camera to perspective takes 20 min to re-parse/re-load despite the use of PT.

Has anyone else experienced problems with RC alongside 3ds max and  what workarounds can suggest.

PS. Railclone used with clipping splines with "intance mode ON" produces many artefacts as well.

39

[Max] General Discussion / Re: Weakness of corona ? - artifical lighting with little daylight - or bad skills

« on: 2019-12-02, 22:29:31 »

You compare soft natural light probably coming from big light source to light with single small spots...Not to mention that most of the objects in the artificial light reference interiors are hard-surface objects, whereas the other ones have some soft materials.
Two very different light scenarios.
 You can mimick the soft look from the artificial light by using  for instance softbox concept with non-renderable light bouncing objects when using artificial lights in conjunction with spot lights. You can then play with light intensity and color of the objects used for bouncing.

40

[Max] Daily Builds / Re: Corona Renderer 5 for 3ds Max - Daily Builds Discussion

« on: 2019-09-24, 10:35:23 »

Posible solutions to the "dancing windows" issue:

I am dual xeon v4 user and experienced  this for quite a long time.
Had sent several scenes as well,  and when rendering experienced the following(regardless Vray or Corona): https://drive.google.com/drive/folders/1T4b851mAo25nYC4vSm9dmOGlub0RpZXW?usp=sharing
Managed to find temporary "silly"solution which worked for me most of the time --> switch user accounts couple of times, until 3ds max returns to proper behaviour.
Was doing this repetitive, laborious  taks for so long that stop paying attention.

In the middle of Summer finally found a  solution, which works, at least in my case - update to win 10 1903. Was using 1803 prior to the update.
Downloaded latest Nvidia drivers, removed the  windows ones, and installed the latest manually, Not via the Nvidia Installer. Actually I was not able to properly install Nvidia drivers with their automatic installer prior to manually doing it.
After doing those two ---> no more flashing, flickering, etc, or switching between user accounts.

Upgraded RAM  in the meantime, but believe the flashing was more of a software compatibility issue.

41

[Max] I need help! / Re: Corona 4 Image Editor Question

« on: 2019-06-20, 12:37:07 »

Thanks! The tip did work, but has a limitation  if one has played with "EV" or other settings. Seems to reset them to default values - in my case the cxr, converted to exr and then open with photoshop resulted in blownout beauty pass.
Anyway, thanks once again - it was a time saver tip.

Would like also to apologize about the question. Have resumed a file inside 3ds max before updating Corona3 to Corona4 and then saved it as exr.   
Swtiching between Vray and Corona just left me with wrong impression that even the Image Editor gives You the option to save a single exr file.

42

[Max] I need help! / Corona 4 Image Editor Question

« on: 2019-06-19, 19:22:44 »

Hi,

Just updated Corona to version 4 and played with caustics.
Great and stable so far. Well done!

Having hard time figuring out how to save a single exr file with all passes  from a cxr file.
Just yesterday was able to do that with Corona 3.

43

Hardware / Re: Advice Regarding RAM

« on: 2019-06-07, 16:44:01 »

Thanks, once again!

Just sent you message!

I will post what has happened  with RAM  in several days!

44

Hardware / Re: Advice Regarding RAM

« on: 2019-06-07, 14:01:59 »

Hi,

As said - another drive is the  last option to resort , and first one I can think of that can help the situation in really short term.
Having the "slower" 256 GB available it does act as extention to the memory. Do not see any reason why another SSD will not help in this regard, when all I currently need is sufficient space after windows/3dsmax/corona trespass the 128 Gb threshold.
The option for another disk is temporary to fix it and  much quicker to act and cheaper investment in short term. Considering that possible 100 % solution would be to go with 128 GB RAM straight away.
Completely aware  and agree with You of all the speed drawbacks  and am fine with it.
Nobody will deliver RAM modules from warehouse in Germany within 2-3 days. :) Add the fact that this is picky motherboard and my case might be among those 1 % exceptions which Juraj mentioned and You can quickly go from - "Let's do what I am paid for" to " Let's see what I can pay for , pay and see if it works".

The main scene refers to several xreffed ones, each having 25+ Railclone objects. All is optimized as much as software allows, with only exception to textures. Well RC is mostly used with the instance option off, since it  uses some texture randomization, but believe it will not help much. Anyway, will cope with it- it is a hardware tread after all.
Opening the scene does take like 5 min, but ram stays at around 10 GB. Parsing takes another 5-6 minutes, and considering that obviously SSD helps,  it is hard to guess how much faster it all could be.

Will optimize what can related to 3D and hopefully upgrade memory since do not mean to retire this system in the forthcoming 2-3-4 years.

45

Hardware / Re: Advice Regarding RAM

« on: 2019-06-07, 10:47:23 »

The concept behind adding another storage as temporary "qucik" solution for insufficient RAM is purely for two reasons:

- the existing SSD is only 256 GB one. Yesterday dropped some megascans in an old scene which needed update and boom - Corona and 3Ds Max used 120 GB of memory. Did not expected that much and had PS with one 4k psd file. The scene did have some displacement here and there initially but had to disable it to accomodate  within the  physically available 63.9GB ram and the existing virtual one . Needless to say that within 10 min time saw the available storage space going from 60 GB down to sub 200 MB, and system become unstable. Definitely more storage space would help the system, at least not freezing. Stability vs Speed in real world with deadlines is almost always win for the first "S".

-would rather have new m2 drive installed on a new build than replace the 256GB one with 970 Evo Plus/Pro in as main OS drive, especially due the fact system would not benefit in "full speed" of it. Actually I have one existing 970 Pro, used in a  small barebone server as cache drive - no real benefit, so might just perfectly work as temporary solution.  Know there might be some handy programs for disc cloning, but literally do not have sufficient time to adopt them as long-term workflow benefitting solution.Have to check with the IT guys about switching the abovementioned 2 drive between systems.

Of course, expect them to come back with response about finding working 128 GB memory for the Asus MB. Sadly do not have that much cash to opt with Amazon/Ebay Options available.

Will post if find a solution anytime soon.

Thanks once again for suggestions and for pointing out  all these tiny details.