Search results

  1. D

    FTB - Curse Update

    As long as the Curse Client runs smoothly on any OS that the current FTB launcher does (specifically MacOS) by the time this is finalized, this sounds great to me.
  2. D

    FTB and Forge - Curse Partnership.

    Could I have some clarification on "launcher" vs. "installer" ? That is: What is the difference between them? Which of them from the FTB team exist right now? Which of them from the Curse team exist right now? Which of them from the FTB/Curse merged team will exist in the future?
  3. D

    FTB and Forge - Curse Partnership.

    Unless similar things have already been tried before. If the FTB forum is being turned into a Curse forum, does that mean MC forum-esque pop up ads and such?
  4. D

    The first thing....

    Soviet
  5. D

    The Perilous Parasite

    I'll jump on the slightly smaller bandwagon and vote to lynch Vike.
  6. D

    Unsupported Direwolf 20: 1.6.4 {PUBLIC BETA}

    Edit: Turns out -XX:MaxPermSize=256m seemed to work. Thanks! If it wasn't just one mod causing the error, I'd agree. AM2 alone shouldn't take up that much memory. As I've said before, the pack runs smoothly with Ars Magica disabled. Having game-breaking lag dependent upon a single mod makes me...
  7. D

    Unsupported Direwolf 20: 1.6.4 {PUBLIC BETA}

    I don't think the problem is a lack of memory. The pack runs just fine without Ars Magica, so I think that the problem is probably some bug in that mod.
  8. D

    Direwolf 20: 1.6.4 {PUBLIC BETA} Crash issues

    Try disabling Ars Magica. (It appears as AM2_1.0.2b)
  9. D

    Unsupported Direwolf 20: 1.6.4 {PUBLIC BETA}

    But what does that do?
  10. D

    Unsupported Direwolf 20: 1.6.4 {PUBLIC BETA}

    What's permgen, and how do I increase it?
  11. D

    Unsupported Direwolf 20: 1.6.4 {PUBLIC BETA}

    Try disabling Ars Magica. On the launcher, select the DW20 pack and click the "edit modpack" button. Select AM2_1.0.2b and click disable, then close the window and launch the modpack. This solved the problem for me.
  12. D

    Unsupported Direwolf 20: 1.6.4 {PUBLIC BETA}

    Mod Pack: Direwolf20 1.0.3 (I've encountered similar problems in previous versions, too.) Mod & Version: Almost definitely Ars Magica 2 (AM2_1.0.2b) Pastebin link to console log (crash logs are not created): http://pastebin.com/DdYFnmHD And I'll throw in another for no extra cost...
  13. D

    Unsupported Direwolf 20: 1.6.4 {PUBLIC BETA}

    Oh, now I'm getting a whole new set of errors! >:D http://pastebin.com/8Zha4zxk What is "Google Analytic Tracking", and would it be beneficial for me to disable it in the advanced options? Edit: Disabled it, got the same error. Also, when I first tried to launch it, it took about half an hour...
  14. D

    Unsupported Direwolf 20: 1.6.4 {PUBLIC BETA}

    I assigned 4 GB of RAM in the options tab. I added some new information to my above post.
  15. D

    Unsupported Direwolf 20: 1.6.4 {PUBLIC BETA}

    Edit: I think the problem was just an overburdened internet connection. Completely reinstalling the launcher fixed everything.
  16. D

    Unsupported Direwolf 20: 1.6.4 {PUBLIC BETA}

    Thanks for the clarification.
  17. D

    Unsupported Direwolf 20: 1.6.4 {PUBLIC BETA}

    A couple quick questions regarding proper bug reporting: I'm confused. Isn't this the opposite of what the modpack team/tech support usually says? Is there any distinction between a launcher crash and a minecraft crash?
  18. D

    Unsupported Direwolf 20: 1.6.4 {PUBLIC BETA}

    Use NEI. The recipe lookup system is wonderful.
  19. D

    Direwolf 20: 1.6.4 {PUBLIC BETA} Crash issues

    You should include the crash logs, whether you think they're necessary or not. They really help the tech support crew.
  20. D

    Direwolf 20: 1.6.4 {PUBLIC BETA} Crash issues

    So, are you sure that inventory tweaks is the problem? If so you might want to re-post this report in the proper format, so that the FTB team can use the information to fix the problem.