Topics

1

[Max] Resolved Bugs / RC5 - Network Render Crash

« on: 2015-10-29, 22:46:53 »

all this is in Max 2015 with corona RC1, RC2 and RC5

the scene i'm working works fine locally but if i try to render it over the network trough backburner it crashes, all i get is.

ERR Task error: Launcher: Timed out executing command:"C:\Program Files\Autodesk\3ds Max 2016\maxadapter.adp.exe" "-o" "PingTask" "-l"
ERR Launcher: Timed out executing command:"C:\Program Files\Autodesk\3ds Max 2016\maxadapter.adp.exe" "-o" "PingTask" "-l" "Info" "-j"

i tried with all the RC's i have 1,2 and 5 and they all do the same, but if i install the daily build 2015-10-22, it renders fine no errors at all.

2

[Max] Resolved Feature Requests / Multilayered EXR's

« on: 2015-10-22, 02:35:58 »

Not sure if this has already been asked, but it would be nice to be able to save a single exr with all the render elements in it.

3

General CG Discussion / Huge Slate editor bug

« on: 2015-10-18, 18:07:52 »

I posted here this bug since its not corona related, but i have read many slate editor issues here and i don't think is corona related.

this problem has been bothering me for a long time, i finally had some time to try to replicate it so i can summit it to autodesk.
the slate material editor is practically impossible to use on heavy scenes which are what i use most of the times.

basically if you have a scene of let's say 15000 objects and you try to modify the material in the slate editor by adding lets say a noise map, it will be impossible to move around or edit anything in the material editor again until you restart max.

below i have provided the steps along with a script to reproduce it. even if you have more then 15000 objects/materials you can still modify them relatively fast until you try to add some maps or something else.
I have tried this on 3 renders (standard, vray and corona) they all do the same thing so its a max issue, there must be a memory leak in the slate editor.


1.- run the script attached to create 15,625 objects/materials
2.- open the slate editor
3.- open one of the materials and tweak anything, diffuse for example. it will be fast
3.- right click to add anything (noise map). max will freeze for a little while and after this step max is useless until you restart.

please let me know if anyone else can confirm this.

thanks,

4

[Max] Resolved Bugs / Message window select objects

« on: 2015-10-18, 17:18:25 »

not sure in what daily build started to show the option to select objects that have wrong gamma settings but is great, the problem i encounter now is that it shows this on xrefs too where you oblivious can't select the objects, for xref's maybe show the object names and xref file?

5

[Max] Resolved Bugs / Displacement Crash

« on: 2015-10-18, 08:46:00 »

I'm working on a large interior with lots of displacement, up until build 2015-10-09 it works fine but on build 14 and 17 max crashes if using displacement. if its off it renders fine.

i have not been able to narrow it more. i will let you know if i find more information.  for now i have move back to build 09

using Max 2016

6

[Max] Resolved Feature Requests / Corona Frame Buffer while Network rendering

« on: 2015-10-18, 01:32:11 »

it would be nice to have the corona frame buffer shown while network rendering so the different layers can be reviewed

7

[Max] General Discussion / Resume Render after Network Rendering

« on: 2015-10-17, 22:30:52 »

Is there a way to resume a render after is done rendering trough the backburner?. sometimes renders take a while and you have to stop it, it would be nice to be able to resume an image that was rendering in the network, maybe have a place to specify filename and location?

8

[Max] Resolved Bugs / wrong progress info & stop button.

« on: 2015-10-12, 16:39:37 »

I left a distributed render over the weekend on 3 computers, it was set to do 400 passes, as you can see in the screen capture the max render progress shows 91/400. it has shown that for several days but the stats on the corona frame buffer shows 550 passes. so the max progress is locked some how, and corona did not stop at 400, when i saw that i just left it ruining since there was still noise, the problem now is the render cant be stooped neither the max cancel nor the corona stop buttons work.

I was able to save the image from the corona framebufer but obviously there is something wrong.
the logs in the nodes corona servers shows that it is still rendering but the main max season is not responding.

this is in Max 2016, corona daily 2015-10-09

9

[Max] General Discussion / DOF in panoramics ?

« on: 2015-10-09, 22:16:21 »

I'm trying to use depth of field in a spherical panoramic but I can't seem to get it to work, is it supported?

10

[Max] Resolved Feature Requests / Message window on backburner

« on: 2015-10-07, 19:28:20 »

This is more of a suggestion.

I was rendering something trough backburner and had several objects rendering red with the unsupported message text on it. it turns out i hadn't updated the to the latest daily build on that computer. it would be grate to have the message window to show up on that node that it had a different version of corona, or any other issue for that matter.

11

