Hi guys,
I'm very near completion of a part of a route that I wish to share with everybody, all that's left is registering a domain, designing the website and packing the files for distribution.
Yea, that last part has been abit of a mess during beta-testing. Here is what I've done in CMP: right click Route > List Dependencies > View in Main List > Save to CDP, and repeat same steps for the session.
Some beta-testers reported a couple of missing dependencies, some listed dozens upon dozens, and some run fine right out of the box. All of which is very confusing to be honest, this being my first time releasing something.
Can the more experienced route builders who've completed and released big routes kindly share what you did in the distribution process? I'd have preferred to upload it to the DLS, but during construction many non-DLS assets were used (it was not originally intended for public) so that is out of the question. My goal is to make the installation process for users as seamless and straightforward as possible, through the all-inclusive er..inclusion of every asset used in both Route and Session. These days large file size is not a big concern as most people have high-speed connections and I have access to a server with FTP upload capability.
Manually hunting down every reported missing kuid and reuploading them for every release would be prohibitively time-consuming and unfeasible, so a workaround is needed.
Your advice is much appreciated.
Cheerio,
Nicholas
I'm very near completion of a part of a route that I wish to share with everybody, all that's left is registering a domain, designing the website and packing the files for distribution.
Yea, that last part has been abit of a mess during beta-testing. Here is what I've done in CMP: right click Route > List Dependencies > View in Main List > Save to CDP, and repeat same steps for the session.
Some beta-testers reported a couple of missing dependencies, some listed dozens upon dozens, and some run fine right out of the box. All of which is very confusing to be honest, this being my first time releasing something.
Can the more experienced route builders who've completed and released big routes kindly share what you did in the distribution process? I'd have preferred to upload it to the DLS, but during construction many non-DLS assets were used (it was not originally intended for public) so that is out of the question. My goal is to make the installation process for users as seamless and straightforward as possible, through the all-inclusive er..inclusion of every asset used in both Route and Session. These days large file size is not a big concern as most people have high-speed connections and I have access to a server with FTP upload capability.
Manually hunting down every reported missing kuid and reuploading them for every release would be prohibitively time-consuming and unfeasible, so a workaround is needed.
Your advice is much appreciated.
Cheerio,
Nicholas