Server Help :: View topic - LVZ Builder eating up system resources?

Server Help

LVZ/LVL Questions - LVZ Builder eating up system resources?

Anonymous - Sat Feb 07, 2004 6:04 pm
Post subject: LVZ Builder eating up system resources?

When i choose my .ini file to create my background in the buildlevel.exe, it not only doesn't create the LVZ, it begins eating up system resources - generally about 95% of all available ram..

=/

Whats going on, any ideas?

Cyan~Fire - Sat Feb 07, 2004 6:30 pm
Post subject:

Post your INI here. I'm sure there's a problem in it somewhere.

Anonymous - Sun Feb 08, 2004 1:16 pm
Post subject:

Heres the ini:

outfile=background.lvz

file=background.jpg

[objectimages]
image0=background.jpg

[mapobjects]
0,0,IMAGE0,AfterBackground
0,114,IMAGE0,AfterBackground
0,228,IMAGE0,AfterBackground
0,342,IMAGE0,AfterBackground
0,456,IMAGE0,AfterBackground
etc.

Ini attached as .zip

SuSE - Sun Feb 08, 2004 4:33 pm
Post subject:

takes a hell of a long time

what did you assemble the .ini code in?

Mine GO BOOM - Sun Feb 08, 2004 6:04 pm
Post subject:

Only took 10 seconds to make here (2500+ Barton), not too much ram. But, still, any client trying to enter your zone without a good processor/video card would die. I'd recommend not having a background image, or atleast one so massively global.

Stats from debuildlevel:

Quote:

; Object Information Compression Info:
; FullSize: 207393 Compressed Size: 49821 Compression Percent: 76.0%

Anonymous - Sun Feb 08, 2004 6:23 pm
Post subject: ?!

I didn't follow any of that -- I used notepad to "assemble" the ini -- here's my background image that gets tiled though..

its only 10k, i can't imagine the filesize is collosal

WarFan - Sun Feb 08, 2004 6:53 pm
Post subject:

The ini is huge because your background image is so small. Ive enlarged your background to 500x500 (duplicating your original on a larger canvas), attached the ini and the image. Not sure if this will help you but try building this one.. took about 1 second to build on this pc.

Anonymous - Mon Mar 29, 2004 12:57 pm
Post subject:

Late reply, sorry.

Worked perfectly, and that was indeed the problem. Good call