Skip to content
View in the app

A better way to browse. Learn more.

The AVSIM Community

A full-screen app on your home screen with push notifications, badges and more.

To install this app on iOS and iPadOS
  1. Tap the Share icon in Safari
  2. Scroll the menu and tap Add to Home Screen.
  3. Tap Add in the top-right corner.
To install this app on Android
  1. Tap the 3-dot menu (⋮) in the top-right corner of the browser.
  2. Tap Add to Home screen or Install app.
  3. Confirm by tapping Install.

lliaudais

Members
  • Joined

  • Last visited

Everything posted by lliaudais

  1. Windows startup menu: disable driver signing enforcement by using the Windows Boot menu - accessed by pressing F8 (?) as Windows begins to boot.... I press just as the "load from CD?" message fades. But then I have the boot process displayed by enabling in BIOS so I can see the point where Windows starts to boot....otherwise press F8 every few moments during boot up until the menu is shown. Loyd
  2. Not entirely true.... no accesses means what you said... there are no textures for FSX to accessor it can be this...when I run FSX BEFORE TP, all textures are built as per normal and there are still only default textures showing because TP was not 'connected' into the scenery system in time to be referenced. You also will also get "0" accesses under this condition - I built a lot of scenery this way because the cpu load was significantly less... But I agree, in this W7 environment, this situation is most usually the driver not actually making the tiles yet... Loyd
  3. snap in VC? yesedit cameras.cfg [CameraDefinition.002]Title = Virtual Cockpit.SnapPbhAdjust = SwivelSnapPbhReturn = False edit to same as 2D mode SnapPbhAdjust = OrdinalSnapPbhReturn = True this is NOT the cameras.cfg that is in the FSX folder but in the folder with the FSX.cfg Loyd
  4. Binaonly default textures when TP appears to be working?. 1. Driver running (you think ok) in Win7..2. Is TP started BEFORE FSX?3. are TP regions enabled in scenery.cfg at higher priority than default ?4. Tiles... for KMTH - end of rwy 7: the 1m/level 17 image tile (your cache folder\870\tile_l17_x36023_y74830.jpg)and a 1.3M (1.2m res) scenery tile "your TP photoreal world folder\0302\003123201320212SU.BMP" note: on the "SU" part of the tile name... this will vary with the season you fly in - so always search for files with the season optionalWindows search for 003123201320212??.BMP or 003123201320212*.BMP so it will find any seasonal variation created. If you have the SDK installed, you can view the bmp using the provided image viewer. If not, you may be able to use one of the viewer tools used by folks who do repaints. You cannot use standard image viewers since the scenery tile is multi LOD. regrettably, I do not have TP installed on my current Win7 system; I only have "tools" that allow me to see what the image tiles and scenery tiles should be at a given location. Loyd
  5. I can't comment on the Innsbruck issue but I looked at the bmp tiles in a FS9 download, and they are LOD13/level15/4.8m resolution. They may well have been made from the same source imagery as the 2.2m scenery for FSX instead of a 4.8/5m source. Loyd
  6. If it appears to be running, then you SHOULD have some jpg files (lots) added into your cache folder. These images are distributed between 1000 subfolders (000-999). These subfolders are not created until needed for the first time, so look into one of them and see if you see image tiles of the .jpg 'persuasion'. If you don't have any of these numbered subfolders, then you won't have any images yet, nor will you have any scenery visible. Did you download the functional ini file from Ed's website? Loyd
  7. To the best of my recollection, the Upper Left info CANNOT be changed; the others can be changed (in the fsx.cfg) - and I have done so. Loyd
  8. One folder 'down' from the fsx.cfg file is \Controls\standard.xml - you can open with notepad. Just right-click and select 'edit'.Save frequently to keep your changes. Loyd
  9. I guess you should post your proxyuser.ini and let's see if there's anything wrong... The easiest way to check results is to be at some very specific place so I can tell you what image names to expect and what scenery tiles names and sizes to expect. To that end, save a flight at KFCA as a default flight. Start TP (at 2.4m or better resolution) and FSX. By time the scenery loading is complete, you should have all the necessary images and scenery done. look for newly saved image tiles in your cache:cache\824\tile_l16_x11968_y42840.jpgcache\825\tile_l16_x11969_y42840.jpgcache\826\tile_l16_x11970_y42840.jpgcache\823\tile_l16_x11968_y42839.jpgcache\824\tile_l16_x11969_y42839.jpgcache\825\tile_l16_x11970_y42839.jpgcache\822\tile_l16_x11968_y42838.jpgcache\823\tile_l16_x11969_y42838.jpgcache\824\tile_l16_x11970_y42838.jpgThe scenery tile made from these and nearby images should in the TileProxy Photoreal World scenery 0201 subfolder and named 001222132021020SU.BMP and be 340k or larger in size. Scenery tiles are muli-LOD and can only be viewed with appropriate viewers -such as the one provided in the SDK. Loyd
  10. Jet, I don't know about a "stock" beacon called "FX_padbeaconh" - I certainly don't have one in my effects folder but... When I look at the contents of the fx_strobeh (which is a 2-pulse strobe light, for example), I see 4 blocks of code containing Emitter/Particle/ParticleAttributes sections. The first two specify no delay, the second 2 specify a delay[Emitter.0]Lifetime=0.00, 0.00Delay=0.00, 0.00[Emitter.1]Lifetime=0.00, 0.00Delay=0.00, 0.00[Emitter.2]Lifetime=0.00, 0.00Delay=0.20, 0.20[Emitter.3]Lifetime=0.00, 0.00Delay=0.20, 0.20I think if you remove the .2, .3 sections (all 3 blocks in each section), you will remove the second flash. Loyd
  11. What OS? XP, Vista, Win7What Sim? FS9, FSX? Are you getting any error message in the DOS window at startup to suggest that TP is not running properly? FS9 has occasional issues with black tiles. I never got it to work with FS9 but there are some older posts containing suggestions for dealing with that issue. Windows 7 has it's own issues with not allowing the TP driver to run because it is an unsigned driver and blocked from running. There are several posts over the previous months also dealing with this issue. I had no issues with XP (32bit) and FSX (SP1)I have not reinstalled on my Win7+Acceleration installation. Black tiles might have been created when you originally started with the first .ini. If you go to the same location with a new .ini file, new scenery should have been created. You probably should look first in the active cache folder with Windows search feature and see if you are actually downloading new image tiles when you start up your sim. If not, then no scenery can be made. Loyd
  12. first, make sure the Global Texture resolution didn't get set to a lower valueSecondly... I got unsharp ground on install until I remembered the mipbias setting in the video.device section of the fsx.cfg. you might also accomplish the same thing in your video card settings - I couldn't, so the manual entry took care of it; I was using the 4850 at the time.Loyd
  13. That's the only file of that name on my installation so that's probably what it's looking for...With Win7, you probably will have more luck if you TURN OFF that !#$%^*%&*@@ UAC, then install as Administrator. If you install FSX into program files (default) and have UAC on, your life will be an everlasting misery...Loyd
  14. I noticed that on occasion, when I moved too far while TP was running, it didn't make the transition with me...Since TP begins loading based on the default flight location before actually starting a flight, I got in the habit of going to the new location (without TP) and saving a flight there and making it the default so TP would start there and not in Friday Harbor or wherever my previous default was.Loyd
  15. FSX rain....Go back to the galley and make me some coffee while it's raining. You can still listen to it but you won't have to watch it :( .Loyd
  16. SP2 "hides" the default installation, as it (the default install "FSX") no longer exists. Uninstalling SP2 will restore the FSX to its PREVIOUS version.I installed SP2 also before Acceleration and had to uninstall it before Acceleration could be installed. It did NOT remove FSX itself.Loyd
  17. somehow....?A. use the effects tool from the SDK... that's what it's for. copy fx_smoke_w (white) as fx_smoke_g (green) and edit that file's colors to the shade of green you want-OR-B. Effects files are just text. open fx_smoke_w in notepad, save as fx_smoke_g, then edit the colors to your satisfaction.Reference the desired new smoke color in the aircraft.cfg and you have it. There have been one or more tutorials posted in years gone by on how to do this in detail... one might have been called "Playing with Smoke" or some such...-OR-Easiest....C. look for add-on files that already provide such alternate colors for the Extra or other aircraft. Yes, those have been posted previously also. Once you install those additional colors, you can reference them with any aircraft.Loyd
  18. I'll assume you're asking what key opens the GPS window?The previous posters partially answered the question... IF the aircraft has a gps window, then shift+(some number) should open it. There is NO consistent number used by developers. The most common are 2,3, or 4.But the easiest way to find out is to try Shift+0 (zero) which isn't a normal option or Shift+9 which is rarely used.. you should get the error message on the screen saying that only keys 1 through (something) are assigned and beside each number listed is the function for the number. If a gps is available, you should see it listed - and that is the number you use in THAT aircraft.I prefer always having radios on shift+2, and GPS on shfift+3. The ONLY way to make this true for all aircraft is to reorder the windows in each panel config, so that GPS, if there is one, is always window02, which you open with Shift+3.DO make a backup of the panel.cfg before you start editing or you may regret it...even with the greatest of care, accidents do happen.Loyd
  19. See if it OFF (False) in the default flight also...[Options]Sound=TruePause=TrueLoyd
  20. Getting TP running on W7/64 is a bit tricky...This earlier post contains links to other posts where folks finally got it working on their systems...this one might be especially helpful...Loyd
  21. When first installed, the proxyuser.ini is INCOMPLETE, go HERE to read through Ed's tutorial on getting started. In his pages there is also a link to download a working version of the proxyuser.ini with all the necessary entries filled in.Loyd
  22. When I was on XP, I had virtual memory (Pagefile) fixed at 4G. It would gradually fill over several hours and when it got to 4G, FSX would stop/lockup and I had to restart. After that I would restart when it was in the 2-3G range, just so I wouldn't forget and let it lock up.Here on W7, the Program Manager displays are different so I'm never sure just what I'm seeing. If you have a fixed size pagefile, you might change it to "let Windows manage" and see what happens. I'm NOT running TP in this install, however so I can only offer my thoughts about what I might check in the same situation.Loyd
  23. The "Flight Video" feature in FSX - aside from it NOT being a video, but a flight recording - has always worked fine for me.A gentle smooth flight with the 172 at 5 sec record level was as smooth as the original. Recording aerobatic movements at any speed is likely to give jerky results.If a smooth flight at all speeds is jerky on playback I would try a couple things...Lighten the load on the CPU: AI traffic OFF, weather NONE, scenery densities set to med low and see what the results are.It also might be informative to record a 3min flight then pause the sim... before you view the saved flight, watch the same previous 3 minutes that you recorded with the "Instant Replay" feature. The two features should be displaying the same flight in pretty much the same quality - it's even possible that both are using the same recorded data, though one is saved to the HDD, and the other may be only in memory (I've always wondered where the 'instant replay' flight data was being saved...)Loyd
  24. Each time you add scenery to the scenery library, it is automatically added to the 'top of the list'... highest priority.So when you installed Tileproxy, it also was added to the top of the list. If Netherlands was already there, TileProxy will show in that region because it has a higher priority and you would go into the scenery library, find the Netherlands entry (or entries if there are more than one) and select it, then click the "move up" button until it (or they) are at the top of the list - then click "OK".If you added Netherlands AFTER Tileproxy, then it is already a higher priority and you shouldn't have to do anything - they are already in the best possible order.IF there are conflicts showing, you may have to disable Tileproxy as you cross into the region covered by the Netherlands scenery.I don't have the Netherlands scenery, so I can't test it in advance for you... but that is how I would start testing. Loyd
  25. In FSX, scenery and aircraft can be anywhere. You just have to tell FSX where it is; I have scenery on several drives and many add-on aircraft on another drive.Aircraft: place aircraft folders anywhere and reference thus in fsx.cfg:[Main].SimObjectPaths.5=SimObjects\MiscSimObjectPaths.6=G:\AddonAircraftSimObjectPaths.7=G:\AIAircraft.Scenery: may be deleted individually in the scenery library, files physically moved, then add area back to scenery library at the new location.ORif you trust your accuracy and skill, simply MOVE the files, then manually edit scenery.cfg with the new location; this will keep your scenery priorities the same.this illustrates moving a scenery folder from inside the FSX\Addon Scenery folder to a different drive. I did this once when I moved FSX to another drive and just edited the scenery.cfg to match the new locations.original entry:[Area.186]Title=addon_KSAN15Local=Addon Scenery\KSAN15Active=FALSERequired=FALSELayer=181edited entry[Area.186]Title=addon_KSAN15Local=L:\KSAN15Active=FALSERequired=FALSELayer=181Naturally, make a back up copy of scenery.cfg and do the operation in small steps so you can check that everything is working properly.Loyd

Account

Navigation

Search

Search

Configure browser push notifications

Chrome (Android)
  1. Tap the lock icon next to the address bar.
  2. Tap Permissions → Notifications.
  3. Adjust your preference.
Chrome (Desktop)
  1. Click the padlock icon in the address bar.
  2. Select Site settings.
  3. Find Notifications and adjust your preference.