Sensible advice, but alas I have a 32 bit system and anything above 3 GB RAM goes unnoticed under Windows.
Yet I have always suspected that memory was the culprit. I had some .NET issues which I resolved by reinstalling Windows and the game, but I'm not sure a repeat performance will solve this new problem.
Neverdarklands update
Débuté par
Dementia5
, oct. 26 2010 12:28
Retour en haut
#52
Posté 28 novembre 2010 - 05:48
Anotherone773
-
- Members
- 24 messages
actually its 3.5 GB. 32 bit can use 4GB but .5 GB is reserved for system only use.
When i first got NWN2 and tried to use the toolset. i was frustrated after about 3-4 minutes. I was running an AMD athelon x2 and 2 GB of ram. The lag was terrible. I never touched it again until i got my new pc. Now it works decently besides all the bugs. I ran Vista too. Vista is a terrible OS for doing anything on. XP or Win7 is better.
Besides your OS and RAM, the rest of your system should be able to handle it. Your video card is better than mine despite being 2 years older. Mine has double the memory but yours is faster has a higher bandwidth and better fill rates. A duel core should handle the processing. Though once you get up to 100 MB files it may struggle a bit.
I dont think a reinstall will help. I would just try to maximize the use of the PC memory. I would also try setting the render to the lowest you can get away working with. It may require some going in game to see how it looks but if your pretty familar with NWN2 you can usually guess it close enough. I have went as low as 240x160 on rendering.
When i first got NWN2 and tried to use the toolset. i was frustrated after about 3-4 minutes. I was running an AMD athelon x2 and 2 GB of ram. The lag was terrible. I never touched it again until i got my new pc. Now it works decently besides all the bugs. I ran Vista too. Vista is a terrible OS for doing anything on. XP or Win7 is better.
Besides your OS and RAM, the rest of your system should be able to handle it. Your video card is better than mine despite being 2 years older. Mine has double the memory but yours is faster has a higher bandwidth and better fill rates. A duel core should handle the processing. Though once you get up to 100 MB files it may struggle a bit.
I dont think a reinstall will help. I would just try to maximize the use of the PC memory. I would also try setting the render to the lowest you can get away working with. It may require some going in game to see how it looks but if your pretty familar with NWN2 you can usually guess it close enough. I have went as low as 240x160 on rendering.
#53
Posté 28 novembre 2010 - 05:52
dunniteowl
-
- Members
- 1 559 messages
I run 2GB RAM on XP SP3, with a PCIe X1650 Pro w/512M DDR2, 2.6GHz AMD 64 FX2 dual core and I have never had crashes like you describe. And when I do have troubles, it has turned out to be my power supply or a hard drive going south on me. I leave my resolution at 1280X1024, or 1168X960 or so. Lowest resolution I have used is 1024x768 (pardon if the numbers are slightly off, I am going off memory in my head and not fact checking.)
dno
dno
#54
Posté 30 novembre 2010 - 01:15
Dementia5
-
- Members
- 40 messages
Dropped the resolution to 240x160, still cannot "resave" the module. Sigh.
#55
Posté 30 novembre 2010 - 03:55
c i p h e r
-
- Members
- 261 messages
If you're not already doing so, try working in directory mode. That should eliminate quite a bit of overhead in packing everything into your module file.
Another possibility might be disk space. Could you be running out? A lot of applications use the C drive as a staging area. I haven't paid much attention to the toolset's usage but chances are that it uses your C drive too.
Also, something I noticed on my machine was that free space was mysteriously disappearing over time even though I wasn't installing anything. With the help of this really neat drive mapping tool, I figured out where it was all going: anti virus memory dumps. Who knew. So now I run regular scans with CCleaner to clean up my drives and keep them pruned of all the enormous amounts of useless crap just lying around. It's shocking, really.
They just don't code them like they used to!
Another possibility might be disk space. Could you be running out? A lot of applications use the C drive as a staging area. I haven't paid much attention to the toolset's usage but chances are that it uses your C drive too.
Also, something I noticed on my machine was that free space was mysteriously disappearing over time even though I wasn't installing anything. With the help of this really neat drive mapping tool, I figured out where it was all going: anti virus memory dumps. Who knew. So now I run regular scans with CCleaner to clean up my drives and keep them pruned of all the enormous amounts of useless crap just lying around. It's shocking, really.
They just don't code them like they used to!
Modifié par ç i p h é r, 30 novembre 2010 - 03:57 .
#56
Posté 30 novembre 2010 - 04:49
Dementia5
-
- Members
- 40 messages
Thank-you, çiphér , I think that did the trick. I will test the different areas tomorrow, as it is late. I am less familiar with the contents of this save directory; I hope that I can just backup the whole directory between saves and plop it back into my NWN modules directory when the Toolset crashes again... it will happen, you know.
#57
Posté 01 décembre 2010 - 01:07
c i p h e r
-
- Members
- 261 messages
It's all rather neat and simple. The contents of the save directory are the same contents that go into the module file. Only, they're in a directory and can be directly accessed - or manipulated - by you.
This means you can add files to your module, remove them, copy them elsewhere, archive them (zip, rar, 7z, etc), edit them with other packages, and so on all directly from the folder itself. But just be careful you don't modify files at the same time the toolset is using them. That would probably result in very unexpected behavior.
If I modify anything in the folder, I always restart the toolset so that it can reload the correct "state" of things. The last thing I want to do is run the toolset off the rails - it can do really bad things.
Anyway, have fun and good luck with your project.
This means you can add files to your module, remove them, copy them elsewhere, archive them (zip, rar, 7z, etc), edit them with other packages, and so on all directly from the folder itself. But just be careful you don't modify files at the same time the toolset is using them. That would probably result in very unexpected behavior.
If I modify anything in the folder, I always restart the toolset so that it can reload the correct "state" of things. The last thing I want to do is run the toolset off the rails - it can do really bad things.
Anyway, have fun and good luck with your project.
