| Quote (Bob Crane @ May 22 2005,10:04) |
| I have been getting the same erratic crash results on my new desktop where I upgraded topofusion. For the first few days it shut down every few minutes, now after a few months it shuts down much less frequently(however I have been doing most of my topofusion work lately on my laptop which I decided not to upgrade to the new 2.5 topofusion) Let me know when you figure it out, by the way, topofusion is still the best program I have used for getting quick maps and editing them without much hassle. THANK YOU VERY MUCH, keep up the good work. bob |
| Quote (Bob Crane @ May 23 2005,6:48) |
| Yes, it just disappears without any notice. Really makes you get serious about saving your files often. |
I've recently had some 'poofing' for no apparent reason - - until I remembered that I had gradually been increasing the cashe settings, and the memory use settings. I set all of these way back and the poofing stopped. Then I started increasing them again without problems until...
I increased my RAM from .75 gb to 1.5 gb. Since TopoFusion uses a percentage of RAM to set the memory use values, these numbers increased a lot. Apparently something (XP SP2 or who knows what) could not use all that dedicated RAM, and I got a poof every time I tried to run TopoFusion. I backed the setttings down, and everything is fine again.
By the way Krein, it would be great to know more about the end effect of these settings? For example, for normal use, is their an upper limit beyond which you won't see any difference. Say on the 3D settings. At least that way I could crank up only the settings that really make a difference.
LarryQuote
reported in another thread.
TC
| Quote (tdcarter @ June 10 2005,11:49) |
Quote I've recently had some 'poofing' for no apparent reason - - until I remembered that I had gradually been increasing the cashe settings, and the memory use settings. I set all of these way back and the poofing stopped. Then I started increasing them again without problems until... |
| 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 |