Posts by Methes

We're running modpack called GT New Horizons and for quite some time now the server stalls every once in a while, causing players to time out.
The server has enough RAM and CPU power, TPS is always at 20 with 10ms work time.

Sampler managed to get some info but we lack the skill to pin point the problem when google fails.
Sampler log: http://pastebin.com/M4rspZvJ
Server log: http://pastebin.com/qa4kULKu - happens at 16:32:15

The "Server Thread" is always at the top with the same error you can see in the sampler log.
Does that have something to do with world saving and disk I/O?

Thanks for all the help,
Methes

EDIT:
After removing fastcraft we get a lot more of these
http://pastebin.com/3KaQPriC

Quote from INVICTRA

A friend of mine has to start a 3D game beside Minecraft so he can play. Without he gets 3-10 fps. This forces the activation of his Dedicated graphic card.

Dedicated graphics card can usually be set using drivers (ATI Catalyst or NVidia Control Panel).
If not, you can usually set BIOS settings to use Dedicated card only.

After googling the very first error line, all the results are about using a mod for different MC version. Like 1.8 or 1.6.4
Are you sure you have the right mod versions?

Also this whole problem would fit better in the random thread I think.

EDIT: After looking at the screenshots of your modpack folder, I can see you have downloaded several wrong versions of mods. You probably won't be able to connect, because the server uses older versions of some mods (Galacticraft for example)

Also you have downloaded Thaumcraft for MC 1.8 and not 1.7.10. That's why it doesn't even start.

Also also, it is common sense to post complete/relevat crashlog on pastebin.

Also also also, putting the pack together is one of the prerequisites of joining the server. Using Google too.

Lets stop this spam here in the official thread now please.

BUG REPORT!

[TwilightForest] Biome ID conflict. Biome ID 146 contains a biome named Tundra, but Twilight Forest is set to use that ID.

That could go very wrong.

I was surprised Steve's Carts were in the pack, as it's not that difficult to get self sustaining wood farm with them. I was even more surprised it has not been tweaked in any way.

Twillight Forest can be overpowered with easily accessible redstone, diamonds and lapis. It is also more suitable for smaller servers where stuff doesn't get looted/killed so easily for others.

EDIT: I downloaded CC+ATG+EXB and used the configs posted here. The terrain looks a bit strange and barren. Might be bad luck on place selection. That's with 32 chunk distance btw.

How about Carpenter's blocks?

I'm sorry, I didn't mean to provoke any quarrel. I just wanted to share my thoughts on worldgen - the very basic of stable map.
If those pictures are indeed with 12 render distance, real game might actually look good. Thanks for clarification.

I have done zero work for the server itself so I am in no place to judge your careful selection. I just thought it was a valid concern to talk about.

Thanks,
Methes

I'd like to join too.

My point of view on ATG and RTG terrain types:
These look good only with large view distances. On a server where you have view distance 10 max, all you see is a plain or a part of a mountain.
Terrain with cliffs, overhangs and other stuff blocking your view looks good even with smaller view distance, because you don't get that weird "world edge". BoP or Amplified does that pretty well.
ATG/RTG can look good in pictures or SP, not in multiplayer.

I'll be probably underground anyway.


P.S.: Big Trees mod can make terrain look good too. Has to be tweaked a bit though.

Hey guys,

is there any official info about what's coming? Modlist, configs, scripts, server setup?
It seems to me the info is spread all over this thread and other sources even. It's hard to know what's up.

Quote from Blood Asp

Really long connections with GT cables are not a good idea performance wise.
I have my ideas about long distance energy transfer and the fist but inefficient one will come soon, but a real one able to connect far apart bases with good efficiency will still take some time for me.

The trick of my idea is that once it's set up, the two Transformers act as a wireless transport. They only interact with each other, not the cables. Cables are just sitting there doing absolutely nothing unless broken. So it has zero performance hit over tesseracts.

Got an idea about long energy transportation. Special kind of energy network just for long distance transportation.
EDIT: Forgot to mention this is ment to allow energy transport over unloaded chunks without wireless magic. With proper energy lines stretching 1000 blocks.

Requires:
Input transformer
Output transformer
Special cable (can be multiple tiers along with transformers above)
List for each grid (virtual database)

Mechanics:
When placing the Input transformer, it gets assigned an ID number X and acts as a source of power for the grid. It is also written into a List as a powersource.
Then you have to lay the Special cable all the way to your destination with NO FORKS.
The first cable block checks the ID of connected Input transformer and gets the same number.
Next cable block checks the ID of previous cable block and gets the same number too, creating an energy grid with same ID number X. Also, when assigned an ID, the cable block checks other connected cable blocks and if it finds one without assigned ID, it triggers its call for an ID. //So if you connect proper cable to a bunch of orphan cables, they get assigned one by one
Last block is Output transformer, again with the same ID number. It is also written into the List as powerdrain.
Input transformer and Output transformer have to be chunkloaded. Cables do not.

