[PLUGIN,PARTS] [WIP]: Nuclear reactor

[Emilio]

(deleted post)

Edited May 13, 2015 by Emilio

[StelarCF]

just a suggestion: you don\'t first do the textures and then test the code. You first test the code and see if it works then you do the textures and after that you do more testing

[Corax]

just a suggestion: I don\'t first do the textures and then test the code. I first test the code and see if it works then I do the textures and after that I do more testing

Fixed that for you

I don\'t see why testing code and creating textures can\'t (or even shouldn\'t) go in parallel; they are completely unrelated things...

[StelarCF]

Fixed that for you

I don\'t see why testing code and creating textures can\'t (or even shouldn\'t) go in parallel; they are completely unrelated things...

Because you are a single person.

Not to mention that code can be cumbersome to understand if you didn\'t work on it for a while (believe me, it can) so it\'s best if you work out the bugs first before getting distracted on textures and models.

[Emilio]

Yep, but i need placeholders for testing, the core needs special attachment nodes to attach the coolant system.

[Caesar15]

Just make a copy of the sas module an edit that

[Splendid]

just a suggestion: you don\'t first do the textures and then test the code. You first test the code and see if it works then you do the textures and after that you do more testing

Let the guy do whatever he wants.

[Causeless]

Let the guy do whatever he wants.

I agree completely. It\'s a bit hard to test it and work out bugs without assets, and the order doesn\'t matter much since this doesn\'t exactly sound impossible.

[nivvydaskrl]

I agree completely. It\'s a bit hard to test it and work out bugs without assets, and the order doesn\'t matter much since this doesn\'t exactly sound impossible.

Agreed. Besides, working on one aspect of a project until completion can reduce the fun factor and be frustrating. Then you stop the project altogether.

So long as the end result emerges in proper working order, the development workstream on hobby projects is more or less irrelevant.

[Meatsauce]

Ya - build a frame, then slap on the stucco. Not the other way around.

[Zool]

Agreed. Besides, working on one aspect of a project until completion can reduce the fun factor and be frustrating. Then you stop the project altogether.

So long as the end result emerges in proper working order, the development workstream on hobby projects is more or less irrelevant.

To each his own. I couldn\'t do it that way though, I build and test pretty much every time I write a method, and debug until it works. I would have an unimaginable mess on my hands if I spent all day coding without building along the way to make sure everything works. But maybe that\'s just me not being a very good programmer.

[StelarCF]

To each his own. I couldn\'t do it that way though, I build and test pretty much every time I write a method, and debug until it works. I would have an unimaginable mess on my hands if I spent all day coding without building along the way to make sure everything works. But maybe that\'s just me not being a very good programmer.

A good programmer usually tests everything.

But if he wants to make the assets immediately after coding so be it.

[Emilio]

(deleted post)

Edited May 13, 2015 by Emilio

[Causeless]

Oh, my source code won\'t compile... i may have broken something....

Try showing us the source, I\'ll see if I can spot anything.

[Emilio]

(deleted post)

Edited May 13, 2015 by Emilio

[Cooly568]

Will the reactor come in 1 meter, 1.75 meters, 2 meters, and 3 meters?

Will the reactor have a fuel, heat, and uranium level? (Uranium goes down, fuel goes up)

Can the reactor have meltdown?

These are my questions.

[Emilio]

(deleted post)

Edited May 13, 2015 by Emilio

[Cooly568]

Thanks for responding.