png can be lossless, but it is a raster-based format in the end. It's not a format to store vector images as far as I know. The most widely used for that nowadays is svg (I think, don't have any sources).
(2017-06-30, 12:12)Philippe Hurbain Wrote: [ -> ]Projection from top. So you need to set the dimension of image to match the base of the brick (40x80ldu), and create the pattern using a photo from top as guide (though since the curvature is rather low here, it won't make much difference)
OK, something like this:
[
attachment=2830]
Can you give me a hint how to project it in LDraw format?
(2017-06-30, 13:49)Philippe Hurbain Wrote: [ -> ]Same as usual...
Ah, OK. I am still not too comfortable with the format and metas for texturemapping.
Would attached files be suitable for the 1x4 brick and 1x4 tile?
Is my header format correct?
What about name giving? I thought about ie. 2431bh01 where bh stand for BrickHeads.
(2017-06-30, 12:50)Merlijn Wissink Wrote: [ -> ]png can be lossless, but it is a raster-based format in the end. It's not a format to store vector images as far as I know. The most widely used for that nowadays is svg (I think, don't have any sources).
Still Fireworks makes a great PNG and stores the vector info somehow.
I'll have to check if I can make svg.
(2017-06-30, 14:07)Jaco van der Molen Wrote: [ -> ]Ah, OK. I am still not too comfortable with the format and metas for texturemapping.
Would attached files be suitable for the 1x4 brick and 1x4 tile?
Mmhhh... Travis recommendation about image cropping is still (very) valid!
Quote:Is my header format correct?
No. I strongly suggest that you process files you submit to PT with Datheader
http://ldraw.heidemann.org/index.php?page=datheader (it's soooo easy to forget something!)
Quick review of issues:
- brick size must contain front space character in case size is one digit only, in order to ensure correct sorting
- You must inclue a license notice:
0 !LICENSE Redistributable under CCAL version 2.0 : see CAreadme.txt
- !Category must be ommited when the first word of description IS category
- History is not supposed to be there for a simple PT submit. Note that if you need history line (eg. for modifications, or for LDD shape notice), your name must be enclosed in [], not {}
- Keywords must not repeat words present in description
Quote:What about name giving? I thought about ie. 2431bh01 where bh stand for BrickHeads.
This one is a can of worm... Here is naming policy:
http://www.ldraw.org/library/tracker/ref/patterns/
So I would use 'B' code (superheroes), 2431pb0 and 3010pb0 (see also already used codes for each part:
http://www.ldraw.org/cgi-bin/ptpatterns.cgi?p=2431 and
http://www.ldraw.org/cgi-bin/ptpatterns.cgi?p=3010)
Don't forget the 'p' indicating pattern in filename.
(2017-06-30, 14:48)Philippe Hurbain Wrote: [ -> ] (2017-06-30, 14:07)Jaco van der Molen Wrote: [ -> ]Ah, OK. I am still not too comfortable with the format and metas for texturemapping.
Would attached files be suitable for the 1x4 brick and 1x4 tile?
Mmhhh... Travis recommendation about image cropping is still (very) valid!
Quote:Is my header format correct?
No. I strongly suggest that you process files you submit to PT with Datheader http://ldraw.heidemann.org/index.php?page=datheader (it's soooo easy to forget something!)
Quick review of issues:
- brick size must contain front space character in case size is one digit only, in order to ensure correct sorting
- You must inclue a license notice:
0 !LICENSE Redistributable under CCAL version 2.0 : see CAreadme.txt
- !Category must be ommited when the first word of description IS category
- History is not supposed to be there for a simple PT submit. Note that if you need history line (eg. for modifications, or for LDD shape notice), your name must be enclosed in [], not {}
- Keywords must not repeat words present in description
Quote:What about name giving? I thought about ie. 2431bh01 where bh stand for BrickHeads.
This one is a can of worm... Here is naming policy: http://www.ldraw.org/library/tracker/ref/patterns/
So I would use 'B' code (superheroes), 2431pb0 and 3010pb0 (see also already used codes for each part: http://www.ldraw.org/cgi-bin/ptpatterns.cgi?p=2431 and http://www.ldraw.org/cgi-bin/ptpatterns.cgi?p=3010)
Don't forget the 'p' indicating pattern in filename.
OK, great. It has been a while since I made a real part and got a little rusty on things
It would good to have a suffix for all Brickheadz patterns as there are and there will be a certain amount of part.
As "b" is for Superheroes and as not all Brickheadz are superheroes, there should be some kind of thinking before taking that letter I guess.
(2017-06-30, 17:47)Damien Roux Wrote: [ -> ]It would good to have a suffix for all Brickheadz patterns as there are and there will be a certain amount of part.
As "b" is for Superheroes and as not all Brickheadz are superheroes, there should be some kind of thinking before taking that letter I guess.
Let's use Z for Brickhead
z. So NNNNpz0, et. seq.
I've updated the
documentation.
