Jump to content
You must now use your email address to sign in [click for more info] ×

[1.9.2.1035] File corrupt warning box on file change


Recommended Posts

Hi

Thanks for the update...Just thought I would report this one!

Working on a large new vector based image 1500x600mm with a series of stacked AD files.as usual!.. Previously I have adopted the method of just embedding AD files in a master using layers.

Today I have been trying out the 'linked file' options. Sort of works! but each time I update a link file (Master+linked file is open (tabbed)) I get a 'file appears to be corrupt' warning...even though it is not!. The Master file updates anyway after I close the warning and switch tabs

Also had a crash with no report attempting to paste a layer to second file in same process

 

 

Affinity Version 1 (10.6) Affinity Version 2.3.1 All (Designer | Photo | Publisher)   Beta; 2.3 1.2279
OS:Windows 10 Pro 22H2 OS Build 19045.4046+ Windows Feature Experience Pack 1000.19053.1000.0
Rig:AMD FX 8350 and AMD Radeon (R9 380 Series) Settings Version 21.04.01 
Radeon Settings Version 2020
20.1.03) + Wacom Intuous 4M with driver 6.3.41-1

 

 

Link to comment
Share on other sites

  • 1 month later...

Hi @StuartRc Are you using Publisher? I will get your post moved to the Publisher forum so it's in the right place. 

Could you upload a video of the issue happening and zip up the document and the assets so I can try and reproduce it myself? I have created a dropbox folder you to upload them to here.

Link to comment
Share on other sites

1 hour ago, SPaceBar said:

Hi @StuartRc Are you using Publisher? I will get your post moved to the Publisher forum so it's in the right place. 

Could you upload a video of the issue happening and zip up the document and the assets so I can try and reproduce it myself? I have created a dropbox folder you to upload them to here.

Hi, Thanks for getting back to me!... I will have to backtrack a bit!:)

Yep sure...I will just try and simplify a copy of the folder (it contains sequential versions).. and I will get it to you!

I was using Designer to assemble a sequence of stacked AD files (The Drawings are a bit too complex to have a single file with 1000's of objects)..I used embedding previously but I just thought I would try linking..but I found you had to be careful with updating! or changing the source!

The Master file in this case is just a Layer set with 5 or more linked AD files and a couple of fixes/afterthoughts!

 

I have added the files to dropbox (AD and video)

 

 

Affinity Version 1 (10.6) Affinity Version 2.3.1 All (Designer | Photo | Publisher)   Beta; 2.3 1.2279
OS:Windows 10 Pro 22H2 OS Build 19045.4046+ Windows Feature Experience Pack 1000.19053.1000.0
Rig:AMD FX 8350 and AMD Radeon (R9 380 Series) Settings Version 21.04.01 
Radeon Settings Version 2020
20.1.03) + Wacom Intuous 4M with driver 6.3.41-1

 

 

Link to comment
Share on other sites

Ok I have uploaded a set of files to dropbox

1. The original AD file set (with un-used removed)

2. Video sequence of events

3. jpg of consequences

As below

 

link_box issue.jpg

 

So 

1. Load Camouflage_III_Assembled_08_test.afdesign

2. I reset it..as the layout gets broken when you process the changes

3. Select Layer (top) {C3_Level_01 FG_01}

4. Select the Linked file and Edit Document on Context Bar

Opens a separate tab (2 tabs!)

5. Change it..save it!

6. Go back to original file {Tab 1} Resource should pick up file has changed (AD is doing something a bit different now..the file is disappearing from Layers...which is a bit weird!)

7. Toggle back to Edit file tab and UNDO the Change Then Return to Original Document (You should get a Alert box)

8. Go back to original tab you should get the pop-up and a broken original file.

Sometimes Ad will crash...may have to toggle between the tabs!

Hope this helps

 

 

Affinity Version 1 (10.6) Affinity Version 2.3.1 All (Designer | Photo | Publisher)   Beta; 2.3 1.2279
OS:Windows 10 Pro 22H2 OS Build 19045.4046+ Windows Feature Experience Pack 1000.19053.1000.0
Rig:AMD FX 8350 and AMD Radeon (R9 380 Series) Settings Version 21.04.01 
Radeon Settings Version 2020
20.1.03) + Wacom Intuous 4M with driver 6.3.41-1

 

 

Link to comment
Share on other sites

On 5/19/2021 at 4:36 PM, SPaceBar said:

@StuartRc I have been unable to relocate the linked resources I need to test this as it's saying I don't have permission.

I came across this on the forum permissions

Also came across this Underscores

 

Permission-denied.png

That's Strange...they are not protected in anyway..That file is in the Composites testing folder. let me upload the files separately see if that makes a difference!

 

