Would you build this?
- Thread starter Reika
- Start date
I just did some calculations to determine the absolute maximum power output of the fusion reactor (upper bounds determined by things like melting and emission speed), and it is relevant to this thread's first post:
Now if only we could do this in the real world.
Now if only we could do this in the real world.
ok a bit of a problem I've come across while building the reactor (legit), these liquid pipes like so will self-destruct, you can see the water where they were, the middle ones are empty for some reason, and all of them were at 1.6MPa before placing the fluiducts, of which the 4 pipes blew up and the middle ones drained.
on repeated testing, it seems to be that the middle ones are causing a kind of fill loop, where the surrounding pipes take in any fluid from any other pipes, but duplicate it continuously inside itself until eventually breaking 2-to-many ticks later.
@Reika
on repeated testing, it seems to be that the middle ones are causing a kind of fill loop, where the surrounding pipes take in any fluid from any other pipes, but duplicate it continuously inside itself until eventually breaking 2-to-many ticks later.
@Reika
Mine do not even connect to fluiducts, so you are using an old version.ok a bit of a problem I've come across while building the reactor (legit), these liquid pipes like so will self-destruct, you can see the water where they were, the middle ones are empty for some reason, and all of them were at 1.6MPa before placing the fluiducts, of which the 4 pipes blew up and the middle ones drained.
on repeated testing, it seems to be that the middle ones are causing a kind of fill loop, where the surrounding pipes take in any fluid from any other pipes, but duplicate it continuously inside itself until eventually breaking 2-to-many ticks later.
@Reika
EDIT: Wait, no, the problem is FMP.
Indeed so. It appears we've been waiting for fusion power forever. It's been a topic since I was a child, and now I wonder if I'll see it in my lifetime.
ran across this the other day on the challenges facing fusion as a
biggest problem? containment. D-T reactions need heated to 45 million degrees, give or take, inside a reactor. the sun manages it at about a third of that due to sheer volume. but at either temperature, you will have a very fast moving, totally ionized plasma to contain.
to quote the linked article.
a French project plans on a 480 second burst at 500MW somewhere around 2026, but thermal collection for electricity production will take longer.
but, as the article concludes, we already use fusion for power, under a different name. solar.
...With a 12% efficiency and stupidly large construction cost per unit power thrown in for good measure.
It's also terrible for the environment!...With a 12% efficiency and stupidly large construction cost per unit power thrown in for good measure.
so ie; you going to fix it in 25h? or at least try to? if there's one thing I know about FMP, it has really crappy tile handling so you _must_ use try-cratch and/or re-scan it each tick or problems arise.
also have you actually fixed the empty string bug in the boilers after V25? this one probably annoys me the most due to the 5-10 minutes it takes for the client to start up, how exactly is this even happening though? you shouldn't be using dynamic strings for variable names, nor should boilers have anything along the lines of owner names, and a lot of cases the later uses a player database anyway so you only ever store a single integer...
reason I ask these things is because mod updating is expensive for me for various reasons, I cant be updating mods every single time a patch comes out.
I have fixed it.
Did you read the changelog?
This has nothing to do with owners or variable names. Strings are used for NBT data. It is how saving things work.
Then you are ineligible for tech support.reason I ask these things is because mod updating is expensive for me for various reasons, I cant be updating mods every single time a patch comes out.
awesome
did also mention it when I updated to V25b...
NBT variable names are string types, data is not, which is what's confusing me that you have this bug in the first place when names are only meant to be static/constant/readonly anyway...
so is FTB in general, point being?
though I notice the latest version jumps to V25z, any particular reason for the 'z'?
project work has eased off on my side for now so I'll more than likely update my server this week, we just recently went through our seasonal box migration too.
I added a try-catch. If that does not catch it, then you will have to wait until 1.7.awesome
did also mention it when I updated to V25b...
Fluids are saved as strings and an int. Strings often are data.
As the packs come, yes.
Because it is the final 1.6 version.
I am trying to see it and am getting something that is trying to make me dl tapatalk.Was reading an old fashioned magazine and I saw this.
Imgur mirror?
ok that makes more sense, I half forgot about the fluid registry not using IDs, and yea, strings are just integer arrays encapsulated under a different typename (in java that is, other languages use standard ASCII one-byte chars unless you use a special container type)
that's what I figured, hope you have good results through updating to 1.7, last I messed with it was quite a few months back and it was very very broken, however should be at least somewhere close to what 1.6 is like, and most things haven't changed bar naming changes, IDs moved to a world-side dictionary and some render alterations. add any other forge changes I haven't seen yet.
looks like Ill get a 1/4 power reactor running just before a world wipe to 1.7... which is a good thing fyi, this is what keeps me entertained.
http://img.tapatalk.com/d/14/08/06/thumbnail/9anevymu.jpg
Last edited:
So far, not good. 17k errors - a lot of which are simple but irritatingly pointless renames, fortunately - but the code is still an obfuscated mess and I absolutely cannot develop without the ability to load and modify the vanilla code at runtime, something the 1.7 gradle s*** was explicitly designed to prevent.
I always hated how mojang claims they support modding yet make it as hard as posible. The nature of minecraft makes the code easily visible, so obfuscating it is just taking a royal s*** on mod developers.
the thing I hate even more is their promise to make a mod API. And they never make it. Instead they give us bunnies (vanilla 1.8)