HalestormXV

So we all know Attack of the B-Team is a huge modpack and loads of fun. So my question to you all is how much RAM you think would be sufficient to run a server of this type? I haven't posted this is the server section because it isn't advertising a server and it isn't asking for help regarding a server/modpack. This is more a discussion about the modpack. Thoughts? My feelings are 3 to 4 gigs at minimum. I think 2 would be just too little.

I just want to chime in here as I have gotten this mod pack to work with both OptiFine as well as Shaders however I personally experienced some heavy lag spikes every once and a while as well as some odd glitching (It was dependent on what shaders I was using). Basic thing you need to know in my experience was that any OptiFine version for 1.6.4 above C6 will not load properly. Again strictly speaking from my experience with it.

I have this same error occurring as well. With the Java Access violation, however I have already increased the RAM and the permGen size. There seems to be no rhyme or reason to it. I can be playing for a few minutes to an hour and a crash will happen sporadically. I know it is a java crash though because Minecraft does not crash and the report that is generated is an hs.pid or something like that. But the error message is similar to the OPs. I made a post about it before the bug board was created so I don't exactly want to go and relink it as it will generate traffic to the wrong board. However the one suggestion you made David was to update the LWGJL? Is this accomplished by downloading it and putting it into the folder? And I also see you suggested removing the OpenAL64.dll - I noticed that, that is always referenced in the crash report. What does it do exactly and does it auto re-install itself once removed from the folder?

Hello hello. So as we all know Hexxit is a great new modpack focused on adventure and exploration. Many people are making Let's Plays about it and i am also one of them, but I've decided to do it on Hard Difficulty. So come join me on my adventure into the world of Hexxit, filled with exploration, dungeons, comedy, and even some great fails. Here is the link, let me know what you think Www.youtube.com/playlist?list=PLGUlXzRUq_yO0ztgCKPpUcw1XF1qcc8f1

Minor update to this thread as I saw others on the forums posted about it as well. I tried all of the solutions posted above. And yes to those that think it was the way I launched minecraft I tried it with the Hexxit launcher as well and the same error occurred but one similarity.....it occurred near a DimentionalDoor dungeon. I really don't want to place blame on DD and perhaps it is totally coincidence. But it is something worth reporting.

I had this very same error. It is posted in this thread over here. Perhaps you may want to try some of the solutions in that thread, like increasing memory and permSize. Thread: http://forums.technicpack.net/threads/odd-crashing-latest-stable-hexxit.48827/

Naturally quite a few mods come with that clause. However, the part I bolded and italicized indicates that had the Modpack creators wanted to use it in a modpack they could so long as they received written permission to do so. Many mods require permission before just placing them into a pack to distribute. I was just stating why Modpack creators would not want to seek that permission. Unless you intended to quote the post above me?

That would be nice. But unfortunately OptiFine doesn't always play nice with other mods to my understanding. So it is understandable and I totally agree with it as to why they wouldn't. For example those bugs listed above where the Armor Status icons disappear, or the Smeltery's lava render error. I experienced these as well and it is unfortunate but it is what it is.

Not entirely, because I don't believe the launcher has anything to do with it (other then making it easier to assign larger quantities of RAM and permGen as well as autoupdating), all the mods used by the pure Hexxit pack are copied over as well as the config files. Much the same as when a server owner downloads the server files. Any tweaking i may have done, which quite literally was changing a single id in Biome'O Plenty so it did not clash with the assigned id of BiomesXL, shouldn't have any effect on Hexxit Pack, to my knowledge at least, that would cause a Java Crash. Now one can say that naturally one of the mods I have added could be causing the issue (Mind you I only added 3), of course. But, being that this is not a Minecraft Crash though and it is a java crash and the Hexxit team has more then often managed to fix some errors in 1.0.1 alone with some crash to Desktops (such as the chests being opened which was also if i recall a java crash) i thought it well to post this error here just in case it is in fact something to do with a mod that is in the Hexxit pack/configs. However I could also try to test with the Hexxit Launcher, that is fine. But something tells me it has nothing to do with how I launch Minecraft.

I had this error with another config file. Your MapWriter config file has some type of oddity in it. You can re-download the pack or perhaps try to delete that config file and let it regenerate itself.

