49 réponses à ce sujet

[PJ156]

I know that others have had difficulties with opening specific large areas but I am seeing a steadily increasing problem with opeing two areas at once. The second area opening almost always crashes to the toolset regardless of the area sizes? Any one else seeing this?

Does anyone think a reinstall of the toolset might help. I don't see how it would but I would do it if I though it would make a difference.

PJ

[andysks]

Hi there Peter. My toolset crashes as well, not always, but it does. When I want to open two areas, if one is heavy it could crash. Even if the heavy is already open, and I try to open a light one it might crash. When I say heavy, it can be light heavy, or vfx heavy... not only big. Also, sometimes it might crash if I have this open, photoshop, a live stream of league of legends on the internet, and my girlfriend's account on the PC has also a couple programs running. It seems the toolset will always take priority of crushing when the PC in general is overworked.

[Morbane]

it might be mechanical - when is the last time you had your pc dusted out? also video card fans do wear out - if they get too dusty and you air them out, the fan can go blokko - same for the power supply - just a shot in the dark, but i mentioned this possibility anyway.

[kevL]

parse resources: override, haks, wherever the TS finds a resource it grabs it and hangs on, till closed.

If i'm feeing unlucky i'll even close the toolset and restart it before moving on to a second area (older computer tho)

[Tchos]

Yeah, for me, it seems to be a memory problem that causes the crashes on opening areas. Not sure about it, but that's what it feels like intuitively since it gradually happens more and more the larger the areas get. Smaller areas like shop interiors can open several at once without trouble, but once I open a large area it generally means I'll have to restart the toolset afterward, because even after I close the large areas it'll crash once I try opening something else, even if it's small.

[tropetyper]

I know I have had this problem on and off, and right now more on than off.
My computer is however a dino and soon to be replaced.

But for a while, one of the things that helped was to make the module itself a directory.
I am not sure if you've already done that or not, but it did seem to help...

For a while.

[rjshae]

My new gaming PC has an absurd 24 Gb of RAM and the NWN2 directory is installed on an SSD drive. Alas, the toolset still crashes on a big area. Plus, with this abominable Windows 8, changes such as tinting don't always show up until I reload the area. (Or is that a problem with the graphics card?) Sigh. At least the toolset starts somewhat faster now.

[-Semper-]

the toolset is still a 32bit application and can't utilize more than 4gb of ram.
@win8: why don't you just install win7 or xp on another partition?

[rjshae]

-Semper- wrote...

the toolset is still a 32bit application and can't utilize more than 4gb of ram.
@win8: why don't you just install win7 or xp on another partition?

Right, but with >4Gb of RAM it should no longer need to share a memory squeeze with numerous other apps. At least in theory.

[kevL]

it might (i'm no hardware genius) be able to address *only* the *first* ~4gb RAM (test: if those first 4gb are consumed by other apps it won't start at all)

to the pt: I'm using a 32-bit system (XP) and run a very clean ship, yet can run into problems with ~3.5gb free (~0.5 taken by videocard). And, like tropeT noted above, I've also been able to open large dir-mode modules when the .mod-mode modules crashed (yeah Tani's unpacker!)

I think whatever vRAM your vidcard has, is also reserved by motherboard RAM. So bigger videocards consume more RAM..

[rjshae]

A good OS would use memory mapping, so the app. thinks it is loaded in the first 32 Gb of RAM regardless of where it is located. But this being windows...

[Claudius33]

I am running W7/64 bits and have 8Gb RAM,  an overpowered CPU (8 cores) but with an obsolete graphic card (nvidia GTX 260). 

I have experienced very few issues with the toolset. I often open 2 exterior areas and a couple of interior areas. It is quite convenient as you can copy paste creatures, placeables, environments props from one area to the other. Especially if you have two supoosedly close areas and want that one area background looks like its facing area background.

I also often swicth from one module to the other to do some copy/paste.

Do you guys run all NWN2 executables including the toolset in Windows XP SP2 compatibility mode?

Note : I usually run the toolset (not the game) in admin mode.

Modifié par Claudius33, 03 février 2014 - 09:48 .

[kevL]

@rj
donno. But i've become very 'memory' conscious when using the TS and haven't crashed recently.

Modifié par kevL, 03 février 2014 - 07:45 .

[rjshae]

Claudius33 wrote...

Do you guys run all NWN2 executables including the toolset in Windows XP SP2 compatibility mode?

I pretty much have to at this point.

[-Semper-]

Claudius33 wrote...

Do you guys run all NWN2 executables including the toolset in Windows XP SP2 compatibility mode?
Note : I usually run the toolset (not the game) in admin mode.

yeah, plus i use another small program called "4gb patch" to patch the .exec to use all the available x86 memory space. dunno if it's just shenanigan, but imo it runs way more stable afterwards.

[Claudius33]

Didn't know the "4gb patch", looks very interesting.

[kamal_]

My Path of Evil building pc had 2 ggs of ram and XP, it would crash the toolset if I opened three different external areas without restarting the toolset.

My Crimmor building pc has 8 gigs of ram and Win7. Never crashed the toolset.

[PJ156]

Thanks for all the replys gents, I have 4 GB (actually the system infor says 3.25?) and XP with SP3. I often get the message from Norton that the toolset is using to much processor resource so i guess this is that issue. It's odd that is has become progressivly worse but perhaps that's down to the complexity of may areas.

It's a pain but it's not gonna stop me

PJ

[kamal_]

PJ156 wrote...

Thanks for all the replys gents, I have 4 GB (actually the system infor says 3.25?) and XP with SP3.

You have 32 bit windows, it can't make the whole 4 GB available even though you physically have it.

[kevL]

i bet the vidcard is 750mb - Ram needs to reserve equal vRam...

[kamal_]

Turns out it's a bunch of things: http://en.wikipedia....ki/3_GB_barrier

[Morbane]

PJ156 wrote...

It's odd that is has become progressivly worse but perhaps that's down to the complexity of may areas.

PJ

maybe possibly a reinstall will solve that issue - since it is progressive, the liklihood of a reinstall might "reset" your memory payload?

[Morbane]

-Semper- wrote...

yeah, plus i use another small program called "4gb patch" to patch the .exec to use all the available x86 memory space. dunno if it's just shenanigan, but imo it runs way more stable afterwards.

gonna try it - once i upgrade to 4 gig ram

on that note im on a win7, x86, GT 630, 2 gig ram - i frequently open more than one area, but truthfully my areas are generally not huge.

[PJ156]

Thanks again, seems I am stuck with the way things are without getting a new PC. I will check the MB to see if that is 64 bit. If it is I could go to win7? But I guess if I have a 32 bit OS the processor must match?

PJ