When the grid is completed, you can safely assume it's intact and ready to work.

Broken cable scenario:
When cable block is broken, it marks its neighbour cable blocks with a Flag (creating two cable endings). These 2 Flagged blocks get added to the List above with their coordinates. The grid shuts down.
To repair it, you have to connect cables back to these Flagged blocks. When connecting a new cable block to this Flagged one, it follows the same procedure as above, but the Flag gets moved to this new block (in the List too), because we have a new cable ending.
When two of these Flagged cable blocks meet, the grid knows it has been reconnected, the Flags are removed and everything works again.

Special cases:
Placed cable blocks with no Input transformer or assigned cable blocks around them have no ID assigned and become orphan blocks. They have to wait for assigning avalanche described above.
IF a newly placed cable block finds two neighbours with different ID, a wild explosion of both Input transformes (that you just connected together) is imminent.
IF a newly placed cable block finds two neighbours with same ID but not Flagged, you've connected your fork back to the grid and a short circuit happens. (you can't make forks this way)
IF you try to place a second Output transformer, you add second Powerdrain to the List and the grid shuts down (you have to end one grid and create two new grids to make a fork)
Broken Flagged block is erased from the List.


I have for sure forgotten some special cases that could happen, but right now it seems to me this might work.

Hey guys, I suffer from minor case of blidness.
I can't find a config to enable normal glass bottle crafting. Is it hidden somewhere or do I have to suck it up?

Thanks.

Quote from Bogdan-G

algorithms, cycles, methods of solving the problems has led to what we have(receive). This is a joint problem, it is not built in one solution. Algorithms forced perform series of operations that lead to lengthy analysis and realization in world-chunks.
-----
#reasoning(It is not addressed to a specific person)
What if you do not do series of operations at each re-start? Just save the changed data such as OreDictionary, Dictionary dust, stones Dictionary, Dictionary of other objects. If the configuration file and modpack remains unchanged why each time to cause the addition of dust, ores, ingots, nuggets, objects, blocks, and everything else? Why perform the same thing every time you start?

Quote from GregoriusT

This is not even remotely possible. And I said that too back then.

So yeah.

Unfortunately the loops are still present. Tested only with Glenn's Gases.
GG version 1.5 didn't get the loops (and never did) but the new 1.6 version does, so it's not entirely GT's fault. Any excessive worldgen simply makes the problem more visible.

I wish there was a way to tell server NOT to generate anything past certain border.

Blood Asp,

would it be possible to fix GT5 worldgen loops similarly to how Greg did in 6.00.33. Because it works and I no longer get them with that version, but every version before that just loves to generate infinite worlds.

Quote from Pyure

DreamMaster I've seen some of your other cool stuff so I have faith, but how the hell did you manage to integrate TiCo in a balanced fashion w/o its tools completely deprecating everything from GT/IC2?

I mean who the hell would build a 22nd Century Mining Laser of Doom if you can just make a much-better Big Hammer.

It's pretty well balanced. We use IguanaTweaks with carefully selected configs. Leveling up tools takes quite a bit of time and the chance to get Haste is not great. You'll be happy to get haste 3 times.
AutoRepair is mid-endgame so by that time you already have access to GT or GraviSuite drills (whichever you prefer) - and those you can recharge much faster than with AutoRepair. Simply really hard work to get effective TiCo tools.

Btw. the map is a week old ;).

Quote from SpwnX

Along what choco said, it is to avoid unexperienced users (aka your average user that have little to no idea how to deal with mods themselves) use fastcraft.
Reasons include inability to proper report bugs, the magi-hackish nature of this mod, the very likelyness of something going wrong for apparently no reason and the great chance of conflict with other mods (see shaders, HD resource packs and other fancy rendering stuff)

That's pretty reasonable considering what people like Greg or Reika and many others have to go through from time to time :).

It doesn't happen without Optifine, not even when using vanilla mipmaps.
Only when using Optifine+its mipmaps then it happens.

So after investigation, it's present with Optifine and Mipmaps (any level). (Tried with just Optifine and Fastcraft alone.)

Tried with Optifine HD_B4 and HD_U_B4.
Tried with Fastcraft 1.13 and 1.16.
Tried with Forge 1286 and 1263.
Tried with disabling graphics card features.

Was present every time.
Anisotropic filtering improved it a tiny bit, but there still were remnants.

Any more info I can give you?