Truthan

Hmmm. Your error states: "Proxy Server stopped working"? I'm not familiar with using a Proxy Server for internet access...but if your using one...there IS a section in the TileProxy Manual about configuring TP for use with a Proxy Server. Here'a a link to that section from the online version: http://www.edtruthan.com/tileproxy/manual.htm#26Is that any help? -Ed

From your ini it looks like you are using Service 3 yes? It simply looks like there is a noticable color difference between differing levels of detail thats all. Extending the radius of higher resolution tiles below your aircraft should do it, but which levels they are may take a few boots to figure (probably the 15-14 or the 14-13 boundary). Activating level_mapping should correct the problem. First remove the "#" sign in front of the level_mapping entry for Service 3 like shown below to ACTIVATE level mapping in TP:#level_mapping=9,10,11,12,14,14,15 change tolevel_mapping=9,10,11,12,14,14,15Now, it looks as though level "13" has already been changed to "14" in your ini (but since level mapping wasn't activated there was no effect). See if that setting extends the radius out a bit. If not some alternatives to try would be:level_mapping=9,10,11,12,14,15,15level_mapping=9,10,11,13,14,14,15level_mapping=9,10,11,14,14,14,15Depending on the speed of your machine one or another of these may slow down tile loading times a bit, but the visual results are usually worth it. -Ed

Not sure what happened but if you had re-booted the computer between TP sessions, make sure your virus Software or some other file scanning software didn't turn back on. Also if you flew for "a couple hours" your World Folder and Service Cache's may have downloaded several GB of textures. Though it's nice to have these "cached", for the sake of troubleshooting, you might want to try cleaning out all the textures in your World Folder and Service Cache's and trying TP again. Use the "Cleanup World Folder" and "Manage Service Caches" shortcuts in the TP Start menu. A simple alternative way to completely clear the Service Cache is just to delete any folders named "cache.service1", "cache.service2", etc., (If you installed to the default locations they would be at "C:\Program Files\Microsoft Games") TP just re-generates the entire folder(s) if it doesn't exist at TP boot time.Being as TP worked once (and nicely it seems), it's probably a simple fix, but I'd at least start with the above items.

