[znouza]

Rhinoll 0.5.5 is now UNUSABLE for older scene files without some cheating around, see bug 1

1. SERIOUS - http://www.maxwellrender.com/forum/viewtopic.php?t=2707

2. City names are not sorted alphabetically

3. (SOLVED) Version information in 'about' is old (shows 0.5.1) (the same with rhinoll loading in log messages)

4. hour accepts values more than 24, day the same - error box appears, but dialog closes and value is set eg. to 40 (in day/hour input box) (oldbug)

5. sky dome intensity allows to set negative value (error box appears but dialog closes)

6. allows the scene name leave blank - it'll create ".mxs" and ".jpg" (".tga") files

7. checking 'Render only channels' should deselect 'Open Maxwell display', the same with 'write mxs only' too

8. SM disallows to enter negative values (this is bad, our timezones HAVE negative timezones too)

9. bad Sun behaviour.. see post in Bug forum: http://www.maxwellrender.com/forum/view ... 6779#16779 (oldbug)

10. Materials not saved reliably in the file. I have several instances where re-openning a model has some materials simply forgotten. There is not a pattern as to which ones are forgotten. Sometimes its dielectrics, sometimes emitters and so on (and other times they work as expected) - reported by Thomas An (oldbug)

11. Copying from one Rhino instance and pasting to another Rhino instance will cause the render options of the second to be lost and replaced with those of the first. It will also (occasionally) cause the lens length to jump to something unusual (eg from 50mm to 7mm) - reported by Thomas An (oldbug)

12. Material assignment to more selected object causes Material Error bug. Reported by Frances and Olivier Geoffroy.

[Micha]

... environment sytem dosn't work right (old bug). For example I get no light at 18.00h in Berlin in may.

[Thomas An.]

Materials are not being stored reliably. There are instances where materials are either completely or partially lost after closing and reopening a file.

[Frances]

I'm finding that I get the Error creating (material type) material problem if I assign one material to too many objects at once.

[Tyrone Marshall]

deleted

[Thomas An.]

OLD Bug: Copying from one Rhino instance and pasting to another Rhino instance will cause the render options of the second to be lost and replaced with those of the first. It will also (occasionally) cause the lens length to jump to something unusual (eg from 50mm to 7mm)

[Thomas An.]

Assigning to more than one object generate error creating material type and I have to go back

Yes, this is repeatable and it is a hindrance.

Also, I am working on a scene for a few days now and have been careful to assign materials one-by-one... but today all the materials are gone except the emitters.
-

[iker]

For bug 12 : assign material to several objects at once.

- This only happen when you link to a color map (plain color are OK).

sometimes happens without linking a color map as well

- There is a turnaround which is to select each object individually and then open and close the edit material dialogue. This allow to render.

sometimes works like that, sometimes not, sometimes even renders with a standard diffusse, and when I change just the color (not color map) doesn't render (Error creating diffuse material, or Plastic,etc)

[Thomas An.]

Znouza,

#3 has been resolved

#13 http://www.maxwellrender.com/forum/view ... 0026#30026

[znouza]

I have studied the problem of the missed materials .
.. snap...

Hi lisux..
I've created one scene today.. after I rendered first image, saved the file, close Rhino and reopen the same scene, near all the materials were lost, including diffuse, plastic, emitter. Only metal stayed with the file I'm using RH3 SR3. The same situation - set render properties, presses Render - got Material error.. presses again, and render started... :/

[Thomas An.]

It seems to be a Rhino problem with the plugin ....... but rhinoll uses a lot this buggy stuff

Pablo,

This doesn't sound very promising

This rhino developer have said me that the SR3 solves some of this problems and is one of the reason because Brazil only works with this service release.

I don't think it solves any of the problems.

All the problems were generated while using the latest Rhino V3 SR3c (21 April 2004).

[znouza]

Ok, it's only one posibility, like i have said before i'm working closely with some rhino developers to solve the problem.
Please can anybody send me one scene that causes the error so i can debug it?

Thanks

I'll upload the scene to my server tomorrow (for mail it's tooo big (40megs)) and send you the link.

[hyltom]

Lisux,

what you say sound very strange to me. I have used Rhinoman (plugin for Rhino that allowed you to render with Renderman, AIR...) during one year and I never get any missed materials. As far as I know, Flamingo is also a rendering plugin and I never heard about such problem. So I 'm not sure that this problem of missed material is related to Rhino. Anyway, I hope that you can find the solution. I also used Rhino 3 SR3 and every time I make a scene (with few parts) I got the message - Material error. Sometime i must try to click render around 10 times before maxwell start. And as Znouza, I always lose my material when I reopen my file.

When I read that you want to receive a scene that causes the error, you really scare me...I want to ask you which version of rhino are you using? It seems that you can not reproduce these error

I really hope that you can clear these problems asap, it's really annoying.

Hyltom

[Micha]

Bug or Wish:

The default Rhino DOF looks very ugly for me. It seems to be a problem of the default diaphgram - the DOF blur look like a camera shake during the shot. Two solutions could be useful for the next rhinoll release: more camera control or other internal default camera settings. Please, please, please an small update this friday.
Or can I set a command for an other diaphgram?

[Micha]

Today I have tested the MXI option in Rhino. It works fine, but if I uncheck the option and delete the path, than Rhinoll ignore this and try to read a mxi file again and break with error. Seems to be a bug.