[Max] General Discussion / Exclude from GI

« on: 2015-10-07, 16:57:01 »

is there a way to make an object receive gi but not contribute?

lets say i'm indoors and outside there are lots of trees far a way, i want them to receive gi but if its going to speed things a lot then i don't care for them to generate any gi.

i know i can use the rayswitch but that's going to disable shadows too. perhaps have the option in the rayswitch for receive - contribute?

12

[Max] General Discussion / more then 255 lights

« on: 2015-10-05, 19:53:30 »

I have been using the daily build (2015-09-24), and keep getting the message light sampler can only handle 255 lights efficiently.
for this particular project there is no way around it i need a lot more lights, is there a way to get rid of the message, it pop ups every time i render, clicking ignore or dismiss all, makes no difference.

by the way is it planed to support more then 255 lights? it seems like a limitation to me.

enabling develop mode shows options for solver and sampling mode, can we get some information about the options there? there are no tooltips for them.

thanks,
Guillermo Leal.

13

[Max] Resolved Bugs / strange error in Message window

« on: 2015-09-27, 19:50:50 »

something strange just happened.

I had 2 instances of max running, one had a scene using corona which was just open but nothing was rendering, and the other with vray, while i was rendering in the vray one the message window from corona started to appear (several windows showed up) with the message. the system is running low on RAM. 
I was running out of ram, whats strange was why is the corona message showing up if i'm running another instance of max with vray, not corona. it also showed an error window of wxwidgets but it closed before i could made a screen capture.

corona version is daily build Sept 24 2015

Guillermo Leal

14

[Max] Corona Goodies - User Contributions / Lightlister (script)

« on: 2015-08-24, 02:50:54 »

I needed the lightlister script to work with corona. plus some additional futures for vray so i created this script, maybe some one else find it usefull.

its based on the Lightlister that ships with vray which is based on the original that came with max.

the additions i made are.
- added support for corona lights, corona material and corona light material
- added tooltips to some parameters
- ability to edit ies files on vray, photometric and corona lights
- wider interface

history:

v3.07 :
fix: With corona Lights on initial startup, the wrong elements were being enable/disabled. I was missing +1 on the type of shape variable. (maxscript arrays start at 1 not 0)

v3.06 :
add: Supports for corona3 physical material
fix: on Corona Lights. There were several issues, Some parameters were not being created and then when changing the shape type it would crash the script
add: for corona material and corona physical material now we can control enable/disable of the self illumination texture and the amount of it.

v3.05 :
fix: It was crashing with the newest corona render (3+) as the corona material is now named CoronaLegacyMtl
fix: there was a crash when trying to add or change a texture for the corona material or coronaLight material and the user canceled the process of selecting an image
fix: for lightmaterials if it has a texture it wasn’t been shown

v3.04 :
fix: For some strange reason on some files with corona it was crashing when creating the dialogs, the problem was the method (units.formatValue) which i was using it on the tooltips for some parameters.
fix: Added some checks for certain parameters on corona lights
fix: updated the ranges for the segments on corona lights, it was from 0 -> 100000 which should be 3 -> 128. on certain systems it could cause a crash

v3.03 :
fix: there has been a bug in the function filenameFromPath for a long long time, I thought it had been fixed but not, so i use a custom function for it. that was causing a crash when getting the ies file when the file was missing.

v3.02 :
fix:    crash when deleting a corona light
add:    clicking on the material button now shows an option to select or edit the material

v3.01 :
add: support for coronal materials and corona light materials

initial release:
add:    support for corona lights
add:    tool-tips for the light name as sometimes they have a long name, you need to hover the mouse over the on checkbox as the textedit control does not has tooltips.
add:    tool-tips for some other elements
add:    edit ies files on corona , vray ies lights and max photometric

i know there was already the plugin from ecximer but beside that i didn't want another max version specific plugin i wanted the ability to add whatever i need it to it so i updated this script.

please if you find any issues or do any updates let me know so i keep the script updated.

if you want to use it as a macroscript you need to uncomment lines 135 to 139

you can download it in the following link.
http://www.evvisual.com/lightlister/

15

[Max] Resolved Bugs / Corona Lights display performance

« on: 2015-08-19, 01:05:16 »

I haven't found anyone mentioning this, maybe most people use very few lights. but the viewport display performance of corona lights its extremely slow. the current scene I'm working on has around 800 lights and its just impossible to navigate, i get about  2fps on a dual xeon 2650 with a cuadro k4200 and the same thing happens on an i7 with GTX titan, this on max 2014, 2015 or 2016. as a reference for vray lights i get about 9 fps, its also slow but much better.

am i missing something or this is just how it is with corona lights?

Guillermo Leal.