This will include methods of increasing performance(both basic and advanced), how to read crash logs and tell what mod caused the issue, finding sources of lag, list of known sources of lag, etc etc. Pretty much a compilation of all those important bits of data that are dotted across the subreddit and this forum, as well as personal experience. What would the interest in such a thing be?
Thinking about making an guide for "noobs"
- Thread starter Wagon153
- Start date
-
The FTB Forum is now read-only, and is here as an archive. To participate in our community discussions, please join our Discord! https://ftb.team/discord
I think this would be very helpful if it gets enough visibility. When such a guide is available it might be a good idea if people who know about this guide would point other people to it when they ask a question that is answered in the guide.
I'm probably going to also include a section on cpu overclocking as well, and a list of chips/motherboards capable of it.
Over clocking is not my thing (so is anything related to hardware) but maybe I will read it one day as I said the same for Linux once.
As a side note does any one have some good jvm flags as the one that I currently use make the garbage collector go crazy.
It'd be nice to have a guide like that around. It would certainly help out people. I must recommend you use one hell of a disclaimer on the overclocking bit if you include it. Being blamed for a wrecked cpu would suck. At least with the game and all you can say 'you should've made a backup' lol.
Still, a definitive starter guide for tracing down lag and interpreting logs is essential for any server op and savvy player! Do it!!!!!
Still, a definitive starter guide for tracing down lag and interpreting logs is essential for any server op and savvy player! Do it!!!!!
A guide would be helpful, but I would like to make a few points.
1. I would steer clear of bundling an FTB diagnostics guide with a guide to overclocking. If you want to make two, and link from one to the other, you're welcome to, but I'd advise separation of purpose.
2. Keep in mind who the guide is for, who is the audience, and what the point of it is. From what's been said, the guide will mainly be for regular users who get bored of saying the same thing over and over. The audience is going to be new FTB/MC users (read: relatively non-technical, and impatient at issues encountered). To that end, I'd steer away from technical explanations in the text itself, it'll put off some, and most will simply not be interested. IF technical information is required, it's available, but for accessibility, be careful of the depth you go to.
1. I would steer clear of bundling an FTB diagnostics guide with a guide to overclocking. If you want to make two, and link from one to the other, you're welcome to, but I'd advise separation of purpose.
2. Keep in mind who the guide is for, who is the audience, and what the point of it is. From what's been said, the guide will mainly be for regular users who get bored of saying the same thing over and over. The audience is going to be new FTB/MC users (read: relatively non-technical, and impatient at issues encountered). To that end, I'd steer away from technical explanations in the text itself, it'll put off some, and most will simply not be interested. IF technical information is required, it's available, but for accessibility, be careful of the depth you go to.
I will give the missing anwser later as I am not at home now.
OS for my desktop is still windows 7
and CPU is an i7 don't remember the details will also come later.
16 GB Ram but only 2 allocated because obvious problems with more.
java 7 whatever the latest update is.
my laptop is running debian
8 GB ram
and an 1.8 MHz amd quad core CPU that should be able to reach 2.4 MHz
java for now is openjdk 7 didn't had the time to change it yet
however I am not so worried about this one at the moment as I already know that this thing will not perform good at all
First thing you would need to do I think, is to not call them that. "Newbies" or "novices" is probably better. "Noobs" have a tendency to bring out really negative reactions.
I will be putting the basics in the main guide and links to the advanced/non FTB stuff with wording like "If you would like to learn more".
Yes I will use a healthy amount of "Warning!" And "I am not responsibles!".
model numbers plz when you can.
4829k? Sure you don't mean 4820k? In which case, you don't need any java arguments. You should be in the high hundreds at almost all times anyways. As for your laptop, not much can be done. Laptop CPUs can not be overclocked(you don't really want to either. There's a reason why they are underclocked...). You can try checking the box in the FTB launcher for optimal arguments.
a small typo indeed it was a 4820K sorry about that and I already suspected something like that for my laptop