I have read the snapshot list of new features for 1.3, it seems that the game may use more cpu than in the current version. Will this make mc slower or not work for low quality p.c's?
i would rather then fix the lag then rush the release. it would be more professional to release a working version rather then a half-assed laggy version filled with glitches... lets be honest, there WILL be glitches
i would rather then fix the lag then rush the release. it would be more professional to release a working version rather then a half-assed laggy version filled with glitches... lets be honest, there WILL be glitches
I think the reality is more a question of making everyone wait to fix a problem that only effects 5% of the users.
Seriously, even many people with not-so-great computers have reported minimal problems with the snapshots, including myself. The results are just too variable - you can't tell who will have problems just based on computer specs.
They've already begun on enhancing performance in the latest snapshot. There will be glitches, but that's just a part of Minecraft. You can't really call it half-assed though if you've paid any attention at all to development over the past several snapshots.
Everyones computer is affected differently, its really odd. I get about 30 more fps with 12w26a, and they hadn't, and still haven't fully finished optimizing for 1.3! Although some lower end computers are using more cpu, and getting lower frame rates... so It just depends on your machine. As of now, it seems a bit risky, but by 1.3 they will have optimized it the best they can for now.
Rollback Post to RevisionRollBack
Computer Specs: 4GB 1333 Mhz DDR3 RAM- 320GB 5400RPM Hard Drive- Dual Core Intel Core i5 2415M @2.3 Ghz- Intel HD 3000 Graphics- Only $1200! Yeah, I got a Mac, because I'm stoopid. Scratch that: Intel i5 2500k, 1TB 7200RPM Seagate Barracuda, Gigabyte Z68-D3H-B3, 8GB 1333Mhz DDR3 RAM, Radeon HD 6850, Running OSX.
Well, the elapsed time between 1.2.5 and 1.3 will be 4 months (it'll be 5 months since 1.2). So if you took that as an indicative time span between releases, December would be about right.
Of course the times between 1.1 and 1.2, and 1.0 to 1.1 were less than 2 months apiece, so there obviously is no set schedule.
I guess it depends on how ambitious 1.4 is going to be in terms of content.
I use a laptop from 2007 that has seen some hard time. I play on short draw distance and it the game remains playable. If things get bad for you, wait for optifine to update and use it.
Edit: meant to add that I am using the latest snapshot as well, which I imagine is close to what official 1.3 will be.
I think the reality is more a question of making everyone wait to fix a problem that only effects 5% of the users.
Seriously, even many people with not-so-great computers have reported minimal problems with the snapshots, including myself. The results are just too variable - you can't tell who will have problems just based on computer specs.
It isn't just 5% of the computers and Minecraft users, and with 20 million registered users, 5% of the user base is still a million customers. That should be something worth paying attention to by itself. Of the roughly 6 million that have formally purchased the game, it is still over 300,000 users representing roughly an investment of $1-$3 million of revenue that has been brought into Mojang by these paying customers who you are so casually dismissing and willing to throw away. That should mean something.
What specific issue seems to be plaguing users at the moment in terms of performance is that Minecraft as of version 1.3 is going to be running in two completely different processes now. In fact it will appear as two different applications on your task bar if you are using Windows, as the server and client are now completely separate, and the "server" is running locally. Other operating systems will have similar experiences. For people with a single CPU on their computer, there are some operating system penalties that seem to be hitting some aspects of the game pretty hard, where the "server" side of things (terrain generation, mob spawning, plant growth, etc.) may have a lower priority than the rendering and can "lag" from time to time in a way that is worse than what you see with 1.2.5
For those people who are fortunate enough to have dual processors or even more on their computers, the performance hit isn't nearly so drastic as most operating systems would end up having the "client" and "server" processes working on separate CPUs over time, and you may even see a slight performance increase as the task balance between processors is pretty even for how Minecraft actually works. The number of CPUs that you have on your computer does seem to be the major issue at the moment in terms of performance in the future and not other side issues like memory, CPU speed, or other factors.
Everyone's computer will be effected differently, so we will just have to wait and see. Hopefully everything will be corrected in 1.4 as stated.
Marv
This.
I wouldn't worry too much. The biggest performance sink for most players is rendering, which is still done exclusively on the CPU. Hopefully, when Jens designs the Performance Update (1.4), he'll take a cue from Optifine and enable multi-cored CPU's and (I pray!) GPU's for rendering. (PLEASE!!!)
Rollback Post to RevisionRollBack
The Internet is a big place, friend. I've been places you've n͍̺e̩v̦e̦̰͍͓̩ͅr̜̭̝̬̬͉̤̬ ͙ịm̖͇a͍͇̤͙̥g̤̘i͔͖̤̼̪̬n͖͔̳̬̯e̩̘ḓ͈͔̠̙͇̼̯.͎
It isn't just 5% of the computers and Minecraft users, and with 20 million registered users, 5% of the user base is still a million customers. That should be something worth paying attention to by itself. Of the roughly 6 million that have formally purchased the game, it is still over 300,000 users representing roughly an investment of $1-$3 million of revenue that has been brought into Mojang by these paying customers who you are so casually dismissing and willing to throw away. That should mean something.
Now consider that same situation, but with Microsoft and Windows 7. Or DICE and Frostbite 2.0. Or the shutdown of the 1st Gen XBL. Or old IGPs not getting Windows 7 drivers. Artificially limiting your future prospects for the sake of your fringe cases can be considered an equally bad, if not worse approach to a business. This a group of people who, for whatever reason, have fallen so far behind the mean that we don't even know where they got lost.
As someone who has done support for some organizations with critical legacy apps, I can tell you that its not a sane way to operate. Having to maintain a stock of DOS boxes for a database app that a department can't live without, but doesn't want to spend the money to stand up a new system and migrate. Having to deploy 5 different versions of Java for 12 different programs. Managing a Linksys router (you heard me) for a remote site using per seat VPN. And this one place with a T1 multiplexer to extend a site phone network to these 3 shacks at the other end of the property doing weather research... must had been there since the 80s.
At some point you just need to bite the bullet, and get caught up before something bad has a chance to happen. This is particularly true with software development, where the user demands are always increasing. 95% of your users have been ready to take that next step for the past 5 years.... are you really going to hold them back because 5% of your users are too stubborn or incapable of being where you were 5 years ago?
What specific issue seems to be plaguing users at the moment in terms of performance is that Minecraft as of version 1.3 is going to be running in two completely different processes now. In fact it will appear as two different applications on your task bar if you are using Windows, as the server and client are now completely separate, and the "server" is running locally. Other operating systems will have similar experiences. For people with a single CPU on their computer, there are some operating system penalties that seem to be hitting some aspects of the game pretty hard, where the "server" side of things (terrain generation, mob spawning, plant growth, etc.) may have a lower priority than the rendering and can "lag" from time to time in a way that is worse than what you see with 1.2.5
This has only been true for 2 weeks, and had been merged into a single process over 6 weeks ago. So now your dealing with 1 process, 2 threads and only half the JVM overhead. Anyone with a post P4-Era processors (after 2005) should not have a huge problem running under this setup. Memory requirements are obviously going to be higher, but no system from that time period should be running less then 2 GB, and most are already running 4.
For those people who are fortunate enough to have dual processors or even more on their computers, the performance hit isn't nearly so drastic as most operating systems would end up having the "client" and "server" processes working on separate CPUs over time, and you may even see a slight performance increase as the task balance between processors is pretty even for how Minecraft actually works. The number of CPUs that you have on your computer does seem to be the major issue at the moment in terms of performance in the future and not other side issues like memory, CPU speed, or other factors.
On the contrary, I/O becomes even more important when your trying to run processes or threads concurrently. Outside the CPU, most things can only service one task at a time, forcing the others to wait for the current one to finish. Think about why SSD's help speed up the execution and processing of large data sets vs mechanical drives. A fast processor can speed up boot time, but a fast processor back up by an SSD can do it in less then half the time.
its stupid they get us sooooo happy and rampt up then the day its suposed to come out they move it till augist. if they move it again i will personaly find Mojang and tell them wtf and complain
its stupid they get us sooooo happy and rampt up then the day its suposed to come out they move it till augist. if they move it again i will personaly find Mojang and tell them wtf and complain
There was no day "it was supposed to come out". Frustration comes from one's expectation. You expected something that nobody actually said, therefore you are now frustrated that your expectation didn't come true. So basically you only have yourself to blame!
its stupid they get us sooooo happy and rampt up then the day its suposed to come out they move it till augist. if they move it again i will personaly find Mojang and tell them wtf and complain
What do you want, a finished release or another beta? Your game to work better than 1.2 or worse than 1.2? Why not use the snapshots if you're so upset?
but it should be a worry
Marv
http://www.minecraft...t-a-fan-theory/
There is nothing super-major in 1.3 that makes me go "OMG I GOTZ TO HAVE ET!!".
I'll be fine with keeping 1.2.5 until September or October.
Source?
Twitter: @EvanLange7737
Seriously, even many people with not-so-great computers have reported minimal problems with the snapshots, including myself. The results are just too variable - you can't tell who will have problems just based on computer specs.
They've already begun on enhancing performance in the latest snapshot. There will be glitches, but that's just a part of Minecraft. You can't really call it half-assed though if you've paid any attention at all to development over the past several snapshots.
Computer Specs: 4GB 1333 Mhz DDR3 RAM- 320GB 5400RPM Hard Drive- Dual Core Intel Core i5 2415M @2.3 Ghz- Intel HD 3000 Graphics- Only $1200! Yeah, I got a Mac, because I'm stoopid.Scratch that: Intel i5 2500k, 1TB 7200RPM Seagate Barracuda, Gigabyte Z68-D3H-B3, 8GB 1333Mhz DDR3 RAM, Radeon HD 6850, Running OSX.Well, the elapsed time between 1.2.5 and 1.3 will be 4 months (it'll be 5 months since 1.2). So if you took that as an indicative time span between releases, December would be about right.
Of course the times between 1.1 and 1.2, and 1.0 to 1.1 were less than 2 months apiece, so there obviously is no set schedule.
I guess it depends on how ambitious 1.4 is going to be in terms of content.
Edit: meant to add that I am using the latest snapshot as well, which I imagine is close to what official 1.3 will be.
It isn't just 5% of the computers and Minecraft users, and with 20 million registered users, 5% of the user base is still a million customers. That should be something worth paying attention to by itself. Of the roughly 6 million that have formally purchased the game, it is still over 300,000 users representing roughly an investment of $1-$3 million of revenue that has been brought into Mojang by these paying customers who you are so casually dismissing and willing to throw away. That should mean something.
What specific issue seems to be plaguing users at the moment in terms of performance is that Minecraft as of version 1.3 is going to be running in two completely different processes now. In fact it will appear as two different applications on your task bar if you are using Windows, as the server and client are now completely separate, and the "server" is running locally. Other operating systems will have similar experiences. For people with a single CPU on their computer, there are some operating system penalties that seem to be hitting some aspects of the game pretty hard, where the "server" side of things (terrain generation, mob spawning, plant growth, etc.) may have a lower priority than the rendering and can "lag" from time to time in a way that is worse than what you see with 1.2.5
For those people who are fortunate enough to have dual processors or even more on their computers, the performance hit isn't nearly so drastic as most operating systems would end up having the "client" and "server" processes working on separate CPUs over time, and you may even see a slight performance increase as the task balance between processors is pretty even for how Minecraft actually works. The number of CPUs that you have on your computer does seem to be the major issue at the moment in terms of performance in the future and not other side issues like memory, CPU speed, or other factors.
Version 2.1 now updated for MC 1.6.2
This.
I wouldn't worry too much. The biggest performance sink for most players is rendering, which is still done exclusively on the CPU. Hopefully, when Jens designs the Performance Update (1.4), he'll take a cue from Optifine and enable multi-cored CPU's and (I pray!) GPU's for rendering. (PLEASE!!!)
Now consider that same situation, but with Microsoft and Windows 7. Or DICE and Frostbite 2.0. Or the shutdown of the 1st Gen XBL. Or old IGPs not getting Windows 7 drivers. Artificially limiting your future prospects for the sake of your fringe cases can be considered an equally bad, if not worse approach to a business. This a group of people who, for whatever reason, have fallen so far behind the mean that we don't even know where they got lost.
As someone who has done support for some organizations with critical legacy apps, I can tell you that its not a sane way to operate. Having to maintain a stock of DOS boxes for a database app that a department can't live without, but doesn't want to spend the money to stand up a new system and migrate. Having to deploy 5 different versions of Java for 12 different programs. Managing a Linksys router (you heard me) for a remote site using per seat VPN. And this one place with a T1 multiplexer to extend a site phone network to these 3 shacks at the other end of the property doing weather research... must had been there since the 80s.
At some point you just need to bite the bullet, and get caught up before something bad has a chance to happen. This is particularly true with software development, where the user demands are always increasing. 95% of your users have been ready to take that next step for the past 5 years.... are you really going to hold them back because 5% of your users are too stubborn or incapable of being where you were 5 years ago?
This has only been true for 2 weeks, and had been merged into a single process over 6 weeks ago. So now your dealing with 1 process, 2 threads and only half the JVM overhead. Anyone with a post P4-Era processors (after 2005) should not have a huge problem running under this setup. Memory requirements are obviously going to be higher, but no system from that time period should be running less then 2 GB, and most are already running 4.
On the contrary, I/O becomes even more important when your trying to run processes or threads concurrently. Outside the CPU, most things can only service one task at a time, forcing the others to wait for the current one to finish. Think about why SSD's help speed up the execution and processing of large data sets vs mechanical drives. A fast processor can speed up boot time, but a fast processor back up by an SSD can do it in less then half the time.
There was no day "it was supposed to come out". Frustration comes from one's expectation. You expected something that nobody actually said, therefore you are now frustrated that your expectation didn't come true. So basically you only have yourself to blame!
What do you want, a finished release or another beta? Your game to work better than 1.2 or worse than 1.2? Why not use the snapshots if you're so upset?