Show Posts

This section allows you to view all posts made by this member. Note that you can only see posts made in areas you currently have access to.


Messages - TC

Pages: [1]
2
I guess I should submit the scene as well. I did not attach the scene to my ticket.
Should the assets in the scene (like textures, hdri maps) be sent to you as well?

3
Thank you for the script.
Tried it just now and unfortunately it has no effect on the scene, still a black screen. But it might come in handy for others with volumetric materials in the scene.

Like I said, nothing like that in mine.

If I revert to 9, it renders just fine.

4
OK, thanks.
I must admit though I am very confused as to why 2D-geometry (with no thickness) has become a problem with newer Corona-versions.
For instance, even if I model a ceiling object (I use Sketchup for most of my modelling, did so for the last 15 years), it is very common that the underside of the ceiling has different material than the rest of the ceiling object, which often translates into that face being an object/mesh, the rest of the ceiling another object/mesh and so on. Always been like this. So this can not possibly be the issue, all of a sudden. An outer wall usually has three or more different materials, for instance, they usually get separated into meshes to make for easier UVW-mapping and so on.

Also, there are absolutely no material with volume settings in this scene, not that I know of.

5
If you open a ticket for this problem with the latest scene you tried, and sent in a copy of the scene, that would be most helpful - https://support.chaos.com/requests/new

The only known change in 10 that can make a scene render black is if an object that uses some volumetric shading is not an enclosed 3D object, e.g. is a flat plane for a wall or ceiling. Due to the camera calculating whether it is inside a volume or not, any non-enclosed objects will be considered "infinite" in terms of their volume, so that is what I would check. Planes for walls, ceilings, or anything else, are generally not recommended anyway, as everything should be built physically realistically for best results and everything in the real world has some sort of volume.

Let us know if that resolves the issue. You could test quickly by using material overrides to replace all the materials in the scene and see if everything renders as expected then, and then it would be a case of hiding half the scene objects (without mat overrides), seeing if it renders; if black, hide another half of that half, and so on, until the problematic objects are identified.

PS - where is the previously reported issue, please? Thanks!

Just opened a ticket.
Rendering with a white override-material works just fine. The regular render, on the other hand, is black. Just installed the 11 RC1, same behaviour on a 9-scene that rendered perfectly.

My previous report is within a thread reporting slow asset loading times. That was when I had to revert to 9 to get the work done.


6
Hi,
Decided to make another attempt at installing ll CR10 HF2 efter previously being forced to revert to 9 because of issues with some of my scenes suddenly not opening in 10 (the loading assets issue that few others also reported)
A previous scene rendered perfectly fine with Corona 9 this morning. After the installation of 10 HF2 the interactive screen is pitch black, and so is the render.
No changes whatsoever to lighting, secondary solver or camera settings. The exact same scene.

Already read previously reported similar issues and i can not identify the issue in my case. On a side note : I am legitimately wondering as to why am I forced to revert to 9 again to finish my work (my previously reported issue with 10 did not get any answer or solution), and still paying subscription for a later version that does not work (second issue with 10 in two months now, been holding onto that reliable 9-version for my dear life)

Help would be greatly appreciated.

Regards
TC

7
Just installed v11, the daily build. The scene that I had problems with initially still gets stuck at 98%, loading Corona assets.
As stated before, the workaround for me was downgrade to 9 but also merge the problematic scene into a new max-file. Same scene content, same assets - loading times quite alright this time, given the size of the file. Both 9 and 11 work fine with the merged file.

8
A quick update - the only workaround in my case was to revert to Corona 9, no issues whatsoever afterwards with the exact same scene
Something's not right with the 10-build in terms of loading assets - my experience was that the scene would not load at all (so not that there was a long wait, but the whole thing actually froze)

9 solved the issue for now.

9
+1 here. 3Ds Max 2023, Corona 10 Hotfix 1
Extremely long loading times, stuck at "loading Corona assets". 10 m+ and counting, a 1.23 Gb scene that was quite zippy before. What gives?

Pages: [1]