MultiMC uses its own jar. Essentially you can say i install Hexxit piece by piece.

With MultiMC its very similar to the Launcher. You type in how much you want to allocate. However MultiMC offers another area that allows you to edit the JVM for that instance. So in my case I would input the command: -Xmx4G -Xms2G -XX:MaxPermSize=256M and save it. And now that instance has those settings saved to it. So the JVM will run with those parameters. And to my knowledge MultiMC will take those Parameters and apply them where it has to, because when I look at the startup log it states that it is increasing the JVM memory as well as the permSize. To get Hexxit I use both the Hexxit Launcher for updates as well as another Single Player world. But recently it has been fussing up on me so I use MultiMC and import the mods and make my own changes to the configs as well as add and take things out. Like my Hexxit doesn't have the Better Storage mod because I took it out, however I added in Biomes 'O Plenty because I love the way it plays with XLBiomes. I don't want to derail the topic though. And I do not run a Hexxit Server. EDIT: As you can see by the log it appears to do what it is suppose to do: Instance folder is: T:\Minecraft\instances\Hexxit Working\minecraft\ Instance started with command: "C:\Program Files\Java\jre7\bin\java.exe" -Xmx4G -Xms2G -XX:MaxPermSize=256M -Xms2048m -Xmx4096m -jar MultiMCLauncher.jar "HalestormXV" "1749058707430945534" "MultiMC: Hexxit" "854x480" "Mojang" Loading jars... Loading URL: file:/T:/Minecraft/instances/Hexxit%20Working/minecraft/bin/minecraft.jar Loading URL: file:/T:/Minecraft/instances/Hexxit%20Working/minecraft/bin/lwjgl.jar

I use MultiMC because I have multiple instances with many different packs as well as some of my own packs as well as customize a lot of stuff. So I generally just increase the memory in MultiMC of my instance via the settings tab and then under the Java settings then I have my java path and my JVM Arguments per instance. So when I launch that instance it is all set up. That is why this error threw me off because I have one instance that has close to 90 mods in it and it runs fine without increasing the permSize. Granted those instances also don't have those noob mistakes in them that I overlooked when setting up my launcher.

Yeah that was a typo on my part and I may have used it in the launch command while reviewing over the crash files (silly mistake). I will try the command line you suggested. And thank you for the external link tip. I am so used to just url= etc. Could it very well be the permSize causing this issue? OR more likely the jvm arguments? Wouldn't mistakes like that cause it to lock up at the start? What exactly could I look for that would indicate that? Regardless I appreciate the response and I will be trying that, any other insight? Perhaps a mod misbehaving? Although i doubt that since this is an actual java crash and not a minecraft crash. EDIT: This is a single player

New to posting on these boards been, following for a long time and never really ran into issues except this time. I am running the current Stable Version of Hexxit. Now I have done numerous searches and I find that many people are experiencing these crash to desktop errors. I've done my search and I found several threads on this board. However they are either incomplete or never really resolved. So here is the error and I will be as detailed as possible. This error occured just recently actually twice in a half hour span. And both times I placed a block. (Cobblestone to be Exact). Now the client then immediately crashed to desktop and did not generate a Crash Report for minecraft but instead generated a "hs_err_pid5040" the first time in the directory and a "hs_err_pid5856" the second time in the directory. hs_err_pid5040 hs_err_pid5856 Now as I said I have searched prior to this post, so I saw all of the typical responses and I will answer them right now: Yes I've Updated Java - No Resolution Yes I've Updated My Graphics Drivers directly from my Video Card's Site - No Resolution Yes I've Allocated More Memory to Minecraft - No Resolution Yes I've Allocated More permMemory I think it is called. I've Tried Launching Minecraft with -Xmx2048M -Xms4096M -jar - No Resolution I have NOT tried to update my LWJGL (could that be a cause of these errors?) SPECS: Win 7 64bit Home Premium 8Gig Ram AMD FX-8120 Eight-Core Processor AMD Radeon HD 7700 Series If you need any other info please let me know. I wold really like to resolve this issue. I am curious to know if it has to do with Dimensional Doors. The reason why I signal that mod out is because I have heard that it can cause instability in some cases.