Title Block- Some attributes now missing w/ update

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report
Hi Ya'll,
Searched the forum and haven't quite found my answer to this, nor a solution.
Have been using a QCad generated .dwg title block for about 6 months now, no issue. It had editable attributes in it and life was good. Following the latest update, there are some hiccups I'd like to bring up and hopefully get resolved. I've found a nasty workaround but want your advice first.
My blocks looked like this in the past. Most of the text inside was editable attributes (screengrab from a PDF, image edited to protect my customer)
To confirm, my QCad file looks like this:
When I now open in Fusion any drawing that had this title block, I get something with this general look:
First take, you notice much of the text is "missing" now. Hum, did some digging and can't seem to understand why that is. However you DO see that the logo (blanked) and the DESC_1 and DESC_2 appear as they should. Also, when the block is edited, there appear to be ghost drag points where all of the attributes should be:
Trying to click the drag points, or anything near them, is fruitless. Notice also the static text listing drawing standards/tolerances is gone as well, and no editable attribute drag point is near that blank area of the box.
This leads me to believe this is simply related to the text color or layering is mis-coded somewhere. Clearly some of the pertinent data still lives in the block.
Interestingly, when I change the "Draw Order" in QCad I can get varying results to show in Fusion when I select the .dwg title block. I haven't locked down a method to the madness however (tried a dozen combos of numbers) but there IS a correlation:
(drawing order varies between 1, 0, 11, 2, 7, etc to give this in Fusion)
So you see, Fusion is trying to pull the correct information in, but something is going on here! It is almost like the Drawing Order has a limit, and a variety of numbers is required. Still haven't gotten that theory to pan out though.
Bottom line-Big issue with potentially simple answer. My workflow (and $$) will be hurt when I have to pay my designer to fix a feature that doesn't need to be (nor was) a problem until a few days ago. Thanks for your help.