I wanted to report more about the animation playback issue I'm having, as mentioned here.
In the 1.7 alpha, I tried each of the scripted example models and found no issues, except for 8860. When I started the animation for this one, unlike the others, it played the colorfest animation rather than the 8860 demo. I switched to the 8860 animation and started it. The play button highlighted but the animation did not start, and it remained stuck like that for maybe two minutes. Then the program gave up and just want back to a ready state, and the animation never played.
I switched to 1.6d and went through the same process. The first scripted model I tried, 5510, had the same issue, but the hang time was much shorter, just a couple of seconds. Other scripted models worked fine, as did a second attempt at 5510. Then came 8860, and it had the same behavior as it did in 1.7, except for two things. First, it seemed to get through a single frame (the camera view changed and the counter moved to 0.16 seconds), but otherwise froze up like before. I've attached of screenshot of this stage. Second, it didn't default to the colorfest this time, but opened with its own demo script loaded.
I've also attached log files from these two sessions. (I did try again in 1.7 and it was exactly like the first time except without the colorfest. It didn't get through even one frame.)
I'm quite sure I've run this animation perfectly fine in 1.6d before, so I don't think it's a version-specific problem. But it does seem to be related to the 8860 model somehow.
I am still learning the ways of ldraw and right now I'm trying to understand the last comment on this part. Should all edges and cond lines be in s01? Is that the issue? I didn't find a way to comment on the post. So tried here instead.
I recently dug out LDCad again to build the 75192 Falcon.
I try to implement the structure and building steps of the building instructions to the LDraw file. For realizing this I have to work with the grouping feature.
For example: I build the landing gear (building step 131 to 149) as a group. So I can add these steps exactly as main steps 131 to 149 to the LDraw file.
But I would prefer to build the landing gear as a submodel, as it is much, much more comfortable to work with submodels. But using a submodel instead of using a group is destroying the main step numbering, as a submodel starts with sub step 1.
Question: Is it somehow possible to generate a new submodel AND continue the main stepping (here 131 to 149) within this submodel instead if starting with substep 1?
Hello! I've started learning LDraw recently, and for first parts to be properly made as LDraw ones, I took two ones originally modeled by my friend and converted those to LDraw. Me and him are working together on making library of Bionicle parts 3d models. I want to know, do this two parts fit LDraw standard, or I've missed something? Also, if those are good enough, how can I gan access to uploading parts to part tracker?
Hello everyone! I am having trouble with understanding how spherical texture mapping in LDraw works. I tried to use both guide from the specifications and also looking for some examples on the forum, but for some reason neither are willing to show up after I load them in any LDraw viewer. Is spherical mapping broken, or I might be missing something?
Orion:
71014 is the now obsolete chrome version of this part. Therefore, should we resurrect the old part as an alias or delete this alias?
Max:
Is 71014 the Design ID or Element ID? If it is the design ID then we should make the old (obsolete) file an alias. If it's an element ID, then we can delete this part and have nothing to do with the other one, as we don't support physical colour parts anymore.
I identified what is a potential problem with texture images and the requirements of the CC BY license: there is no current mechanism to track authors and modifications to these images. While we haven't had an image recycled to the library for a fix, I feel it is only a matter of time before this happens. The PT tracks these events internally and this data is saved between releases but there is no method for someone who downloads the library to know who has authored an image and what its license is. A solution needs to be found.
I have a few options I can think of:
1. A "Texture Attribution" document included with the library that lists the filename, author, modification authors (if there are any), and license for each image.
Pros: Does not require any modifications to the PT software.
Cons: Labor intensive for the Parts Admin.
Note: I have made such a document and will be including it with the library starting the May release.
2. Add this information to the PNG meta data
Pros: info lives in the files
Cons: Very technically challenging, data not available in an intuitive way, not sure if this meets the intent of CC BY, would have to research.
3. Have a parallel dat file for each png file or, conversely, include texture mod HISTORY in the parent file
Pros: Easy to implement, uses the standard header.
Cons: Adds complexity to the library.
