No Forum Help on V1?

[Nita Reed]

I can't find the ability to start a new topic on my issue.  Is there no forum help for anything prior to V2?

[walt.farrell]

3 minutes ago, Nita Reed said:

I can't find the ability to start a new topic on my issue.  Is there no forum help for anything prior to V2?

If you want to ask a question, you just created a topic in the right place.

If you want to report a bug, you would do that in https://forum.affinity.serif.com/index.php?/forum/120-reports-of-bugs-in-affinity-version-1-applications/

If you want to request an application improvement, you would do that in https://forum.affinity.serif.com/index.php?/forum/52-feedback-suggestions/ but probably in the V2 section there, as V1 is not being enhanced.

[Nita Reed]

5 hours ago, walt.farrell said:

If you want to ask a question, you just created a topic in the right place.

If you want to report a bug, you would do that in https://forum.affinity.serif.com/index.php?/forum/120-reports-of-bugs-in-affinity-version-1-applications/

If you want to request an application improvement, you would do that in https://forum.affinity.serif.com/index.php?/forum/52-feedback-suggestions/ but probably in the V2 section there, as V1 is not being enhanced.

I recently purchased a new laptop and my Affinity Photo v 1.10.6.1665 won't stay open...keeps closing.  I've checked driver...it's up-to-date.  I unchecked the hardware acceleration.  I even make sure everything else is closed (except fontbase).  I can't do anything for longer than say 5 minutes or so...just crashes/closes.  I'm not even doing live filters or tonemapping...it's beyond frustrating.

Processor    11th Gen Intel(R) Core(TM) i5-1135G7 @ 2.40GHz   2.42 GHz

Graphics iRIS xe
Installed RAM    8.00 GB (7.65 GB usable)
System type    64-bit operating system, x64-based processor
17" Display
 

[thomaso]

20 minutes ago, Nita Reed said:

everything else is closed (except fontbase)

Can you boot your PC without running FontBase in the background? Or could there be a corrupted font file? If not, I wonder if you got any app / system relevant file installed that might conflict with APhoto in the background. As mac user I don't have any specific in mind, I just noticed you had the same problem last August on a different computer … and solved it by resetting that PC. Did it continue to work well, with/without (same) fonts or FontBase version? Did you copy apps or system data from your last PC to the new one, or reinstall everything from scratch? How about logging-in as a new, 'virgin' user on your new PC and try APhoto without any further installation?

[v_kyr]

7 hours ago, Nita Reed said:

Is there no forum help for anything prior to V2?

See also ...

• Pre-V2 (so V1) Archive of Affinity on Desktop Questions (macOS and Windows)

• Where to find Crash Reports (V1)

[Nita Reed]

1 hour ago, thomaso said:

Can you boot your PC without running FontBase in the background? Or could there be a corrupted font file? If not, I wonder if you got any app / system relevant file installed that might conflict with APhoto in the background. As mac user I don't have any specific in mind, I just noticed you had the same problem last August on a different computer … and solved it by resetting that PC. Did it continue to work well, with/without (same) fonts or FontBase version? Did you copy apps or system data from your last PC to the new one, or reinstall everything from scratch? How about logging-in as a new, 'virgin' user on your new PC and try APhoto without any further installation?

THANK YOU!  I went back down the rabbit hole...it was the Fontbase.  Now, I'm just dreading the loss/redoing of 15k in font collections!

[Nita Reed]

55 minutes ago, v_kyr said:

See also ...

• Pre-V2 (so V1) Archive of Affinity on Desktop Questions (macOS and Windows)

• Where to find Crash Reports (V1)

Yes.  I was not looking for the archive...  I couldn't post a new topic, only search, read & comment on existing.

[thomaso]

7 hours ago, Nita Reed said:

THANK YOU!  I went back down the rabbit hole...it was the Fontbase.  Now, I'm just dreading the loss/redoing of 15k in font collections!

