[MOC] 1:8 Koenigsegg Agera RS

[mihao]

On 9/15/2025 at 3:35 PM, 2GodBDGlory said:

That's what I was wondering, which is definitely unfortunate. I guess what I'm trying to say is that probably at least 98% of builders on here do have access to Bricklink, and so for most builders it's not too unreasonable of an ask. It definitely does make it harder for people to build out of their parts on hand, but in this case there were limited options, and the builder thought using rare parts was worth it.

Could you look into 3D printing a copy of those parts? That's probably what I would do if I wanted to try building this

Yes, when I decided to use these Znap parts, I realized that they have already been discontinued, but given that they are relatively cheap on bricklink, so I chose to still use them. I just can't find any good replacement with other parts.

On 9/15/2025 at 11:48 PM, Sokolov Edward said:

In the original, this part of the roof has the shape of half an oval, not a semicircle. So the options for replacing these parts will be relevant.

https://www.the-blueprints.com/vectordrawings/show/21384/koenigsegg_agera_rs

 

This car is convertible, which becomes a signature feature of it, so I don't want to miss it in the design. When the roof is detached, it is basically a half circle left there. I have thought about using soft axle or similar, but none of them can achieve the clean result like the current one.

[Fcrocks]

Very cool.

[Zerobricks]

How about using a quarter circle gear part (banana gear)?

[mihao]

On 9/18/2025 at 2:27 AM, Zerobricks said:

How about using a quarter circle gear part (banana gear)?

Yes, I thought about that, but that part is a bit too big here.

[Zerobricks]

What about the smaller version?

[mihao]

On 9/19/2025 at 10:32 AM, Zerobricks said:

What about the smaller version?

A bit small, but possible to use with additional structure. Also need to revise the related areas like the windshield side bars.

 

[Zerobricks]

Think it's a good compromise indeed.

[Sokolov Edward]

17 hours ago, mihao said:

A bit small, but possible to use with additional structure. Also need to revise the related areas like the windshield side bars.

The Znap parts can be replaced with flexible hoses and tubes of lengths 1 and 2, or they can be built from bricks.
When will the Android app be updated?

[mihao]

On 9/22/2025 at 4:56 AM, Sokolov Edward said:

The Znap parts can be replaced with flexible hoses and tubes of lengths 1 and 2, or they can be built from bricks.
When will the Android app be updated?

Yes, flexible parts can be used for that, but I don't think they'll as neat as the current way. For the Android app, seems that OBB has some issue with certain regions so right now I am trying to change them into Addressable asset bundle being loaded from CDN. I will send you a message when it is ready to test. Thanks.

[Sokolov Edward]

On 9/23/2025 at 10:18 PM, mihao said:

For the Android app, seems that OBB has some issue with certain regions so right now I am trying to change them into Addressable asset bundle being loaded from CDN. I will send you a message when it is ready to test. Thanks.

The Android app is working well. When is it planned for general release?

[Sokolov Edward]

I've completed this rather challenging build. I replaced the antique "znap" parts with assemblies made from connectors #3 and #4.

Instruction errors:
1. Step 132 – the far left black pin cannot be installed because a blue pin is already there. Besides the "pin to pin" error, there are also errors with installing the round pin into the axle hole.
2. Many 61184 pins are used that require the corresponding black 2L pin, but they are not labeled. Maybe I should change their color?
3. A number of parts cannot be installed because previously installed parts are in the way and must be removed.
4. Step 535 cannot be completed without completely disassembling the right side of the dashboard or without doing step 521 first.
5. When installing a number of parts (steps 25 and 36), there's no indication that the part is to be installed in a different position and then rotated to the specified location.
6. There are no instructions on the position of the axles and parts when joining the assemblies.
7. There are no intermediate checks of the assembled mechanisms.

Design flaws:
1. The transfer case switch doesn't work.
2. Adjusting the suspension height requires a lot of effort.

Below are my suggestions to the author, sent by email for general discussion and additions. I also tested the program on a large touchscreen in Samsung Dex mode. So far, my only complaint is the inability to move the model view vertically or horizontally during assembly. You can only zoom and rotate. In some cases, the model appears shifted up or down, leaving a significant portion of the screen blank. Swiping with two fingers doesn't do anything—could it be used to pan the view?
A few more comments and suggestions regarding the program's functionality.
1. The parts list is still not fixed (2739 -> 2739a).
2. I'd like to be able to search by part number in the list. I'd also like to be able to jump to the assembly steps that use the selected part—this feature is essential when analyzing the possibility of replacing parts.
3. Add an exit button to the app on the home screen.
4. If you use the app generator, it most likely supports the Windows Store as well. This feature would also be of interest to many. I'm willing to participate in testing on this platform as well.

Edited 9 hours ago by Sokolov Edward

[mihao]

On 10/15/2025 at 11:52 PM, Sokolov Edward said:

I've completed this rather challenging build. I replaced the antique "znap" parts with assemblies made from connectors #3 and #4.

Instruction errors:
1. Step 132 – the far left black pin cannot be installed because a blue pin is already there. Besides the "pin to pin" error, there are also errors with installing the round pin into the axle hole.
2. Many 61184 pins are used that require the corresponding black 2L pin, but they are not labeled. Maybe I should change their color?
3. A number of parts cannot be installed because previously installed parts are in the way and must be removed.
4. Step 535 cannot be completed without completely disassembling the right side of the dashboard or without doing step 521 first.
5. When installing a number of parts (steps 25 and 36), there's no indication that the part is to be installed in a different position and then rotated to the specified location.
6. There are no instructions on the position of the axles and parts when joining the assemblies.
7. There are no intermediate checks of the assembled mechanisms.

Design flaws:
1. The transfer case switch doesn't work.
2. Adjusting the suspension height requires a lot of effort.

Below are my suggestions to the author, sent by email for general discussion and additions. I also tested the program on a large touchscreen in Samsung Dex mode. So far, my only complaint is the inability to move the model view vertically or horizontally during assembly. You can only zoom and rotate. In some cases, the model appears shifted up or down, leaving a significant portion of the screen blank. Swiping with two fingers doesn't do anything—could it be used to pan the view?
A few more comments and suggestions regarding the program's functionality.
1. The parts list is still not fixed (2739 -> 2739a).
2. I'd like to be able to search by part number in the list. I'd also like to be able to jump to the assembly steps that use the selected part—this feature is essential when analyzing the possibility of replacing parts.
3. Add an exit button to the app on the home screen.
4. If you use the app generator, it most likely supports the Windows Store as well. This feature would also be of interest to many. I'm willing to participate in testing on this platform as well.

Hi Sokolov, thank you for testing it thoroughly, I will address the instructions issues soon.

The two finger panning is a good suggestion for more viewing freedom. The second suggestion is an interesting one, I have also thought about that clicking a part in the view can lead to the step where that part is added in the first place. But it does require each part in the view is clickable, but right now, some part exists in a sub module, and it means that user can only click into the sub model first then to the individual part. I think it is tolerable. 

For Google store release, I haven't collected enough testers there, and there is some new issue reported from Google store which I have to fix. It seems a lot more restricted requirements to publish in Google store than Apple store. I am using Unity, so it should be straight forward to generate Windows store app, but using Windows is not part of my original intention, given that windows PC is not as agile as mobile device. Anyway, will let you know when I need some testing there. Thanks in advance!