Jump to content
THESE FORUMS ARE READ-ONLY: Please Read Me ×

Jon P

Staff
  • Posts

    3,364
  • Joined

About Jon P

Profile Information

  • Gender
    Not Telling
  • Member Title
    QA

Recent Profile Visitors

8,470 profile views
  1. @big smile Can you upload your file here and mention which PDF presets are causing an issue (if it's specific to the preset) and I'll look into it. We do already have another issue logged relating to the fix so are aware that there is more to it. Edit: Sorry, forgot to add dropbox link, to keep it private upload it here
  2. That line is coming from the svg itself, if you zoom in within your document you can see it. I would advise re exporting that SVG out from what created it, potentially just as a PNG instead, as all the SVG seems to contain is a base64 image that's clipped, which I believe is causing that line to appear
  3. You are welcome to save as a package and I can take another look and see if I can reproduce it, the above link should still be active. If you replace the svg with itself in Resource Manager does that help?
  4. Thanks for the report @NotMyFault. This should be fixed in the latest beta just released
  5. Thanks for that, the issue with that image is also present on 2.6.2 for me so it doesn't look unique to the beta, that embedded bmp (If you open resource manager it's called Image.bmp) seems to be partially corrupt (it renders the corruption at certain zoom levels so maybe that was why it wasn't seen before), or missing some data which is causing the issue. It's embedded and looks like it potentially came from your clipboard, do you have that image still, or can you look at downloading it and replace the embedded version with it again?
  6. Hey @diwatamnl, welcome to the forums! Would you be able to attach the file or upload it here (if you'd prefer to keep it private). I'll open the file in 2.6.2 and 2.6.3 and see if I get this box appear Thanks
  7. Thanks for sending the file, i've reproduced the crash with your file. From what I can see it's not a 2.6.2 regression, it was crashing for me exporting in 2.6.0, but definitely didn't get covered by a couple of DWG/DXF export crash fixes that went in for 2.6.2. It's now logged with us, thanks again for the report!
  8. Hi @Fixx, If you can upload the file here it will be private and I'll look into it and log it if I can reproduce the issue. Thanks
  9. Hey @dcarvalho84, Sorry for the late reply, but that crash seems to be related to loading a font, so we may need a copy of your system fonts to reproduce it. Has it still been an issue for you in the latest betas?
  10. Thanks @MikeTO, we spotted this whilst looking into a similar issue and it's fixed internally, should hopefully be fixed in the next beta (subject to some more testing!)
  11. Thanks Mike. I've reproduced that and logged it
  12. @MikeTO Just to update you, the preflight error when loading the file from 2.5.7 is by design due to a change that's been made for 2.6, and Fix should always clear them up (your other issue is being investigated, as that should be being fixed).
  13. Thanks for the feedback @MikeTO. I've reproduced both your comments and logged them as separate issues
  14. Hi @Laganama, Many thanks for the report. I've reproduced this, it's due to the layer on the master page. If you move the objects out of that you should be able to disable facing pages without encountering a crash. I'll get this logged
  15. Thanks, unfortunately your file is not crashing for me. Are there certain pages that crash when you try copy and paste? Unfortunately I'm missing your linked images which I suspect is part of the reason. If you could save as a package and re upload that may help us reproduce it. The crash report is similar to one we have logged so I've added this threads info into that report. Unfortunately it will be tricky for us to fix until we can reproduce the issue internally.
×
×
  • Create New...

Important Information

Terms of Use | Privacy Policy | Guidelines | We have placed cookies on your device to help make this website better. You can adjust your cookie settings, otherwise we'll assume you're okay to continue.