Building Cities in YATT

indio · Post by **indio** » Tue Dec 11, 2007 3:15 am

http://www.thesilvermarches.net/uploads ... index.html

Best way to help is to try and follow it and report its shortcomings. Will update as we go.

Thangorn · Post by **Thangorn** » Wed Dec 12, 2007 11:01 am

I can't update my area with new textures once I have placeables in, it crashes my toolset and corrupts my area.. looks like I need to height & position lock all my placeables, make a new area with YATT and cut/paste the placeables in.

lost all the work I did on my Phlan area last night trusting folder mode too much to keep things on an even keel.. another few hours work down the toilet once again :/

indio · Post by **indio** » Wed Dec 12, 2007 11:23 am

Blast.

It works ok for me, so maybe it was a memory issue.

Thangorn · Post by **Thangorn** » Wed Dec 12, 2007 11:31 am

how much memory do you have?

I duplicated the effects quite a few times using the same process..

Seems to me whenever I mess with large TRNs or if I am adding a large amount of placeables soon after a large TRN modification (Terracoppa, YATT, etc.) is when I get my crash. If I'm in Mod mode it corrupts my entire module, if i'm in folder mode, it corrupts the area I am working with..

I've got my puter running on one core in the toolset now and it hasnt seemed to make a difference. I'm wondering whether my vast amount of UEs come from a lack of memory when dealing with large amounts of placeables and big TRN modifications.

I dont suppose you or anyone else can shed some light? I'd like to find a solution as I find these crashes extremely demotivational..

indio · Post by **indio** » Wed Dec 12, 2007 11:44 am

2GB using WinXP.

Google "Cacheman" and run it, and every time you've performed a major task and are about to perform a new one, right click on the taskbar icon and select "Recover Memory Now".

I find crashes are almost exclusively memory related. The CPU dual core issue has never bothered me, but I'm using Core2Duo's now, not AMD X64's.

I've actually got a spare box which sits around not doing much at all...Core2Duo and one I used to do all my building on. If you're interested we could arrange to transport it.

Thangorn · Post by **Thangorn** » Wed Dec 12, 2007 1:25 pm

yeah I have 2Gb and a core2duo e6600. so I guess my crashes arent memory and proc speed related then if you arent experiencing the same thing. Any special system settings you use I need to know about?

indio · Post by **indio** » Wed Dec 12, 2007 5:51 pm

I've used separate partitons for the program and module save locations, and a third for OS files.

I defrag each of these partitions each night.

Cacheman, as mentioned above.

But I haven't crashed on my desktop computer since MotB was installed. The only place I crash is on my laptop, where I've got 2GB of memory, but it allocates that memory more suggishly. If I've got fewer than 500MB of memory available when I start a YATT area update, YATT crashes. If I've got around 300MB availabe and I try to open a new area, bake an area, or perform a major copy/paste job, NWN2 crashes.

AcadiusLost · Post by **AcadiusLost** » Wed Dec 12, 2007 7:02 pm

Just as an outside question, have you tried running tests on your RAM? If one of the sticks has some dodgy bits, maybe they're mucking up the works. You can also try scaling back the timing or clock cycles to the RAM if you're suspicious of it causing problems.s

Thangorn · Post by **Thangorn** » Wed Dec 12, 2007 9:51 pm

I never run out of RAM, according to cacheman I've still got more than 1100Mb to play with before I start YATT and it never goes much beyond that but I can duplicate the crash everytime just by trying to update the terrain and textures with YATT in an area that already contains placeables and water.

the crash happens in the NW2ToolsetRenderer. Any other ideas?

indio · Post by **indio** » Wed Dec 12, 2007 9:58 pm

Water...try removing it. Erase it all.

The placeables should not be an issue....I'm not certain, but I've never had a problem rebuilding a heightmap with placeables before.

Otherwise, if it's not ram or water, there's hard drive install corruption, or more likely, drivers, especially video.

But don't lose heart...seriously, I will work with you till this one is solved.

HEEGZ · Post by **HEEGZ** » Thu Dec 13, 2007 12:14 am

This is partly why I gave up over the summer. I've got a dual core w/ 2GB of RAM as well. Even with all but essential processes running I would still crash or otherwise be unable to save my work. I've got MotB arriving in the mail in a few days and I'm gonna try it out again and hope for the best. At the time I am pretty sure I had the latest or even beta drivers but I think they're out of date atm. Anyways, looking forward to giving this another shot.

Nate

indio · Post by **indio** » Thu Dec 13, 2007 12:47 am

New version, new address:

http://www.thesilvermarches.net/ALFA/al ... index.html

Thangorn · Post by **Thangorn** » Thu Dec 13, 2007 2:01 am

Thanks Indio. Just so you know, I'm nowhere near about to stop building..

I was not even going to say anything this time as it doesnt help bring builders in bitching about problems with the toolset. However, I decided to take a proactive approach that may well help avoid new builders get disheartened by crashes and try and get together a list of possible things people can do to avoid crashing..

Water removed.. same crash in the NW2toolsetrenderer

I'm sorry to mess with your thread mate, I just thought it was pertinent to the YATT city building situation is all..

indio · Post by **indio** » Thu Dec 13, 2007 2:32 am

Can't reproduce the problem this end.

I put the textures in place, and a new heightmap, I select the area to be updated, and click update. It does what it usually does and finishes. The area has about 200 placeables in it.

When else do errors either in YATT or the toolset occur for you?

indio · Post by **indio** » Thu Dec 13, 2007 2:35 am

Have you got a series 8 nVidia graphics card?