LDraw.org Discussion Forums

Full Version: Some of my youth town series models
You're currently viewing a stripped down version of our content. View the full version with proper formatting.
this were some of the models i had at home. others were already build by some other ldraw users. if i recall more models i will be uploading them too


[Image: AOBupzq.png]

Set: 6609-1 - Race Car
Year: 1980
OMR Compliant: Yes
Missing: Nothing
CAD: LdCad 1.6b "the beast"
Comments: This was my fist ever Lego kit i had. This one is the guilty kit to my self being here posting lol....
[Image: DRjjjzz.png]

Set: 6608-1 Tractor
Year: 1982
OMR Compliant: Yes
Missing: Nothing
CAD: LdCad 1.6b "the beast"
Comments: This was my fist Lego kit i purchase with my money, i still remember it cost me 8usd. It was a loooooot of money for a kid in those days.
[Image: 9dAY9Fa.png]
Set: 6657-1 - Fire Patrol Copter
Year: 1985
OMR Compliant: Yes
Missing: Nothing
CAD: LdCad 1.6b "the beast"
Comments: none
[Image: Mr127wS.png]

Set: 6688-1 - Ambulance
Year: 1985
OMR Compliant: Yes
Missing: Nothing
CAD: LdCad 1.6b "the beast"
Comments: none
[Image: T33k4Rs.png]

Set: 6612-1 - Fire Chiefs Car
Year: 1986
OMR Compliant: Yes
Missing: Nothing
CAD: LdCad 1.6b "the beast"
Comments: none
Very nice! What renderer? No logo on studs? on these tiny models, they are really lacking Wink
(2019-05-02, 11:55)Philippe Hurbain Wrote: [ -> ]Very nice! What renderer? No logo on studs? on these tiny models, they are really lacking Wink

im using stud.io, it may be not showing the logos due it has low resolution configured on the parameters. let me test with the tractor and upload it on hi res.

[Image: pYY9K6u.png]

UPDATE: No its not. i m rendering with hi res parameters now, and its not showing me the lego logos, i dont know why any idea?
Ldview shows me the logo on the studs. it should be an issue with studio configuration. or may be studio its not rendering any longer the lego logo. dont know

UPDATE2: yes its in the rendering configuratation on stud.io you can enable or not le stud logo.

[Image: TKv428L.png]


[Image: TeqPqgW.png]


they look like chinese Lego version lol

@philo render edition Wink

[Image: y9KCD5W.png]

This other render has enable some scratches on the bricks. (this are all options on studio render configuration) Stud logos / Uv degradation / Scratches)

[Image: JZLYIH4.png]


This has some extra Scratches and Uv Decoloration. it looks like he has a hardworkWink
[Image: 8ijjLnb.png]

Set: 7733-1 - Truck & Forklift
Year: 2008
OMR Compliant: Yes
Missing: Stickers, Minifigs
CAD: LdCad 1.6b "the beast"
Comments: ok.... this wasn't when i was kid Wink
The forklift is not on the same level as the truck and seems floating in mid air Wink

Are you using rubber black for the tires? they look quite shiny...
(2019-05-02, 15:10)Philippe Hurbain Wrote: [ -> ]The forklift is not on the same level as the truck and seems floating in mid air Wink

Are you using rubber black for the tires? they look quite shiny...

this is a special version of the forklift its levitation version lol.  Wink

i made the pbg file grabbed from rebricable. The colors are the ones set from Rebricable, i did not change them. i will pay attention on that detail. and re render to check how it looks.

Now that you mention that i though the same, the render was too shinny but i thought it was due how the render was done not due the material, now im rendering a new one with rubber black on the wheels and let you show.

update:

[Image: afxHT01.png]

They look better but dont know if they look natural either.
(2019-05-02, 16:46)tatubias Wrote: [ -> ]The colors are the ones set from rebricable, i did not change them. i will pay atention on that detail. and re render to check how it looks.

I already brought up the rubber color issue with Rebrickable. The problem is that Bricklink doesn't have a separate color for rubber black. Therefore all black tires are assigned color 0 (Black) and not color 256. This won't change until they implement some sort of material classification to the parts.
(2019-05-02, 16:51)Orion Pobursky Wrote: [ -> ]I already brought up the rubber color issue with Rebrickable. The problem is that Bricklink doesn't have a separate color for rubber black. Therefore all black tires are assigned color 0 (Black) and not color 256. This won't change until they implement some sort of material classification to the parts.

