Quote (tdcarter @ June 11 2005,12:19) |
Scott, Alan, and the rest of the gang....
Okay. I'm thinking Larry's post is either different, or much more involved then my non PA mind can handle.
I can play back tracks fine if I disable tile downloading. But I turn it on... and *poof's* start happening at random. They do seem to happen in patterns. One day, I can't play back a track for more then a few minutes without a blow-out. So I finally give up. next day, I play it back and download all the tiles just beautifully.
So with my limited knowledge of code (as I'm a sys-admin), I'm assuming it has to be something in the download. Something is timing out badly.
Here is a proposal. I can send you some tracks of mine that I've had trouble playing. Maybe when you play them back it'll recreate the problem. Thus narrowing it down to the data of the tilesets I'm downloading or the servers database of them.
Or.... if the problem is in my connection or hardware (what??? a sys-admin problem, never..)
Why not custom compile a debug version of TF. Insert a loop that writes out a log of each and every time a tile is requested, the ack's received, and any other data necessary. Yeah, It'll slow me down, but in the interest of solving this problem, I'm game.
On a similar note, I recently played back a track that covered old data I know I already downloaded. But... it re-downloaded the data again and constantly crashed. I was using the .25m urban tileset.
So did it really need to get the data again? Was it redundant? How are you checking for old/outdated tilesets? Was it crashing for no reason? In my maps directory I have a 640m file that was map1 and should have already contained the tiles of the urban data for that area. But now it was making a maps2 file and re-downloading the data. Is that within defined parameters?
TC
PS If you want to contact direct, get more info and take this post momentarily offline, let me know at tc.carter at charter.net |
Hi,
Try cranking your 'tile cache size' setting down all the way, then see if you can still get it to go poof on you. That's all Larry's fix entails.
It could be a matter of how much available memory you have when you start TopoFusion up. If the problem is a memory cache that's too large then it should go poof more often if you start it without other programs loaded.
But it could be a download problem, as you're saying. I agree that making a debug version for you to try is the next step. Glad you're up for testing it out for us.
Are you 100% sure you already had those maps and that it didn't crash sometime before those tiles got written out? The starting of a new maps file is suppose to happen at 640mb in case folks want to burn them to CDs (we had to cap them at 2 gig anyway). It might be that there is something screwy in the mapindex file, though. Another thing to try is to changing your map directory (starting fresh) temporarily to see if it still poofs.
Go ahead and send me your files for me to playback if none of this helps.
Thanks