Hi,
When I tried to make sticker part, I faced a problem with Sticker Generator.

I saved 256 color BMP file from scaned real sticker image like below.





I tried to convert it to DAT file by Sticker Generator and got below result image.







When I saw this DAT file by LDview 4.1 and MLCAD 3.3, it showed like below.



I was disappointed at the result image so much.



Corresponding sticker part is here : http://www.ldraw.org/cgi-bin/ptdetail.cg...22303i.dat
It shows very high quality like below.
It looks like not from BMP image.





Here are my questions:

1. Why couldn't I get correct DAT file by Sticker Generator? Did I neglect any important option or anything else?

2. How can I get better quality sticker rather than from BMP file?

How come 3024.dat is exported as LDX_3024_dot_dat,
while 3008.dat becomes LDX_3008_dot_dat_sub_part?

This makes it impossible to create generic Datshine Attribute files compatible with LDView POV export.

And yes, I use unmodified, official versions:
3024.dat - !LDRAW_ORG Part UPDATE 2002-03
3028.dat - !LDRAW_ORG Part UPDATE 2004-03

/Tore

Would there be any interest in having an LDraw IRC channel?

I found one Tim created a long time ago but it's long dead.

I can see the potential for more in-depth discussions between LDraw software developers/users and discussions among PT admins about specific parts.

A real-time discussion format would allow for a higher level of discourse that would not be otherwise happen due to the long delays between post/read times between LDraw users.

There is also the disadvantage of these communications not being logged and thus matters discussed would not be on public record for reference by those who come after. Although a bot could easily log the public channel and publish it someplace, private discussions between two people would be nowhere to be found, and so it would not be ideal. For instance, I like how the LSC has done everything publicly so I was able to catch up on what I missed, if some of the debates had happened over IRC, I might not have been able to understand why some decisions were made because I could not find record of them, so we as a community would need to be careful about what discussions we have on IRC and publish transcripts of them if something noteworthy was concluded.

Just thought I'd throw the idea out there.

Following some discussion elsewhere I figured it would be worth writing a bit about this issue. I'll add to this if I think of things and welcome questions.

Introduction

LDView has offered the option of POVray export for quite a while now. This allows some quite powerful manipulations via POVray. Here I'll focus on two important options: Top include file and Bottom include file.

As the name suggests this inserts a line including a file either up top (straight after all parameters have been declared) or down bottom (right at the end of the file). Combined with the list of parameters this allows quite a lot of automation via these include files, beyond that which could be expected from the export alone.

Top include file

This file is particularly useful for overriding colours but might also be used for other things. It has access to all parameters output by LDView including details of the camera, floor, model bounds and other details but typically would probably just include personal declarations for colours.

Note that the colours LDview declares are only ever called if the colour isn't already declared. So whatever colours you declare will carry through to all other parts.

I've attached my default file legocols.inc here (note it calls lugnetcolors.inc but you can comment this out).

Bottom include file

This file is very important. It can be used to declare the floor, override the camera, declare lights (if you don't like the defaults switch them off and set them here). And it too has access not only to the same declared parameters as the top include file, but also indirectly to the filename details [1].

For example I like to surround all my POVray files by a large sphere with a skymap to improve (IMO) render quality. This depends both on the distance of the lights and camera (they must be inside the sphere) but also on the floor position (so I can center the sphere appropriately). The details are unimportant but I can get all this useful information straight from the main file.

Similarly I like to set my own lights to improve rendering. Again these are set in the include file.

Perhaps most useful for many people (and the reason this file is called last) is the ability to use the include file to override the camera. POVray only ever uses the last declared camera so whatever is declared in the include file is what will be used in the rendering. This is especially useful for animation. Note that the camera you set here means the camera set by LDView will be ignored. If you wish to use the camera set by LDView you must use the parameters LDXCameraLoc, LDXCameraSky and LDXCameraLookAt

I've attached my default file ldview.inc here (it may not run due to other files but it can be read).

Attached Files

  legocols.inc (Size: 17.58 KB / Downloads: 1)
  LDView.inc (Size: 1.74 KB / Downloads: 2)
  floorsphere.inc (Size: 1.27 KB / Downloads: 1)

anybody interested in making the dolphin?
http://www.bricklink.com/catalogItem.asp?P=6228u

There is a LDD shape available....

I think I'd like to add an off topic forum. I sometimes have technical question that aren't necessarily LDraw related that I know a lot of the regulars here can answer. It would at worst save me a frustration Google search. Of course any off topic forum will be heavily moderated and flame wars, etc... would be ruthlessly terminated.

Feature request:
- MPD model support. Too late into my authoring of the Super Star Destroyer did I find out that SR 3D Builder doesn't apper to support MPD models. If it does, it's not readily apparent.

Quesiton:
- Is there a good usage tutorial for using this program? The user manual was decent at explaining how to edit and move parts around but less helpful in how to move the camera around.

Hi,
Here is the most huge official technic model ever

You can download my model at http://pds22.egloos.com/pds/201111/29/09/8110.zip
LDR file contain the code line for stickers but L3B file don't, because SR3D couldn't read the file with the stickers to the end.
I recommend that if you want to use SR3D, then choose L3B file, and if LDview or MLCAD, then LDR file.

Here is the sticker files that I used as reference. (You should download at parts folder and do 'Scan part' in MLCAD)
http://www.ldraw.org/cgi-bin/ptscan.cgi?q=4622303
http://www.ldraw.org/cgi-bin/ptscan.cgi?q=4631649

Enjoy

KWON

Attached Files

  8110.ldr (Size: 562.58 KB / Downloads: 27)
  8110.L3B (Size: 551.03 KB / Downloads: 6)

Personally I've always got a bit annoyed seeing embedded images larger than about 500x500px. They take up too much screen real estate and, more importantly, make browsing on small screen devices like phones very difficult. Not to mention the excessive bandwidth.

So I'd like to see a maximum size limit imposed on them. Whether by request or software.

Tim

I think that it might be a good idea to open Annoucements to responses. We've already got a place to make announcements that can't be responded to (on the website) and, many of the topics we've opened have to be duplicated elsewhere for further discussion (most recently by Travis).

I'm not saying anyone would be able to start a topic there, but I do think allowing responses would be a good thing.

Tim