Hi Ian,Here's what I usually use for FS9 and my somewhat aging rig gets reasonably good visuals and performance:preload_min_lod=9preload_max_lod=12Then under your chosen "Service Example x": min_level=9max_level=15level_mapping=9,10,11,12,14,14,15A few brief explanations:The maximum LOD (preload_max_lod) FS9 can load is 13, which is the same as the Service Example's "max_level=15" (the map service equivalent of an FS LOD is always TWO digits higher. There

gfurm,Hmmm. I guess I confused you with another person who'd emailed me from the tutorial link. I had asked him if this was his post...(as his TP error notices were similar to yours)...and he said it was. Guess not. Anyway...glad it helped Rafa to get up and rockin! I'll try to incorporate a sub-page at the tutorial addresssing the issues of the "re-install to default", "cross drive issues" troubleshooting idea. At least it helps get a user on a footing of knowing whether their problem is simply a simple install/drive glitch or something more serious. -Ed

Rafa,For you and others who've been following this thread, I wanted to mention that I was actually able to get the author of this thread, "gfurm", up and running via personal email correspondence. Though this might not solve your problem Rafa, I thought I'd post an edited version of my email to him here for those who may be having similar difficulties while using "external" drives for their cache locations. It involves a clean re-install to the default C:\ drive locations for troubleshooting purposes. Some people's problems may be more advanced of naturally, but as it helped the author of this thread with his difficulty, I thought I should post it here...The correspondence reads as thus:"My instinct is that either one of two (or both) things may be causing the problem:1. That TP doesn't (for whatever reason) like being on an "external" F:\ drive as the TP cache and "TileProxy Photoreal World" folders home or...2. That "something" went wrong with the initial installation (like external drive and the TP drivers not communicating over the drive connection). That said, I have suggested that other users who could not get TP up and going should simply do a complete uninstall and a clean re-install, and several have had great success. Why? I don't really know, but my theory is that when TP doesn't work right at first, and then downloads thousands of "corrupt" tiles at a given location, and the user continues to try and fix the problem while all the while re-booting TP in that same location, they're just spinning their wheels reloading corrupt data. Now I assume that you chose the external drive F:\ because you wanted to conserve precious drive space on the laptop (usually C:\ drive). A good way that you can test whether the problem is indeed your system simply having some unforeseen "incompatibility" with TP or that the F:\ drive problem is really the culprit is simple: Un-install the current installation and re-install using the default TP cache and "TileProxy Photoreal World" locations the installer suggests...i.e. "C:\Program Files\Microsoft Games". "This will do two things that may illuminate the problem. One, it will test if the initial installation that specified F:\ drive for the cache folders has some kind of "systematic" incompatibility with your setup (who knows why!?) , and two, if their was some "corruption" of the already downloaded data you keep trying to load by loading fresh tiles from the internet."To try the "uninstall/re-install clean" idea, proceed as follows:1. Go to: "Start>All Programs>TileProxy>Uninstall TileProxy and Data" and follow the prompts.2. Afterward, go into your FSX root folder (should be "C:\Program Files\Microsoft Games\Microsoft Flight Simulator X" and if there is still a "TileProxy" folder within it manually delete the folder. 3. Reboot4. Install a new TP Beta 8 version using all the default cache folder locations.5. Place my latest pre-configured ProxyUser.ini file (available at "Step 2"at www.edtruthan.com/tileproxy/tutorial ) for FS in the new TP root folder in "C:\Program Files\Microsoft Games\Microsoft Flight Simulator X"6. Boot TP and FSX and see if it works. (Change the map service if you wish of course)"A simple as it sounds, this entire exercise will only take a few minutes of your time and will at least narrow down whether the problem you've been having is an "external drive" issue, or a "system issue". If the latter remains true, at least you'll have a "default" C:\ drive installation with which to proceed with further troubleshooting."If a lack of C:\ drive space is an issue you can always periodically clean out the "cache.servivce.x" and "TileProxy Photoreal World" folders as you troubleshoot along to keep the file size down, which should be done ANYWAY while troubleshooting any TP difficulties so you don't end up loading any "corrupt" files over and over."Users should also be aware that during installation, the installer usually points the TP default ProxyUser.ini file it creates to: "C:\Program Files\Microsoft Games\cache.service1" because the "Microsoft Games" folder already exists in most users installations and thus requires no additional folder creation on a particular users part. My pre-configured tutorial ini file points there too. But remember! If you decide to move your cache locations AFTER INSTALLATION, and subsequently point your proxyuser.ini file to a new location, you must MANUALLY add the "parent" cache folder you point it to..(not the "cache.service1" folders, because TP will generate those upon boot...but the parent folder JUST ABOVE them). For instance, say you want to change to F:/ drive for your cache locations and you you accordingly change the respective Service Example entries to look like this:Service Example 1"cache_folder=F:\TPCache\cache.service1""...then you simply need to MANUALLY create a folder named "TP Cache" on your F:/ drive for TP to work right. Remember, you won't need to create the "cache.service1" folders, because TP will generate those upon boot."In any case I have found time and time again that a clean, (and careful) un-install followed by a clean (and careful) re-install (especially to the default C:/ locations) often works wonders. At least if you get TP to work with default cache locations you know it CAN work with your system, then all you have to do is solve the cross-drive issue if you MUST use another drive due to space considerations, fragmentation issues, etc..."-Ed Truthan

Well, the credit actually goes to Christian Buchner not me. He's the the author and designer of TileProxy and the "cbuchner1" on this forum. I'm just a "fan" who conjured up a tutorial to help new users get a leg up on TP. I mention that early in the tutorial, but some folks miss it I suppose when whisking through to get up and running. No worries though mate! Your enthusiasm has been felt by all who've had the same rush when TP cranks up for the first time...for us long tome flight simmers the feeling can only be described as like being "Born Again". Enjoy TP and thanks for the screens.-EdP.S. CB... I'll move the mention about you being the author to the head of the tutorial so folks aren't confused. I've received a few emails from folks with programming questions too...so it's likely a common mis-understanding.

If your using FS9, then you may as well set your "max_lod=" level at "max_lod=13" (4.75m/pixel) as that is the maximum resolution available in FS9. Vista sometimes exhibits a few quirks with TP, so if you're using it for the first time with the program it's recomended you disable your Vista "User Account Control" (UAC) as outlined here: http://www.petri.co.il/disable_uac_in_windows_vista.htm Also, if you wish, the FS9 version of the ini file from the tutorial is pre-configured specifically for FS9 users so if you have any other problems, you may want to try that file just for good measure. Just change the map service to your desired one and you're good to go...Good Luck and Happy Landings!-Ed

Hi Hilton,I assume you are using FSX?What I noticed is your max_lod= is set at "16" which is 60cm/pixel resolution. That's a real bandwidth clogger even if your connection is good. Try lowering it to "max_lod=15" (1.1m/pixel) or even "max_lod=14" (2.3m/pixel) and see how you fare.Also you have both "water_blending=" and "water_smoothing=" set to the "on" position. This is not recommended. The ini file clearly states:----"Recommendation: FSX users: Use water_blending=on, water_smoothing=off to get soft land/water transitions"--------"FS9 users: Use water_blending=off, water_smoothing=on to get hard land/water transitions which Tileproxy tries to match pixel-exact against coast-lines"--------"Combining water_smoothing and water_blending is discouraged. It's slow and gives weird results."----Perhaps the combination of these two factors in association with a possible connection problem have caused your "freezing".-Ed

have you tried the FSX version of the ini file available in the zip file available in "Step 2" on this page: http://edtruthan.com/tileproxy/tutorial/It should work fine. Just edit this:#source=Service Example 1#source=Service Example 2source=Service Example 3#source=Service Example 4to this:#source=Service Example 1source=Service Example 2#source=Service Example 3#source=Service Example 4That will change the ini to your desired source. This file has been working fine for most users. If the problem persists, it may lie elsewhere than the ini file. What are the symptoms of "nothing works"?-Ed Truthan

Michael,No joy yet huh? Well, I don't know if you've tried this yet, but some users wth recurrent problems such as yours have fixed them by completely uninstalling TP, (with it's "Uninstall TileProxy and Data" programs menu shortcut),then manually removing any folders the uninstaller may have left behind, and doing a CLEAN RE-INSTALL. Q: Why does this work? A: Who knows. My only theory is that it may work for some users because "something" (a TP file, etc.) was blocked or did not install properly to begin with previous to you having shut down various system processes (UAC, virus scans, etc.) It's also possible that in troubleshooting the issue something became corrupted as well. As I haven't seen from this thread that you have tried this yet, I thought I'd suggest it. I have seen several users, who, after pulling their hair out for days trying to get TP to work properly, took 10 minutes to do a clean re-install and presto! Again...WHY it works is anybody's guess, but you may wish to try it and at least eliminate it as a possible cure before spending more time troubleshooting other issues. Do the re-install with all your virus and security scanners off of course.Good luck and we'll keep an eye on this thread.-Ed

Hi all! Sorry for the long silence...we've been busy moving to another home across the state since July 1st and I've finally got my rig back up and running. Whew!I've just updated the Pre-Configured ProxyUser.ini file available at the Quick-Guide Tutorial to reflect the new map versions and Service 2's "kh*" to "khm*" URL changes. All services seem to be working fine with them. The Beta 6 ProxyUser.ini file has been updated too for those who still prefer to use that version, and I added a few minor clarifications to the tutorial text as well. Thanks to Arista for the updates too!Happy Landings to all!-Ed

Hi Alan,If you're still having troubles, try this ProxyUser.ini file: http://edtruthan.com/tileproxy/ProxyUser_Beta6.zipIt's the updated (08/17/08) version of the pre-configured Beta 6 ini from the TP Quick Guide that includes the new map versions and Service 2 URL changes from kh* to khm*-Ed(Finally got things updated there...I've been moving...)

Hi all!I'm finally back in the saddle! We've been busy moving to another home across the state since July 1st and I've just recently got my rig back up and running.I've updated the Pre-Configured ProxyUser.ini file available at the Quick-Guide Tutorial to reflect the new map versions and Service 2's "kh*" to "khm*" URL changes. All services seem to be working fine with them. The Beta 6 ProxyUser.ini file has been updated too for those who still prefer to use that version, and I added a few minor clarifications to the tutorial text as well.Happy Landings to all!-Ed

Hmmm. This is just conjecture on my part, and Christian would know more, but he's currently away on vacation:I've never personally encountered this problem, but if you haven't already found the answer, judging from the fact that you have both FS9 and FSX installed, but you seem to have put TileProxy into the FS9 root folder, my first thought was try uninstalling the program through the TP start menu uninstall link, then manually delete the TileProxy root folder from your FS9 folder (the uninstaller does not do this), then re-install the program into the FSX folder instead, rather than FS9. The TP installer wants to place TP into FSX by default in the first place so maybe have an impact on the problem. A fresh TP re-install has helped clear up a lot of varied anomalies that people experience from time to time anyway, and since it only takes a few minutes to do it's certainly worth a quick shot. My instinct is that if you have both programs installed TP prefers to dwell in the FSX root folder, even if you use FS9 alot. Again it's really just a guess on my part.If you solved your problem by this means, or another already, you may wish to post your results so other users who may have the same issue can benefit from the forum archive on the subject. Good luck and let us know how you do ay?

Well shucks Kelburn. Hmmm... A while back in this thread: http://forums.avsim.net/dcboard.php?az=sho..._id=2922&page=2TP user Bob Brown just could not get Beta 7 to work on his rig no matter what we tried. Never did find the problem. Even Christian was stumped as to why. He finally dropped back to Beta 6 (still available at: http://www.sourceforge.net/projects/tileproxy/ ) and TP fired up perfectly. I believe another user recently had to do that too. Why these particular systems balk at Beta 7 is thus far a mystery. In any case, as a troubleshooting measure to see if the problem is in fact Beta 7 or something in your system, trying Beta 6 might help clarify things. Beta 7 of course does benefit from the newly increased Tile loading speeds for Dual Core and above machines, but other than that Beta 6 has the superb global water masks and all the whistles and bells Beta 7 has in general. You can grab a pre-configured Beta 6 ini file at the link on this page: http://edtruthan.com/tileproxy/tutorial/fs9users.htm-Ed

wmayo44,Nice clip. Not sure if you were using FS9 or FSX but if you enable the 2x water in FSX the water motion and wave reflections is really stunning over the FLA Keys. I'm away from home for a day or two but maybe will record some video when I get home and post to this thread...

Sounds like heaven CB. Have a fantastic trip. I'll assist here where I can.

You can empty the Caches for each indivdual service with the Cache Manager applet in the Start Menu- All Programs- TileProxy shortcuts folder. It's a great little program with world map and tile management tools. There's also a shortcut in the TP shortcuts that clears the TP Photoresl World folder.

Actually Barry, your screens look great! Perhaps one difference is it looks like you're flying at a lower elevation, (I flew about 3800 ft. AGL) and I took my shots with the zoom level backed out a bit more, so maybe the illusion of clarity might be a bit more enhanced. I also flew at mid day so the light and color may have been a bit more vibrant. Lastly, if you took your shots "on the fly" it could be that the highest LOD level hasn't fully loaded yet. In any case, thanks for the screens! You gotta love all that blue water...

Just for good measure, you may want to clear out your Cache and Tileproxy Photoreal World folders beween boots of TP/FS to make sure no corrupted textures etc from previous attempts are being reloaded. I don't use Vista so can't advise on possible OS issues that might be effecting your attempts. I have seen black tile issues before, but the "jumbled" nature of your last screenshot is puzzling. Some users have cleared up strangly irreconcilaby issues with a clean uninstall/ reinstall of TP.... i.e. the things you have since de-actvated (UAC, Avast, etc) may have effected the install to begin with. Just shots in the dark I know, but might help ...

Funny you should ask, I added links to my FSX and FS9 screenshots and clips at the top of the "Quick Guide" main page last night...(my "personal" home main page hardly exists, never really spruced it up, I mostly use the domain as "a place to put stuff").

This post got me kinda itching for some refreshing FSX "blue water" motion so I went looking around a bit. Turns out that Map Service 1 has some utterly fantastic and very seamless coverage of the Florida Keys from about Key Largo all the way to Key West (about 100 nautical miles) with very good color balance (though perhaps just a tad bluish) and plenty of leeway for water blend_distance experimentation. The water masks work perfectly, and even (amazingly enough) most of the default FSX causways line up perfectly too! This was a great ride...Here are some screens from a flight and some notes on the ini settings used: http://edtruthan.com/tileproxy/keys/floridakeys.htm TP is just so gaawd awful cool CB...-Ed

Not sure I can help you because I'm not sure what your error represents, but since no one has replied yet to your post I thought I'd pipe in...The address in your error "C:Program FilesMicrosoft GamesFlight Simulator 9TileproxyModulesFDSConnection.dll" seems strange because although there is a "Modules" folder in FS9 by default, it is NOT in a "Tileproxy" folder therein, even if you had once installed TP in your FS9 root folder at one time rather than the default location in the FSX folder, the TP root folder does not by default contain a "Modules" folder. My FS9 root folder 9and presumably everyone's) DOES contain an "FDSConnection.dll" in this location: "C:Program FilesMicrosoft GamesFlight Simulator 9ModulesFDSConnection.dll" but there is no Tileproxy folder in the string. Hmmm...so, have you figured out your problem yet? If you DO have a TileProxy folder in your FS9 root folder you may wish to delete it and also unistall TP through the "Uninstall Tileproxy and Data" link in your Start Menu. A "TileProxy" folder may remain in your FSX folder afterwards too so delete it manually as well and start all over. Finally, I'm not sure of this, but judging by the error, if the TP installer needs to modify your FS9 "FDSConnection.dll" in the FS9 "Modules" folder, and since that was the object of the error, you may wish to make sure that this file is not set as a "Read Only" file because it could not therefore be modified, etc. (Right click on file and select "Properties" to check.) Admittedly, I'm in the dark here. Anyone else seen this?Lastly if you wish to try BETA 6, a Beta 6 pre-configured ProxyUser.ini file is always available in the Quick Guide for users that have less trouble with that version. See this page: http://edtruthan.com/tileproxy/tutorial/fs9users.htm

Hi Mike,I'm not sure how to monitor the the map service changes directly, (CB should know...?)but I did notice that in the the recent March 21st, 2008 release of TP: Service Example 1 is now up to "map_version=117", Service Example 2 is now up to"map_version=25". Aside from these two changes the ProxyUser.ini does not appear to have been altered from the March 12th, 2008 versions.-Ed