Messages

31

[Max] Bug Reporting / DR node reporting version incorrectly

« on: 2017-04-25, 13:33:45 »

Hi, have just installed 1.6 on render nodes and desktop. First DR render went OK, but re-render says that there is a version mismatch (slave version: unknown (pre 1.3), master version:1.6)

I restarted the nodes (was difficult to get DR to close) and now rendering OK.

Using Max 2015 as master and the nodes have both Max 2013 and 2015.

32

[Max] Resolved Bugs / Re: PNG Error on render node

« on: 2017-04-20, 16:57:33 »

Sorry to bump this again. I know there are probably other things to fix before the 1.6 release. In fact it may have been fixed in 1.6.

We are still getting these errors, but we never output to .png and we also don't use .png files in our textures.

The Max forums higher up in the thread weren't that helpful really.

It's really got nothing to do with the fact that Corona saves various dr-out.png passes here?
C:\Users\*PC_name*\AppData\Local\CoronaRenderer\DrData\

Seems odd that we only got these since moving over to Corona.

Thanks,
Adam

33

[Max] Resolved Bugs / Re: *SOLVED - USER ERROR :) Light material not appearing in reflection

« on: 2017-03-23, 17:54:34 »

Yep, it's a great community, full of talented and skillful people without egos who are happy to help out other artists.

Reminds me of good old days of Silo and Subdivisionmodelling forums :)

34

[Max] Resolved Bugs / Re: Light material not appearing in reflection

« on: 2017-03-23, 16:43:09 »

Thanks!

I feel like a right wally now. I suspected I may have been doing something wrong :)

35

[Max] Resolved Bugs / Re: Light material not appearing in reflection

« on: 2017-03-23, 12:15:18 »

Curiouser and curiouser :)

I cut the scene down and now I can't see the light at all in the reflection!

Have attached file. I'm sure I must have turned something off accidentally, but I've checked in all the usual places and I can't find anything wrong.

36

[Max] Resolved Bugs / Re: Light material not appearing in reflection

« on: 2017-03-23, 09:59:00 »

Light settings attached. I'll upload cut down scene this afternoon (got to get the job out this morning).

37

[Max] Resolved Bugs / Re: Black squares on frame buffer and saved image

« on: 2017-03-22, 12:41:26 »

Sorry, I can't remember what file was causing that (quite a few jobs ago).

We're all upgraded to latest hotfix now and we haven't had a problem with this recently. I will upload if I get a re-occurrence.

38

[Max] Resolved Bugs / *SOLVED - USER ERROR :) Light material not appearing in reflection

« on: 2017-03-22, 12:09:58 »

I've used a light material on some geometry to make a nice glow in a downlighter - there may be more efficient ways to get this outcome :)

The problem is that it doesn't appear in the mirror. Non light materials appear fine.

The light is an instance.

Easy to sort it in post, but be good to know if I am doing something wrong or if this is a bug/feature.

39

[Max] Feature Requests / Re: Which 3D soft to integrate into next?

« on: 2017-03-06, 14:20:17 »

Houdini +1

:)

40

[Max] Resolved Bugs / Re: PNG Error on render node

« on: 2016-12-02, 16:48:42 »

Necrobump.

We've been getting the same problem quite a lot.

I've been looking for the png recompile that was mentioned and it's disappeared. I'm not technical enough to do that sort of thing myself. If anyone can point me in the direction, I'd be grateful.

I guess this hasn't got anything to do with the fact that the Corona DR server writes a DR_Out.png file? Or is that just a red herring?

Thanks,
Adam

41

[Max] Resolved Bugs / Re: Internal error - Bad Allocation

« on: 2016-11-30, 18:05:04 »

0_o

I've not seen the commit size thing before.

If it happens again (seems OK for now) I'll send scene and more details.

Thanks Ondra.

42

[Max] Resolved Bugs / Internal error - Bad Allocation

« on: 2016-11-30, 17:18:52 »

Error report from clipboard:

===== Error(3) =====
Internal error. Please report it at https://corona-renderer.com/link/2001:
Bad allocation
Wanted to allocate: 346MB
Used virtual memory: 47013MB
Total virtual memory: 47018MB

Stack trace:
 6 Corona::preAssert  0x7ff9bacc8540
 5 Corona::coronaMalloc  0x7ff9bacc9510
 4 Corona::PropertyDescriptor::getNth  0x7ff9a5ccc9b0
 3 Corona::IFrameBuffer::ExrStats::fromString  0x7ff9a5dbfca0
 2 Corona::IFrameBuffer::ExrStats::fromString  0x7ff9a5dbfca0
 1 Corona::IFrameBuffer::ExrStats::fromString  0x7ff9a5dbfca0
 0 CanAutoDefer  0x7ff9baa57aa0


This popped up at render time. It's possible it's something else than Corona because my whole system is flaking out (Photoshop just took about 5mins to launch after first crashing out) but I'm still reporting it because the error box asked me to :)

Windows 10, Max 2017, Corona 1.5 hotfix 2

43

[Max] Resolved Bugs / Re: Parsing the scene

« on: 2016-11-18, 16:30:49 »

No, just Forest Pack and I'm pretty sure there is no collision checking in this scene, but they are nested (ie some FP objects are masking other Forest Pack objects).

It's actually rendering fine as long as I don't have a Forest Pack selected/open when I start the render.

44

[Max] Resolved Bugs / Re: Parsing the scene

« on: 2016-11-18, 13:48:28 »

I don't know whether this is connected, but I've got a complicated Forest Pack scene and when I have been testing changes with Forest Pack I've been getting parsing freezes.

I've found that if I have selected the Forest Pack when I press render, it freezes while parsing. If I don't have anything selected it parses OK.

45

[Max] Resolved Bugs / Re: Black squares on frame buffer and saved image

« on: 2016-11-02, 17:08:59 »

It happened again so have uploaded EXR dump as suggested to Mantis. I can send scene if you need it.