SylvainLS

Eurobricks Counts
  • Content Count

    1304
  • Joined

  • Last visited

7 Followers

About SylvainLS

Spam Prevention

  • What is favorite LEGO theme? (we need this info to prevent spam)
    <p> Classic Space </p> <p> Go Brick Me! </p>

Profile Information

  • Gender
    Male

Extra

  • Country
    France
  • Special Tags 1
    https://www.eurobricks.com/forum/style_images/tags/LDD_builder_yellow.gif
  • Special Tags 2
    https://www.eurobricks.com/forum/style_images/tags/ldraw_builder.gif

Recent Profile Visitors

5393 profile views
  1. Hi, Knowing your operating system (Windows? macOS?) would help. If you can’t uninstall, the simplest is to delete Studio’s files (in C:\Program Files\Studio 2.0 on Windows and in /Applications/Studio 2.0 on macOS) and reinstall Studio from scratch. If you have custom parts, it’d be wise to at least at first move them from your user’s directory and reintroduce them later when everything works. (User’s directory: C:\Users\<username>\AppData\Local\Stud.io on Windows (AppData is hidden), /Users/<username>/.local/Stud.io (.local is hidden, use Cmd+Shift+.)).
  2. Hi, You’re not alone, see this thread on the Studio forum. Simplest solution for now is to revert to the previous version (how to is explained is the thread).
  3. 50956p01.dat (a) uses s\50956p01s01.dat (b) which you need to edit. So you can skip the “s” subfolder if you change the reference “s\50956p01s01.dat” in 50956p01-renamed.dat (a) to “50956p01s01-renamed.dat.” You are already renaming the file (b) and you already need to change the main file (a) to reflect that, so yes, you can also remove the “s\” bit. I explained everything wih keeping the “s\” because it’s needed or simpler to keep it in many cases.
  4. Ok, then (part of this you seem to already have done but for completeness): Look into data/StudioPartsDefinitions2.txt to see that 50956pb023 uses 50956p01.dat. There’s two copies of that file, one in ldraw/parts and one in ldraw/Unofficial/parts. Fortunately, they are the same. Copy it in your working directory (you may rename it to be sure there’s no confusion). Open it: it uses two subfiles, one is for the studs (stu(d)g(roup)), the other is a subfile. Create a subdirectory ‘s’ in your working directory. Copy the subfile in it (rename it too). Open the file. You see two subfiles used at the top (it’s subfiles all the way down!): the first one is in colour 16, and looking its description inside, you see it’s the “body” without the surface, not interesting for us, the second is in colour 4, it seems to be the coloured stripe, the rest of the file is all in colour 16, and the comments show it’s the rest of the surface, not interesting for us. You don’t need to copy these files, they don’t need to be changed: we found the stripe, it’s the subfile s/50956p01s02.dat and its colour is given in s01, so we don’t need to edit it (it’ll be colour 16 in there). Now you can edit the files: Change the main file name if not already done in 3. Change the first subfile name if not already done in 6. Edit the main file to use the new name. Edit the subfile and change the colour 4 to 72 or whatever. Now you can import the main file in PartDesigner, it should load the subfiles (modified and unmodified) and now the stripe should be 72. Export to Studio. Repeat for the other part (or not, as it’s a mirror… but it may be simpler to just repeat). The keys are: Finding the .dat files. Understanding how subfiles work in LDraw, particularly: that 16 is the special “current colour,” that “s\” means that the file is in a subfolder named “s” Understanding how PartDesigner and Studio work with subfiles: PD looks for them in the current directory, and then in Studio’s files that’s why you need an “s” subfolder (unless you remember to remode “s\” in the calling files), that’s why you don’t need to copy all the subfiles you won’t modify. When PD saves or exports a model, it “flattens” the first level (that is, the subfiles used in the main file are incorporated into the resulting .part/.dat, the sub-subfiles are left untouched). Studio first look for subfiles in its files. So beware when you modify subsubfiles: PD will load the modified ones, Studio won’t find them or will load the unmodified ones. Hope that’s clear for you because I’m not sure it’s clear for me
  5. Hi, It would be simpler if you named the parts (LDraw ID / filenames) and told us which CAD you’re using (LDCad, MLCad, LeoCAD, Studio, …?).
  6. Everybody is annoyed with the flexible parts in Studio, including the Studio team.
  7. The problems with such books are: someone needs to write them, they don’t pay much, they quickly become obsolete, you can’t fill them with “hem, uh, oh” like on videos, though a lot are filled with big screenshots
  8. Glad you found the problem, Berthil Still, there’s something fishy with the zoom in Step Editor: it should zoom to show the parts in the step, but it seems the zoom is first set to see the whole model the first time you go to Step Editor and “Reset Origin” doesn’t always change it, even if you change the parts afterward. It works on this model though, so it’s okay for mobiletransaltor, but it’s still a bug (and explains why my simple test didn’t work). BTW, simple way to select the part you can’t see: rectangle-select the model (that you should see), then Ctrl+Shift+V to revert the selection. Now you have the bad part selected and you can just delete it. (Rectangle-selection = start grabbing with the mouse outside the model, then pass over the model, a rectangle is drawn and every part that’s inside or crosses the model is selected and lights up.) Forgot: Nice model
  9. In Building mode, on the right, there’s the list of parts. It’s the Step List. The simplest way to make the test is to: Select all the parts in the Viewport (Ctrl-A will do it). Move the pointer to the Step List and right-click on a part. Choose MoveTo > Step 2. That will move all the parts in Step 2. (From the picture, you already have a step 2. If not, choose New step.) Now, still in the Step List, right-click on only one part (a simple one, like a brick). Choose MoveTo > Step 1. That way, the first step will only have one part. Go to Instruction mode. If you now correctly see only the one part, then something is wrong with the rest of the model.
  10. Well, it’s normal: as you have only two steps, there’ll be many parts in the parts lists and it will be hiding most of the model. The test was to know the extent of the problem (there’s been some graphics problems that were in both Instructions modes but not in Build or vice-versa). Please try the “only one simple brick in one step” test.
  11. Do you see the model if you go in Page Design? There may be something wrong with the graphics (incomplete drivers?). What’s your GPU? and your OS? Otherwise, you can contact the dev team by e-mail (studio -at- bricklink.com). You’ll need to re-state everything, give your system info, and better join Studio’s log file (file PrevPlayer.log in C:\Users\{YOU}\AppData\local\Stud.io on Windows and /Users/{YOU}/.local/share/Stud.io on MacOS; AppData and .local are hidden). You may also post on the Studio forum (from Studio: Help | Submit feedback and create a new post; you need a BrickLink account). Then I’ll flag the post to the devs (I can’t give them a post from this forum: they can’t have accounts everywhere to answer), so it can take longer. BTW, I just noticed that the step previews on the left are also empty, so there’s something really wrong. Also, another idea: in Build mode, use the Step List (bottom right) to make a step with only one simple brick in it. Then go in Instruction mode, and select that step if it’s not the first one (just click on it on the left). If it can show one part, then there’s more chances something is wrong with the model (or with how Studio can handle the model) than with the system/graphics.
  12. Right click in the area where the model should be, above the parts. Then choose “Reset Origin” in the menu that appears. That should recenter and rescale the view on the model.
  13. Boone’s are good. Some things may be a bit outdated (new parts palettes, new features, a few changes in the UI) but they are still the best I saw (no blah, no errors). They also complement well the help pages (which need a few updates too, but it’s in the works), which is why they are linked there. Without wanting to “poach” users from here , there’s also the Studio forum, where there’s a parts FAQ and a few posts about new features.
  14. Pro-tip: Black renders faster than White. (Same model, same parameters, almost all the model in one colour: White = 100%, Yellow = 94%, Red = 90%, Blue = 89%, Black = 87%.) I haven’t tried in Rubber Black but that should be even faster… but then, I’m not sure we’d really see anything Another thing: exporting to DAE can be very long (minutes) for big models, so it may be faster to do a Rotation animation with 4 images (4x png, not a mov/gif) than to take 2 or 3 pics around the model. I mean, when you just want to see what it’d look like, not for a final render. Lastly: yep, the render is faster if you leave the computer alone. Usain Bolt is also faster when he doesn’t stop to sign autographs along the way… well, with him, you never know, but for renders, that’s certain