Though I could ask, would it work to just make them 3.7 for now, upload, and then revise them to 3.5 once the server's fixed? If they're 3.5 capable/validated, they should be ok, or close to, in 3.7.
Hmm, interesting idea.
I'm worried it would confuse Trainz though.
Let me clarify what I mean.
As I understand it, currently, if someone tries to download an asset that a route needs, it will check for the newest version of that asset that's valid for that build, but ignore newer versions of the asset that are meant for higher builds.
That's the common sense approach, and I believe that's how Trainz/CM does it.
But, if I was to upload 3.7 versions of the assets as version :1, and then later upload 3.5 versions of the assets as version :2, I wonder if it would work as intended.
It depends how clever or thorough they were when they wrote CM.
My worry is that the 3.5 versions uploaded at a later date may never be recognised by CM or Trainz, as they don't increase the build number set by the previous version, and that would mean my assets would be stuck at 3.7, which is exactly what this thread was against.
I've no problem uploading them as you suggest, until they roll back the support version, but only if I could be sure my worries are unfounded, and that I could set lower build versions on later asset versions.