Affinity Version 1 (10.6) Affinity Version 2.3.1 All (Designer | Photo | Publisher)   Beta; 2.3 1.2279
OS:Windows 10 Pro 22H2 OS Build 19045.4046+ Windows Feature Experience Pack 1000.19053.1000.0
Rig:AMD FX 8350 and AMD Radeon (R9 380 Series) Settings Version 21.04.01 
Radeon Settings Version 2020
20.1.03) + Wacom Intuous 4M with driver 6.3.41-1

 

 

Link to comment
Share on other sites

Ok all files from Composites_testing folder added to dropbox..

It opens Ok here!. with filename 'Camouflage_III_Assembled_08_test.afdesign' Working on PC not Mac...I didn't think that would make a difference!

I opened it in AD Beta 1.9.4.1065 just to see if there was a difference! result is as below. 

Created a new zip file containing a folder where the files have full permission:'Full Permissions'..added that to dropbox

 

Resources folder.jpg

 

Affinity Version 1 (10.6) Affinity Version 2.3.1 All (Designer | Photo | Publisher)   Beta; 2.3 1.2279
OS:Windows 10 Pro 22H2 OS Build 19045.4046+ Windows Feature Experience Pack 1000.19053.1000.0
Rig:AMD FX 8350 and AMD Radeon (R9 380 Series) Settings Version 21.04.01 
Radeon Settings Version 2020
20.1.03) + Wacom Intuous 4M with driver 6.3.41-1

 

 

Link to comment
Share on other sites

37 minutes ago, Wosven said:

Same problem than in this Apub's bug:

 

Hi,
Similar...:)
I was not sure until I saw the last quote in the thread...I could understand why AD pop's up a warning box with a comment that cannot be true!

I worked on the file sometime ago now...There are 2 drawings with Camouflage III project. The first (the one above with the issues!) was built in AD as a Layer stack with linked rather than embedded files (I thought it would be a good idea to try it out). It works mostly!:). But I a lot of problems making changes to the linked files..I kept getting issues like the one above (video) when I tried to update..For the second drawing I went back to embedded files as I knew this workflow  is 'smooth' 

When @SPaceBar picked up the bug report I had already completed the project. Had to backtrack a bit to rebuild the file set up.. I believe the work was mostly completed with AD 1.9.0/1.. So when you open/edit the linked file from inside the Master/Parent file it opens in new tab. Change it in some way then save. Then by clicking on the Master file tab you can activate this alert box. If you pursue the process by clicking between tabs and or closing the alert box sometimes AD would crash. However with the new version 1.9.2.1035, There are a couple of other events. If you watch the video, The linked file when edited and saved disappears from the Master file. Even though the layers panel suggests that it is still present. Also AD knows the file has changed but does not automatically update.  You can still also place the file again so as far as I can see it is not corrupt.

 

 

Affinity Version 1 (10.6) Affinity Version 2.3.1 All (Designer | Photo | Publisher)   Beta; 2.3 1.2279
OS:Windows 10 Pro 22H2 OS Build 19045.4046+ Windows Feature Experience Pack 1000.19053.1000.0
Rig:AMD FX 8350 and AMD Radeon (R9 380 Series) Settings Version 21.04.01 
Radeon Settings Version 2020
20.1.03) + Wacom Intuous 4M with driver 6.3.41-1

 

 

Link to comment
Share on other sites

Sorry being dumb! I had not uploaded video to forum, just dropbox..so here you are!:)

It's a bit jittery but you can see what happens!

 

2021-05-18 13-34-06.mkv

 

Affinity Version 1 (10.6) Affinity Version 2.3.1 All (Designer | Photo | Publisher)   Beta; 2.3 1.2279
OS:Windows 10 Pro 22H2 OS Build 19045.4046+ Windows Feature Experience Pack 1000.19053.1000.0
Rig:AMD FX 8350 and AMD Radeon (R9 380 Series) Settings Version 21.04.01 
Radeon Settings Version 2020
20.1.03) + Wacom Intuous 4M with driver 6.3.41-1

 

 

Link to comment
Share on other sites

25 minutes ago, StuartRc said:

AD pop's up a warning box with a comment that cannot be true!

At least in my version, I known the popup was false, and I just had to close it and keep on working. Nothing disappeared.

Your art is so detailed, that embbeded files should give huge files and take a lot of memory, isn't it? It would be sad that a nasty bug stop you to share impressive artwork.

I hope they'll find a solution :).

Link to comment
Share on other sites

11 hours ago, Wosven said:

At least in my version, I known the popup was false, and I just had to close it and keep on working. Nothing disappeared.

Your art is so detailed, that embbeded files should give huge files and take a lot of memory, isn't it? It would be sad that a nasty bug stop you to share impressive artwork.

