Superkalle

Hi there Let's hope someone can help you. In the meantime, please use capital letters when you start a sentence. Thanks.

First, the error report usually isn't much help. Normally these error reports are just dumps of the offending program (which is allready known) and the content of various memory areas and registers. But maybe someone with more Mac knowledge can answer that. About why it keeps crashing, can you please provide detailed information exactly when and how. What are the steps leading up to the crash?

You should only know that if you post them on CUUSOO you loose all rights to the design. It is all taken over by LEGO even if the model is never set in production.

Modular Star Fighter concept Our member Vynsane has created a Vic Viper style modular concept. It's built around a couple of base modules that can be combined and expanded. A really cool idea. Download the LXF-files and discuss it here.

Cool with MSPaint - just tried it and it works just like you say. Didn't know that. About removed elements, one thing that the LDD developers could easily implement is to preseent a list of removed elements using a dialogue box, or just output a textfile with them - or why not generate and LXF with the removed elements in. It would be so easy. In the meantime, what you can do are one of two things: 1) Unzip and open the "UnplaceableBricksDump.lxfml" in a text editor. Search for MaterialID 21 (red), because those are the bricks that were removed due to collision. 2) Open and "Save as" the file. Then import that file along with the original LXF into LDD Manager. Then run the Compare Models function.

I'm not sure yet about Boney. I suddenly realised it might be nice to bring the whole family like Dfenz. Have to look into it.

Ultra cool. 'Nough said

Some quick comments: Most Windows software that I know of have the same functionality, i.e. a Save kills all undo. Maybe it's a Windows design guideline. The problem is that the incorrectly placed parts are colliding with some other part - hence they are simply not possible to show, even in a "buyability tool" feature. The "UnplaceableBricksDump.lxfml" file is not supposed to be used by normal users - it's actually intended only for LDD developers because they have ways during development to turn off collision control, hence they can open the file without any bricks being removed and then spot the issues.

RAILBRICKS Magazine issue 10 out The excellent and always enjoyable RAILBRICKS magazine is out with a new issue. Download here

Absolutely super review Rufus. Crisp pictures, detailed text....the works

I'm in Me + one child Staying entire event

Yes, you're right. Should have done that earlier. Fixed now.

This needs a name: VMSFC - Vynsane Modular Star Fighter Concept ...or something

I couldn't access it either May I recommend www.brickshelf.com Free. Plus it allows upload of LXF-files and pics.

I've put it in all kinds of places, and never noticed any difference. One time I even put it in the fridge, and that worked too.

Thanks for moving here Brickster! @Tearloch: There's no way to add bricks to LDD. Extended mode contains the largest selection of bricks (all that are available), so first thing is to enable that (as linked to by Calabar). We (meaning all of us here in the forum) have compiled and sent in a list of wanted bricks, and are hoping some of them make into the next release. That's the only way to do it as of today.

Yeah, I relly like the thought behind the modular concept. Makes it something more then just a Vic Viper. It's the kind of product LEGO should sell - allow you to build and collect various boosters and packs to your model.

Hey Vynsane Great to have you back And as usuall - lovely work on those fighters + the sweet photoshoping!

I couldn't help but to laugh though. "The main attraction will be the first roller coaster in the world to combine a 5-metre-drop with an outing among live penguins. " I don't know what Legoland means by "drop" but I immedatily though: Ooohhh my goood, 5 meters high. Really. And among LIVE penguins....That's just too much....I'm fainting.

Please note you've used the wrong brick. It should be 4733 A good idea is to use the BrickLink or Peeron inventory catalogs to make sure you used the right bricks. In this case it doesn't matter however, because the dragon pieces won't fit in 4733 either (which is a good brick bug find). EDIT: I suspect it should be 4733 in the mast too.

It's a bit apples and pears. What I was explanining was just why it is slow today, and that is not primarily becuase it's not multi-threaded, but because it needs to load all 3D data. I'm no expert, but I think simple, quick solution is to use the PNG-thumbnail, not re-write the application to be multithreaded. That also gives the benefit that you can see all recently used files, not only that you can interupt the loading

The LXF-link is to the JPG thumbnail, not the LXF itself.

Yes, I think you interpreted it just right. And yes, it would only take away the painstaking job of assembling a massive model from submodels, but personally that is the thing that is driving me completely nuts. And if it enables us to open larger files without crash - the better Actually, there should be a way to do it even without marker bricks: 1) Open the master file (with maybe just a baseplate on it or so) and attach one submodel. Save as SubModel_1 2) Open the master file again (with just the baseplate) and attach a second submodel. Save as SubModel_2 Now, both these files (SubModel_1 and SubModel_2) share the same coordinate system with the same origo. Open the two sub-models and remove the baseplate (and everything else that is in the master file). You can now continue working on the submodels until they are finished. As long as you don't move the entire model relative to the scene floor they will always maintain their position in x-y-z space. When you are ready to assemble, all you have to do is unzip and open the master in a text editor. Then you open the sub models one by one, edit the Ref-values(adding to them so they do not "collide" with each other) and pasting into the master file. Save as LXFML file and open in LDD. LDD will re-order the Ref-values in a subsequent string. Something like that. I'll do some test and look into adding it as a feature in LDD Manager.

We've kind of made a decision to stay out of those type of discussions here in the forum. Firstly, because we then move into a grey zone about what is OK and what is not from a legal perspective. Secondly, because there are a lot of kids reading this forum, and if this spreads it won't be long before TLG gets support calls to their Help Desk from kids who have messed up their LDD installations. And then TLG will surely wake up. Maybe a bit exaggerated, but you get the idea. Thirdly because there has been debate before about the usefulness of these kind of customizations. Whenever you make a file with custom items, there is no easy way to share them with others since you need to share the underlying custom elements. And finaly because adding more bricks to LDD is really complicated. Besides the geometries you need to add collision volumes and connectivity points. It's a lot more then for example in Ldraw.

Thanks for that summary Alienwar This whole thing got me thinking about a new feature in LDD Manager. Basically the idea is that you put small "marker" bricks (like a 2x2 corner plate) in different colors in the base model. Then you put identical markers on the sub-models. In the end, it's just a matter of programmatically merging the sub models into the base model using the marker bricks as sync points. How does that sound?