^^
I was finding it amusing too, more so with some 64 bit systems having the same out of memory errors as 32 bit.
You just fail to read the thread. You read the first 2 posts and skipped to typing a message? THE GAME IS 32 BIT IT DOESN'T GIVE A F*CK WHAT BIT SYSTEM YOU HAVE. Whatever hugh said on the second post just shows how disconnected with reality some of the devs are.
I had a crash on a 64bit system yesterday too. Granted, it's rare, but it happened. Sent those reports, but even on 64bit, the game is not crash-proof.
^^
I was finding it amusing too, more so with some 64 bit systems having the same out of memory errors as 32 bit.
You just fail to read the thread. You read the first 2 posts and skipped to typing a message? THE GAME IS 32 BIT IT DOESN'T GIVE A F*CK WHAT BIT SYSTEM YOU HAVE. Whatever hugh said on the second post just shows how disconnected with reality some of the devs are.
http://forums.unknownworlds.com/discussion/132111/ns2-failed-to-allocate-bytes-and-will-now-terminate#latest
^^
Have a read of this thread before your next brain fart concerning me and you will see that i have been having this issue for weeks and i am not posting random comments without having some experience of it myself.
What i was refering to with my comment was the fact that some are still under the illusion that these crashes and poor performance that a lot of players are experiencing is a result of 32 bit users and 64 bit users are immune, which is simpley untrue.
Yes its been going on too long and yes i am a little p*ssed.
In their explanation as to why this was happening, I find it odd to blame it on the new player skins. How do skins cause the game to consume 7 times more memory than before the update?
Before the update I recall seeing the game consuming about 500 MB of memory. I have 16 GB of ram on Windows 8 Pro 64-bit. Now it's consuming in excess of 3 GB at the time of crash (as reported by task manager).
IronHorseDeveloper, QA Manager, Technical Support & contributorJoin Date: 2010-05-08Member: 71669Members, Super Administrators, Forum Admins, Forum Moderators, NS2 Developer, NS2 Playtester, Squad Five Blue, Subnautica Playtester, Subnautica PT Lead, Pistachionauts
@ninja_iguana
Because originally it was just the 3 different male models : Black, Normal, Deluxe.
With the model and animations running just over 100 MB each.
Now these new models have been introduced: Assault, Elite Assault, and soon female Assault and elite assault, shadow skulk, female normal, female deluxe, female black ... that's 8 more models. 0.0
The female marine obviously does not use the same animations as the male model, either.
Are UWE considering adding an option to just display the default skins/models as the devs of the Unreal game introduced, seems like this would put these new crashes to bed, as has been suggested on these forums ?
IronHorseDeveloper, QA Manager, Technical Support & contributorJoin Date: 2010-05-08Member: 71669Members, Super Administrators, Forum Admins, Forum Moderators, NS2 Developer, NS2 Playtester, Squad Five Blue, Subnautica Playtester, Subnautica PT Lead, Pistachionauts
@majorpain
Actually it was quake 3 who did that first iirc.
And yeah I've suggested it to the devs and so have others. It would slightly dampen the reward though with certain users no longer able to see what goods you paid for.. So it should be considered as a last resort.
Rest assured though, the Devs are working on fixing this issue as I type this. I am betting Max will be able to sort this out with ease ;-)
In their explanation as to why this was happening, I find it odd to blame it on the new player skins. How do skins cause the game to consume 7 times more memory than before the update?
Before the update I recall seeing the game consuming about 500 MB of memory. I have 16 GB of ram on Windows 8 Pro 64-bit. Now it's consuming in excess of 3 GB at the time of crash (as reported by task manager).
Animations take up a lot of the memory footprint of new models. With Reinforced, before we even put in the new donation reward skins, we had added the female marine with her own entire animation set, which is quite extensive. We also added 3 different grenade types, with their own set of first person and 3rd person animations.
We have discussed adding an option to disable the new skins, but it isn't very realistic, because we'd also have to remove grenades as well as female marines. We would also have to devote programming time to adding that option in, testing time to insure it is working properly, so we've decided it is much better to devote the time and energy into fixing the problem the right way, which is what we are doing. It might mean a few extra days of living with the crashes, but it won't be much longer now.
I still do not understand, why 32-bit is so widespread in 2013. A lot of people run around with Dual or Quad Core CPUs, at least 4 GB of memory, or even more. *hint*8GB in my rig*hint*
If I look back, then only a handful of games either have both x86 and x64 binaries or only x64.
Sure, 64bit is more like "Oh my goodness, I can allocate more than 4 GB", but think about that. Games get more and more...graphical. Such data needs more memory to be placed in.
If I look back at Hellgate: London for example...it ships with x86 and x64 binaries (depends on what version you install). DX10 was included, too.
My Fallout 3/New Vegas installations were always modded to hell, so that I needed at least 4 GB of memory just for the game. Same applies to Skyrim.
32Bit is, in my opinion, restricting development for both Games and Applications, because you are limited to 4 GB of Memory instead of 512 GB.
Yes, 512 GB sounds ridiculous, but still...that's the amount of memory, which Windows 8 Ultimate can allocate. Windows 7 Ultimate can allocate up to 192 GB.
I am not familiar with the entire technical mumbojumbo now and do not know, if a 64bit EXE for Natural Selection 2 would be a curse or would do something good...but I hope you know what I mean.
I do agree with you, but my inner geek must object with you in a few things. Windows 8 Ultimate doesn't exist... and those memory limits are actually purely artificial as well. There exists a 512 GB limit for Windows 8 Pro and Windows 8 Enterprise, and a 128 GB for Windows 8 Core and Windows 8 Single Language. The x64 architecture can address up to 16 exabytes of memory
In their explanation as to why this was happening, I find it odd to blame it on the new player skins. How do skins cause the game to consume 7 times more memory than before the update?
Before the update I recall seeing the game consuming about 500 MB of memory. I have 16 GB of ram on Windows 8 Pro 64-bit. Now it's consuming in excess of 3 GB at the time of crash (as reported by task manager).
Animations take up a lot of the memory footprint of new models. With Reinforced, before we even put in the new donation reward skins, we had added the female marine with her own entire animation set, which is quite extensive. We also added 3 different grenade types, with their own set of first person and 3rd person animations.
We have discussed adding an option to disable the new skins, but it isn't very realistic, because we'd also have to remove grenades as well as female marines. We would also have to devote programming time to adding that option in, testing time to insure it is working properly, so we've decided it is much better to devote the time and energy into fixing the problem the right way, which is what we are doing. It might mean a few extra days of living with the crashes, but it won't be much longer now.
Been unable to play since the "update" the game simply wont work without a fatal crash. This is effecting both me and my sons accounts, how close are you guys to a fix and what compensation will we receive?
Have you deactivated all mods? Did you send the crash report to UWE?
Yes and yeah off both machines Ive run it on. Shame because with over 1200hrs of game play its daft that since the update Ive been unable to get past the loading screen.
I've got crash issues as well. I noticed that every time I ALT-TAB when joining a server (during loading map & precaching), the next changemap or main menu return, the game crashes.
It doesn't happen when I do not ALT-TAB. I only ALT-TABed on the 1st loading (which is sooooo long), so I can't tell if it happens everytime.
Running NS2 on Windows7 64-bits, Full screen with DXD9.
The problem wasn't here before the Reinforced update.
In their explanation as to why this was happening, I find it odd to blame it on the new player skins. How do skins cause the game to consume 7 times more memory than before the update?
Before the update I recall seeing the game consuming about 500 MB of memory. I have 16 GB of ram on Windows 8 Pro 64-bit. Now it's consuming in excess of 3 GB at the time of crash (as reported by task manager).
Animations take up a lot of the memory footprint of new models. With Reinforced, before we even put in the new donation reward skins, we had added the female marine with her own entire animation set, which is quite extensive. We also added 3 different grenade types, with their own set of first person and 3rd person animations.
We have discussed adding an option to disable the new skins, but it isn't very realistic, because we'd also have to remove grenades as well as female marines. We would also have to devote programming time to adding that option in, testing time to insure it is working properly, so we've decided it is much better to devote the time and energy into fixing the problem the right way, which is what we are doing. It might mean a few extra days of living with the crashes, but it won't be much longer now.
I'm a bit confused by your answer, maybe you can clarify this a bit:
You basically say that the reason for the new content requiring multiple amounts of the previous memory usage is because of the new content (wasn't that the premise of the question anyway?), particularly model animations. And because disabling the extra content is "not an option" you have just decided to give it some extra days and "do it right" - but what is done right in this case? Reducing models, working on in-memory representation of some 150MB of model data, improving engine scalability...what can expect in a few extra days?
And what happened to the other issues, like the increased memory fragmentation, cases where the game runs for a while even with the memory consuming female animations. Have these issues been fixed in the previous two weeks before? (possibly in 256?)
And maybe the big question: Can we expect that the game will ever run sufficiently on the pre-253 hardware specs again?
I'm a bit confused by your answer, maybe you can clarify this a bit:
You basically say that the reason for the new content requiring multiple amounts of the previous memory usage is because of the new content (wasn't that the premise of the question anyway?), particularly model animations. And because disabling the extra content is "not an option" you have just decided to give it some extra days and "do it right" - but what is done right in this case? Reducing models, working on in-memory representation of some 150MB of model data, improving engine scalability...what can expect in a few extra days?
And what happened to the other issues, like the increased memory fragmentation, cases where the game runs for a while even with the memory consuming female animations. Have these issues been fixed in the previous two weeks before? (possibly in 256?)
And maybe the big question: Can we expect that the game will ever run sufficiently on the pre-253 hardware specs again?
I was merely clarifying that the problem goes beyond just the addition of the new skins as part of the donation reward tiers, that some people have been implying, and that it isn't as simple as just adding an option to turn off those skins. Because we'd basically have to roll back the actual gameplay content, such as hand grenades, as well, which is much more complicated and time consuming, and frustrates the majority of players who are not having these memory issues.
There were a number of things, not just with the new art (and each pretty small by themselves) that were added / changed in 252 that just tipped the game over the edge on the memory usage.
There is a whole range of different optimizations that can and are being done, most of them over my head on the technical side. There have been quite a few checkins such as "Changed the Broadphase class to use a pool allocator to reduce fragmentation" and " Reduced memory usage for storing model indices (saves about 16 MB on ns2_summit)" , so there are a lot of different ways the memory issue is being tackled, and lots of good progress is being made.
We fully intend to be able to get the game running on the pre-252/253 hardware specs, and ideally improve things so that the game runs even better then it was before.
There were a number of things, not just with the new art (and each pretty small by themselves) that were added / changed in 252 that just tipped the game over the edge on the memory usage.
There is a whole range of different optimizations that can and are being done, most of them over my head on the technical side. There have been quite a few checkins such as "Changed the Broadphase class to use a pool allocator to reduce fragmentation" and " Reduced memory usage for storing model indices (saves about 16 MB on ns2_summit)" , so there are a lot of different ways the memory issue is being tackled, and lots of good progress is being made.
We fully intend to be able to get the game running on the pre-252/253 hardware specs, and ideally improve things so that the game runs even better then it was before.
Thanks a lot for this! There's finally some beef which makes sense to me and probably a lot others with a bit of technical background.
I'm not sure if you think that such details are usually wasted in a forum post about what's going on, but imho the gist of progress posts seemed a bit shallow recently, but I definitely appreciate those details, it had a more positive effect on my picture about the development than all those "Things being fixed! Things looking good! Fixing things better!"(excuse my bluntness) reports .
IMHO anyone still using 32-bit has no right to complain. There's no reason anyone should be using XP anymore and 32-bit Windows Vista/7 is just stupid, you're crippling yourself for no reason. Seriously guys, 3 GB of RAM? You want to play games on that in 2013?
UW's obligated to support your sorry-ass computers because they said they would from the beginning but I really hope the next generation of consoles having 8 GB of RAM finally renders these 32-bit dinosaurs obsolete so we can all move on from the dark ages.
I have heard of some games having an option to display a standard skin/model for all player classes to reduce memory use. Why not implement this for ns2, since the memory crash is evidently affecting a significant portion of the user base. Or some setting which prevents textures from fully loading and keeps them in the primitive form you see when the game has just loaded.
IMHO anyone still using 32-bit has no right to complain. There's no reason anyone should be using XP anymore and 32-bit Windows Vista/7 is just stupid, you're crippling yourself for no reason. Seriously guys, 3 GB of RAM? You want to play games on that in 2013?
UW's obligated to support your sorry-ass computers because they said they would from the beginning but I really hope the next generation of consoles having 8 GB of RAM finally renders these 32-bit dinosaurs obsolete so we can all move on from the dark ages.
why would I use a 64bit operating system? You got a bunch of driver problems, especially in Windows 7 64bit (have to deal with that on a nearly daily basis, because customers think '64bit == better'). Also the game itself is only a 32bit program anyway, so it can't even use all of your shiny 16 GB overpriced memory.
The problem here is that a game uses such an amount of RAM without needing it. Seriously, take a look at openworld games or MMORPGs, you got a huge amount of models and items there and those games rarely take in more than 1.5 GB.
Because I'm sure each individual model and texture in open world games and MMORPGs has the same graphical fidelity as a model in a less broad, more focused game.
Comments
Was your face painted 50% blue when u wrote that september13 post? Epic speech lol. "WE MIGHT NOT BE BLIZZARD! BUT.. RRAAWRRR!"
Edit: not a real quote, i know.
Edit2: Name Dropper badge! fuckyeh!
Hi all,
Not sure where to post this but It is a momory error.
Windows 7 64bit 16GB RAM. SSD
ERROR MESSAGE after CRASH
"NS2 failed to allocate 25772600 bytes and will not terminate"
Please help. Happen say every 1-2 hours of play
meanwhile we have people claiming UWE is "TEH BEST DEVELOPER PERIOD!!1!" in other threads.
you people never fail to disappoint.
I was finding it amusing too, more so with some 64 bit systems having the same out of memory errors as 32 bit.
You just fail to read the thread. You read the first 2 posts and skipped to typing a message? THE GAME IS 32 BIT IT DOESN'T GIVE A F*CK WHAT BIT SYSTEM YOU HAVE. Whatever hugh said on the second post just shows how disconnected with reality some of the devs are.
http://forums.unknownworlds.com/discussion/132111/ns2-failed-to-allocate-bytes-and-will-now-terminate#latest
^^
Have a read of this thread before your next brain fart concerning me and you will see that i have been having this issue for weeks and i am not posting random comments without having some experience of it myself.
What i was refering to with my comment was the fact that some are still under the illusion that these crashes and poor performance that a lot of players are experiencing is a result of 32 bit users and 64 bit users are immune, which is simpley untrue.
Yes its been going on too long and yes i am a little p*ssed.
Before the update I recall seeing the game consuming about 500 MB of memory. I have 16 GB of ram on Windows 8 Pro 64-bit. Now it's consuming in excess of 3 GB at the time of crash (as reported by task manager).
Because originally it was just the 3 different male models : Black, Normal, Deluxe.
With the model and animations running just over 100 MB each.
Now these new models have been introduced: Assault, Elite Assault, and soon female Assault and elite assault, shadow skulk, female normal, female deluxe, female black ... that's 8 more models. 0.0
The female marine obviously does not use the same animations as the male model, either.
Actually it was quake 3 who did that first iirc.
And yeah I've suggested it to the devs and so have others. It would slightly dampen the reward though with certain users no longer able to see what goods you paid for.. So it should be considered as a last resort.
Rest assured though, the Devs are working on fixing this issue as I type this. I am betting Max will be able to sort this out with ease ;-)
We have discussed adding an option to disable the new skins, but it isn't very realistic, because we'd also have to remove grenades as well as female marines. We would also have to devote programming time to adding that option in, testing time to insure it is working properly, so we've decided it is much better to devote the time and energy into fixing the problem the right way, which is what we are doing. It might mean a few extra days of living with the crashes, but it won't be much longer now.
I do agree with you, but my inner geek must object with you in a few things. Windows 8 Ultimate doesn't exist...
I like the attitude of not doing a band-aid fix.
Yes and yeah off both machines Ive run it on. Shame because with over 1200hrs of game play its daft that since the update Ive been unable to get past the loading screen.
It doesn't happen when I do not ALT-TAB. I only ALT-TABed on the 1st loading (which is sooooo long), so I can't tell if it happens everytime.
Running NS2 on Windows7 64-bits, Full screen with DXD9.
The problem wasn't here before the Reinforced update.
You basically say that the reason for the new content requiring multiple amounts of the previous memory usage is because of the new content (wasn't that the premise of the question anyway?), particularly model animations. And because disabling the extra content is "not an option" you have just decided to give it some extra days and "do it right" - but what is done right in this case? Reducing models, working on in-memory representation of some 150MB of model data, improving engine scalability...what can expect in a few extra days?
And what happened to the other issues, like the increased memory fragmentation, cases where the game runs for a while even with the memory consuming female animations. Have these issues been fixed in the previous two weeks before? (possibly in 256?)
And maybe the big question: Can we expect that the game will ever run sufficiently on the pre-253 hardware specs again?
There were a number of things, not just with the new art (and each pretty small by themselves) that were added / changed in 252 that just tipped the game over the edge on the memory usage.
There is a whole range of different optimizations that can and are being done, most of them over my head on the technical side. There have been quite a few checkins such as "Changed the Broadphase class to use a pool allocator to reduce fragmentation" and " Reduced memory usage for storing model indices (saves about 16 MB on ns2_summit)" , so there are a lot of different ways the memory issue is being tackled, and lots of good progress is being made.
We fully intend to be able to get the game running on the pre-252/253 hardware specs, and ideally improve things so that the game runs even better then it was before.
Thanks a lot for this! There's finally some beef which makes sense to me and probably a lot others with a bit of technical background.
I'm not sure if you think that such details are usually wasted in a forum post about what's going on, but imho the gist of progress posts seemed a bit shallow recently, but I definitely appreciate those details, it had a more positive effect on my picture about the development than all those "Things being fixed! Things looking good! Fixing things better!"(excuse my bluntness) reports .
UW's obligated to support your sorry-ass computers because they said they would from the beginning but I really hope the next generation of consoles having 8 GB of RAM finally renders these 32-bit dinosaurs obsolete so we can all move on from the dark ages.
I laughed, but not as much as when it was said that 32-bit was the cause!
It is the cause? Are you even here?
why would I use a 64bit operating system? You got a bunch of driver problems, especially in Windows 7 64bit (have to deal with that on a nearly daily basis, because customers think '64bit == better'). Also the game itself is only a 32bit program anyway, so it can't even use all of your shiny 16 GB overpriced memory.
The problem here is that a game uses such an amount of RAM without needing it. Seriously, take a look at openworld games or MMORPGs, you got a huge amount of models and items there and those games rarely take in more than 1.5 GB.
Please, use some common sense.