Wierd title, I know
After a conversation in the screenshots forum, I had a bit of a brainwave. I've always seen dozens of tiny threads about missing depenencies, post dozens more posts spamming release threads about "where does such-and-such come from?" and "where can I find this-and-that?" And despite what anyone else says, trying to find missing dependencies via Google is like pulling teeth: more often than not you're directed to a thread here that someone else posted about trying to find the same dependecies! Here's the worst part, half the time nobody ELSE who replies knows where they are!
That led me to the aforementioned idea. I thought, "why not start a central thread where people could post the dependency(/ies) they're missing?" I figured a single location like this was a good idea because A) there would now be a specific place you can go to if you want to ask about something missing, basically eliminating the infamous game of "Hunt the KUID" plus , B) if anybody else is missing the same thing(s), all they have to do is scroll through the thread and look for it.
There are some guidelines:
1. Linking directly to the site(s) of the author(s) who created the asset(s) is perfectly fine, as is directly linking to the download, as long as that link comes from the author(s) site(s).
2. In the above case, bear in mind that links can change, so the asset might not always stay in the same place. I'll do my best to keep on top of them, and I might ask a friend of mine to help me out (read: He's gonna get Shanghaied into service helping me with the monstrosity I could very well have just created)
3. Sending an asset via PM is not recommended, nor is asking for it to be sent to you via e-mail, especially if you flat-out post your e-mail adress here on the forums (believe me on that one; I've gotten more than enough spam over my tenure here that I will never forget that lesson).
4. Under NO circumstances is someone allowed to upload a copy of someone else's work to their own site/the DLS/TPR/whatever, UNLESS they have specific permission of the author first; first off it's Illegal, and second it's just plain disrespectful.
5. If you are someone who was directed here in search of an asset, I highly discourage simply scrolling through the thread. Instead, use the "search thread" function on the top center/right just above this leading post and every post at the top of the following pages. I will post a "how-to" on how to use this at a later time.
6. I add this one because I have personally come across these instances a number of times; there will be cases (especially in relation to DLS-hosted content) where an asset will have one of its depencies updated with a 2:XXXX:XXXXX:1 number, which obsoletes the original and removes it from the DLS, thus listing the asset as "Missing" since often the main object doesn't get updated and its config still contains the old KUID number (There are a few of Vulcan's aircraft that do this, for example). If that is the case, and the question comes up here, I will leave this notice here as a reminder: Exhaust all options before coming here! Search the DLS first, I beg of you. If nothing else, punch in the old KUID number, or even just the first half, which is the author's personal ID number. In addition, I have come across several locomotives whose configs contain erronious KUIDs that are not required for the loco to function. and are often only listed in one place. here again, I add this notice: Exhaust all options before coming here! If the asset is not on the DLS, then check the the config file to see what the KUID is for (bogey, hornsound, corona, etc.) and if it is even needed at all.
So, with that, I open this up to all of you. Hopefully this will put a damper on all those saturdays spent waltzing all over the blasted internet trying to find that one dependency that seems to have dropped off the face of the planet.
fire away boys!
After a conversation in the screenshots forum, I had a bit of a brainwave. I've always seen dozens of tiny threads about missing depenencies, post dozens more posts spamming release threads about "where does such-and-such come from?" and "where can I find this-and-that?" And despite what anyone else says, trying to find missing dependencies via Google is like pulling teeth: more often than not you're directed to a thread here that someone else posted about trying to find the same dependecies! Here's the worst part, half the time nobody ELSE who replies knows where they are!
That led me to the aforementioned idea. I thought, "why not start a central thread where people could post the dependency(/ies) they're missing?" I figured a single location like this was a good idea because A) there would now be a specific place you can go to if you want to ask about something missing, basically eliminating the infamous game of "Hunt the KUID" plus , B) if anybody else is missing the same thing(s), all they have to do is scroll through the thread and look for it.
There are some guidelines:
1. Linking directly to the site(s) of the author(s) who created the asset(s) is perfectly fine, as is directly linking to the download, as long as that link comes from the author(s) site(s).
2. In the above case, bear in mind that links can change, so the asset might not always stay in the same place. I'll do my best to keep on top of them, and I might ask a friend of mine to help me out (read: He's gonna get Shanghaied into service helping me with the monstrosity I could very well have just created)
3. Sending an asset via PM is not recommended, nor is asking for it to be sent to you via e-mail, especially if you flat-out post your e-mail adress here on the forums (believe me on that one; I've gotten more than enough spam over my tenure here that I will never forget that lesson).
4. Under NO circumstances is someone allowed to upload a copy of someone else's work to their own site/the DLS/TPR/whatever, UNLESS they have specific permission of the author first; first off it's Illegal, and second it's just plain disrespectful.
5. If you are someone who was directed here in search of an asset, I highly discourage simply scrolling through the thread. Instead, use the "search thread" function on the top center/right just above this leading post and every post at the top of the following pages. I will post a "how-to" on how to use this at a later time.
6. I add this one because I have personally come across these instances a number of times; there will be cases (especially in relation to DLS-hosted content) where an asset will have one of its depencies updated with a 2:XXXX:XXXXX:1 number, which obsoletes the original and removes it from the DLS, thus listing the asset as "Missing" since often the main object doesn't get updated and its config still contains the old KUID number (There are a few of Vulcan's aircraft that do this, for example). If that is the case, and the question comes up here, I will leave this notice here as a reminder: Exhaust all options before coming here! Search the DLS first, I beg of you. If nothing else, punch in the old KUID number, or even just the first half, which is the author's personal ID number. In addition, I have come across several locomotives whose configs contain erronious KUIDs that are not required for the loco to function. and are often only listed in one place. here again, I add this notice: Exhaust all options before coming here! If the asset is not on the DLS, then check the the config file to see what the KUID is for (bogey, hornsound, corona, etc.) and if it is even needed at all.
So, with that, I open this up to all of you. Hopefully this will put a damper on all those saturdays spent waltzing all over the blasted internet trying to find that one dependency that seems to have dropped off the face of the planet.
fire away boys!
Last edited:
So that is why packages appear mid night 
