mezzoprezzo
Content appreciator
Preferably the correct one!
The asset name says "Box Cargo", but the description (see last line in the posted sceenshot) clearly say logs.
Attention Content Creators
- Thread starter timberdv
- Start date
- Status
The asset name says "Box Cargo", but the description (see last line in the posted sceenshot) clearly say logs.
BLACKWATCH
Mechanical Engineer
Anyone got a screenshot to spare ?
NSWGR_46Class
Just call my Captain Rude
The saddest part about this is thanks to PEV tools there is a real quick and easy way to do the screenshot thumbnail from the IM file and really is no excuse for not doing it as part of the process of writing / setting up the config file. It really is just as easy as two moue clicks and it all done for you.
Thank you Zec for your clear and concise post on this matter.
However, I must take you to task on the matter of the 'description'. I have just noticed some updated content on the DLS which appeared today (14th Jan) from Auran (author name). While all of the items had an accurate thumbnail, none of them had a description.
Peter Ware
However, I must take you to task on the matter of the 'description'. I have just noticed some updated content on the DLS which appeared today (14th Jan) from Auran (author name). While all of the items had an accurate thumbnail, none of them had a description.
Peter Ware
Interesting, because I cannot remember a similar discussion in the last few years or at least since I have been actively monitoring the forums.
I think the description should clearly identify the asset and it's purpose. If it is a complex asset, say part of a set or toolkit then an HTML pointer to somewhere that explains it would be useful. For example, trying to use the AJS station kit without reading the instructions would be foolish.
The point about narrow gauge is a good one. I'm not a NG person but I had occasion to build a test track while testing something for NG and I soon found out the issues identified in the earlier posts.
Perhaps the config.txt tags could be expanded to include additional tags that provide more information. Some of those tags could be mandatory. As a start how about:
I like to write my description fields and other relevant tags when I first create the asset. I don't see it as polishing or a job to be done when the asset is complete. If anything, I may forget to go back and see if my original prose is still relevant.
Likewise, I write comments in my Trainzscript (and other) code as I write it because it helps me understand what I am building.
BTW I do not see the OP as "the correct way" of documenting an asset. It is one way.
Cheers
I think the description should clearly identify the asset and it's purpose. If it is a complex asset, say part of a set or toolkit then an HTML pointer to somewhere that explains it would be useful. For example, trying to use the AJS station kit without reading the instructions would be foolish.
The point about narrow gauge is a good one. I'm not a NG person but I had occasion to build a test track while testing something for NG and I soon found out the issues identified in the earlier posts.
Perhaps the config.txt tags could be expanded to include additional tags that provide more information. Some of those tags could be mandatory. As a start how about:
Code:
Description: (mandatory)
Purpose: (mandatory)
Special requirements: (optional)
Track gauge: (optional)
TrainzDev WiKi page: (optional) (special instructions)
...I like to write my description fields and other relevant tags when I first create the asset. I don't see it as polishing or a job to be done when the asset is complete. If anything, I may forget to go back and see if my original prose is still relevant.
Likewise, I write comments in my Trainzscript (and other) code as I write it because it helps me understand what I am building.
BTW I do not see the OP as "the correct way" of documenting an asset. It is one way.
Cheers
I just find that funny because almost all of your assets have missing dependencies or typos in the config that could be fixed easily by CCP, yet here you are talking about other creators overlooking things.
That is not my experience. My CM has reported only 26 assets with problems (missing dependencies or otherwise) from the 741 NSWGR_46class assets that I have downloaded from the DLS. Thats 3.5% - hardly "almost all".
amigacooke
Well-known member
Some might say that H222's posts 'almost all' try to stir up trouble of some sort.
I wouldn't say that of course
PortlandBill
Member
Zec wrote:
Just downloaded 4 new assets by creator "Auran" none have a description. Surely, with the advent of T:ANE, new content provided by Auran/N3V should be examples of best practice that other people can follow?
Last edited:
I tried to look for a certain creation from "Rob" (523) on the DLS, he creates for N3V. Although he is an excellent content creator, most of his TS12 created items have no description. Why is this so?
I do not want to belittle Rob or neither pick a fight or argument, far from it but it seems there are certain rules for the common content creators and there are different rules for others.
Lennard
I do not want to belittle Rob or neither pick a fight or argument, far from it but it seems there are certain rules for the common content creators and there are different rules for others.
Lennard
I agree with Lennard that especially N3V or anyone publishing under the title of N3V should at least publish assets with a thumbnail and a description.
Btw, Lennard, where can I find your assets? No offence, but I just looked for content made by a certain "Lendorf" (#185369 ) on the DLS and I found nothing.
Btw, Lennard, where can I find your assets? No offence, but I just looked for content made by a certain "Lendorf" (#185369 ) on the DLS and I found nothing
.I agree with Lennard that especially N3V or anyone publishing under the title of N3V should at least publish assets with a thumbnail and a description.
Btw, Lennard, where can I find your assets? No offence, but I just looked for content made by a certain "Lendorf" (#185369 ) on the DLS and I found nothing
The reason you have not found any created content of mine (yet) is simple. I have not created for Trainz yet but nevertheless I am creating as we speak (or rather as I write):
Above is one new spline item among others I am presently working on. Perhaps you have read some of my posts regarding splines for TS12 3.7 in this forum, well, above is one such spline I have already placed in my TS12, 61388, and this will be soon, among others I will create, be on the DLS. I have been busy modding in another game in the past, hence my 3D experience but since I stumbled onto TS12 recently, I would like to do some creating there too.
For the last few weeks I have been reading up, asking here and probing in my TS12 all I need to know for creating content.
Happy with my explanation :wave:?
Lennard
If you ever find this Holy Grail or Nirvana, please let us know. Most of us are still stumbling around in the wilderness. Well, if not most of us, then at least me. :wave:
There are some types of assets I am comfortable with making but others elude me. That includes splines. Mostly because I haven't tried yet.
Dinorius_Redundicus
kuid 68213
You should not need to be a creator to have your opinion respected. I also think being a creator should not make one immune from criticism or correction. In fact they are the ones that most need it. Without feedback, we risk making the same annoying mistakes again and again. Polite feedback of course will get a better response.
The best way to learn something new is, if there is an "example" file to study and to examine, that includes a current config.txt. Sadly, there are lots of such example files still missing in the DevWiki but at least, through Rob's (N3V creator par excellent) generosity I was supplied with such example file.
Lennard
I agree with that and I saw Rob's post.
When I started building locos I spent a lot of time dissecting assets and asking myself questions such as "what does this do, and why is it here". But one has to be wary of older assets as the rules are changing.
Yup. Bit longer then I expected though :hehe: and I obviously overlooked one or more topics of your hand about splines.
And I agree with pcas1986; let us know when you figured those tunnel splines out.
I agree. Polite feedback from everyone is welcome; it is rare we get any however. Which is why I also replied politely to Lendorf.
I hope you agree it is not rare we get impolite feedback by people who never have and never had the intention yet to create anything themselves.
When I stop learning (and start making the same mistakes again and again), I will look for a new challenge (and when I stop teaching, I will look for a new job, but that's a different story :hehe
.- Status