Excellent, good to know for future renders Wink
[Image: 4pKxNT9.png]

Set: 6607-1 - Service Truck
Year: 1982
OMR Compliant: Yes
Missing: Stickers
CAD: LdCad 1.6b
Comments: i did not have this, but i like it.
Renderer: Stud.io 2
[Image: 1xCgAOe.png]

Set: 6651-1 - Post Office Van
Year: 1982
OMR Compliant: Yes
Missing: Stickers
CAD: LdCad 1.6b
Comments: I did not realize that it was already published Wink on omr site.
Renderer: Stud.io 2
[Image: Ng4DKGi.png]


Set: 6653-1 - Highway Maintenance Truck
Year: 1982
OMR Compliant: Yes
Missing: Stickers
CAD: LdCad 1.6b
Comments: I did not realize that it was already published [Image: wink.png] on omr site.
Renderer: Stud.io 2
[Image: FiUoHHU.png]



Set: 6675-1 - Road & Trail 4x4
Year: 1988
OMR Compliant: Yes
Missing: Stickers
CAD: LdCad 1.6b
Comments: I did not have this but i like it too.
Renderer: Stud.io 2
fun models but what's with all the people from krypton?

You could use 2D projection mode to make sure all things are aligned with the car wheels at ground level.
(2019-05-04, 17:50)Roland Melkert Wrote: [ -> ]fun models but what's with all the people from krypton?

You could use 2D projection mode to make sure all things are aligned with the car wheels at ground level.

this happens when i try to arrange the objects using studio., thats all.
[Image: xSqE6Xw.png]

Set: 6605-1 - Road Racer
Year: 1984
OMR Compliant: Yes
Missing Stickers: No
Missing Patterns: Yes (3039pb007.dat)
CAD: LdCad 1.6b "the beast"
Renderer: Stud.io
Comments: Its missing the brick 3039pb007.dat that its a 2 x 2 slop with a "3" printed. i will be making this part, i will be posting it in a minutes.
[Image: Zw826v4.png]

Set: 6606-1 - Road Repair Set
Year: 1983
OMR Compliant: Yes
Missing Stickers: Yes
Missing Patterns: No
CAD: LdCad 1.6b "the beast"
Renderer: Stud.io
Comments: None
[Image: FYkYpV8.png]

Set: 6641-1 - 4 Wheelin Truck
Year: 1987
OMR Compliant: Yes
Missing Stickers: No
Missing Patterns: No
CAD: LdCad 1.6b "the beast"
Renderer: Stud.io
Comments: None
[Image: Mbm04jD.png]


Set: 6647-1 - Highway Repair
Year: 1980
OMR Compliant: Yes
Missing Stickers: No
Missing Patterns: Yes
CAD: LdCad 1.6b "the beast"
Renderer: Stud.io
Comments: None
[Image: JfcoQn0.png]


Set: 6658-1 - Bulldozer
Year: 1986
OMR Compliant: Yes
Missing Stickers: No
Missing Patterns: Yes
CAD: LdCad 1.6b "the beast"
Renderer: Stud.io
Comments: None
[Image: UVkKOQV.png]

Set: 7236-1 - Police Car, Black Logo
Year: 2005
OMR Compliant: Yes
Missing Stickers: No
Missing Patterns: Yes
CAD: LdCad 1.6b "the beast"
Renderer: Stud.io
Comments: None
[Image: fBUxoo8.png]
Set: 7245-1 - Prisoner Transport, Black Logo
Year: 2005
OMR Compliant: Yes
Missing Stickers: No
Missing Patterns: Yes
CAD: LdCad 1.6b "the beast"
Renderer: Stud.io
Comments: None


not Kryptons guys here!!!!
i have updated all the download links. also here are all the files together. all files look like this output.

i have lots the file of Set: 7733-1 - Truck & Forklift


[Image: YlW68jB.png]
In principial the files are OMR compliant, but 3 little things.

First the file names should be renamed to for example "6608 - Tractor.mpd" without the Qualifier after the set number.
See http://www.ldraw.org/article/593.html

