Eurobricks Citizen
  • Content count

  • Joined

  • Last visited

1 Follower

About GREG998

  • Birthday 11/20/79

Profile Information

  • Gender

Recent Profile Visitors

1001 profile views
  1. Here is how i deal with this "problem". I remove the involved parts (in this case 62520.dat X2 and 62519.dat X1) from the PLI and put over the PLI a picture of the complete assembly (mimicking perfectly a PLI). In the case other parts than 62520 and 62519 are involved in the step, i include them in the picture to.
  2. That makes sense, it could explain the LDconfig issue.
  3. Just tried it but it doesn't change anything.
  4. Looks like the Ldconfig file issue is another problem (or a spin-off the slowliness). i struggle with this bad behaviing LDconfig file, it self updates without any action from me (it reverts to default settings time to time). Perhaps MLcad updates it but i wonder how, when, why? I've tried to replicate the issue but it doesn't work.
  5. Great news! A question about updating via LDview: When there is an updated LDConfig file available, does LDView update it to?
  6. Hi everyone. I encounter a sligth issue with MLcad 3.5. Since i have done a fresh reinstall of Lpub3D, MLcad is now slow to launch (7 to 10 seconds from the moment you click the icon or a file that opens with it). Before that, it was very quick to launch. I know the link between this slowiness and Lpub3D install is kinda fuzzy but something strange happened at this time: my LDconfig file had been reverted to default (whereas i had some custom setting for colors such as black, dark blue). The new LDconfig file (i've tuned it back to my personnal settings) has now a kind of light yellow as "main_color", but that color remains dark grey when you use it. Not a big deal as i dont' use it but it confirms the ldconfig file has been modified. So, what's your point of view?
  7. Probably, and i could be interested by such a system....but i wonder if you can spend hours with a VR helmet without issues like headaches, sickness.
  8. That's a problem you'll meet with several color: olive green, metallic silver and others. Ldraw colors code and Brickstock colors code don't completely match. Even more tricky: Trans Orange in Ldraw is considered as Trans NEON Orange in Brickstock/Bricklink. So, you'll have to manualy edit the part list when file is imported in Brickstock (like Olive Green parts) then carefully check the list to fix the "trans-orange/trans-neon-orange like" problems. However, if someone knows a way to unify the way ldraw and brickstock are managing colors, i would consider him as an half-god.
  9. No problem, let' see it in PM.
  10. I've tried to reproduce the problem with a pretty simplistic file. Try the following thing: Unpack the callout. Then convert it back to callout. At this point, the part list should be WITHIN the callout area. Right click in the callout and chose "no part list per callout". Tell me what it gives.
  11. That's weird....It should propose you "Hide part(s) from part list" AND "change part margins", even with a callout or a submodel treated as a part. What version of Lpub do you use?
  12. Try to put the cursor right on the part/callout you want to hide. It "should" propose you to hide it. If you really want to keep the calloup on the parent model page, maybe should you try to display it as a column (on the callout area, right click then "display callout as column").
  13. I've found a better fix and almost found the root of the problem. For unknown reasons, time to time, the rotation matrix values get corrupted. For exemple, instead of "1 0 0 0 1 0 0 0 1", you get "1 0 0 0 -1 0 0 0 1". The result is a mirrored submodel (things you can see only if the submodel is asymetrical) and a corrupted appearance in Lpub. FIX: just reset the rotation matrix values to "1 0 0 0 1 0 0 0 1" and readjust the submodel position to fit the way you want.
  14. No offence intended guys, but someone comes with questions so let's try to bring him answers, not other questions. In the PLI: Have you tried to put the mouse on the callout and right click it? It will propose you to "hide part(s) from part list". If the callout is too large, i prefer to let it unpack. It improves the lisibility of the step.