Hey guys, long time no see =)

I was wondering if anyone has the same problem I am having: When I start Direwolf 1.7 from the FTB launcher, the launcher closes and the game crashes without any visible error indication. Since I saw a direwolf server is in the planning here, I wanted to get everything working in time and practice some of the tech a bit, but that's kind of hard when the game won't even launch =( Does anyone know what the problem might be other than the amount of allocated memory (currently 4 gigs and still crashing)?

Belated merry christmas!

Yeah i was having that issue as well. I've compiled a list of things to do for new direwolf players.

These will solve "most" problems.

Make sure you are using Direwolf 1.7.10

1. go into FTB options > Advanced > insert this line into the java launch properties > "-XX:PermSize=512m" (w/o quotes)
2. Set the memory allocation to no more than 4Gb
3. uncheck "show console"
4. In minecraft video options, set mipmap to 0


I had a lot of crashing issues initially but these seemed to settle down after playing it for a while along with these adjustments.

I just tried loading it out of curiosity and it appeared to work first time, though only after a long load time.

Previously I'd had a video problem with "1.6" minecraft where attempting to minimise the window while in a 3D view would cause an instant crash, that problem appears to have gone.

Found everything except the mipmap, but i still crash once i try to launch.

Does the equivalent "Vanilla" version launch OK?

every time i make a new world in creative i get instant crash, but seems to work in survival...

Does the equivalent "Vanilla" version launch OK?

boriseng

Without a hitch

For what it's worth I'm finding that DW 1.1.1 has broken rendering (not crashed).

BTW It's no big deal. I just wanted a look around, I don't think I'm serious about playing it right now.

To elaborate: Minecraft loads but the initial menu screen 3D view is confined to a small square and the menu doesn't appear. The console view is reporting a string of "GL" errors. The equivalent "Vanilla" version loads fine.

Also the load time is ludicrous. With console turned off it looks like its crashed but its still loading.

Im getting a new PC between today and saturday, depending on when my video card comes in. Hopefully, that one will like DW a bit better =)

I get the feeling its more of a "frankenpack" than Monster was and that's saying something.

Works fine for me Boris. 100% clear sailing.

Yep and the earlier release worked fine for me too, I just reloaded 1.0.4 to confirm.

So far I think I've narrowed it down to COFH mods. COFHcore breaks it, so for an experiment I tried updating COFHcore to v211 but then something else breaks it and by elimination it appears to be MFR.

Yes, disabling everything then enabling COFHcore breaks graphics. Updated COFHcore+MFR = crash, Updated MFR = crash too.

Resurrection appears to use older versions.

I'd just like to add that version 1.2.1 did load on my machine. Looking at the console there's still a lot of yellow warning lines and a big chunk of red relating to microblocks I think.

One graphics error but it doesn't recur.

[12:52:01] [Client thread/ERROR]: ########## GL ERROR ##########
[12:52:01] [Client thread/ERROR]: @ Post startup
[12:52:01] [Client thread/ERROR]: 1282: Invalid operation

BTW how about referring to error lines as "tomato" and warning lines as "banana" instead of talking about errors and warnings?