I hope they'll find a solution :).

Don't worry it wont stop me!:)...

You are correct the files do get quite large but it also works pretty well. I just thought it would be nice to try out the new feature. Which seems to create images of the linked files inside Designer..that slows down slightly.. I have always been impressed with the volume of vector objects you can add before AD starts to slow. In 'Poison', the mushrooms!..AD only started to slow down when I was trying to finalise the shadows at which point I embedded the red mushrooms. With all the other drawings I have not really had an issue. It is all in the planning and organising the file structure such as having the shadows on separate layers between embedded files, so you do not have to open embedded files all the time and copying layers between documents. There is a version of Camouflage III (2) that is just one file without any embedding. The only slow or 'slowing' file that caused be issues was 'Ecosystem' which all raster but 3 metres wide..

I am sure it will get resolved..:)

 

Affinity Version 1 (10.6) Affinity Version 2.3.1 All (Designer | Photo | Publisher)   Beta; 2.3 1.2279
OS:Windows 10 Pro 22H2 OS Build 19045.4046+ Windows Feature Experience Pack 1000.19053.1000.0
Rig:AMD FX 8350 and AMD Radeon (R9 380 Series) Settings Version 21.04.01 
Radeon Settings Version 2020
20.1.03) + Wacom Intuous 4M with driver 6.3.41-1

 

 

Link to comment
Share on other sites

failure to access the files bugged me a bit!...so I had a play around with the file structure and naming!

I have reconfigured the linking structure today to see if it helps

So

All files have been renamed without underscores and relinked to separate files using collection in resources (process works really well!:))

I have uploaded a new zip file to dropbox containing only the necessary files and renaming the master accordingly and created a new folder to contain links (checked whether files associated correctly first)

File=uploaded.zip

let me know if anything changes!:)

 

 

 

Affinity Version 1 (10.6) Affinity Version 2.3.1 All (Designer | Photo | Publisher)   Beta; 2.3 1.2279
OS:Windows 10 Pro 22H2 OS Build 19045.4046+ Windows Feature Experience Pack 1000.19053.1000.0
Rig:AMD FX 8350 and AMD Radeon (R9 380 Series) Settings Version 21.04.01 
Radeon Settings Version 2020
20.1.03) + Wacom Intuous 4M with driver 6.3.41-1

 

 

Link to comment
Share on other sites

7 minutes ago, Wosven said:

Sorry for bugging on this line, but was it causing trouble?

You are not bugging!...:)..any input is welcome...

Well The bug issue ie the alert box(+crash) with weird responses still stands!.. but When I uploaded the files SPacebar was having trouble accessing the AD file. Which I thought was a bit strange...So I had a dig around on the forum and found a couple of issues highlighted regarding naming and file permissions..

So

Basically I renamed all the files.. removing all underscores; condensing the naming so each file was just a single name but also used the Collection/Package feature on resources panel to collect all the files in master document after they had been renamed and relinked...to see if it would solve the issue 

This seems to have allowed the file to be opened
Process 1
Check permissions on files in folder. Make all same and all accessible

Process 2
1. Duplicate folder containing the files
2. Rename linked files
3. Open Master and relink all files
4. Rename the master file
5. Use collection to assemble the links
6. Once complete save the file so that all the links are sourced from the new folder

A useful process if you want to consolidate all the files

 

 

Affinity Version 1 (10.6) Affinity Version 2.3.1 All (Designer | Photo | Publisher)   Beta; 2.3 1.2279
OS:Windows 10 Pro 22H2 OS Build 19045.4046+ Windows Feature Experience Pack 1000.19053.1000.0
Rig:AMD FX 8350 and AMD Radeon (R9 380 Series) Settings Version 21.04.01 
Radeon Settings Version 2020
20.1.03) + Wacom Intuous 4M with driver 6.3.41-1

 

 

Link to comment
Share on other sites

I have edited the original process instructions to recreate the alert box (Undo and save!)

 

Affinity Version 1 (10.6) Affinity Version 2.3.1 All (Designer | Photo | Publisher)   Beta; 2.3 1.2279
OS:Windows 10 Pro 22H2 OS Build 19045.4046+ Windows Feature Experience Pack 1000.19053.1000.0
Rig:AMD FX 8350 and AMD Radeon (R9 380 Series) Settings Version 21.04.01 
Radeon Settings Version 2020
20.1.03) + Wacom Intuous 4M with driver 6.3.41-1

 

 

Link to comment
Share on other sites

@StuartRc Are you saving again between these steps? I have not yet managed to reproduce the error.

7. Toggle back to Edit file tab and UNDO the Change Then Return to Original Document (You should get a Alert box)

