myclay

To add to @walt.farrells posting; If you are using the msix versions of the Affinity programs and are unable to bridge it to other programs, the user @rvst made an excellent exe to which you would make a bridge to. You just need to download it from github and rename AffinityPhotoLauncher.exe to any of these; AffinityPublisher2.exe AffinityPhoto2.exe AffinityDesigner2.exe and link your other programs to that exe. Keep the exe file in a place where you don´t accidentally delete it. I even made three copies of that exe and renamed them so I can easily link to each Affinity program depending on the usecase. https://github.com/dl12345/AffinityPhotoLauncher/releases/tag/v1.1.0-x64 More info and source code download ; https://github.com/dl12345/AffinityPhotoLauncher

ah, I see,my bad.😊 The second link is just general Linux Wacom support. For the Pen-computer its supported straight up in the Linux kernel so for that device the support goes much deeper into the OS and the second link is redundant.

Not sure from whom you got that quote from? I was talking about this pen-computer called WacomMobileStudioPro from Wacom. On this device you can install Linux with full support for the device from the Linux community. This would be the closest you can get to your dream setting.

So basically the already existing Pen computer from Wacom with added Linux? https://www.phoronix.com/news/Linux-Wacom-MobileStudio-Pro https://linuxwacom.github.io/ <- some general Wacom Linux driver information/support and not relevant to this discussion . The missing ingredient would be Affinity on Linux.

I am tipping on a software conflict. Both systems manufactures have problematic software affecting multiple consumer programs. the former pc was an Asus now it seems that both systems are from MSI? For your old PC its either Asus Sonic or Asus GPU Tweak III In the Msi systems case(the laptop of your daughter and your new PC) its probably Nahimic.

This wrapping stuff around with the help of AI looks interesting. EDIT; not 100% useful when it needs to be accurate and or truthful to reality but for quickly modifying placeholder images it looks interesting.

Maybe tie it to the brush size and have the picker sample a square area with full pixels, that way the user can set how big the sampling area needs to be without having to zoom in constantly. Edit; the automated size change depending on the zoom level has its pros but I am not a fan of such forced automation (maybe as an optional tick in the settings) + tying the colour picker sampling area to the brush size is self- explanatory, -revealing and makes sense since the user has already had contact with brush size changes when using a brush.

Might be a task for some forensic checking. https://29a.ch/photo-forensics/#error-level-analysis Drag and drop the image into the site, its locally edited in your browser. The sunlight colour seems convincing? The cows are a domestic cattle breed so if this was AI generated, at least some tiny amount of thought went in... Anyhow if its true that its AI generated(need more convincing proof for that claim), AFP could still lose its entire reputation.

That image is from AFP, Agence France-Presse, Ishara S. Kodikara. https://twitter.com/AFP/status/1665954542071201792/photo/3 German state media isn´t the best in fact checking but If its´s an generated image, AFP and the Photographer would be in trouble. AFP is like DPA or Reuters.

Rasterizing and trimming is helping to fix the symptom but maybe not the root cause? I tried to replicate the bug but wasn´t able to get your error but when you scroll thru the history, the equation is vanishing in the first procedural Texture layer. Backwards scrubbing thru history keeps it intact but going forwards from step 0 it vanishes. Seems like copypasting formulars could be a culprit. 32x32 test.afphoto

Best guess; the image for the Explorer thumbnails (128x128,256x256,512x512) need to be generated while the original image is too small. this is the result when you upscale it to 512x512 Bilinear The averaged result in the middle is odd, maybe Affinity has used a tiling method like Affine to fill the thumbnail image? This preview thing also happens on windows. The 31x32 within Affinity is truly odd, copy pasting that pixel layer into Paint results in 32x33px.

This surpasses my knowledge. Maybe you could ask Jarek Majewski who used Affinity Photo/Designer in conjunction with Unity and also wrote the 2D Game Art book which was released by Unity; https://resources.unity.com/games/2d-game-art-animation-lighting-for-artists-ebook http://www.mindjardesign.com./ The book besides the slices workflow only mentions to rename the psd file in your windows explorer to psb and then Unity can load in layers.

Go to the export persona and use slices for every element you want to be separate. In the Layers, there is a Create Slice button. Use it to create a "new file" for each element you want to be separate. moving to Slices, you can then export the slices and set which file format they have to be. A bonus point is, you could use the Batch Builder preset spline Json which depending on the support of your game engine means, the order and placement we currently see in Affinity Photo will be brought over. Edit; Apparently for Unity renaming the .psd file to .psb can help too.

