fireflies

[akinlolu olugboji]

Why the fireflies.

Interior lighting scheme

30 lights 25W all spootlights

packet tracer 20 passes

[Roy Hirshkowitz]

The units did somehow get messed up in this one, I'm not sure how.  Although the thing is reporting INSUNITS of 4, somehow we're not picking up on it.  I suspect there's some bad legacy data here.  To fix it do the following:

1. Open the drawing.
2. Load nXt.
3. Type INSUNITS and enter 5
4. Type INSUNITS and enter 4

Some material scales may need to be adjusted.

 

[akinlolu olugboji]

That sure sources it but like you said had to rescale all material definition with maps.

[Roy Hirshkowitz]

Something really bad happened to this drawing.  I don't think I've seen this before.

[Ros. Riha]

Why not to try AutoCAD remedy then:

1. Open the fireflies.dwg using the RECOVER command
2. COPYBASE all entites you need
3. Create new empty drawing with correct units etc.
4. PASTE entites into it
5. Try to render - should work better.

[akinlolu olugboji]

Will give it a try. Thanks.

[Ros. Riha]

other tricks to clean up a drawing:

• killdots.lsp - deletes zero length entities
• expresstools OVERKILL command - deletes duplicated entities

[Roy Hirshkowitz]

None of this will save you from having to manually alter the material tile sizes, etc.. They were created with the drawing in its indeterminate scale format.  I'm very curious how this drawing got into the state it was in-- i.e. how did the INSUNITS report one thing but the AutoCAD API report another?

[Ros. Riha]

I know - I was merely putting together procedures that should everybody follow once using DWG data created outside "proper" AutoCAD - there is always risk something could be wrong and cause problems later...if akinlolu did this prior fiddling with materials, he might have saved himself problems he is facing now.

[George Ioannidis]

That is general rule I follow when importing anything into AutoCAD from application which is not.... ehm... AutoCAD :D

 

Strip it down to the bone, purge, merge, dodge, abolish, wblock, explode, audit, defragment, recover, annihilate, decompose, weld, transform, reorganize and then.... set the correct units. Sorry for that, I just couldn't resist. Don't get me wrong, OK? :D

[Ros. Riha]

Well, George, you have still much to learn - you forget to mention you have to position your carpet towards Mecca and kneel down three times and make your prayers while you are purging ...and (in turn) I have almost forgotten that "blood of a virgin goat" bit.

Now, seriously, it is worth IT to make an article on nXt wiki how to handle non-autocad-but-still-dwg-data... do it once and save yourself plenty of time

[George Ioannidis]

Ros, I forgot to mention appropriate sacrifices to Odin, to Zeus of mount Olympus, to Gitche Manitou and other gods  as well (no animal harm, please...)

As regards to carpet orientation, well, one can use GPS or other equal methods to determinate the proper position :D

My actual routine to transfer 3D data from my "other" application is rather straightforward. Never had any problem with that. Was there any request for some guidance on that here? I don't remember any.

[Ros. Riha]

yes, answering again one step up:

1. Who the <|> is the Gitche Manitou?
2. I should have imagined you Greeks would be very particular on GOAT sacrifice...
3. But still: What is your foolproof procedure to use not-quite-dwg data? let us put it all together (there is another related topic on TEXMESH command around here) and have at least an article on wiki to refer to...(improvement on TEXMESH would be even better)