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 - v.p.vlasenko

Pages: 1 2 [3] 4 5
31
1. Black edge where object with refractive material contacts other geometry - image attached.
2. Setting opacity to 0 makes fog like material.
On the second image water material have opacity 0, but underneath surface have blue color.
The third image is a preview but the sphere is still barely visible.

Both problems appear on physical and legacy materials.

Corona V7.

32
Hi Rowan,

I don't know how corona working but should it be reparsed each time I move it or change scattering settings? Why this not happens with geometry in the scene. For me it looks like something I wrote about in the first post - looks like vdb loaded from disk each time I move it during IR.

Anyway, I checked it with arnold active shade and everything works fine.  wdas_cloud.vdb - instant response to moving volume instead of waiting 13 seconds with locked max.

So probably that's not something to be expected.

33
Yes, landscape model there (island)

There are 4 materials mixed in multilayer material. Each of those materials applied separately gives a way higher rays/s. Seems like from 7 to 14 million on my PC, but mixing them in multilayer gives something around 1M.

Actually I may be wrong and that not corona distance - I didn't tried a bitmap mask, maybe something with multilayer material.

Anyway, such slowdown looks weird.   

34
I thought it was pretty simple, but ok

I have cloud VDB loaded in corona volumegrid, it takes some time to start IR. After that I can move/rotate the camera and everything runs smoothly. But if I try to change the position/rotation/scale of corona volumegrid during IR it takes a lot of time. Same if I try to change some settings like scattering or absorption.

Just checked - 7 seconds for a particular VDB file. So if I try to move it or change the scattering scale I have to wait 7 seconds each time. And max is locked during those 7 seconds.

I can send VDB but I see no reason for that - it behaves the same with any VDB. The bigger grid (amount of cells) - the bigger lag.

Checked with Pixar cloud (I think you have it) - wdas_cloud_sixteenth.vdb runs smoothly, wdas_cloud_eighth.vdb a bit slower, lag is quite visible on wdas_cloud_quarter.vdb, wdas_cloud_half.vdb - 5 seconds to refresh IR, wdas_cloud.vdb - 13 seconds.

35
file called "scene with max freeze.zip" uploaded to dropbox.

There is a mess with objects and materials, but sometimes I need to work on tight deadlines with models given by the client - in scenes created from scratch by me I didn't have max freezes.

I isolated 3 objects showcasing 3 problems I created topics for.

Try to change house model materials during IR to get freeze.
The landscape model uses corona distance and causing a serious slowdown.
And the pattern on sea displacement.

36
I have few materials. When applied to object separately speed ranging 7-14M. When mixed in multilayer material with corona distance - speed is 700k +/-

Same problem with opacity. I have a landscape model + a lot of buildings with pools. Bottom of pools below ground level - instead of cutting geometry I used corona distance to cut it during render - speed dropped twice.

Maybe that's correct behavior with opacity, but 10 times slowdown with mixing materials looks strange.

37
Nothing to explain here - moving vdb or changing settings very slow, looks like reload each time

And the problem with the visible bounding box still here - with global volume or inside/intersecting with another object with volume mtl.

38
example of PhoenixFD ocean

This could be solved by switching to 3D displacement previously but not anymore

Same weird result I had with prosimplex.

39
1. max 2019 with latest updates
2. seems like it happens even without any plugins
3. 7980XE, 128GB, 1080Ti, Windows 10
4. Yes, all software, drivers are up to date

I'll check some scenes where that happens and send one of them.
Btw, I created minidump some time ago, if that will help. I'm not sure if 789Mb is normal size for it.

40
The problem looks similar to already posted here by mahjoub but I created a new topic because of:

1. It happens for a couple of years already and I'm using the latest daily builds, so the problem here for a long time.
2. Happens in completely (almost) different scenes.
3. Not looks like it bound to resolution.

Almost different is because those scenes have something similar - a lot of objects and a lot of materials (and big scale, but I don't think that's the problem). It never happened with productviz scenes and some small archviz like couple of buildings or some interiors.

So the problem: if I run IR and moving or creating objects, moving camera - all fine most of the time, let's say 95% it works fine - I can stop IR and all good. BUT, if I do changes to some materials - it works fine until I stop IR, then max becomes locked for a long time (5-40 min). And again that not 100% cases but it almost for sure, that after doing changes it'll lock max.

Sometimes that happened if I even didn't make any changes, so just run IR and stop it after some time lock max as well, same for regular render - but that happens rarely.

The problem occurs even with isolated objects, so hiding everything except one certain object will behave same way, so I have to move that object to another scene to work with it and then back.

Another interesting thing - sometimes I still can work for a couple of seconds after closing IR and then max became locked.
 
At some point in those scenes I stopped using IR and did regular test renders instead with cancel at the end, not stopping. Can't say for sure, but seems like cancel work better - I can't remember freeze after cancel, but can't guarantee that.

And one more thing I tried - selected all objects in scene (seems like there were around 12k of them) and applied one material to all. IR seems to be running ok after that. I did 3-4 runs, applied some materials to few objects during IR and seems like all fine. Again - can't say for sure if the problem eliminated, as it does not occur in 100% of cases.

Summary of the bug: scenes with high object and materials count, freeze occurs mostly after doing changes to materials during IR, but sometimes it happens without any changes and with regular render. PROBABLY reason is a lot of materials.

P.S. I'll create few more topics with bugs that annoy me for a long time and with newcomers found recently. That about 2,5D displace quality, openvdb and corona distance.

 




 



41
@martvaiss and @v.p.vlasenko - can you guys send us a simple scene demonstrating this behavior? The uploader is in my signature. After the upload, please let me know which upload method you used and what was the file name.
Also, what file format are you using for the mask image?
Does it have some sort of alpha channel in it?

Possibly reproduced, but a user scene would still be welcome.

(Internal ID=550612271)

Hi, uploaded using Private Uploader as 1597684477_1.zip

I simplified the scene even more. My mask image doesn't have any alpha, just black and white.
Btw, 3dsmax bitmap working fine.

42
Something similar here.

I used bitmap for masking with disabled tiling (black background, white text). The bitmap not covered entire object, just small part of it. Previously it worked fine - paper material (base material) over entire object and black glossy text corresponding to white text on mask bitmap (layer 1).

Now I'm getting black glossy (layer 1) for entire object and text. Paper only where the black background on mask bitmap.

I'm adding some screens.
1 - wrong result (previously worked fine), 1_1 - mat setup
2 - looks like correct result but I had to invert mask and base/layer 1 materials - 2_1.

43
No again - there are no screen for 32 bits, add gives wrong result

44
just tried - nope, not working - results still different.

45
The problem is simple - adding CShading_Caustics in photoshop produce completely different result than on raw render.

Doesn't matter which mode I select - the result is different. I tried screen and linear dodge (add), but both at 100% produce too bright (more like atomic explosion) result.

Renders in png 16 format, and working in 16 bit.

Any suggestions?

Pages: 1 2 [3] 4 5