[Thomas An.]

TRACKING STARTED (SEP-12-2005) for Rhinoll v0.7.0
_________________________________________

CRITICAL

• Empty

SERIOUS

• (S050923.00. Assigning an empty material to an object will cause a crash. Steps to repeat:
  • Open a new Rhino file
  • create one object (say a cube)
  • Open the material editor and create one empty material
  • Assign material to the object and render
  • Rhino will crash
• (S050919.00. Materials from the current Rhinoll file will "leak" into the next if you use the "open" command to open an old file (or template) that contains no Rhinoll 0.7.0 plugin data, or no Rhinoll data of any kind (completely untouched by Rhinoll). This can mess-up the material library of the files. Reported by: Micha
• (S050914.00). Do not use the minimize button of the material editor. If the Rhino file is saved while the material editor is minimized then weird behavior occurs that results in either a crash when attempting to open the file on itself, or the editor becomes useless and no more materials can be added. - Reported by Frances

AVERAGE

• (A050925.00). Rhinoll writes the MXS using all bitmaps of all materials of the editor; instead of sending only the ones actually in use.

  Bug: I have some materials in my editor with textures, but in the scene I have used only a dielectric without any texture, but the MXI viewer say for a long time "Loading bitmap" and in the scene data I find bitmaps too. Rhinoll load unused bitmaps to the mxi scene file.

• (A050920.00).

  I just noticed that the fog setting in the environment is a radio button instead of a check box. Can't apply it without turning off the physical sky!!!

• (A050920.01).

  ....it is possible to use the same name twice in the material edito. I think, this is not so good and could bring confusion. Maybe be good, if Rhinoll say something like that "Current name is existing, please use an other".

• (A050918.00). The 125% and 100% values are in reverse order in the viewport-scale list. Reported by: Micha
• (A050916.08). The Z Buffer range values have no effect. Reported by: Micha
• (A050916.07). When checking the Z-buffer channel, then a cosCamera channel is rendered as well. Reported by: Micha
  Related issue: Selecting the CosCamera channel all by itself has no effect. A cosCamera file is not being created.
• (A050916.06). The "same as 3dm" option does not stick when the current Rhino model is saved under a yet different name. Result is to output a render under the previous name ovewriting the olded mxs and image files. (unless the checkbox is manually touched; unselect and re-select again). Reported by: SMB
• (A050916.05). There is something wrong with the sun system: For example for NewYork at hour=12 day=5 the render appears dark (twilight ?) but when I look outside the window it is high-noon. (Is this a "solar time" vs "Mean time" discrepancy ?)

  This is a engine problem not a plugin problem i think.

  Links to sunsystem related bugs reported in the main Maxwell section:
  Link1: Detailed summary of sun bugs, with test scenes and more info
  Link2: Sun position calculation bug - revisited
  Link3: Bad sun beahivour and calculation

  ...It's not hard to fix, as the sun simulation is actually pretty good - there are two things to change:
  The longitude coordinate must change sign to get to the correct hemisphere. As a side effect this will change the north/south vector (whatever axis that is), so the the north vector has to change sign so the sun is at the right position regarding north/south.
  That's basically it - it really takes less time to fix it than to find it - so please, NL...
  .....
  Well, comparng the Cinema sun with the Maxwell sun does make sense, when you take care to compensate the Cinema time for both, your current local time and the local time of the scene. So if your computer is set to timezone +2, and would like to render an image taking place in timezone -3, then you have to add 5 hours. Strange, but true. In fact, it turned out that the Maxwell and the Cinema sun have indeed the same south direction.

• (A050916.04). Something isn't right about the Hyperfocal distance calculations. The values do not check with the results seen here: http://www.dpreview.com/learn/?/Glossar ... eld_01.htm
• (A050916.03). When first opening a Rhino file with a scene that already contains materials, then several objects appear selected even if the material editor is not active. As a mater of fact even if Maxwell is not the current renderer then Rhinoll still manages to select materials when Rhino first opens.
• (A050916.01). Applying materials via layers causes an empty material named "Dielectric", instead of the generic "Material" name.
• (A050916.00). Material editor should not close merely by pressing the enter key. - Reported by: Holger
• (A050914.00)

  ... if I minimize the Rhino window, than the material editor stay a the screen like a separate window. If I click on the rhino tab Rhino dosn't come back, only "wiederherstellen" (rebuild ?) helps.

• (A050913.00)

  I can't see my textures and material colors in the rendered viewport, am I doing something wrong?

• (A050912.00)

  Here a first small bug: the render region dosn't work per menu in the german version. But if I type "_RenderWindow" it works good.

• (A050701.10. The default film width and height (36mm, 24mm) will produce a render that is a mismatch with the Rhino Viewport. When the film width and height are 24mm, 24mm the result is correct.
  
• (A050701.08. The longitude/latitude data are not in a D.d form.
  http://jwocky.gsfc.nasa.gov/teacher/latlonarchive.html

SOLVED
Issues solved from previous Rhinoll version:

• S01 (SOLVED). 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.
• S02 (SOLVED). Assigning materials to block instances not supported.
• S03 (SOLVED). City names are not sorted alphabetically.
• S04 (SOLVED). When Rhinoll becomes the current renderer then the "Render" tab in Rhino options should be replaced with the Rhinoll "Maxwell" options tree.
  
• S05 (SOLVED). Materials not saved reliably in the file, they are lost unpredictably after reopening the 3dm. It can happen with large scenes as well as small scenes. Sometimes merely working on an object (joining, trimming, exploding surfaces) will cause other objects to lose their materials. Other times when the materials are lost the render view still shows the textures although Rhinoll cannot retrieve the info.
• S06 (NO PLUGIN FAULT). (A050916.02). In the layer properties, when pressing the create button, the new material name is not instanteneously shown in the text box unless the "Browse" button is pressed afterwords.

  About the layer material assigment i think that is most a Rhino problem, i have tested with rhinoman and it has the same problem. I think that rhino doesn't update the material name for the layer when a new material is created, and i don't know at the moment if i can do something, or only rhino can do it.

HISTORY
Links to previous bug reports

• Rhinoll beta 0.6.1 bug reports

[Micha]

... Pablo and Thomas thank you for the new release.

Here a first small bug: the render region dosn't work per menu in the german version. But if I type "_RenderWindow" it works good.

[Thomas An.]

Hi everyone,

Please try to test this Rhinoll version (0.7.0) as much as you can especially against old issues to make sure they are gone.

Of particular interest is the old material loss issue. I haven't been able to reproduce it with the new Rhinoll, but please report if you find occasions where material loss still persists.

[hyltom]

I noticed a strange behavior with the editor.
If I had assigned few material to different objects and then click on one material name that have been created, the corresponding object is selected. But if after that I select an other material, the first selection is kept in memory and the corresponding object of the new selected material is also selected. is it clear...may be not! I can do it in french if you want

Hyltom

[Thomas An.]

I noticed a strange behavior with the editor.
If I had assigned few material to different objects and then click on one material name that have been created, the corresponding object is selected. But if after that I select an other material, the first selection is kept in memory and the corresponding object of the new selected material is also selected. is it clear...may be not! I can do it in french if you want

Hyltom

Hyltom,

I know what you mean ... but ... it is not a bug. Go to the MaterialEditor-->Material (Menu)--> Put a checkmark in the "Replace Selection" option.

[hyltom]

that's perfect

Thank you very much Thomas.
Hyltom

[Thomas An.]

Hi Thomas
problem: no write MXI file

thank you
giorgio

Can anyone else confirm this ?
So far I have not seen this problem occur.

[Polyxo]

gurk wrote:
Hi Thomas
problem: no write MXI file

thank you
giorgio Sad

Can anyone else confirm this ?
So far I have not seen this problem occur.

Yes, I've seen that too, but can't reconstruct it right now. As soon as all objects had a Maxwell Material, it worked.

[Micha]

only a small bug again:

... if I minimize the Rhino window, than the material editor stay a the screen like a separate window. If I click on the rhino tab Rhino dosn't come back, only "wiederherstellen" (rebuild ?) helps.

[Thomas An.]

only a small bug again:

... if I minimize the Rhino window, than the material editor stay a the screen like a separate window. If I click on the rhino tab Rhino dosn't come back, only "wiederherstellen" (rebuild ?) helps.

Got it

Thanks !

[Frances]

This is also related to the Material Editor dialog and large scenes.

Steps:
1. minimize the Material Editor dialog

2. save the file

3. while the file is saving, open another app's window over top of Rhino

4. when the file is finished saving, the Material Editor dialog cannot be maximized

Notes:
a. If a scene takes more than a few seconds to save, I get bored and do something else. Trying to re-open the file in the same session crashes Rhino. Creating a new file in the same session doesn't let you maximise the dialog even if you close it prior to creating the new file.

b. In order to get the dialog back, I have to close Rhino and re-open the scene to get it back.

c. Workaround is to not minimize the Maxwell Material Editor if the Rhino window loses focus during a save operation.

[added]
Looks like material definitions are lost on a Rhino crash.

[Thomas An.]

c. Workaround is to not minimize the Maxwell Material Editor if the Rhino window loses focus during a save operation.

Got it.
Thanks !

Yeah, there is something wrong about saving a file while the editor is minimized.

[Polyxo]

Just a small thing, if not mentioned before: All newly created materials are called dielectric (number) and will keep this name, although I make say a plastic material out of it. Wouldn't °Material(number)° make more sence?

Holger

[Thomas An.]

Just a small thing, if not mentioned before: All newly created materials are called dielectric (number) and will keep this name, although I make say a plastic material out of it. Wouldn't °Material(number)° make more sence?

Holger

Yeah, this is known if you apply materials via layers. Do you see it happen in other situations too ?

Also, (you probably know already) you can double-click a material name to re-name it.

[Polyxo]

What I do is: Open a new file. Create some geometry or leave it and just open up the Material Editor from the menu. °Rightclick over Library field/Create empty° or °(Material Editor ) Menu: Material/create empty° will create an empty material called °Dielectric0°
Has nothing to do with assignment.
Yes, sure, one can rename them, but Material0 appears unnamed, wheras Dilelectric0 already suggests a property. Could be irritating.

Holger