Kuramapika1
Eurobricks Vassals-
Content Count
97 -
Joined
-
Last visited
About Kuramapika1
Spam Prevention
-
What is favorite LEGO theme? (we need this info to prevent spam)
Space
-
Which LEGO set did you recently purchase or build?
6982
Profile Information
-
Gender
Male
Extra
-
Country
Argentina
Recent Profile Visitors
-
Custom LDD bricks and fixes
Kuramapika1 replied to Equilibrium's topic in Digital LEGO: Tools, Techniques, and Projects
Yes, that file. Unfortunately I am unable to solve the problem with LIFExtractor. -
Custom LDD bricks and fixes
Kuramapika1 replied to Equilibrium's topic in Digital LEGO: Tools, Techniques, and Projects
Hello: actualy, you can use the A, W, S and D keys. What you need to do (as you say) is: go to your LDD instalation folder and find Assets\Scripts\EditMode folder. in there, open the MenuLayout.xml file: find </MenuItem> when you reach that line, find <MenuItem locText="DELETEBRICK" key="D" command=".LDD.commands.editMode.deleteTool"/> and change the letter D to any unused letter. That's all. -
Position of electric pin holes of 6216m2 - Electric, Motor 4.5V Type 2
Kuramapika1 replied to Holly-Wood's topic in LEGO Technic, Mindstorms, Model Team and Scale Modeling
Go to https://forums.ldraw.org/thread-27852.html -
Custom LDD bricks and fixes
Kuramapika1 replied to Equilibrium's topic in Digital LEGO: Tools, Techniques, and Projects
I tested your image (without adjusting it) and, in my case, the sides are showing in the front. Comparing the two images (my UV map and your template) your color UV map have sligtly bigger sides. -
Custom LDD bricks and fixes
Kuramapika1 replied to Equilibrium's topic in Digital LEGO: Tools, Techniques, and Projects
I give a try, and I wish the same to you in your work. I found this video that can be usefull: Video -
Custom LDD bricks and fixes
Kuramapika1 replied to Equilibrium's topic in Digital LEGO: Tools, Techniques, and Projects
I think I worked in vaine (jaja!): as you figure it out (my gess) the UV maps depends on how the 3d cad software (in my case Blender) create it (you can see it in the image). Anyway, I did some image to try helping you but you solved it. Here it is what I do: UV map Sticker set 7994 LDD 1 LDD 2 The last 3 are my test; the back sticker is no truth in real life. If the "sticker set 7994" image is of use to you feel free to correct it and publish it. -
Custom LDD bricks and fixes
Kuramapika1 replied to Equilibrium's topic in Digital LEGO: Tools, Techniques, and Projects
What a problem you have! Question: do you keep the Assets.lif file? the DB.lif file is inside of it (Assets.lif, in the instalation folder). -
Custom LDD bricks and fixes
Kuramapika1 replied to Equilibrium's topic in Digital LEGO: Tools, Techniques, and Projects
Hello @Stephan: I did your request but I'm not sure if it is what you wanted, specialy the UV images. Here By the way: how did it go with the 4274.xml and DB folder? Can you solve the problem? -
Custom LDD bricks and fixes
Kuramapika1 replied to Equilibrium's topic in Digital LEGO: Tools, Techniques, and Projects
Yes, it's funny. Maybe if you extract db.lif again have the proper folders? -
Custom LDD bricks and fixes
Kuramapika1 replied to Equilibrium's topic in Digital LEGO: Tools, Techniques, and Projects
Checked: it's nothing to do with "Toggle Physics Test" (it turned ON). By the way: I have two DB folders: one in C:\Users\[user name]\AppData\Roaming\LEGO Company\LEGO Digital Designer and the other in my pre-defined folder (the one LDD ask to install the software the first time; in my case it's in an external HDD). When I use the .xml file from the C:\Users\[user name]\AppData\Roaming\LEGO Company\LEGO Digital Designer have no effect at all; so I need to use the other .xml, from the other folder. -
Custom LDD bricks and fixes
Kuramapika1 replied to Equilibrium's topic in Digital LEGO: Tools, Techniques, and Projects
Never touch the collision; and if I did it, I didn't realize. I will check if the collision is turned on or off and see if this is the "origin" of the problems. -
Custom LDD bricks and fixes
Kuramapika1 replied to Equilibrium's topic in Digital LEGO: Tools, Techniques, and Projects
Very strange. When I delete the folder and open LDD, it apear again. Maybe you are doing something wrong? Any way here it is my code (the only diference is the length): <Connectivity> <Axel type="19" length="0.3" requireGrabbing="0" startCapped="0" endCapped="1" angle="120" ax="-0.57735" ay="0.57735" az="-0.57735" tx="0" ty="0" tz="0"/> <Custom2DField type="23" width="2" height="2" angle="90" ax="-1" ay="0" az="0" tx="-0.4" ty="-0.4" tz="-0.8"> 29:0,29:0,29:0, 29:0,3:4:38,29:0, 29:0,29:0,29:0 </Custom2DField> <Axel type="6" length="0.979" grabbing="0" startCapped="0" endCapped="0" angle="120" ax="0.57735" ay="0.57735" az="0.57735" tx="0" ty="0" tz="-0.979"/> </Connectivity> Question: do you open the .xml file from your folder of choice or from C:\Users\[user name]\AppData\Roaming\LEGO Company\LEGO Digital Designer? Before to copy my code, try open the .xml file from the folfer of choice and do the changes, repeating the process I write before. -
Custom LDD bricks and fixes
Kuramapika1 replied to Equilibrium's topic in Digital LEGO: Tools, Techniques, and Projects
Stange; this is wath I do: a. Open the .xml file, make the change needed and save the change. DO NOT CLOSE THE FILE! b. Then delete the db folder located in roaming/legocompany (I think you know wath I'm saying) c. Open ldd and check if the change in .xml file work d. If it work, adjust as your pleasure til you are happy. Then and ONLY then close the .xml file Hope this help you. -
Custom LDD bricks and fixes
Kuramapika1 replied to Equilibrium's topic in Digital LEGO: Tools, Techniques, and Projects
Just open the 4274.xml and change the legnth of axel 19 to a number less than 0.8 -
Custom LDD bricks and fixes
Kuramapika1 replied to Equilibrium's topic in Digital LEGO: Tools, Techniques, and Projects
Hello: long time no see you! I take a look into these: And find two solutions in the part 4274.xml: Delete axel type=19 entirely, in the connectivity section or Change the length of the same axel to a small size. So, in response to: it's not a bug; rathern a missmatch of the length.