Need help? Ask me.

I would like to say any developing help for objects ONLY i am here to help. Both ".csv" and ".animated" files are my main areas of knowledge. I don't really understand ".B3D" files, neither do i understand coding for routes. But by all means hit me a pm if you need any help. or post here too.

Seems fair enough mrknowitallexceptb3dfiles, expect to be bombarded with questions that would make teh spanish inquisition seem tame.

I know about them, making the name work i just am not 100% , And the more the merrier

Good to have a volunteer. Anyway, you might not be the only source of information here, but you definitely will be a valuable one.

.b3d files are not greatly different to .csv ones. A lot of people prefer .b3d as the syntax is tidier, with less typing to do.
Main differences, csv first, .b3d equivalent:
CreateMeshBuilder, = [meshbuilder]
AddVertex, = vertex
AddFace, = face
SetColor, = color
GenerateNormals, = not used
LoadTexture, = [texture]
load filename
SetTextureCoordinates, = coordinates
SetDecalTransparentcolor = transparent

You see, its a lot less wordy and no need for comma after command word.
Now go and throw all those mouldy old .csv files in the bin!!

I'll go along with that. Although i dont do developing myself I can never understand why people want to type 3 times as much wording into a file which doesn't do any more than a b3d file. Csv is a waste of space and must surely slow down the sim. Also why do people persist in using the generatenormals bit, which is ignored by openbve, and put commas at the end of each line, which aren't necessary?

I would not do that, since *.b3d cannot use commands "cube" and "cylinder". Therefore it would be much more typing and calculating when creating these...

EDIT: OK, that was a test. I was just curious whether somebody will correct me. Good to know you will, since I am just a human, who sometimes makes mistakes, of course.

Derryck wrote:I would not do that, since *.b3d cannot use commands "cube" and "cylinder"..

This is a misconception. They certainly do recognise these commands. Same syntax but without the comma.
Csv files have absolutely no more functionality at all over b3d files.

Right, a point for you. By the way, I have heard the above mentioned argument so many times I have been loosing count.

Humorist wrote:I'll go along with that. Although i dont do developing myself I can never understand why people want to type 3 times as much wording into a file which doesn't do any more than a b3d file. Csv is a waste of space and must surely slow down the sim. Also why do people persist in using the generatenormals bit, which is ignored by openbve, and put commas at the end of each line, which aren't necessary?

Well, in my case, it is more of a habit than a strict sticking to one format... I usually create new object by simply copying one face from another and then just modifying vertex positions. So, should I break that habit?

Looking at the wonderfully detailed items in the First Brno route I think the answer must be, "Whatever works best for you". And your results seem to show that your methods are right. I have looked a bit at some object building tips, as I thought I would like to give it a try. I found a simple guide for eejits (whatever those are??) on that paddy website and Mick or whatsisname seems to go with the b.3d files. Can't be too hard then! If anyone wants a peep I found the stuff here, http://www.iwrsim.graymacimage.com/iwrsimdownloads.html

I've worked with objects of both types at the same time (Al's Class 47 and the TSC Mk2 stock, .b3d and .csv respectivley) and of the two i prefer .b3d simply because it seems less prone to dodgy typing. Looks neater too. It seemed easier to mentally swich from working on a .csv to .b3d than the other way round.

Humorist wrote:Also why do people persist in using the generatenormals bit, which is ignored by openbve, and put commas at the end of each line, which aren't necessary?

In the case of the former, usually because an object has been derived from another older object, and i'm not sure that anyone would think to actually bother removing them- they're like CreateMeshBuilder/[Meshbuilder], you get to regard them as part of the furniture, and in the case of the latter, i'd suspect automatic typing. Personal preference though; for example, i always prefer the same number of digits in each column for e mesh, as i find it easier to find what i'm looking for, i'll usually change the parts of a file i'm working on to be like that, but i wouldn't bother changing the whole lot.