Stinn
-
Posts
17 -
Joined
-
Last visited
Posts posted by Stinn
-
-
When exporting a file from Designer it keeps messing up the sizes. Relative the sizes are fine, but the measurements are not the what I set.
What I've tried:
EPS
SVG (with 300 and 72 DPI, with Set ViewBox enabled and disabled).
I need the measurements to be correct (I worked in mm, in the document everything is exactly right) because I want to convert it to DXF for CnC.
There are a LOT of other similar posts. I've tried a lot of the answers I've seen floating around, nothing works. It always gives me weird results.
-
42 minutes ago, Chris B said:
This is what IrfanView is showing.
So essentially the reset fixed? It would be nice to work out what happened with the old appdata folder though so we're going to keep poking.
Yes the appdata reset completely fixed the issue. I can't reproduce it unless I use the old version. It happened right after the latest update. Thanks for the help to both you and Gabe, and good luck!
-
6 hours ago, Wireless said:
(This got tagged to the wrong message).
Re-naming the '1.0' folder was the solution to my problem, and (in my humble but hard-won experience) beats forcing Windows to update any day of the week..
Nice! Glad it worked for you!
-
1 hour ago, Chris B said:
...and use IrfanView, it's correctly reporting 8 bit no matter what I do...
What do the images I uploaded produce in that application? Also, when you say 8-bit do you mean 8 bits per channel or per pixel? Because if it's exporting an RGBA image by mistake (on a greyscale export setting) it might still be 8bpc, but 32bpp.
-
Hi @Chris B,
All I'm doing is looking up the bit-depth in the file properties Detail panel (of Windows 10). I know that's not always accurate, but the filesize increases too while using the exact same image and document/export settings.
All I'm doing is creating a new document in Photo with my 2K Greyscale preset, dragging in an image (from Windows explorer) straight into Photo, adjusting the position and size (I bake my textures at 4096x4096 and drag them into the 2048x2048 document) and then exporting it out using a Greyscale TIFF preset.
The image I'm dragging in is a 4096 square, 128mb, uncompressed TIFF. It reports (and the math would agree) a 64bpp (16bpc) RGBA image. That's how xNormal (the application I use to bake textures) outputs textures when choosing TIFF, even when it's a monochromatic image (like a heightmap or ambient occlusion map).
The preset is in my old 1.0 folder from appdata, the one I uploaded to DropBox. The export settings are default (TIFF Greyscale 8-bit or 16-bit, the latter for the images I uploaded in DropBox).
Having said all that I can't reproduce it with new user settings either, only if I revert to the old settings (exact same as in DropBox). I can upload the baked image from xNormal if that could give you any insights. I don't have time to do a screencap right now, but it wouldn't help anyway. I don't have any other programs open and when testing it I always did the minimum steps I described above, never any extra image editing or what have you.
-
@Wireless you might try resetting all user settings by quitting Photo going to %APPDATA%\Affinity\Photo and renaming the 1.0 folder to something else (like 1.0-backup) and restarting Photo.
All your settings will be reset to factory defaults, but you can always throw away the newly created 1.0 folder and naming the -backup folder 1.0 again. But at least that way you can see if the user settings affect it.
I had a very weird issue too that got resolved by doing that.
-
On 4/21/2021 at 6:12 PM, Komatös said:
Please update Windows! The versions from 1.9.x of the Affinity programmes have many innovations that do not work with Windows < 20H1.
It's not the best to expect everyone to be up to date though. I had to install the October update myself manually through the Update Assistant, Windows update would not offer it to me.
With the 2004 update, I had to do that too and a bunch of extra stuff because it would BSOD every time trying to install the update until I found out that turning off some Windows features that are activated by default for everyone actually allowed the update to succeed.
You can't expect people to be up to date, unfortunately. And even if they try to be up to date, if they're not very knowledgable on the ins and outs of Windows it might mean they can't even upgrade even if they wanted to.
I think Serif should advise before updating that it'd be better to stay on an older version (EDIT: of Photo) if they rely on new Windows features to be honest. Windows update just isn't stable enough to expect everyone to be even reasonably up to date.
-
2 minutes ago, Gabe said:
In dropbox please. Zip both up and upload them on the same link.
Done.
-
I've switched the appdata folders around again to create a new faulty image. It outputted a file again with a bit-depth of 64.
I can upload two images if you want, one with the "factory reset" that is correct, and one that is faulty. The export settings for both were identical; just using the TIFF Greyscale 16-bit preset, without changing anything else.
Do you want them in Dropbox or here?
EDIT: Oh and I forgot; doing the same with the Tiff Greyscale 8-bit preset will output a 32bpp file instead of 8.
-
10 minutes ago, Gabe said:
Any chance you can also upload one of those 64bit images? We only have support for 8/16/32 bit so it's interesting what's going on here.
The only thing that could make the math work (because I've never heard of 64bpp greyscale either) would be that Photo exported 16bpc RGBA when I set it to greyscale 16-bit, and 8bpc RGBA when I set it to 8-bit. I don't think any image format (except maybe for RAW?) can go higher than 32bpc?
I'm editing heightmaps for use in 3D applications; they are exported from a texture baking program called xNormal. It outputs 16bpc RGBA for heightmaps, which I then load into photo to edit if necessary (baking errors / tiling seams) and export out as either 8- or 16-bit greyscale images to save diskspace.
I didn't check before if Photo mistakenly exported RGBA even though I set the preset to Greyscale... If you want I can re-instate the backup and make sure that's actually what was happening.
-
1 hour ago, Gabe said:
What do you mean by 64bpp? Can you zip up your "backup" folder and upload it on this link? I would like to see what went wrong. https://www.dropbox.com/request/oDeQN13r6YR43Z4S1xXx
I meant that the bit-depth (as reported by the file property window from Windows) will say 64.
I've uploaded the zipped folder.
I've tried breaking it again, but everything seems stable and has been exporting flawlessly since the reset of the user settings.
-
4 hours ago, Gabe said:
Very odd. 2 of us here tried it and was fine. Can you try this please?
Close Photo. Navigate to %AppData%\Affinity\Photo\ and rename 1.0 to 1.0.backup. Reopen Photo and see if it's any better. Don't worry about the missing stuff. It's all kept in the .backup file.
@Gabe thank you for the suggestion, that did seem to fix it. After more testing I saw that when it got messed up it would save 8bpp as 32bpp and 16bpp as 64bpp, until I opened a file with a lower bpp. It would then save correctly again if the export bpp settings matched the import bpp settings (so not the document itself, but imported image(s)).
Very strange behaviour, seemed to happen after the latest update.
I understand that naming the 1.0 folder will cause Photo to not find it, and then create a new 1.0 folder with factory settings; can I safely copy over raster_brushes.propcol and vector_brushes.propcol from the user directory, so that I don't have to import all my brushes again? Or does that not copy over imported brushes? Would save me a bunch of time.
EDIT: Copying those files over does seem to work. Thanks for your help Gabe.
-
Here is an image with the document preset and export settings I used.
-
Hi @Gabe,
After trying it again, it seemed to work, I created a new document with Grey/8, exported it using TIFF Greyscale 8-bit and it was indeed 8bpp.
I thought "must be something weird that got fixed after reboot then", loaded up the file I was working on yesterday, and it exported to 32bpp again. I tried converting the file to D50 ICC, then exported using use document profile in the More... section of the export window, but alas, it kept exporting 32bpp.
The data in the input image I use is indeed 32bpp, and it seems to stick to 32bpp if I use that file by opening it in Photo, but also as an import (dragged from Windows explorer) and maybe even when 32bpp data is in my clipboard. This happens across documents, and seems to be stuck at 32bpp once it happens.
So, when I open (after fresh boot) a new document with Grey/8 and save it with the TIFF Greyscale 8-bit preset, it is 8bpp as expected. If I then open a 32bpp TIFF file from disk in another document (not doing anything else), go back to the previously correctly exporting document and export it as a TIFF again it is now 32bpp instead of 8. Even though it correctly exported as 8bpp before.
It will keep exporting to 32bpp until I reboot.EDIT: The last statement is false. Only opening an 8bpp TIFF file from disk will fix it. If it's stuck at exporting as 32bpp no matter what, it will remain even after a reboot, I tested this 2 times to be sure.It seems like something gets flagged somewhere and just sticks to 32bpp from then on.
EDIT: Opening an 8bpp TIFF in Photo, then dragging in the 32bpp TIFF from disk and exporting that as 8bpp fixes it. But opening the 32bpp file in a new document alongside the 8bpp TIFF's document will revert to exporting everything as 32bpp again, even the 8bpp variant that exported correctly just before.
-
On 4/6/2021 at 8:34 AM, Komatös said:
Another one for whom the word "search function" is a foreign word!
Can you be a little less condescending please?
-
When I try to export to TIFF it will always export a file with a bit depth of 32 instead of the chosen bit depth. Whether I choose a preset in the export panel or use the document's settings while using an ICC profile; nothing changes the outcome. Before I updated this was never an issue, but I don't know if that was updating from 1.8.x or 1.9.1.
Photo version 1.9.2.1035
Win10 version 19041.928
Wrong export measurements in Designer
in Pre-V2 Archive of Affinity on Desktop Questions (macOS and Windows)
Posted
The SVG sets the document size (pixels) as integers. Which results in data loss with DPI because my document size (in Designer) was set in mm integers.
The weird thing is EPS does store the correct high quality pixels (with 2 decimal places) but doesn't use them when importing, resulting in the same rounding error.
PDF does the exact same. Since all of them are mainly web documents I guess pixels make sense, it's just annoying. I'll use rounded pixel document sizes in the future. That would fix the problem since positions are stored as floats.