Welcome, Guest |
You have to register before you can post on our site.
|
Forum Statistics |
» Members: 4,999
» Latest member: TSAI
» Forum threads: 5,993
» Forum posts: 50,709
Full Statistics
|
Online Users |
There are currently 406 online users. » 0 Member(s) | 402 Guest(s) Applebot, Baidu, Bing, Google
|
|
|
*** MLCad V3.40 *** |
Posted by: Willy Tschager - 2011-12-27, 16:39 - Forum: LDraw Editors and Viewers
- Replies (15)
|
 |
Crossposting from Lugnet.com/Cad:
Hello all,
I would like to announce that there is a new version of MLCad available!
MLCad V3.40
What's new:
- Implemented basic undo functionality (might be a bit slow, but should work)
- Improvements for network installation or installation under Windows Vista and above.
MLCad now doesn't write to its installation path anymore.
- Save pictures in more formats, now supporting Bitmap, Jpeg, Gif, Tiff and Png.
- Serveral bug-fixes
More detailed information is available in the release notes and on the web-site:
http://mlcad.lm-software.com
I wish you fun with the new release and a HAPPY NEW YEAR!
Best regards,
Michael
|
|
|
Idea/Proposal: Create a Part Update Schedule |
Posted by: Jude Parrill - 2011-12-27, 2:41 - Forum: Parts Authoring
- Replies (10)
|
 |
