Jump to content

_DroidFreak_

Members
  • Posts

    4
  • Joined

  • Last visited

Converted

  • Gender
    Undisclosed
  • Personal Text
    I am new!

_DroidFreak_'s Achievements

Tree Puncher

Tree Puncher (2/8)

0

Reputation

  1. I'm trying to run a forge server, and for some reason I can't allocate more RAM to it. I'm using a batch file with this command: "C:\Program Files\Java\jre7\bin\java.exe" -Xms2048M -Xmx6144M -jar "forge-1.7.10-10.13.1.1217-universal.jar" As you can see, I have 64 bit java, am running the latest Forge version, and have it set to use 2-6 GB of RAM. As far as I can tell I am doing nothing wrong. However, whenever I start up forge it seems to be using far less RAM than I allocated. It seems to max out at 250 MB or so, and throws "java.lang.OutOfMemoryError: PermGen space" pretty frequently. Can anyone help me out?
  2. I do recognize that modifying the base classes is probably a bad idea. I even think Optifine should probably come out with a Forge version and make all our lives easier. Unfortunately, I'm not Optifine's dev, I'm just a player and server admin who wants to run Optifine and Forge together. Isn't there a better way to convince Optifine to port to Forge than making Forge intentionally incompatible? In any case, I wish you the best of luck in convincing sp614x. If there's any way you think I could help (Besides, you know, spamming the Optifine thread with "Y U NO FORGE") I'd be happy to. If sp614x is willing I might even be able to help with the porting, as I'm fairly experienced as a programmer, although I haven't developed anything major in Java. Also, what do you mean by "flags to turn this off"? Do you mean the -Dfml.ignorePatchDiscrepancies=true JVM argument? Because I was using that (as per Optifine's instructions) in all cases mentioned, both the 777 case that worked and the post-780 cases that didn't. If that is the correct flag, post-780 Forge ignores it and if there's another flag I was not aware of it.
  3. I had the exact same problem but I know the cause: LexManos made FML check for and reject jar mods (such as optifine) in build 780. Try build 779 or 777, they should work with Optifine. See the thread I just started for more specifics on the problem.
  4. I got Forge build 777 to work with Optifine HD U A2 last night, so I was completely baffled when I tried the exact same Optifine version and the exact same install procedure with Forge build 789 without success. I got this error: "The minecraft jar file[...]/minecraft/server/MinecraftServer.class appears to be corrupt! There has been CRITICAL TAMPERING WITH MINECRAFT, it is highly unlikely minecraft will work! STOP NOW, get a clean copy and try again!" I thought it might just be a small bug, so I tried with the recommended version, build 784. The result was the same. It then occurred to me that since build 777 works and the newer builds don't, I should look up the changelog. Here's what I found: "Build 1.6.2-9.10.0.780 LexManos Updated FML: MinecraftForge/FML@c997f2adbc4c11cd8c2abe5f82ccd00b0e954b68 FML now verifies that the minecraft jar is correct and intact. This is intended to discourage those who think that modifying the minecraft jar is still acceptable." Hold on just a second there! LexManos made FML check for and reject jar mods! His intention was probably to prevent noobish mods from crashing Minecraft, but this is Optifine we're talking about here. I'm 95% positive that if it FML didn't check for jar mods and continued everything would work fine. I think that FML shouldn't try to prevent jar mods. Let's do a risk assessment: Noobish jar mod + FML checks for jar mods = FML arrests startup, Minecraft doesn't start. Noobish jar mod + FML accepts jar mods = Minecraft crashes. Legit jar mod + FML checks for jar mods = FML arrests startup, Minecraft doesn't start. Legit jar mod + FML accepts jar mods = Minecraft works fine. If the jar mod is noobish and is going to crash MC anyways, this change accomplishes nothing because a failure to start and a crash on startup are virtually identical. If the jar mod is legit, however, this change is bad because it STOPS MC from working. If someone's trying to use a jar mod that's going to crash the game anyways, I say let them proceed and crash the game. I'd much rather deal with a crash than with Forge flat-out refusing to try.
×
×
  • Create New...

Important Information

By using this site, you agree to our Terms of Use.