Jump to content

Roger Wensley

Registered Users
  • Posts

    724
  • Joined

  • Days Won

    1

Everything posted by Roger Wensley

  1. OK, I will ask: what "brake message" is that, which I do not see when I start FS9?
  2. There used to be a better-than-nothing CYOW that the creator occasionally updated. It wasn't up to today's standards of expectation, but at the time it was good enough so that nobody else took CYOW on. Including me when I was living there full time. Now, well it is probably too late......
  3. And I include my email address in every posted scenery. Plus CYCV is not listed so I don't think I will be making it.
  4. There is a limit to the number that can be loaded into the Scenery Library, as I recently discovered. I realised that new entries were not appearing so I grouped existing airports geographically into, for instance, RW western Canada, and made space for new items. I currently have 1,010 library items so maybe the limit is 1,200?
  5. There are a couple of points: If you change the wind direction so that atc will direct you to a certain runway you don't have to save the flight, you just have to change the time by a second AFTER you change the wind direction and atc will take the new wind direction and act accordingly. But (and FS9 sometimes conjures up "buts" from thin air) if one of the runways has an ils then atc sometimes prefers to use that no matter the wind direction. At an airfield with no control tower ai planes will always use the ils runway for landing until the wind speed is over 30 knots even if this means a Cessna 172 is doing a 90 degree crosswind landing.
  6. Well it is possible. Though there was one more puzzle that I discovered just has to be ignored and it solves itself. Sitting watching an ai plane taking off on 34 for a downwind take off it was obvious that the runway was now "16 only for landing and 34 only for take off" no matter which way the wind blew. Good. But when I tried to select a runway for take off I was offered only 16?!? That made me think that it wasn't working.... After checking things I gave up. But, when I accepted the offered 16 it changed to 34! Don't ask me why or how, but it all actually works while sometimes pretending not to.
  7. OK, here is a tragic tale of blank memory. After I discovered that I could close a runway for either take off or landing with AFCAD I then discovered that I could do the same with SceneryGenX, which I have been using for scenery making for only 15 years. Whoops. But it gets worse. I then opened an Idaho scenery I made maybe 4 years ago and which I remembered as also having a mountain at one end of the runway and found that I had already used SceneryGenX to close the runway etc etc. Couldn't remember doing that at all. Double Whoops.
  8. Well, I have been using AFCAD for years to delete unwanted taxi lights or for elevation adjustments etc, but I had never noticed that it was possible to close a runway for take off or landing! Thanks for that ColR1948.
  9. Closing a runway does not work, as I need the landings to be on 16 and take offs on 34, so they will still be using both runways while not taking account of the wind direction. Can a runway be closed only for landing? I will have a look to see. The ILS idea could work as AI planes will always chose a runway with ILS for landing until the wind is more that 30 knots, and only then do they take account of wind direction. But, that ILS on 16 that makes them land on 16 will not make them use 34 for take off. Plus this is a backwoods runway in Monument Valley in Utah and an ILS would be an unlikely discovery.
  10. I have probably asked this question before, some years ago. If a runway is "single end" because at one end is an inconveniently large mountain is it possible to get ai to land or take off downwind if necessary? My scenery programme (SceneryGenX) has a setting box to be "ticked" for a single end runway but it appears to make no difference.
  11. If I remember correctly, there are two versions of the Alaska add-ons, for with or without UT.
  12. Reduce the visibility distance in the weather settings to 20 miles and then it won't worry you.
  13. Sorry not to reply before. I use a programme that I think came with SBuilder. Or maybe not? Anyway, it is called "Imagetool.exe". You load textures into it (5 or 10 at a time, not one by one) and it shows you the texture and the format, whether it is 32 bit, 8 bit, DXT1, DXT3 etc. You can then transform a 32 bit texture to a DXT1 etc and save it with the same name but a new format. You can also see if there are mips or not, and if not you can "create mips" and save it, etc. Sorry, but although I have DxtFixer I have never used it as I use Imagetool. It probably is fine, like the other programmes produced by the same folk.
  14. A bit late to write this now but maybe someone else will read it and benefit. When I upgraded from Windows XP to Windows 7 I first downloaded my entire FS9 to a back up hard drive. I then installed Windows 7, and then installed FS9 from discs as a new installation to C/FS2004. I checked it, and it worked. From the back up hard drive I then replaced the entire contents of the new C/FS2004/ folder with my original installation with all the add on scenery, some 700 airfields and/or scenery areas at a guess. It all worked.
  15. Some odd comments here re 2020. Surely it is simple? We don't know much about it right now. When it comes out all will be revealed, the good points and the bad. If it then seems to be on balance significantly better than FS9 then I will install it. If after some time I realise I am no longer using FS9, even though I have made over 600 scenery airfields for it, then I will be content.
  16. It is almost certainly a texture clash, so look at scenery object textures that you already had before you installed the new Glacier Bay scenery. Could be just one 32 bit texture that all the new DXT1 textures don't like. You can recognise it as it will show as a texture picture and not as an icon when you make the icons large. It could also be a non-mipped texture as having both mipped and non-mipped in sight causes this. Could be a non-mipped scenery texture 20 miles away.
  17. I forgot to mention that the AI updates also Allakaket with a Saturday Everts cargo delivery.
  18. This is not a problem, it is reality. The WW2 fighters still being flown (eg. by Vintage Wings of Canada based at Gateneau near Ottawa) never go to full power on take off as..... you've guessed it! They cannot be kept on the runway if they do.
  19. It says the scenery is for FS2004, but in the read me it says it is for FSX!
  20. Anyone willing and able to modify a DC4 by stripping off the wings so it can be used for a wreck in an Alaska scenery? I have a pic of the textures needed, which are pretty simple.
×
×
  • Create New...