This is something I've been thinking about for some time, and now that there's a new Part Update looming and excitement in the air, it's been on my mind even more.
It would be REALLY nice if there was some kind of release schedule for the Part Updates. I can think of a couple good reasons for this: Firstly, users would know when to expect new releases. Instead of just checking in periodically to see if there's been a new update, they'd have solid date(s) for when to look for them. Additionally, I do think this would actually improve some of the throughput from the PT. By introducing deadlines, you create a period of "crunch time" where part creators work faster/harder than they normally would in order to get the most possible parts released.
Consider the recent stickied post "Parts for Urgent Review" and the response that has gotten and the increase in parts that'll now be available for the next update. That thread essentially created a crunch time by saying, "A part release is coming VERY SOON, so you'd better ready your parts." And what happened? People started working much faster and harder than usual in order to get as many parts as possible into the next update. Now imagine that happened everytime there was a release. Would that be such a bad thing?
Personally, I think a 2-updates-per-year schedule is probably ideal, although I do think a strong case could be made for 3 updates as well (I think 4 may be a bit excessive and demanding, but maybe I'm wrong). Last year saw 3 updates spread evenly apart, and so far this year, we've had one update with presumably one more to be released before/around the end of the year.
So, how would this work? Let's say a 2 UPY schedule was agreed upon. Furthermore, it was agreed upon that the updates would be released at the ends (30th or 31st) of June and Decemember. Now, there would likely end up being several deadlines involved.
For example, for the June release, you might have:
June 15th - Deadline for Part Certification.
June 27th - Deadline for Part Review.
June 30th - Update is Officially Released.
So part makers and reviewers would have until the 15th to get their parts certified for the next update, the admin would then have approximately two weeks to review as many parts as he/she can for the update. Then, those who prepare the release (is this also the Admin?), would have a couple days to make any last preperations needed, get everything in line, and publish the release. Obviously, these dates may need to be adjusted, but I think you get a sense of the general process involved.
Would the LSC and/or Steering Commitee (I can never keep track of what each of these does), in conjunction with the Parts Admin, consider the possibility of formalizing a release schedule (and then ensure that it is adhered to)?
|
|
|
replacing the filename with the file data but getting no graphical data |
Posted by: SNIPE - 2011-12-26, 21:55 - Forum: Parts Authoring
- Replies (21)
|
 |
Hi,
If you load in a file data to a project, how do you edit the part colour like you would if you were to edit an entire sub part, for example by typing:
'1 16 0 -4 0 6 0 0 0 1 0 0 0 6 4-4disc.dat'
The '4-4'stud.dat' part is replaced by the file data, and that file data is listed below:
3 16 0 0 0 1 0 0 0.9239 0 0.3827
3 16 0 0 0 0.9239 0 0.3827 0.7071 0 0.7071
3 16 0 0 0 0.7071 0 0.7071 0.3827 0 0.9239
3 16 0 0 0 0.3827 0 0.9239 0 0 1
3 16 0 0 0 0 0 1 -0.3827 0 0.9239
3 16 0 0 0 -0.3827 0 0.9239 -0.7071 0 0.7071
3 16 0 0 0 -0.7071 0 0.7071 -0.9239 0 0.3827
3 16 0 0 0 -0.9239 0 0.3827 -1 0 -0
3 16 0 0 0 -1 0 -0 -0.9239 0 -0.3827
3 16 0 0 0 -0.9239 0 -0.3827 -0.7071 0 -0.7071
3 16 0 0 0 -0.7071 0 -0.7071 -0.3827 0 -0.9239
3 16 0 0 0 -0.3827 0 -0.9239 0 0 -1
3 16 0 0 0 0 0 -1 0.3827 0 -0.9239
3 16 0 0 0 0.3827 0 -0.9239 0.7071 0 -0.7071
3 16 0 0 0 0.7071 0 -0.7071 0.9239 0 -0.3827
3 16 0 0 0 0.9239 0 -0.3827 1 0 0
0
I can save the filename as newstud.dat for example
When I type this file data and the string '1 16 0 -4 0 6 0 0 0 1 0 0 0 6' to edit the whole part I just get a white screen when I save it and open it in the grapical display panel.
any ideas?
|
|
|
Need help identifying colo(u)rs |
Posted by: Jean-Philippe Ouellet - 2011-12-26, 1:44 - Forum: Help
- Replies (12)
|
 |
Merry Christmas everybody.
I am trying to define a custom LDConfig.ldr for the 10220 - Volkswagen T1 Camper Van so that it takes less time to model, however, I am having a hard time identifying the exact color of some of the parts.
Unfortunately, peeron does not yet have an inventory of the set, so I can't just get the colors from there.
I took a picture of the parts I am having trouble with next to parts of similar color for reference. I tried to take the photo in the best light possible, I can take another if necessary.
![[Image: 3nB34.jpg]](http://i.imgur.com/3nB34.jpg)
Here's my attempt at identifying the colors:
- Known to be 14 (Yellow). Provided for reference.
- Slightly darker than part #1. Possibly 125 (Light_Orange) or 191 (Bright_Light_Orange)?
- Known to be 2 (Green). Provided for reference.
- Slightly lighter than part #3. Possibly 10 (Bright_Green), probably not 17 (Light_Green), possibly 74 (Medium_Green).
- Not in the set, I think it's 38 (Trans_Neon_Orange).
- In the set, I think it's 57 (Trans_Orange). Do i have #5 and #6 swapped?
- Pretty sure it's 70 (Reddish_Brown) but may as well ask to be sure.
- Pretty sure it's 6 (Brown).
- Pretty sure it's 46 (Trans_Yellow).
- Pretty sure it's 42 (Trans_Neon_Green). Do i have #9 and #10 swapped?
- No clue here.
- I've always believed this color to be 19 (Tan) but seeing #11 makes me wonder.
I tried to compare these colors against this, this (wish they were pictures), and these but I'm still uncertain, so could somebody please look at the above and let me know what is right/wrong?
|
|
|
*feature request* User script to auto-update the part appearence when the file code is altered |
Posted by: SNIPE - 2011-12-24, 17:45 - Forum: Parts Author Tools
- Replies (4)
|
 |
Hi,
Rescently I have been getting to grips with bricksmith/LDraw, but when making a part using the script window I have to save the file then load it in the viewer window so I can see what it looks like as an image. I , and maybe others would like to have some way of automatically altering the graphical presence of the part whenever the script of the file of the part is lt alterred, note that this means having both a script window open and LDraw.
This an be done by having a shell command that enables LDraw to alter the grapic when a change in the script is returned to LDraw.
This means we would not have to keep saving the code and reopening the file in LDraw.
Either a regular text window program such as terminal or noteapad could work or a tool built into LDraw could also work, not sure which one is best.
|
|
|
Bold "New Posts" flag |
Posted by: Jean-Philippe Ouellet - 2011-12-24, 3:48 - Forum: Website Suggestions/Requests/Discussion
- Replies (2)
|
 |
I am referring to the little
(1 new)
that shows up on the front page when there are unread messages.
I would prefer if that text were bold, like so:
(1 new)
because then it would stand out more when quickly scrolling the page as well as not require me to zoom in on my phone to just quickly check if there is anything new.
That text is in a span with class "new-flag" and just adding
to the css would be great.
Having the text slightly larger would do the trick too, but I think it would look somewhat odd.
|
|
|
|