Jump to content

jakj

Members
  • Posts

    3240
  • Joined

  • Last visited

  • Days Won

    1

Everything posted by jakj

  1. I've been holding onto 1.5.1 because too many good mods haven't updated for 1.5.2 (which for most of them is just a recompilation) and won't recompile with the "srg" names either. Feeling sympathetic? Don't. Because y'know what I just did? I just deobfuscated the 1.5.1 Ars Magica using Immibis's "Bearded Octo Nemesis" in 1.5.1 MCP/Forge. Then I reobfuscated it with the srg names. Then loaded it in 1.5.2 without even a single error. Minus the time spent figuring out how to do it, and just counting the time actually doing it, this was roughly five minutes of work for one mod. Yeah. A whole five. Before anyone says "They're doing this for free out of the goodness of their hearts! Stop bitching or they might stop wanting to do it for ungrateful people.", I get it. I do. But this was five minutes, which obviously would have been a bit less without the added step of having to deobfuscate in the first place. You want to know how easy it is to do this? I'll tell you. Normally, the last step in making a Minecraft mod ready to publish is running a file called "reobfuscate.bat" (or .sh): This changes all the names into the alphabet soup that is Minecraft's primary anti-piracy measure. To recompile with srg names, you run a file called "reobfuscate_srg.bat" (or .sh). That's it. No, really: That's it. Thanks to the magic of by-default alphabetic ordering in most operating systems' file browsers, they're even one above the other! 1) Deobfuscate with BON. 2) Copy contents of mod into mcp/bin/minecraft. 3) reobfuscate_srg.bin/.sh 4) Copy contents of mcp/reobf/minecraft into mod. *sigh* If anyone has any 1.5.0/1.5.1 mod that won't work in 1.5.2 that they want ported, give me a link and I'll see if I can't get it working just as easily as this one.
  2. Be careful about using Minecraft as any sort of performance metric: It does things in ways most people would never even have imagined, and it requires a whole different set of adjustments for performance than any real software you may use.
  3. Dual core will help very little, beyond letting the OS run concurrently. The OS shouldn't be doing much anyway, ideally.
  4. Well, after a certain point you may get disk bound. Even my gtx460 3.4ghz and super fast ram gets me 60 only after loading the chunks. An ssd would maybe get you a couple frames more but not worth the money just for Minecraft because the CPU limit would kick right back in. I'd say take what you have and enjoy it, personally.
  5. Or this? http://forums.technicpack.net/threads/fixed-unable-to-find-a-version-of-runtime-to-run-this-application.3665/
  6. My only contribution to this stale argument is that the word "dickpickle" is amazing and I will be using it from here on.
  7. Having dedicated VRAM is great for keeping textures on the card, so you get a benefit from that. My one gig card handles up to 128x packs.With no texture pack, Minecraft would barely touch a fraction of that gig but it's better than shared memory.
  8. If your VRAM is actually your RAM and you don't have dedicated VRAM, that adds a whole other ball of wax, your system bus becomes even -more- important, and your RAM's clock speed and latency comes into the picture in a big way. Forget shaders, because Minecraft doesn't use them: It's purely fixed-function with client-side vertex arrays that are reconstructed every object every frame. Hands down, the CPU's single-core speed is your #1 upgrade for Minecraft.
  9. Minecraft is singly-threaded for the most part, and is system-bus bound in terms of rendering, so the two biggest factors in Minecraft speed are 1) how fast ONE CORE of your processor is, and 2) the width (bits per clock tick) and frequency (clock ticks per second) of your system bus. Since Minecraft uses only GL 1.1 and no shaders, the shittiest 3D-accelerated graphics card is just as good as a GTX 680 with the sole exception of VRAM (which matters only to the point of being able to hold your entire texture pack in VRAM at the same time). So much time is spent in Minecraft redundantly transforming vertices and transferring over the system bus, that even the aforementioned shittiest graphics chipset is going to finish its rendering of the paltry couple triangles Minecraft gave it before it even receives the next batch. You should really read upon the history of OpenGL and DirectX: It's rather fascinating. http://en.wikipedia.org/wiki/OpenGL#History
  10. There only is one damn page, genius. The date of the thread is RIGHT THERE. You can resurrect a thread 1) if it's still relevant and 2) you actually contribute something meaningful to continue the discussion. This was neither.
  11. OpenGL 1.1 has a software-emulation mode, so you can run it even without a GPU at all.
  12. Most likely it isn't whaleboxed because the whalebox is for posts that are actually entertaining in their stupidity: It's a showcase, not a landfill. Why in the ever-loving doublefuck did you resurrect a thread more than a month old to say THAT?
  13. You have the Bukkit team to thank for it. Some choice quotations: minecraftcpw ‏@minecraftcpw @Ashfire908 @CraftBukkit Given they've told me to FOAD in no uncertain terms in the past, I'm very skeptical. Hence my announcement minecraftcpw ‏@minecraftcpw @Ashfire908 @CraftBukkit @jkazos yup. choose. forge or bukkit. I know which choice I'm making. Bukkit can't compete. Forge is still alive. minecraftcpw ‏@minecraftcpw @Ashfire908 @CraftBukkit @jkazos all bukkit plugins should be portable to forge.Come on over! We listen over here- just ask nicely minecraftcpw ‏@minecraftcpw @D4rK_CooL @EvilSeph one of his minions already declined my request. I hold no hope of a change of heart...
  14. How? In the future, Forge and Bukkit may be unresolvably incompatible, leaving a Bukkit modpack of Forge mods near-impossible.
  15. Intel integrated graphics would tend to be crap when it comes to advanced OpenGL support, yes, because Intel and Microsoft are bosom-buddies and Intel supports as little of GL as it can without starting a shitfest. It's not that Intel makes bad hardware, because it doesn't: It just doesn't give two fucks about anybody but Microsoft and Windows, meaning they have terrible support in the Linux kernel (there being more frustrating bugs, glitches, crashes, and panics because of Intel graphics chipsets than because of any other).
  16. Then they should go follow their new objectives in life, not try to warp and twist their old efforts to their new objectives. If you want to make money off of something, you should either provide a valuable service, or you could create something novel and useful. Making modifications to an existing video game is neither of those things. It is Mojang's business, not theirs. An outsider's contribution to an existing business is either money (or refusal to provide it) or constructive criticism: Speak with your wallet, or speak with your reason. You don't get to walk into somebody else's business and say "I'm going to make money off of you, now, so we're going to do it -this- way.". Our credibility was untouched: We know very well at whose feet lay the force behind the disruption, and we had a good little shitfit over it; I dare you to find anyone here with an IQ above 6 who says "Technic sucks because they made the bees explode.". It actually pains me to say this, but I have to say it anyway: You are (slightly) underestimating the overall intelligence-level of the Technic playerbase, to say that the majority of them don't know what mods are or how they work. I can see some of the people who come here purely from Yogscast videos might at first not understand that it's a pack of mods and not just one big thing, but that really doesn't last long, not with the vast lack of integration between mods making it clear as you play that you're dealing with a very disjoint collection of sets.
  17. Since it's taking me longer than I had anticipated to get the actual mod part of this thing done (blocks/items/interface), I thought I'd go ahead and post this up here for people to diddle with in the mean time. All of the actual rendering code (including VBO usage) is in there, and you can see some of how it fits together. (It's not set in stone, obviously, but this as-is does work perfectly, so any changes in the future would just be improvements.) Known issues: Lighting still isn't perfect, nor will it be, because Minecraft's default "lighting" is a combination of actual GL lighting, fake lighting done by rendering shadow textures and using color multipliers, a lightmap overlay for some but not all objects, weird and inconsistent usage of normals, and so forth. Also, the SmoothModelBuilder class needs to be reimplemented (the version with coalesced normals and texture coordinates per vertex, the counterpart to RoughModelBuilder which uses facet normals and disjoint texture coordinates), but the old code file with the algorithm in it is there to look at. Not included is the collision-detection (both AABB and pixel-perfect) which I have spread across several test files and isn't in a state suitable for public consumption at the moment. Currently based on Minecraft 1.3.2 with Forge 4.1.4.298. http://j-a-k-j.com/ImaginariumWIP.zip
  18. He doesn't even know what the word "metaphor" actually means, so I wouldn't bother dissecting his opinion too deeply.
  19. The following is the attitude Minecraft modders should have. http://twitter.com/SeargeDP/status/262293083943731200
  20. Reminds me of the time I tried to kick a soccer ball while standing on a cement walkway, except I kicked just -behind- the soccer ball.
  21. Damn. You folks must have chosen hardcore difficulty when you were spawning.
  22. I just got back from the clinic for persistent dizziness. Diagnosis: So much ear wax it's pressing on the internals. Treatment: Sticking a miniature golf club in there and digging. What "fun" times have y'all had?
  23. I had to stick with 2.1 for now to not leave out too many. This thread alone had three such responses.
  24. Am I the only one not sickened by both this attitude and its easy acceptance? This quotation right here, in context, implies directly that mod-makers have the inarguable right to do anything they want, and if they don't, we should count our lucky stars and be grateful. We should be upset at that idea, even to the point of boycotting the mods. Nevermind if someone doesn't do nasty things: That they freely admit that they could and might should be enough.
  25. Angband is amazing, as long as I turn off permadeath. :P
×
×
  • Create New...