Do you know what exactly was causing the problem for APhoto: The FontBase application / its way to work in the background – or its font data base on your computer in particular? In case of the latter I still wonder if a corrupted font file might be the culprit, not the entire FontBase data base itself. In this case it wouldn't help if you re-create your collections with including the corrupted file(s) again.

Maybe FontBase (or Windows?) offers a tool to search for corrupted fonts? Also just duplicate fonts may cause issues (if FontBase allows to activate duplicates at all).

Concerning the new creation of the font collection: If they are currently sorted in their Windows Explorer folder structure alphabetically only it appears useful to group / sort them there first, with new parent folders that will be used later as collection sections in the font manager. This could make it easier to choose the group folders for the FontBase collection creation + can get used to setup the collections in a different font manager app (imagine you want or need to move from FontBase).

[Nita Reed]

7 minutes ago, thomaso said:

Do you know what exactly was causing the problem for APhoto: The FontBase application / its way to work in the background – or its font data base on your computer in particular? In case of the latter I still wonder if a corrupted font file might be the culprit, not the entire FontBase data base itself. In this case it wouldn't help if you re-create your collections with including the corrupted file(s) again.

Maybe FontBase (or Windows?) offers a tool to search for corrupted fonts? Also just duplicate fonts may cause issues (if FontBase allows to activate duplicates at all).

Concerning the new creation of the font collection: If they are currently sorted in their Windows Explorer folder structure alphabetically only it appears useful to group / sort them there first, with new parent folders that will be used later as collection sections in the font manager. This could make it easier to choose the group folders for the FontBase collection creation + can get used to setup the collections in a different font manager app (imagine you want or need to move from FontBase).

i really don't know...I just opened AP with Fontbase closed & I was able to actually work through a file...to completion.

Now, I'm going to investigate the issue.  I hope I can figure out how.  I've not downloaded the fonts to Windows...straight to Fontbase...because I needed to sort and categorize into collections.

Sigh.  Overwhelming really.

I'm just sooo happy to be able to work again.  THANK YOU!

[thomaso]

56 minutes ago, Nita Reed said:

Now, I'm going to investigate the issue.  I hope I can figure out how. 

First I would search for a tool that can inspect all your fonts and detect a.) corrupted files and b.) duplicates. Possibly this is sufficient to continue with your current collection setup (reduced by the conflicting fonts). – If no corrupted or duplicate font was found then it is possibly a corrupted FontBase data base file, that you possibly can re-create without the need to re-create your custom collections. – If no other FontBase user pops-up in this thread then you might get info on the FontBase website.

56 minutes ago, Nita Reed said:

I've not downloaded the fonts to Windows...straight to Fontbase...because I needed to sort and categorize into collections.

That is why I mentioned the other method. If you organize your fonts in a Windows folder structure as you like them sorted in your fonts collection then the creation of the collection in any font manager app can be easier. Then you can use/add your already sorted parent folders to the manager app.

For instance: my folder structure and the according font manager collection, simply created by dragging the about 20 folders one by one to create the various collection groups. Faster than sorting all fonts within the manager!

[thomaso]

10 hours ago, v_kyr said:

See also ...

• Pre-V2 (so V1) Archive of Affinity on Desktop Questions (macOS and Windows)

Meanwhile this V1 subforum gets used also by V2 users, to add their V2 questions / report V2 issues that continue from a V1 topic.

This makes this V1 "archive" as an explicite subforum a bit confusing and possibly obsolete or "wrong" in the explicite V1 section of Questions – and I wonder if there would be any disadvantage if both would be in one / in the current V2 parent forum. Most of the V1 threads would be sorted simply by their creation / the last response date and thus appear in the full topic list accordingly, with the old V1-only at the end, @Patrick Connor? The advantage could be that users wouldn't need to check at two places (the parent V2 and the separate V1).

edit: Or what if the V1 archive would be set to "read only", maybe with the recently modified V1 threads moved to V2 before closing V1?

Edited July 14, 2023 by thomaso