BUG: Export Image produces wrong resolution when Windows 10 scaling option is on

BUG: Export Image produces wrong resolution when Windows 10 scaling option is on

robduarte
Collaborator Collaborator
679 Views
2 Replies
Message 1 of 3

BUG: Export Image produces wrong resolution when Windows 10 scaling option is on

robduarte
Collaborator
Collaborator

I am using Windows 10 on a high resolution laptop (Dell XPS 13). The Windows "Make everything bigger" setting is set to the default of 300%. (If this option is turned off - ie: set to 100% - everything in eagle is microscopic). When I choose Export Image, it shows me the correct image dimensions in the Eagle dialog. When I actually export, the image is the wrong size - ie: an image that Eagle says should be 2000x2000 at 1000 dpi would instead be 6000x6000 after exporting. This has been a normal part of my workflow since I started using Eagle so it's frustrating that this is broken. (I am cursing this high resolution display - nothing but headaches).

 

Rob Duarte
Associate Professor in Art, Florida State University
Co-Director FSU Facility for Arts Research
http://art.fsu.edu/rob-duarte/

Twitter | YouTube

680 Views
2 Replies
Replies (2)
Message 2 of 3

jorge_garcia
Autodesk
Autodesk
Hi Rob,

I hope you're doing well, it's nice to hear from you again. I've added your comments to an existing ticket on this issue. For now the workaround would be to turn off the scaling when you go to generate the image.

I encourage you to play with the HDPI settings that are now available under Options > User Interface. Perhaps some combination of those settings can get you the result you need.

Please let me know if there's anything else I can do for you.

Best Regards,


Jorge Garcia
​Product Support Specialist for Fusion 360 and EAGLE

Kudos are much appreciated if the information I have shared is helpful to you and/or others.

Did this resolve your issue? Please accept it "As a Solution" so others may benefit from it.
0 Likes
Message 3 of 3

CarlConquilla
Enthusiast
Enthusiast

This appears to still be an issue in 9.4.2, has this issue been fixed in the latest? @jorge_garcia 

It's workable if you already know the scaling factor but would be nice to know if it's worth interrupting my workflow to update to latest on all my machines.

0 Likes