Base File Naming
Each model in the OMR will consist of several files that are packaged together into a single MPD file. For sets that include instructions for multiple models, each model will have its own MPD file. Each MPD for the set will be named in the following manner:
Code:
<Set Number>[-<Optional Qualifier>] - <Set Name>[ - <Sub Model Name>]

The optional Qualifier is not mandatory and gets added only if there is more than one set that could be assigned the same.
The first set using a given number would be understood to never contain the qualifier however numbering should start with the oldest set and some investigation should be done in existing set databases.


Second:
If the Model only use one .ldr file, this file shoud be insert in a .mpd file.

Third: The file 7733-1 - Truck & Forklift.zip contains a .png file not the .ldr file.

I have OMRized the files and attached.
I will upload the the files to the OMR asap.

Johann
(2019-05-29, 20:06)Johann Eisner Wrote: [ -> ]In principial the files are OMR compliant, but 3 little things.

As those models are drawn with LDCad using its "Clean up" tool to omr a mpd should be much easier then all those manual checks

It's in the file menu.
(2019-05-29, 20:12)Roland Melkert Wrote: [ -> ]As those models are drawn with LDCad using its "Clean up" tool to omr a mpd should be much easier then all those manual checks

It's in the file menu.

So was my approach to these files.
1st .: file opened
2nd: added new submodel "Main"
3rd: .ldr file inserted into the "Main" submodel
4th: Main submodel defined as "Main Model"
5th: File cleanup..
6th: saved as .mpd
7th: cross-checked with MPD Center

I love the "Cleanup" in LDCad.
Thank you guys,  for all the consideration and comments.

Regarding Third: The file 7733-1 - Truck & Forklift.zip contains a .png file not the .ldr file. I made amiatake and delete the original one so i did lose all that model.
hovercraft ambulance? Wink
(2019-05-30, 13:30)Steffen Wrote: [ -> ]hovercraft ambulance? Wink

It could happen. Although I think it might maneuver somewhat terribly.
(2019-05-29, 20:58)Victor Di Rienzo Wrote: [ -> ]Thank you guys,  for all the consideration and comments.

Regarding Third: The file 7733-1 - Truck & Forklift.zip contains a .png file not the .ldr file. I made amiatake and delete the original one so i did lose all that model.

My file of 7733 - Truck & Forklift uploaded in the thread "2000+ Town, Trains, Buildings, etc"

[attachment=4550]

Happy new year
Updated set 6609:
- Corrected the tyre colour (256 rubber black)
- Split submodel of minifig

[attachment=6673]
[attachment=6674]

OMR conform
Missing items: none
Updated set 6647:
- Split submodel of minifig
- Added missing stickers and tree 3471

[attachment=6678]
[attachment=6679]
Updated: Corrected misplaced parts (tyres)

[attachment=6797]
[attachment=6798]

OMR conform
Missing items: none
Updated: Corrected misplaced parts (tyres)

[attachment=6799]
[attachment=6800]

OMR conform
Missing items: none
Updated: Added missing sticker, corrected tyre colour, and split submodels

[attachment=6855]
[attachment=6856]

Currently not OMR conform (Unofficial stickers not inlined)
Missing items: none
Updated: Corrected colours, prints, and misplaced parts

[attachment=6915]
[attachment=6916]

OMR conform
Missing items: none
Updated: Corrected colours and misplaced parts (removed the stray arm causing "hovercraft ambulance" :-) )

[attachment=7048]
[attachment=7049]

OMR compliant
Missing items: none
Updated: Corrected missing parts and split minifig submodel

[attachment=7302]
[attachment=7303]

OMR compliant
Missing items: none
Updated: Corrected misplaced parts and split minifig submodel

[attachment=7317]
[attachment=7318]

OMR compliant
Missing items: none
Updated: Corrected misplaced parts and colours

[attachment=7405]
[attachment=7406]

OMR compliant
Missing items: none
Updated: Corrected misplaced parts and colours

[attachment=7527]
[attachment=7528]

The hovering problem is due to 8-LDU (a plate) offset between front and rear axles.
I've resolved this by inclining the vehicle to front slightly.
(2022-02-11, 14:41)Takeshi Takahashi Wrote: [ -> ]Updated: Corrected misplaced parts and colours




The hovering problem is due to 8-LDU (a plate) offset between front and rear axles.
I've resolved this by inclining the vehicle to front slightly.

This is where my imagined "put on ground" script would come in handy. :-)