Jump to content

TwoTails

Members
  • Posts

    358
  • Joined

  • Last visited

Posts posted by TwoTails

  1. OK, this is not a FIX you can apply yourself.... This needs to be updated with the launcher itself.

    But its the reason why its broke (as far as I can tell)

    Technic Launcher FORCES the 2.9.0 version of the Java Light Weight Game Loader (jlwgl.dll) and all its associated files....

    It force overwrites it every time it launches the game. (I went to an extent to try to prevent overwrites, and if I got it not to overwrite it simply halted game launches and wouldn't start) It downloads and forces this 2.9.0 version to vanilla minecraft, all modpacks, tekkit, voltz, the big dig... everything.

    2.9.0 was a junk version, it didn't work on a large handful of systems for the audio, its why we don't have working sounds!

    Verify for yourself! Go download the real vanilla minecraft 1.7.4 from mojang, use their launcher, and then after it loads and audio DOES work, check the file versions of the jlwgl in the folders there, they are running 2.9.1

    Can we PHUuuuuuLEEEEEeeeeeaaaase get the technic launcher to run 2.9.1 instead of 2.9.0 !!?!!?

    it'll make all of us no-sound whiners really happy.

    It changes absolutely nothing that might break the game as far as I know... However I do know that it fixes the audio.

    "[06:00:53 INFO]: Client> 2014-01-05 06:00:53 [iNFO] [Minecraft-Client] LWJGL Version: 2.9.0"

    right off the default client running unmodded 1.6.4

  2. Just an fyi, we can't help you if you don't include the full report. Saying "...29 more" doesn't give us enough if the solution is shown in one of those twenty nine other lines. Just copy the full report and paste it between the following:

    ["code]paste here["/code]

    Remove the quotes.

    he didn't make it say "...29 more" the minecraft crash report does that when the crash reason is fucking huge.

    He didn't have the modlist there eather...

    so, for all we know, it could just be NEI or something of the same sorts crashing the server by the looks of it.

  3. I removed those and some others. Still same error. Is there anyway to check which mods are client side, besides going to each of the mods' page?

    Heres the new crash report: http://pastebin.com/5FQDXfdg

    well, now that I look closer, it isn't even loading MCP.

    check to see if your forge install on CraftBukkit is even vaild. (IE: run it without anything in the mods folder to see if it will work)

  4. start 1.6.4 in the default launcher and copy everything from:

    Windows: C:\Users\(USERNAME)\AppData\Roaming\.minecraft\assets\virtual\legacy to C:\Users\(USERNAME)\AppData\Roaming\.technic\assets

    Mac: ~/Library/Application Support/minecraft/assets/virtual/legacy to ~/Library/Application SUpport/Technic/assets/ (I think that is where Technic is installed on Mac...)

  5. Or you could give us the following, (ALL of the following!);

    Operating system, (Pc or Mac?)

    Java version

    Graphics card model

    Modpack you are using

    And a screenshot of what the glitch looks like.

    that would help a lot more.

    so would a link to said pack if it is not a Technic default.

  6. Update 'em anyways.

    If that doesn't work, then you should file a bug report for the pack you are using, if it's an official pack.

    and if not, post on the pack's discussion board and hope the author of the pack sees it.

×
×
  • Create New...