/-/S'pht-Translator-Active/-/ |
Re: Massive memory leak in Forge using Classic | ||
Posted By: treellama | Date: 8/2/06 8:46 a.m. | |
In Response To: Re: Massive memory leak in Forge using Classic (Aaron Sikes) : I get serious screen lag, jumpy views in visual mode, and crashes, crashes,
Not sure where you get that impression. It can certainly handle longer view distances than Forge can, and instead of crashing when you use a lot of transparent lines, just gets really slow. But, "any length of view?" Not at all :) Forge will definitely crash if you put too many transparent lines in, one way around it is to partition your map into pieces (either build thin dividers between the parts, or mark the lines dividing them solid, non-transparent, and empty), texture each partition, then fill the dividers / mark the lines transparent and non-solid, when you're done with visual mode. Or you could use Pfhorge, which, while a bit more buggy than Forge, can handle greater view distances and more transparent lines than Forge can. That said, ask yourself, "Do I really need this many polygons / that long a view distance?" 99% of the time, no, you don't. There are many tricks, most involve adding negative space, that you can do to make things work smoothly in Forge, and will keep your map useful on lower end machines (which there are still quite a number of)
|
|
Replies: |
|
Problems? Suggestions? Comments? Email maintainer@bungie.org Marathon's Story Forum is maintained with WebBBS 5.12. |