New Service release on 7-10-2012

I just posted a new service release for NXT which includes these improvements:

Many crash dumps fixed.

Added “Use Rhino viewport and size settings” option to the Automate Render dialog which is on by default. When this is set and automation is enabled then the active Rhino view is always rendered using the size specified by the active Rhino or Bongo settings.

Refined mapping widgets by constraining to the active construction plane instead of the X-Axis circle plane causing the widget to get wonky when dragging around. It should improvement mapping a plane and box mapping.

Changed tooltip in the render output window for the Export EXR option, it incorrectly said Export EPIX.

Fixed error when disposing of post-process bitmap.

Fixed file bloating when exporting a few curves from a model with a bunch of materials that contain textures.

Batch render definitions could duplicate themselves. We put a clamp of reading/writing 100 definitions as a safeguard.

When a block is inserted and there are less than three instances of the block Flamingo transforms the block definitions render mesh to the inserted location. When this happens the mesh face normals were not getting transformed causing blocks that are rotated to render black. This is now fixed.

Null pointer reference found when processing crash dump file.

Fixed - Setting numeric control to value outside of valid range causing exception to be thrown in the sun settings pane in the nXt control panel.

Fixed - Setting numeric control to value outside of valid range causing exception to be thrown in the simple texture material editor.

Yes I get it too. That doesn't mean there's an update available though. I have the latest version, so it means something's got a bug... Probably the nxt taskbar util. Or it's not finding whatever it's checking for online.

I also get the same problem...somewhat annoying to say the least. What I am even more surprised about is that there has been no reply to several inquiries on this topic. Is there a release coming out to fix the problem? Or will we have to endure a critical update balloon every time we fire up Rhino. Scott we await your insight with grave patience.