(OpenTTD) North American Road Vehicle Set (NARVS)

[oberhümer]

(never mind, wrong assumption here)

[NekoMaster]

Maybe some American vehicles from Long Vehicles could be downsized... It seems that they are free to use if the author is credited, according to this.

THing is, I want my vehicles to be articulated. If someone can make them articulated then Ill include them

Edit : Some work on the 2010 International Lonestar

[NekoMaster]

New nightly in 2nd post Link

[oberhümer]

I coded up some of DanMacK's buses. Also, the Mercedes Sprinter has been sold as the Freightliner/Dodge Sprinter since 2001 in the U.S., replacing the Dodge Ram van(I might draw that), so it could go in. With modified livery, of course.

Also, maybe the Orion II for a small bus?

[andythenorth]

Neko - do you know the source of the template you are using?

I ask because I'm setting up Pikka's standard train templates for use with RVs. Thought it might be useful for other sets, and helps keep things to similar scale.

Won't be done for a while though, don't have much OpenTTD time at the moment

[NekoMaster]

Neko - do you know the source of the template you are using?

I ask because I'm setting up Pikka's standard train templates for use with RVs. Thought it might be useful for other sets, and helps keep things to similar scale.

Won't be done for a while though, don't have much OpenTTD time at the moment

Im using pikka's templates but sometimes some things get a little too big so thats why things look a little bigger then pikka's templates

[NekoMaster]

Update on First page, post 2

[OzTrans]

NFORenum is there for a reason; use it please. It does avoid having obvious blunders in your GRFs.

TTDPatch is not as forgiving as OpenTTD, it complains about incorrect graphics versions, as well as another couple of blunders. RVs ain't trains ...

NARV error.png

Code: Select all

// Automatically generated by GRFCODEC. Do not modify!
// (Info version 6)
// Format: spritenum pcxfile xpos ypos compression ysize xsize xrel yrel
    0 * 4	 1C 01 00 00
//!!Error (69): Invalid GRF version number.
//!!Warning (143): Offset 128: Using unspecified control character 0A.
    1 * 162	 08 01 04 5C 03 0C 4E 6F 72 74 68 20 41 6D 65 72 69 63 61 ... 
                 ... 42 6F 62 5F 6D 61 63 6B 65 6E 7A 69 65 0D 0A 43 6F 64 65 64 20 62 ... 
                 ... 72 68 FC 6D 65 72 00

  241 * 9	 02 00 0D 01 01 00 00 00 00
  242 * 7	 00 01 01 01 0A 0E FF
//!!Error (188): Offset 5: ID 0D is defined with feature 00.
  243 * 7	 03 01 01 0A 00 0D 00
  
  279 * 9	 02 01 07 01 01 00 00 00 00
  280 * 9	 02 01 06 01 01 01 00 01 00
  281 * 9	 02 01 05 01 01 02 00 02 00
  282 * 9	 02 01 04 01 01 03 00 03 00
  283 * 7	 00 01 01 01 56 0E FF
  284 * 7	 03 01 01 56 00 07 00
//!!For feature 1 the following cargoIDs have not been used since their most recent definition:
//!!04 (last defined at sprite 282)
//!!05 (last defined at sprite 281)
//!!06 (last defined at sprite 280)

[NekoMaster]

NFORenum is there for a reason; use it please. It does avoid having obvious blunders in your GRFs.

TTDPatch is not as forgiving as OpenTTD, it complains about incorrect graphics versions, as well as another couple of blunders. RVs ain't trains ...

NARV error.png

Code: Select all

// Automatically generated by GRFCODEC. Do not modify!
// (Info version 6)
// Format: spritenum pcxfile xpos ypos compression ysize xsize xrel yrel
    0 * 4	 1C 01 00 00
//!!Error (69): Invalid GRF version number.
//!!Warning (143): Offset 128: Using unspecified control character 0A.
    1 * 162	 08 01 04 5C 03 0C 4E 6F 72 74 68 20 41 6D 65 72 69 63 61 ... 
                 ... 42 6F 62 5F 6D 61 63 6B 65 6E 7A 69 65 0D 0A 43 6F 64 65 64 20 62 ... 
                 ... 72 68 FC 6D 65 72 00

  241 * 9	 02 00 0D 01 01 00 00 00 00
  242 * 7	 00 01 01 01 0A 0E FF
