I guess (hope) this includes some tweaks to the marine strafe-jump?
Probably alien nerfs. :>
(Well, my guess would be that at least Gorge Tunnels are back to requiring research at the Hive but without Biomass requirement, as in previous Beta Test mod versions. People were just not happy with Gorges being able to fortify any position in the map with instant reinforcements from the Hive right away from the start of the game.)
i cant believe some people are still using 32bit, i switched to 64bit and sticked with it since 2006, please, switch to 64bit and if you need to buy memory, please do so, its 20 dollars for an extra gig...cmon, dont upgrade it just for the game
It may be my imagination but every time hear this standard chitchat it sounds like an accusation as if the developers don't know what they are doing and that they should have done it right just from the beginning. Why are people oversimplifying the problems and hurdles of programming? In a complex software like a game engine there are so much dependencies and uncovered and therefor undiscovered combinations of states which lead to bugs like the '32bit problem'. You cannot test everything to make 100% bug free code because humans DO mistakes and that will never change. NEVER EVER. Of course there are test patterns you can run your code through but it doesn't cover the whole code (because those tests have to be made or managed also by humans) and there will still be white spots of bugs among the code which just appears under certain circumstances. Fact is you really have to hunt down that damn buggy code! And there is no one-size-fits-all-tool. You have to be creative about the it. Some problems may be easy to find because they can be allocated to one specific module of code. But boy, some just are a pain in the ass because the problem is scattering all around the code and you simply don't know which thread of dependency you should follow which might cause the problems. So that is (at least what I think) why @Max did the visualization of the RAM allocation to see more easily where the problem lies and and to see if they succeeded in code changes or maybe just to see how the RAM allocation behaves over time.
TLDR: There is NEVER 100% correct code, due to code changes bugs appear you just cannot foresee.
On another topic.
It is not that I agree with the "buy more RAM" mantra or get a proper 64bit system gibberish . But you have to realize that there is a shift happening in the game industry that moves away from 32bit to 64bit systems. It mustn't be the fact for NS2 but like @Hugh already mentioned it will be the fact for 'AAA' titles like Watch Dog or future CoD titles.
Why? Short answer: Consoles! Consoles held back the need of PC upgrades for some years now because most PC games nowadays are console ports. When a game runs OK on a console it was just fine for a mid gaming rig. The 360 and PS3 have way under 4GB RAM the magic 32bit limit. But now that the next gen consoles have 64bit CPUs the demands are suddenly rising and 32bit will no longer be supported for a good reason. Watch Dogs will need 6GB minimum(!) because the next gen consoles aren't forcing the developers to cripple the graphics, animations etc. anymore.
That said you may not need more RAM for now for NS2 but possible future major additions or even performance improvements to NS2 may be difficult or even impossible due to hardware constraints of 32bit systems and the lack of sufficient RAM.
Three words to those who have this issue: Buy more RAM. This is 2013, get on with the time. Upgrade your rig to 64 bit systems and save developers the unnecessary headache, time and money.
Lol at but more ram, I have
win7 64 and 4gb ram...
Thing is my motherboard is DDR2 and my heat sink blocks 2 slots... Do you know how expensive 2x4gb of DDR2 is?
Three words to those who have this issue: Buy more RAM. This is 2013, get on with the time. Upgrade your rig to 64 bit systems and save developers the unnecessary headache, time and money.
Lol at but more ram, I have
win7 64 and 4gb ram...
Thing is my motherboard is DDR2 and my heat sink blocks 2 slots... Do you know how expensive 2x4gb of DDR2 is?
It'll be the same as with ns1, it was run by engine with tested and managed by a large company(read resources), and in the end everyone was playing it on computers light years beyond what it was made for. ns2 is made on their own engine, there's only two ways to improve your gaming experience, one is wait for more and more tweaks to the game and engine by Charlie's Angels. The other is to stop being a cheap tart and upgrading your computer.
All in all, the game is good enough for me atm so extra additions and fixes are just an added bonus to the experience and my fps!
Only beef i got is with people hosting servers with too many player slots for the game to handle.
I really think UWE should just stop setting deadlines for their own work, take a leaf out of the Valve playbook and just release stuff "when it's done."
...Our new target date is the evening US-PST on the 15th of October...
@Hugh, Check your inbox.
For failure to comply with demands I'm making good on this threat.
I have lots of other body parts that I'm proud of so you better fucking post in GMT or UTC from now on.
...Our new target date is the evening US-PST on the 15th of October...
@Hugh, Check your inbox.
For failure to comply with demands I'm making good on this threat.
I have lots of other body parts that I'm proud of so you better fucking post in GMT or UTC from now on.
I second that. Er, not the part about the body parts, but about time zones.
I didn't even know there was a deadline. Just release stuff when it's done , thanks for the post nevertheless.
The whole "buy more RAM" argument is nonsense, more RAM will delay memory leak problems at best, not fix them.
The 257 build crashes quite often in-game for me on my 16G system, so I should get 32G to play a game that has 4G recommended?
Also, I'm on a 64-bit architecture (i7) and like I said, the in-game crashes are frequent.
Although I'm not sure if the Linux version is 32-bit only. That would be a shame considering the great (and early) 64-bit support history of Linux. Why does anyone even bother with 32-bit PC games today anyway?
While it would have been desirable not have these bugs in the first place or a quickie fix just to adress those issues, I'm glad to see UWE is communicative and are trying to step up to the challenge.
Looking forward to increased stability on my 64-bit 16G system when 258 is released!
2 Things about problems in IT: Never try to solve a hardware bug in software and never try to solve a software bug in hardware. Instead, solve the software bug in software and the hardware bug in hardware. That's the only correct approach. Everything else is set to fail at some point.
i cant believe some people are still using 32bit, i switched to 64bit and sticked with it since 2006, please, switch to 64bit and if you need to buy memory, please do so, its 20 dollars for an extra gig...cmon, dont upgrade it just for the game
It's not 20 dollars for the 64 bit Windows license, though.
Aside from the enormous hassle that you have when you need to set up a new OS and migrate all your personal data, reinstall every program (over 250 in my case) and configure it again. Bonus points if you only have less than 500 kbps download speed on your internet connection.
I second that. Er, not the part about the body parts, but about time zones.
I didn't even know there was a deadline. Just release stuff when it's done , thanks for the post nevertheless.
Yeah, I'm not at all bothered by the delay either. At least they communicate, that's the foundation of all good relationships right there. Compared to many many other devs out there UWE has done great.
So help me Satan though if he keeps posting local time zones to a global community. I will find that filthy bogan and slather his naked body in salty lemon Tabasco sauce while I thrash him with jerking socks filled with used needles.
Then I'll make him watch Justin Bieber DVDs as he slips slowly from the mortal coil. I'm so fucking serious @Hugh, don't even tempt me.
I know you got my message btw, you were on this morning. Don't just ignore it. Absorb it, look at those little beards. Use that fear as a tool to better yourself. Be like the batman of time zones.
NarfwakJoin Date: 2002-11-02Member: 5258Members, Super Administrators, Forum Admins, NS1 Playtester, Playtest Lead, Forum Moderators, Constellation, NS2 Playtester, Squad Five Blue, Reinforced - Supporter, Reinforced - Silver, Reinforced - Gold, Reinforced - Diamond, Reinforced - Shadow, Subnautica PT Lead, NS2 Community Developer
I'm mostly just happy that the shotgun hitch is finally actually fixed (knock on wood). It's big for both smooth client play and since it was causing most if not all of the large hitches on the server that result in severe rubberbanding we shouldn't be seeing that much anymore either.
+1 for not rushing the update. Given that that release will be out for at least several weeks before the next one hits, it better be rock solid.
As for balance changes, I'm hoping to see three things: reduced Marine strafe jumping, reduced Jetpack fuel regen, and a slight buff to Fade energy management. Obviously, Marines would need something to compensate, without breaking something in another place...
Three words to those who have this issue: Buy more RAM. This is 2013, get on with the time. Upgrade your rig to 64 bit systems and save developers the unnecessary headache, time and money.
Lol at but more ram, I have
win7 64 and 4gb ram...
Thing is my motherboard is DDR2 and my heat sink blocks 2 slots... Do you know how expensive 2x4gb of DDR2 is?
They sell low profile RAM for people who have large heatsinks
TLDR: There is NEVER 100% correct code, due to code changes bugs appear you just cannot foresee.
Keep believing that. These problems are a direct result of something in the program not working as it should, thus "bad code".
There's a world of difference between "bad code" and "bad coding", which you wrote in your first post.
"Bad code" being the cause of non-hardware bugs is a tautology. "Bad coding", however, implies that if only developers did a better job, there wouldn't be any bugs. And that's simply untrue. The effort to produce fault-free software skyrockets the closer you get to 100%, so 100% is pretty much unattainable. That's why it's only even *attempted* for software where lives depend on it (nuclear reactors, aircraft, military, ...). Every other decent-sized software has bugs, no matter how good the developers are. That's why there is always testing, bug reports, and updates.
My guess is there will neither be a marine-strafe tweak nor an alien tunnel nerf. Purely a performance update, which is okay. I'm still not going to play aliens for a while though.
Comments
Probably alien nerfs. :>
(Well, my guess would be that at least Gorge Tunnels are back to requiring research at the Hive but without Biomass requirement, as in previous Beta Test mod versions. People were just not happy with Gorges being able to fortify any position in the map with instant reinforcements from the Hive right away from the start of the game.)
It may be my imagination but every time hear this standard chitchat it sounds like an accusation as if the developers don't know what they are doing and that they should have done it right just from the beginning. Why are people oversimplifying the problems and hurdles of programming? In a complex software like a game engine there are so much dependencies and uncovered and therefor undiscovered combinations of states which lead to bugs like the '32bit problem'. You cannot test everything to make 100% bug free code because humans DO mistakes and that will never change. NEVER EVER. Of course there are test patterns you can run your code through but it doesn't cover the whole code (because those tests have to be made or managed also by humans) and there will still be white spots of bugs among the code which just appears under certain circumstances. Fact is you really have to hunt down that damn buggy code! And there is no one-size-fits-all-tool. You have to be creative about the it. Some problems may be easy to find because they can be allocated to one specific module of code. But boy, some just are a pain in the ass because the problem is scattering all around the code and you simply don't know which thread of dependency you should follow which might cause the problems. So that is (at least what I think) why @Max did the visualization of the RAM allocation to see more easily where the problem lies and and to see if they succeeded in code changes or maybe just to see how the RAM allocation behaves over time.
TLDR: There is NEVER 100% correct code, due to code changes bugs appear you just cannot foresee.
On another topic.
It is not that I agree with the "buy more RAM" mantra or get a proper 64bit system gibberish . But you have to realize that there is a shift happening in the game industry that moves away from 32bit to 64bit systems. It mustn't be the fact for NS2 but like @Hugh already mentioned it will be the fact for 'AAA' titles like Watch Dog or future CoD titles.
Why? Short answer: Consoles! Consoles held back the need of PC upgrades for some years now because most PC games nowadays are console ports. When a game runs OK on a console it was just fine for a mid gaming rig. The 360 and PS3 have way under 4GB RAM the magic 32bit limit. But now that the next gen consoles have 64bit CPUs the demands are suddenly rising and 32bit will no longer be supported for a good reason. Watch Dogs will need 6GB minimum(!) because the next gen consoles aren't forcing the developers to cripple the graphics, animations etc. anymore.
That said you may not need more RAM for now for NS2 but possible future major additions or even performance improvements to NS2 may be difficult or even impossible due to hardware constraints of 32bit systems and the lack of sufficient RAM.
Lol at but more ram, I have
win7 64 and 4gb ram...
Thing is my motherboard is DDR2 and my heat sink blocks 2 slots... Do you know how expensive 2x4gb of DDR2 is?
Yep. It's about $40 on eBay.
Keep believing that. These problems are a direct result of something in the program not working as it should, thus "bad code".
All in all, the game is good enough for me atm so extra additions and fixes are just an added bonus to the experience and my fps!
Only beef i got is with people hosting servers with too many player slots for the game to handle.
For failure to comply with demands I'm making good on this threat.
I have lots of other body parts that I'm proud of so you better fucking post in GMT or UTC from now on.
I second that. Er, not the part about the body parts, but about time zones.
I didn't even know there was a deadline. Just release stuff when it's done
The 257 build crashes quite often in-game for me on my 16G system, so I should get 32G to play a game that has 4G recommended?
Also, I'm on a 64-bit architecture (i7) and like I said, the in-game crashes are frequent.
Although I'm not sure if the Linux version is 32-bit only. That would be a shame considering the great (and early) 64-bit support history of Linux. Why does anyone even bother with 32-bit PC games today anyway?
While it would have been desirable not have these bugs in the first place or a quickie fix just to adress those issues, I'm glad to see UWE is communicative and are trying to step up to the challenge.
Looking forward to increased stability on my 64-bit 16G system when 258 is released!
It's not 20 dollars for the 64 bit Windows license, though.
Aside from the enormous hassle that you have when you need to set up a new OS and migrate all your personal data, reinstall every program (over 250 in my case) and configure it again. Bonus points if you only have less than 500 kbps download speed on your internet connection.
Yeah, I'm not at all bothered by the delay either. At least they communicate, that's the foundation of all good relationships right there. Compared to many many other devs out there UWE has done great.
So help me Satan though if he keeps posting local time zones to a global community. I will find that filthy bogan and slather his naked body in salty lemon Tabasco sauce while I thrash him with jerking socks filled with used needles.
Then I'll make him watch Justin Bieber DVDs as he slips slowly from the mortal coil. I'm so fucking serious @Hugh, don't even tempt me.
I know you got my message btw, you were on this morning. Don't just ignore it. Absorb it, look at those little beards. Use that fear as a tool to better yourself. Be like the batman of time zones.
The best advice I can give the devs is to not rush, no pressure! Take your time.
[On the otherhand I have very few problems with the game and didn't encounter a lot of fps drop compared to last few builds, so good job there!]
As for balance changes, I'm hoping to see three things: reduced Marine strafe jumping, reduced Jetpack fuel regen, and a slight buff to Fade energy management. Obviously, Marines would need something to compensate, without breaking something in another place...
They sell low profile RAM for people who have large heatsinks
There's a world of difference between "bad code" and "bad coding", which you wrote in your first post.
"Bad code" being the cause of non-hardware bugs is a tautology. "Bad coding", however, implies that if only developers did a better job, there wouldn't be any bugs. And that's simply untrue. The effort to produce fault-free software skyrockets the closer you get to 100%, so 100% is pretty much unattainable. That's why it's only even *attempted* for software where lives depend on it (nuclear reactors, aircraft, military, ...). Every other decent-sized software has bugs, no matter how good the developers are. That's why there is always testing, bug reports, and updates.
If in return, Cargo gets more cover so it isn't a camping Marine's wet dream anymore, I'd be fine with that. :P