Space Design - Version KE13 - Possible Bug ???

Replies to This Discussion

Permalink Reply by Howard Leslie on May 14, 2011 at 3:40am

Al,

Ignore above Bug Report !!!

I've got Space Design KE13 running OK now.

I've got no idea what was causing Bug but its now stopped !!!

...............

Filtering works well.

Rattled thru a massive model in seconds and produced a report.

...............

Thanks once again for producing latest version.

Howard L'

• ▶ Reply

Permalink Reply by Render Plus on May 14, 2011 at 6:11am

I had a similar problem when I set a filter to an attribute which was not actually set.

 

I'll take a look and try to fix it for future versions.

 

If you do get the same problem again, try opening the ruby console. If you can send me the last few ruby messages before the error it will help me track it down.

• ▶ Reply

Permalink Reply by Howard Leslie on May 15, 2011 at 3:33am

Al,

See attached txt file, may help.

Info from Ruby Console just before error message appears as suggested.

..........

Regards

Howard L'

 

Attachments:

• SpaceDesignKE13-Bug_RubyConsoleDump.txt, 6 KB

• ▶ Reply

Permalink Reply by Render Plus on May 16, 2011 at 6:45am

I will add some better rubu console messages to try to trace this.

 

If it happens again, open the ruby console and enter:

 

$entity

 

and

 

$entity.name

 

If it is a component instance, try also:

 

$entity.definition.name

It sould also help if you would save the model and send the .SKP to support@renderplus.com

 

• ▶ Reply

Permalink Reply by Render Plus on May 16, 2011 at 7:44am

Were you filtering on material names.

 

I found a bug which could cause this problem if you were filtering on material names and the component on group did not have a materials.

• ▶ Reply

Permalink Reply by Render Plus on May 16, 2011 at 2:43pm

We posted a new version which may fix the .name problems, or at least should give some better error messages.

• ▶ Reply

▶ Reply to Discussion