yes of course The linked file is a temporary .psd file with a name which the other program doesn´t allow a namechange on it. The LayerZ.psd is the first file. the 2LayerZ.psd is the second iteration but the number 2 needs to be removed. Its uploaded to wetransfer and contains the afpub file as well as two example psds. https://we.tl/t-lmXadhMavG

@walt.farrell whenever the file is externally updated, that edit Document option vanishes and it looks like in the image below; When using edit document on a first time linked file works, it does not update the layers once you are again start editing the document outside of affinity.

The auto reload feature of Linked files is quite intriguing. It would be cool if we where able to directly edit the layers and saving over the original file.

unless I am misinterpreting you, I thought that there are plans to provide a plugin SDK.

EDIT; ups nicht genau hingeschaut. Die Pixelgröße stimmt nicht überein?! 2PX fehlen beim Export. hm, scheint nach Recherche ein "User" Bug zu sein. Eventuell das Bild verschieben und in der Mangetischen Ausrichtung (Magnet) die Pixelausrichtung erzwingen aktivieren und um ganze Pixel verschieben deaktivieren damit das ganze dann hinhaut beim korrekten verschieben.

As Komatös wrote, ipad like systems from wacom exist but the prices are really high for what it offers. The Wacom MobileStudio Pro 13 in my region costs ~1500€ up to 1800€. It has only 512GB SSD, 16GB RAM and an Intel Core i7 with two cores and 3,3GHz and an camera for 3D scanning. This offering might be unsatisfying to your needs but you have a battery for ~6hours usage. The questions one should ask themselves are; Do you have programs where developers do not support alternatives like Huion, XP-Pen etc? Do you use Programs right now where support is not there (yet) which you use regularly? (if so skip the competition) Do your programs have features like tilt support where wacom wise you should only purchase the Pro products? Do you want or have to be mobile at all times? (Pen computers like the Wacom MobileStudio Pro are then needed. Do you already have a PC and want to upgrade it and save money but be much more stationary? either choose Pen Displays and keep an eye out for Huions,XP-Pens they might be suitable or use Pen Tablets again, the competition is available too and depending on the usecases and support they can be nice alternatives. Do you want to have a full view at the screen or can you endure not seeing what is covered by your hands? (If you need a free view at all times choose Pen Tablets) Do you want or plan to replace your device cheaply when its broken? choose Pen Tablets as the cheapest and easiest product to replace. Do you want to do renderings and GPU intense stuff too? a Pen Display or Pen Tablet on your PC would be in my view the best solution. Edit; other questions you should ask yourself are; Do you have the needed space for such hardware? How big does the tablet need to be for you? I personally stay clear from the smallest and biggest Versions ( S and L Editions) since to me they can feel uncomfortable when you work for a longer time and want to limit the amount of repetitive or body straining movements.

Wenn man dieses Apps den Zugriff auf Ihre Bibliotheken erlauben deaktiviert sollte es gehen? Da ist Affinity Photo nicht drinnen und verweigert deswegen die Sicherung. Aktuell dürfen keine "fremden" Daten abgelegt werden außer von Programmen aus der Liste. Habe bei einer Suche auch nicht herausgefunden wie man als einfacher Nutzer ein Programm auf diese Liste bekommt. Ist eventuell eine meldung wert für einen Entwickler.

To me it seems you are trying to save into onedrive? That might cause issues. I think if you where to save it into your lokal Bilder/picture folder it would work.

maybe changing the Candidate List to for example All layers fixes this for you?

It works in multiple Editing Programs like for example with Affinity Photo. Jpeg XL is a brand new file format. In March 2022 it was standardized. Jpeg XL got its documentation update roughly a month ago. https://ds.jpeg.org/whitepapers/jpeg-xl-whitepaper.pdf Regarding support; Facebook, Adobe,Serif, Intel,Vesa,Krita, The Guardian, libvis,Cloudinary,Shopify and others have shown their support for Jpeg XL. https://cloudinary.com/blog/the-case-for-jpeg-xl For example; Adobe recommends Jpeg XL for HDR output. https://helpx.adobe.com/camera-raw/using/hdr-output.html

There is a clear explanation/tip given to Beta testes to not use beta versions for day to day productive purposes since backward compatibility is not guaranteed. Another way which might work is copy pasting layers from beta to stable.

Good to know, you could look into the Jpeg XL fileformat inside Affinity Photo. import as well as export is supported. Affinity Photo allows exporting HDR JXLs using 32-bit float pixel data. Google (Chromium) so far seems to be against Jpeg XL. https://bugs.chromium.org/p/chromium/issues/detail?id=1178058