Jump to content

Olloth

Members
  • Posts

    101
  • Joined

  • Last visited

Everything posted by Olloth

  1. Oh, yeah sorry. The other guy was right for this particular problem it's actually java 7 on OSX doesn't work with lwjgl even minecraft has problems with it. Sorry the log you posted threw me off because that error message in your log was our server issue. Rolling back to java 1.6 fixes LWJGL for OSX.
  2. What error are you actually receiving?
  3. Can you link or PM me your 1.5 modpack platform link? Thank you.
  4. The problem should have had nothing to do with downgrading to 1.6, I believe you just happened to do that when our servers got fixed. This problem shouldn't be happening anymore, we believe we sorted out all the server and launcher issues causing it.
  5. This should be resolved now, we had some extreme server issues and the latest build of the launcher is now putting much less strain on it.
  6. This should be resolved now, we had some extreme server issues and the latest build of the launcher is now putting much less strain on it.
  7. Please download the newest launcher from www.technicpack.net/download
  8. http://forums.technicpack.net/threads/changing-destination-folder-causes-folder-wipe-and-infinite-folders.41185/#post-337950 I believe I have solved the issue, sorry for the trouble.
  9. I've taken some steps to try and prevent this sort of thing from happening again: https://github.com/TechnicPack/TechnicLauncher/commit/0c0247a0e1067b3d0cf65bb7a95bbefbf9f76d5a If it happens again please report it immediately. I'm not entirely sure if I fixed it since I can't reproduce it, but I did disallow selecting a non-empty folder. That means if it were to happen again, you WOULDN'T be able to have your entire documents folder selected and thus it can only ever delete the files it uses itself. I will be promoting this fix shortly and your launcher should update with the fix automatically. I am absolutely sorry for any saves or relatively important minecraft files anyone may have lost.
  10. Wow. Yeah I am very sorry, this is a severe problem I'll get to work on it right away and keep everyone posted.
  11. Careful he's shifting his goalposts. He got you to imply we thought having links to content is illegal at all.
  12. hire me too cats farts people who post on this forum jelly beans and has 6 major programming projects
  13. Olloth

    Helen Keller

    I LIKE THIS THREAD U SHOULD MAKE MOVIE 4 W/ HELEN BONHAM KELLER AS OP
  14. dad said "olloth dont be a dumb" but it was two leight
  15. welp. That's not how that URL works unfortunately, you'll just have to wait.
  16. Maybe if you didn't start out with hostility you wouldn't get it in return. I called your bullshit on how we're terrible programmers, because I don't let that kind of thing stand. I will look into how to potentially get better instructions or finding the correct JVM version for people on mac but in the mean time I wanted you to be aware that I won't stand for you outright fabricating the simplicity of the problem. It's not as simple as you made it out to be and if you want to backseat code fix it yourself. You back pedaled out of all that stuff into discussion about which JVM to use at this point which means we were right. It's a JVM issue. I don't want people reading the thread to openly believe your statements about our ability to change a line of code and make the problem go away. It's a lot more complicated than that. I have to reproduce the problem, then reproduce the solution, then post the steps to the reproduction of the solution in a way that a lot of 12 year olds can figure it out. Reproducing the problem is tough because I have to find someone with a mac that knows how to use it enough to follow directions and manually install a bunch of different JVMs to test it out. I'm not simply saying it works on my machine. I'm saying I have an extremely hard time fixing bugs for machines I don't own. This is an open source project and a volunteer one at that. I don't have the resources that a real company would to purchasing multiple sets of hardware to test on. If you can figure it out without me I would appreciate that, it seems you already found one not ideal solution and in the future I can potentially help people by referencing that. But don't say it's all our fault and we're doing nothing. That's untrue.
  17. I don't see anything in this post that helps. I just pointed out exactly what the problem is with the JVM what do you want me to do. Submit a pull request to Oracle? I'm sorry that Apple/Oracle support sucks. It's their fault, not ours. It's not some 'stupid mistake' we made.
  18. If you want you can even look in the OpenJDK version of the JVM and you can see here http://grepcode.com/file/repository.grepcode.com/java/root/jdk/openjdk/7-b147/sun/font/FontUtilities.java#411 that they cast without checking type. So correct, someone was indeed stupid enough to upcast and not check the exception or that it was safe to cast in the first place. Specifically my hunch is that the bug is provided entirely from within the JVM. We ask for the Arial font, and the JVM provides itself the wrong class when loading the Arial font on a mac and then crashes on casting it. I'm not sure what we can do about that.
×
×
  • Create New...