Jump to content

mqudsi

Members
  • Content count

    153
  • Joined

  • Last visited

About mqudsi

  • Rank
    Advanced Member

Profile Information

  • Gender
    Not Telling

Recent Profile Visitors

441 profile views
  1. mqudsi

    Vector EPS loads extremely aliased

    I don't understand your question. It's the same document zoomed to the same level. But it's not an issue of scaling, straight lines are being rendered as blocks, curves are broken (look at the letters), many artifacts.
  2. EPS is attached. Comparison with Illustrator: Background ramadan mubarak vector design set 15.eps
  3. I have an AD file that has some text from a font (Lavenderia) that has overlapping glyphs. They are displayed and rendered correctly in AD, but upon export (with or without rasterization enabled), the stroke around both the behind and in front character is visible (i.e. the rear glyph's stroke is not obscured by the front glyph's stroke). in AD: Resulting PDF:
  4. mqudsi

    High idle GPU usage

    Just experienced this again. Went through all the tabs and hit 'ctrl+d' as per your instructions in another thread, but no effect. ~60% GPU and 20% CPU (out of 8 cores) doing nothing:
  5. I don't understand. Everyone is reporting different results. I create a document then add a second art board (to the right of the first) and I end up with artboard 2 on page 1 and artboard 1 on page 2. That's the exact opposite of what @walt.farrell is reporting?
  6. I don't know if you're seeing the same crash that I'm seeing, because mine traced back to a null dereference in libraster during the draw operation.
  7. No, they're all local. Nothing special about the on-disk layout.
  8. Do you mean in the opposite order that they were created?
  9. @Chris_K and others, just ran into this again with 1.6.4 and caught myself before submitting for print at the last second. This isn't an issue with PDF's patchy support for embedded content, there's a bug in AD that is causing extreme bitrate starvation in the jpeg compression when a downsample is triggered from an embedded document. It's important to point out that "embedded document" can mean something as simple as a JPEG that has been dragged onto the canvas. Please look at the following two PDFs. They're the same file exported both "for print" and "for export". The "for print" is not even usable on a dot matrix printer from the 90s let alone professional printing. The "for export" exhibits compression artifacts (far greater than I'd expect) but it's at least usable. The other one, despite still being 2MiB in size, is absolutely unfit for any purpose.
  10. @Chris_K in the closed duplicate thread, you wrote: Yes, I see some basic CMYK profiles there (such as US Web Coated SWOP). However, none of these appear in the print dialog's color profile drop-down. Is that a bug?
  11. I don't think that should preclude it from activation when being clicked on, though. A regular "group" can be clicked on to select, and this is more or less just a special group.
  12. Thanks, @Chris B I would appreciate if you could post a beta build with the fix for this as soon as it's available. It happens in a lot of other cases when simply moving or resizing regular content in embedded documents (not just past the edge of the canvas), I lost a lot of work yesterday thanks to this combined with the lack of ctrl+s within an embedded document.
  13. 1. Create new document 2. Add artboard 3. Export to PDF The resulting pdf has artboard 2 as page 1 and artboard 1 as page 2.
  14. AD's "print range" feature when printing set to "document" results in an usable rectangle centered on all artboards rather than printing an artboard per page (or at least offering that option). e.g. currently designing a tri-fold brochure, so I need artboard 1 to print on one face and artboard 2 to print on the other. AD only lets me print one or the other via manual selection, while selecting the desired "document" range results in the following: This is what my artboards look like, each is an 8.5x11 document:
  15. Thanks, @MEB. Glad to know it's considered a bug and not by design for reasons beyond my limited comprehension! Cheers.
×