//!!Error (188): Offset 5: ID 0D is defined with feature 00.
  243 * 7	 03 01 01 0A 00 0D 00
  
  279 * 9	 02 01 07 01 01 00 00 00 00
  280 * 9	 02 01 06 01 01 01 00 01 00
  281 * 9	 02 01 05 01 01 02 00 02 00
  282 * 9	 02 01 04 01 01 03 00 03 00
  283 * 7	 00 01 01 01 56 0E FF
  284 * 7	 03 01 01 56 00 07 00
//!!For feature 1 the following cargoIDs have not been used since their most recent definition:
//!!04 (last defined at sprite 282)
//!!05 (last defined at sprite 281)
//!!06 (last defined at sprite 280)

If you havent relised it yet I'm only using GRF Maker because I don't know how to code. And looking through the stuff in grf maker theres nothing in there that is coded as a train.

[AndersI]

If you havent relised it yet I'm only using GRF Maker because I don't know how to code.

Then you should be happy to get help GRFMaker can't magically eliminate the need to understand what you're doing, it just helps with the details.

And looking through the stuff in grf maker theres nothing in there that is coded as a train.

There probably is, even though you don't see it immediately. Note that all the 'Vehicle X' blocks in GRFMaker have a field where you select the type of vehicle - Train being the default. Maybe you have missed to change one? You can definitely trust OzTrans + NFORenum: If they say something "is", it's quite stupid trying to defend "no, it isn't"

[NekoMaster]

If you havent relised it yet I'm only using GRF Maker because I don't know how to code.

Then you should be happy to get help GRFMaker can't magically eliminate the need to understand what you're doing, it just helps with the details.

And looking through the stuff in grf maker theres nothing in there that is coded as a train.

There probably is, even though you don't see it immediately. Note that all the 'Vehicle X' blocks in GRFMaker has a field where you select the type of vehicle - Train being the default. Maybe you have missed to change one?

NFO Coding is a little too complicated for me.

And after a closer inspection, turns out the sprite block for the ACF-Brill was a train one, then again I only copy and pasted the data from the stuff oberhümer uploaded not too long ago

[AndersI]

NFO Coding is a little too complicated for me.

But that makes it an interesting challenge, especially as we (NFO dabblers) try it because we want to see our things in the game!

Don't give up yet!

[NekoMaster]

NFO Coding is a little too complicated for me.

But that makes it an interesting challenge, especially as we (NFO dabblers) try it because we want to see our things in the game!

Don't give up yet!

When I say Its too complicated I mean it, I could probably do C+ or Java if I tried but NFO is far too confusing because its only numbers for the most part, and most values I don't know what they do.

[AndersI]

NFO is far too confusing because its only numbers for the most part, and most values I don't know what they do.

The Wiki will tell you - but not in five minutes.

[NekoMaster]

NFO is far too confusing because its only numbers for the most part, and most values I don't know what they do.

The Wiki will tell you - but not in five minutes.

Still too confusing, and why can't I just be a sprite artist? I know theres sets out there with seperate spriters and coders\

EDIT : Update in 2nd post, fixed the sprite block problem...

[NekoMaster]

Update : Fixed ACF-Brill Alignment (I dunno why it got like that in the first place :\ )

You can find the updae in the second post (or in my signature)

[Emperor Jake]

Great set, but there's one thing that bugs me...
What is it with these purple windows cropping up everywhere? They look really ugly IMO. Window colour should be mauve.

Thanks,
Jake

[ColdIce]

Emperor Jake, why do you ask the same question on 3 different topics?

[NekoMaster]

Great set, but there's one thing that bugs me...
What is it with these purple windows cropping up everywhere? They look really ugly IMO. Window colour should be mauve.

Thanks,
Jake

Its the color that most people use for vehicle windows

[colossal404]

Its the color that most people use for vehicle windows

Oh yeah? I think the most popular is mauve (darker or lighter, doesn't matter), not purple...