Hi,
You may have heard rumors that a fixmore3.pod is on the drawing board, and this is a short note to let you know it's true. The primary focus for this update will be performance issues. Malibu350 and I have been gathering a list of common 256x256 texture names that are used in places where 64x64 textures will do perfectly well. The goal, then, is to remove as many large textures from memory as possible, potentially up to a dozen in a race, and so cut down on in-game chugging. Well, ideally, that's the plan.
Secondly, and this is where you can help, new models sometimes appear in tracks that shine through the terrain. We've all seen this. The most recent example would be the sign in Desert1 by Yves_B which doesn't look like it'll be updated, so it's a good candidate for the fixmore pod. Another is the mtm1 track called Jump which has a couple problem models not yet covered by previous fixes.
How can you help? Easy, if you've noticed, discovered or found texture or model oddities in your game (billboards with wrong web addresses?), let us know so we can look into the cause, and maybe fix it. Not everything is fixable, but a lot of things are. For example, wk mentions
Quote:
I assume SMPHOTL4.BIN version is an unchanged version of the original mtm1 bin. [fix-it pod alert]
http://forum.mtm2.com/viewtopic.php?p=15071#15071
While I still have to find out which model exactly he's referring to, you don't have to be so precise. Just say the track and the problem, and we'll see about hunting it down. If it's fixable, we'll do it. If it's not, we'll let you know the reason why.
Thanks for the tips, if you have any.