@bmike said: @unknownuser said: @bjanzen said: Yes. This is a known issue on Windows. When you launch both apps, if you "Run as Administrator" it'll work. b Yeah tested this by sending one model to LO, then made new one saved and tried sending, no luck. My user account is an administrator, well, the only admin on this comp. Using vista home premium SP2, not sure if this is an issue... Cheers again Pretty sure you still need to tell the program to run as admin... If you right click on the .exe icon to launch, you can get to a check box under advanced. This should keep the setting so you do not have to right click each time. Ha yeah that did the trick, learn something new everyday Thanks bud

It should be, and I'd be interested if you have a reproducible case where it isn't. Where it definitely is not robust at this time is if you dimension in LayOut, then make a bunch of geometry changes in SketchUp to the model. The points we attach to in your 3D model are not persistent / uniquely ID'd so that we can say that we can find the point you wanted after the geometry changed. For this reason, we'd recommend doing dimensions after the modeling has settled down. Anything more specific? Modes of how to update the model, or workflow? We'd also suggest turning auto rendering off, and controlling model rendering yourself for larger documents (when there are model changes); you can right click on a page with dirty models and select "Render Models on Page". b

Hm... Barry and Jeff, here is another post about the same colour profile issue (although the calibration was different there). I even reported it about 2 months ago...

I like Layout. I tried to get away without it for a while, but it is invaluable for sending drawings to clients and subcontractors. Aside from the bug just mentioned, my largest frustration is that I have to command click on each view repeatedly to set scale, scene, and view. If the contextual menu could be rigged to stay open until I'm done it would make the work surprisingly faster, especially given the bugs I just mentioned. BEst, Jim

Thanks! The Auto-render box, when selected, did the trick. I didn't catch that one, and still unclear about the difference between checked and unchecked, but that solved the problem..thanks for your time..I really appreciate that....thanks too Matteo....

I'll try to respond both here and to Google Help: we did test our files on 10.4.11 (and one machine with ATI 1600 - the common MacBook Pro graphics card of 2 years ago), and we're not seeing it. To send in the file, Help->Contact Us->File a Bug and you can attach a file to the bug you're reporting. I'll get it from our support group and we'll test with your OS & graphics card, and this time with your file. Thanks. We have had a regression bug from LayOut 1 where this would happen, but we haven't seen it lately. Just for grins, upgrade to 2.1.5803 if you could: LayOut->Check for Update.

Ah - so what's your OS and what's the fileserver OS? We put things on a server all the time, but it could be that we're not getting a consistent / true file status. Let me know, and we'll try to duplicate it and fix / change if possible. b

Tim - if you can send me the file, I'll take a look, fix it, and see if we can categorize it. b

Thanks guys. Some info about this problem: 1- There are no text saved at all, on any of Xml files; 2- The problem isn't only about the text - some imported images disappears too, and the LO shows a red "X" on screen over those objects; 3- If I have some 4 or 5 objects from one or more big sketchup models, and some images and text, the problem occurs when activating the "hybrid" rendering on those objects - then some bitmap images "disappears" from screen - next time to try open the file, and LO shows this message then exit: "Microsoft Visual C++ Runtime Library - Runtime Error! - Program: (empty) - This application requested the Runtime to terminate it in an unusual way. Please contact the application's support team for more information". Even the debug window do not shows up. The system is a XP64 still Sp2, with several GB of Ram, and LO never uses more that 1.5 GB.

I'm n ot sure you can use ruby for LO U(at this point at least). But I think the development team will soon find out something (this is always the case with new OS X issues).

First, try to save to multiple locations - is there something wrong with where you're trying to save the document? Try "Save As" and see if you can rename. If you're saving to a network drive there can be issues. The file is not "Untitled" so you've saved before, and maybe it looks like a file system issue. b

@gpaul said: Hi Tim, I'm Paul McLean and I am the Google engineer who is mostly responsible for text in LayOut. Thanks very much for explaining the problem. @gpaul said: What you are trying to do is a great idea and entirely reasonable. The hitch is that LayOut stores text in the document in RTF format. RTF does not support alpha (transparency) values for font color, so that information is lost when the internal text engine generates the RTF for LayOut to store. Granted the UI shouldn't be giving the user the expectation that alpha is supported for text (this is a logged bug and not as easy to fix as you might imagine). Ah, right. Good old RTF. I don't suppose the colour table in indexed by the font foreground command can include transparent colours? Probably not. RTF was carefully designed to be infuriating... @gpaul said: A work-around might be to create a "water-mark" image with transparency (PNG supports this) and overlay that on the page. Put it on a layer by itself and it will stay out of your way when editing the document. Yah. Excellent idea. I already have the text on a layer so I can easily turn it off when the drawings are printed in final form, so this should be easy. Thanks again. [Edit] Created a PDF file with just the large text in low-opacity colour, inserted it into the draft layer and presto - no more issue.

@bjanzen said: This speaks to unbounded versus bounded text boxes, [snip] Ah, I see what you mean. I'll modify my bug-claim then - the unbounded table seems to be really unbounded. It doesn't have a right edge (that I can discover) at the right edge of the paper area and in fact seems to place it completely off the right of the 'world'. If the bounding box of the unbounded box (urk!) were actually selectable it would be easy and obvious what needed doing. I would also tend to expect that swapping from unbounded to bounded would create a bounding box around the available text i.e. typing some text and going unbounded>bounded ought to return the box to where it started.

In the file attached you can find both bugs: Some text disappear when rerendered in raster mode Some lines of the section slice are not with their proper lineweight bugfile.layout

@crt said: Yes I did update my scenes... Yes, and with the scenes you should have updated your styles as well - that's why I asked.

@cannon5598 said: Hi all, I do however have a small problem with Layout (I know it is still Beta) but when I try to save a drawing A1 as a pdf it is always blank, is there a work around or is this to be fixed. Try LO 2 and see if its working now. It has much better handling of large page sizes now. It even has multi-core support. (Win only for now)

Thanks for the reply Anssi, I actually just resolved the issue. Apparently it's an issue with the particualr template that I was using. Default/Template/Titleblocks/Rounded/letter/right. When I choose the same template but in a "block" rather than the "rounded" version, it works just fine.

Are you on Windows? You could try registering the SketchupViewer.dll- LO probably can't find it. Open a DOS box, and cd to here- C:\Program Files\Google\Google SketchUp 6\LayOut or where your layout.exe is installed. Then do- regsvr32 SketchUpViewer.dll This should popup a dialog saying succeeded. If it doesn't say succeeded, then reinstalling is best.

The beta isn't out yet... I just tested your doc and the arrows exported correctly.

[edit] okay so i just realized which forum this was posted in (i use view new posts instead of browsing individual forums)... at least i now realize what 'LO' stands for in the above posts.. please ignore the following maybe i'm not understanding your problem correctly but i just tried --> --open two windows - one set to decimal/mm and the other to architectural/inches.. --in the decimal window, draw a circle measuring 20,000mm diameter and group it.. --copy that group and paste it into the architectural window.. --measure the diameter which is ~65' - 7 3/8" that's a correct conversion... is this not what you're trying to do?