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 - mommus

Pages: [1] 2
1
This is one of many issues I have with Max 2017, but I was wondering whether anyone else has had this problem.

Corona materials (textures, checker etc) show up correctly in material editor, but once applied to an object just look black in the viewport. If I turn 'show shaded...' on and off, the object has shading visible when texture is turned off, but is flat black on all sides when it's turned on.

I'm currently running Nitrous 11....

...just tried Nitrous 9 and all seems well again. I don't think Corona likes Nitrous 11

2
thanks for the info re: CPU running in low priority mode after memory overrun.

The thing is, in Max 2013 and the previous version of Corona, my memory was only half utilised. Now it all seems to be getting gobbled up.

3
to add to the joy it seems Corona 1.5 is not capable of rendering large images.

I left it running last night on a not-especially-large 4000 x 3000 image and it's only managed five passes this morning.

It also appears to only be using 9% of CPU resources, rather than the 100% that the previous version would utilise (there is nothing else running on my workstation, and low-priority is disabled)

4
going to have to go back to using vray

5
even rendering out tiny test passes takes forever.

also, there are graphics errors in the render setup window (blank areas that require window to be opened and closed repeatedly)

6
Everything is updated

I've also noticed that the pre-render stuff, like scene parsing and building acceleration structure takes much longer than previously

7
hmmm... my scene's not quite as large as yours, though there are a lot of corona proxy trees in it.

I've also noticed that corona/max's response to light is a lot different with 2017 and corona 1.5 - scenes that were previously lit quite nicely are now completely dark or massively blown out.

8
I've just installed Max 2017 and Corona 1.5, having used 2013 and 1.4 for ages.

The first thing I've noticed with the new software is that scenes which previously rendered with no problems are now using up all my memory (15BG installed)

Cancelling a render once it's started also takes about 10-15 minutes

I'm not sure whether this is a Corona or a Max issue.

9
C:/users/[your username]/AppData/Local/CoronaRenderer


10
dump report

11
No, unfortunately 1.00.02 is also causing max to crash - in the same way.

it seems related to the material editor, which when opened causes max to hang after a few minutes.

If I open a Corona scene, Max works ok, and can even render out at low resolution. However if the render finishes, or you cancel the render, a second attempt to render the scene also causes a crash - though in this instance, a max error message appears, allowing a recovery save.

As previously, the free version works fine.


12
haven't been able to do any work this week - are you any closer to a solution?

I've tried to roll back to the free version but max will no longer start

13
any luck?

14
just uploading a dump data zip called 1425377550_dumpdata_mommus.zip

second file is 1425377601_3dsmax_minidump.dmp

thanks for your help

15
it's a 2 mb dump file

where should I send it

Pages: [1] 2