assets.propcol in a network enviroment.

[dm0ysie]

Hi,

Is there a way to have a shared assets.propcol within a network enviroment for all users to access. Currently it looks like we will have to copy this file onto all users profiles. Also is there a way top split the assets file up? Currently its at about 20GB.

TIA

Dave

[v_kyr]

In the pasts (v1 times) accessing remote network stored files always were problematic and often resulted, sooner or later, in file access errors and sometimes also data losts. So the common advice was always, to work locally with all related project files and use network drives just for copied over backups (so not depending on direct remote file access).

As the assets.propcol file is a dynamic loaded one part of the Affinity apps it has to be accessable & reachable by the apps. Splitting it into seperate file chunks is dependent on the file format and AFAIK not supported for this type of file (...how should it load up all the related file chunks or now which assets are wherein then?). - Remote shared access depends on the remote connection stability and speed, aka if the external storage place is always speedy accessable from a client computer and not in idle mode, or having some lost connection.

 

[dm0ysie]

Thanks for the response.

I feared that may be the case and agree accessing from remote or cloud based libarties would be hugely problamatic. This would be accessing resources on a local LAN. 

Ultimatley It would be nice to have a way to centrally manage LAN based resources, such as assets, so there is not the need to push huge files to every users profile (on windows) each time we do an update of the library.

 

 

[v_kyr]

45 minutes ago, dm0ysie said:

This would be accessing resources on a local LAN. 

In the pasts (v1) it didn't matter if accessed from a local LAN, NAS or directly connected external storage disk etc. as it partly happened on pretty all of those. Though can't tell if things have now changed here with v2 apps in this regard. - One of the reasons for the overall difficulties in remote file handling here might be, that the proprietary Affinity file formats are built up in an incrementally manner.

52 minutes ago, dm0ysie said:

Ultimatley It would be nice to have a way to centrally manage LAN based resources, such as assets, so there is not the need to push huge files to every users profile (on windows) each time we do an update of the library.

I know what you mean, always syncing a >= 20 GB changed/updated file in a local LAN among possible xx users can produce time wise high traffics. - But on the other hand, I can imagine that sharing and accessing concurrently, one and the same incremental build file (...read/lock/write/release lock/read changes), at the same time also has its risks here. - So one should always also have enough file backups then.

[carl123]

2 hours ago, dm0ysie said:

Also is there a way to split the assets file up? Currently its at about 20GB.

What is taking up 20GB?

If you have large images, overlays, textures etc in your assets you may want consider moving all the large stuff out of the assets file and create a folder for them on your Lan, you could then split that folder into sub-folders to organise things

TLDR; Just keep small stuff in assets - this also helps with performance issues

[dm0ysie]

It's a mixture of trees, vegitation, skys, people and other assets we use a fillers for context in images. Individually they are all relativly small files, there is just a lot of them.

They are all organised in a folder with subfolders etc. We were looking at options around giving the team easier access to them from within the tool set.