Jump to content

Recommended Posts

Posted

When creating a HDR image, with two or three Tiff files the software crashes when loading the Tone Map. Auto ghosting is checked.

I signed up for a 90day trial 3 or 4 days ago, but the start up screen tells me I have 9 days left.

If I turn off Tone Map, the HDR process completes.

I tried the panorama stitching and focus stitching  both work well.

Thank you for your help!

Regards, Tom Wiggins

  • Staff
Posted

Hi @TWP46

Welcome to the forums. 

On 1/21/2021 at 7:20 PM, TWP46 said:

I signed up for a 90day trial 3 or 4 days ago, but the start up screen tells me I have 9 days left.

Sounds like you did not put in your product key. You will find this in your affinity.store account. 

On 1/21/2021 at 7:20 PM, TWP46 said:

When creating a HDR image, with two or three Tiff files the software crashes when loading the Tone Map. Auto ghosting is checked.

This must be an isolated issue, as I can't replicate it here. Does it happen why any TIFFS? can you attach some samples so we can have a look? 

Have you got Hardware Acceleration ON or OFF in Preferences > Performance ? 

Posted

Hi getting same issue with crashing only using raw files not tiff have tried different images same result. Uninstalled  done a complete fresh install same issue.

Have you got Hardware Acceleration ON or OFF in Preferences > Performance ?  no option to turn on or off.

How do I summit bug report, option showed up the first time but as I figured it was a one of declined but it has happened every time since.  :)   

Posted

I'm using 1.8.5.703.  I just tried HDR merge with Olympus ORF files and TIFF versions of the ORF files they both  worked!

Thanks,

Tom 

 

 

Posted
3 minutes ago, KennethJCoxPhotography said:

Hi thanks Gaba no I am using the latest full version 1.8.5.703 I trend not to use Beta as normally they are the ones with stability issues. 

Then you don't have and never had a hardware acceleration option if you're on Windows. That's only in the 1.9 beta (which this topic is about).

-- Walt
Designer, Photo, and Publisher V1 and V2 at latest retail and beta releases
PC:
    Desktop:  Windows 11 Pro 23H2, 64GB memory, AMD Ryzen 9 5900 12-Core @ 3.00 GHz, NVIDIA GeForce RTX 3090 

    Laptop:  Windows 11 Pro 23H2, 32GB memory, Intel Core i7-10750H @ 2.60GHz, Intel UHD Graphics Comet Lake GT2 and NVIDIA GeForce RTX 3070 Laptop GPU.
    Laptop 2: Windows 11 Pro 24H2,  16GB memory, Snapdragon(R) X Elite - X1E80100 - Qualcomm(R) Oryon(TM) 12 Core CPU 4.01 GHz, Qualcomm(R) Adreno(TM) X1-85 GPU
iPad:  iPad Pro M1, 12.9": iPadOS 18.5, Apple Pencil 2, Magic Keyboard 
Mac:  2023 M2 MacBook Air 15", 16GB memory, macOS Sequoia 15.4

Posted

Being an admin does not give you the right to patronize me! Had you read what I wrote the first time you would have seen that I had stated I was using the full version! I would have thought if this issue is an issue in the full version it would have been fixed before releasing a beta with same issue after all this is payed software  and not free. I have noticed this issue has been reported in other version releases so beta or fall it needs addressing and fixing not sarcastic reply's from someone who is supposed to be here to help.

Posted
4 minutes ago, haakoo said:

Walt is just another user of the affinity programs and points rightfully that this is an issue with a beta version.
Better report your issue in the appropriate forum
 

clipimage.jpg

Yea well maybe in the next beta Affinity can add a feature where we can contact a dedicated technical support instead of having to go through a forum to address an issue. Regardless It does not take a brain surgeon to realise the issue is just carried on from previous versions if it had been fixed in 1.8.5.703 then this post would not even be here.  Capture one has dedicated support, Adobe has dedicated support affinity needs to do the same.

  

  • Staff
Posted
On 2/1/2021 at 10:41 PM, KennethJCoxPhotography said:

Yea well maybe in the next beta Affinity can add a feature where we can contact a dedicated technical support instead of having to go through a forum to address an issue.

I'm not really sure what kind of "dedicated" support are you looking for. Depending on where on the forums you post, you will either have a QA member (if it's a QA matter - posted in Bugs or Beta forums), a Tech Support member (if posted in Questions), or a Customer Service member (if posted in Customer Service) replying to your thread. 

We also have an email address: affinitysupport@serif.com . 

----

You've posted in a BETA thread, so one assumes from your first post that you're using the beta. 

On 2/1/2021 at 10:03 PM, KennethJCoxPhotography said:

I trend not to use Beta as normally they are the ones with stability issues. 

In this case please don't post in a beta forum, as you don't know if that issue has actually been fixed or not. Please use the general Bugs forum. 

On 2/1/2021 at 10:41 PM, KennethJCoxPhotography said:

Regardless It does not take a brain surgeon to realise the issue is just carried on from previous versions if it had been fixed in 1.8.5.703 then this post would not even be here.

Well, not really. There are BETA specific issues, and issues that were ported from 1.8 to 1.9 beta. But that does not mean ANY bugs found in 1.8 are also present in 1.9 beta. A lot of the bugs have already been fixed. 

----

Anyways, back to the chase. 

If you create a new post here from this link: https://forum.affinity.serif.com/index.php?/forum/71-bug-reporting/ , following the template you find at the top of the page, we can have a look. Please include a crash report with your post. 

 

 

×
×
  • 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.