8. Go back to original tab you should get the pop-up and a broken original file.

Link to comment
Share on other sites

Hi,

Using 1.9.2.1035 I am still getting it!.... just checked So I logged the full process/sequence below

Process
1. Open File C3v8Packaged01
2. Expand Layers
3. Select the Ad file in C3_level_01 FG_01
4. Select Edit Document (Top Context/Settings Bar)
5. Select Rectangle Tool (M)
6. Draw a filled rectangle on the opened edit file (C3L01FG01)
Shows as modified
7. Save file
8. Return to C3v8Packaged01 (using open Tab!)
File disappears bur registers as modified
9. Click Back onto C3L01FG01 File (Tab)
10. Undo the rectangle
11. Save 
This is where I am getting Failed to open file popup!. The file modified alert box (with link to resources also occurs briefly)

This is slightly different from the original bug registration as the alert box comment was suggesting the file was corrupt (I am wondering whether this is to do with the underscores! or the original naming convention!)

Also while I was registering the process in Notepad++ AD closed/crashed all on its own The 2 files and alert box were visible as the last event

I have a crash report which I have attached

Hopes this helps:)
 

964b6883-b65d-4474-bf15-ab82a6107ff9.zip

 

Affinity Version 1 (10.6) Affinity Version 2.3.1 All (Designer | Photo | Publisher)   Beta; 2.3 1.2279
OS:Windows 10 Pro 22H2 OS Build 19045.4046+ Windows Feature Experience Pack 1000.19053.1000.0
Rig:AMD FX 8350 and AMD Radeon (R9 380 Series) Settings Version 21.04.01 
Radeon Settings Version 2020
20.1.03) + Wacom Intuous 4M with driver 6.3.41-1

 

 

Link to comment
Share on other sites

5 hours ago, SPaceBar said:

@StuartRc Are you saving again between these steps? I have not yet managed to reproduce the error.

7. Toggle back to Edit file tab and UNDO the Change Then Return to Original Document (You should get a Alert box)

8. Go back to original tab you should get the pop-up and a broken original file.

Hi I have relogged the process...There are 2 points of save 1 After editing the linked file. One after undoing the change!

 

Affinity Version 1 (10.6) Affinity Version 2.3.1 All (Designer | Photo | Publisher)   Beta; 2.3 1.2279
OS:Windows 10 Pro 22H2 OS Build 19045.4046+ Windows Feature Experience Pack 1000.19053.1000.0
Rig:AMD FX 8350 and AMD Radeon (R9 380 Series) Settings Version 21.04.01 
Radeon Settings Version 2020
20.1.03) + Wacom Intuous 4M with driver 6.3.41-1

 

 

Link to comment
Share on other sites

I just tried this process with the latest [AD Beta 1.9.4.1065] and it crashed immediately while trying to open the file.
So

1. Open File C3v8Packaged01 in Beta. I received an alert box regarding missing linked file then Designer just closed! (To test need a saved file with missing link file!)

2. Returned to AD released fixed the issue (Which was missing file!)..I assume I just had not cleaned up/reversed the process in last test .. and it then opens OK in beta.

 

 

Affinity Version 1 (10.6) Affinity Version 2.3.1 All (Designer | Photo | Publisher)   Beta; 2.3 1.2279
OS:Windows 10 Pro 22H2 OS Build 19045.4046+ Windows Feature Experience Pack 1000.19053.1000.0
Rig:AMD FX 8350 and AMD Radeon (R9 380 Series) Settings Version 21.04.01 
Radeon Settings Version 2020
20.1.03) + Wacom Intuous 4M with driver 6.3.41-1

 

 

Link to comment
Share on other sites

Hi

Had a play around with the beta version to see if any different!

1. Fixed the files.. renamed and Collected a beta linked set of files in separate folder for testing
2. Followed same process.
3. Edit top file in layers (just draw a box and save)
4. Have a different alert box..
5. This time when you return to the Master file (first tab)..the file updated...Very quick I must admit!

I have added an image below

ADBeta test.jpg

When I undid the change Another alert box pops up with the message 'This file type is not supported'....interesting AD doesn't support it's own file type wow!:)..telling me porkies!

 

Affinity Version 1 (10.6) Affinity Version 2.3.1 All (Designer | Photo | Publisher)   Beta; 2.3 1.2279
OS:Windows 10 Pro 22H2 OS Build 19045.4046+ Windows Feature Experience Pack 1000.19053.1000.0
Rig:AMD FX 8350 and AMD Radeon (R9 380 Series) Settings Version 21.04.01 
Radeon Settings Version 2020
20.1.03) + Wacom Intuous 4M with driver 6.3.41-1

 

 

Link to comment
Share on other sites

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.

Guest
Reply to this topic...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

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