[ARCHIVE] Pre-1.0 Daily builds

[blank...]

@blank... : can you give an exact list of repro steps begining with starting max as fresh start?

1. start max
2. switch renderer to Corona
3. create a plane, about yea big
4. create a teapot
5. orbit aimlessly around teapot to confirm that it is in fact, a teapot
6. create Corona sun (not daylight system)
7. click to add corona sky under Coronas sun properties
8. hit F10 an switch secondary to Path tracing
9. assign Corona material to everything
10. start IR
11. orbit aimlessly around teapot and marvel at your creation and how nice the shadows are
12. grunt a little about the fact that Corona has issues with low poly objects
13. grab any bitmap from your computer and drag it in slate material editor
14. plug it in displacement slot
15. watch it crash and burn.
16. start max again
17. repeat steps 2-9
18. don't start IR
19. try it with normal rendering, about hmmm... let's say 30% of the time, it will also crash.
20. nothing for 20, it just looked silly to end a list with 19 :)

[borisquezadaa]

Hello Everyone, I would like to make a really important post, so please read it carefully.

I will start with the basic information about dailies, testing and guidelines of reporting the issues.

•   Daily builds are development builds to test the functionality of the application.
•   They do not always represent the final product.
•   They will have bugs.
•   Use it at your own risk at real production. Dailies are for the brave.
•   We are giving you the access to them, so you can find and report problems, stability issues and bugs.
•   For reporting bugs USE MANTIS. Posting on forum or in thread is NOT enough.
•   Posting on forum or in this thread without stating version of the build, OS version, max version is completely useless info and wasted energy.
•   If you feel the necessity to write a post in a thread, please always state a following info:
severity of the issue, how to reproduce issue, OS version, 3ds Max version, any plugins which you are using in project, short summary and description of an issue
•   Issues reported in Mantis will receive feedback. (Sooner or later)
•   Every reported issue is then replicated by our Support Specialist – Marcin Miodek (Maru)
•   If we cannot replicate the issue or if it is obvious that the problem is caused by the user rather than software, then this issue is ignored and user is notified via mantis.
•   Posts in this thread or daily builds thread can slip undetected > So use mantis.
•   Posts in this thread or other daily builds thread might be registered by us, but we do not necessary answer on these as we would be doing nothing else than writing responses.
•   Please do not expect that we will immediately react on posts, we are a small team at the moment. So it is not possible. If you need an answer. Write “URGENT” in the beginning of the post or send us an email to info@corona-renderer.com or fill in a support ticket via www.corona-renderer.com/help
•   Please use mantis
•   Please use mantis
•   Please use MANTIS
•   If you will not follow the rules, you will be kicked out from daily builds :( 

I hope that we can all agree on these simple rules. It will make our lives as developers much easier and we will be able to react and fix the issues in an effective way. We all want one thing, to create the greatest render engine possible and we cannot do it without your help.

Thanks for your understanding and for all your testing efforts so far. Corona would not be what it is now, without you.

[juang3d]

@borisquezadaa This is already posted in mantis, we are just discussing it here :)

@blank... I had no luck at first (with the crash), everything was working great but then I used a new bitmap, a different one, a gradient, and I'm not sure if it crashed because my teapot had 200 segments+1 turbosmooth (I played with segments with IR active without a problem) or if it crashed because the displacement, repeating test now.

Cheers!

[juang3d]

I just repeated the test, and I can't manage to crash it with displacment, however I found some strange behaviors, I've been playing with the testure tiling and I found that the IR was not responding well, I disconnected the displacement, reconnected it and it's behaviour changed and started to be correct again, but then i changed the tiling again, from 1 to 2, then to 5, then to 10, then to 1, and I moved the camera and this is what I found, something weird is happening with IR, displacement and the camera fustrum.

I'm not sure about repro steps, as soon as I can reproduce it with clear steps I'll post it in Mantis.

Cheers!

[Ludvik Koutny]

Displacement won't update on view change. That would make IR unusable in pretty much any scene that has displacement in it, because displacement would have to re-tessellate with every view movement, and that would make navigation ULTRA-slow. To refresh displacement, simply move timeline.

There was a "refresh displacement" button planned, but didn't make it into 1.0

[juang3d]

Ok, so it's not a bug :)
Thanks!

About the crash, I wasn't able to reproduce it again, I've been playing with displacement, different textures, different geometry density, and no crash at all :P

Cheers!

[Ondra]

found possible cause. RC3 rolling in...

[lacilaci]

I can only make it crash only if during one IR session I plug-in noise to displacement and after that I disconnect noise and drag from displacement in slate material editor into open space and from there load a bitmap!

just as in that video... otherwise pretty stable for me.

[twoheads]

I can only make it crash only if during one IR session I plug-in noise to displacement and after that I disconnect noise and drag from displacement in slate material editor into open space and from there load a bitmap!

just as in that video... otherwise pretty stable for me.

I got the same problem when I disconnect noise and connect other map to displacement slot. As my predecessor wrote everything else seems pretty stable.

[Ondra]

RC3 ETA 20 minutes, any testing will be appreciated

[gk]

First post I guess.
I'll give it a spin.

[twoheads]

the night is young, lets give it a try :)

[Ondra]

Dropping RC3. Changelog:
some tooltips wording improved
fixed assert when closing licensing and DR server from tray
renamed DrConfigA7.2 to DrConfig-1.00
fixed crashes with displacement + bitmap textures

[lacilaci]

Dropping RC3. Changelog:
some tooltips wording improved
fixed assert when closing licensing and DR server from tray
renamed DrConfigA7.2 to DrConfig-1.00
fixed crashes with displacement + bitmap textures

That IR+bitmap loading crash is still not fixed! Watch the video from mantis and replicate Slate material operations exactly as in the video.. crashes every time..

Loading bitmap during IR is not a problem, problem appears only if IR is running and you plugin noise and then unplug and load NEW bitmap from disk directly connecting it to displacement..

[gk]

RC3 loads and plays back files, I have no issues so far.