Roger Wensley

Try just looking at the texture files in the texture folder with the size set at "large icons". All the dxt1 or dxt3 format textures will show as "icons", while any 32 bit texture will show as a "picture". Take that texture and format it and your problem is solved.

Almost certainly the crashes are caused by scenery texture clashes, and probably within 20 miles of your position at the time of the crash. I say 20 miles as that is the sort of distance at which FS9 is preparing to use a texture, and then discovers it clashes with a second texture it is already using, or with all the textures it is currently using. Could be one 32 bit texture against DXT1 or DXT3 textures (happened to me). Could be an unmipped texture versus mipped textures (again, has happened to me). Check your scenery texture folders for the one that stands out as different.

OK, I sorted it out now. So that is why there is a carbon Cub included in 2020. And Xplane 11? Hmmm, gets me thinking.

Or did I misread it and this was a radio controlled model and not for flight sim at all?!? Drat!!!!!!

What happened to the XCub that was made for Flight? I think there was one? Or was it only in the process of being made? If there is one plane that I would like to see in FS9 it is the XCub.

Thanks for that Bean!

Does anyone happen to know the name of the runway texture that provides the wind blown snowy asphalt texture? A first search of the bmp textures didn't come up with an obvious candidate, so is it one of the r8 textures? And what is "r8"?

Nope, making it layer 6 didn't work either.

Tom, it didn't work. I made a trial "gap cover" polygon over one gap and gave it layer 1 while the original grass is layer 4. No success. I then tried loading the "cover" into a separate scenery folder and giving it a higher FS9 library priority above my Gander scenery and again no success. All the gaps are still visible. Ah well, never mind. Unless layer 4 is a higher priority than layer 1? Try again Roger.

Tom, Aha! I will try that.

Tom, what I did to freeze the lakes was to make a huge VTP2 polygon in SBUilder, then select coral as the polygon texture, and voila the lakes looked like they were frozen and could be landed on with wheels or skis, and the land just looked like there was snow on the ground. But, in the middle distance there were black lines visible in the "ice", just as there are now in my airport grass background.

Tom, given that Holger does not reply to my email, and given that I still don't remember how, and given that you are the only person to make a suggestion, how would I do what you are suggesting? Maybe you are suggesting what Holger already described but I don't know enough to recognise it as such.

The idea was to save the originals too, and you could move from summer to winter and back by ticking or unticking the winter textures in the fs9 library list. They are still posted here on flightsim.

 

No Tom, it was actually doing something extra, like making another "ice" texture that spanned the gap between adjacent "ice" LOD rectangles in the lakes. So in a big lake it took some time. Making the initial winter ice textures was very different and I was making hundreds of square miles in a few minutes by blanketing the whole area but only affecting the water, not the land. If you look at Holger's three west coast texture areas you won't see any rectangular lines in his lakes as he only had a few to fix and he probably got it done in one day.

 

So I guess I hassle Holger.

Years ago Holger Sandmann told me how to turn a water lake to an ice lake, and I froze Canada for the winter, and posted the result. He also told me how to get rid of the dark lines that appear from a certain distance between the rectangles of ice. I did not do that as it was 10 minutes per lake and I didn't have the 20 spare years to do every lake in Canada. As a result I cannot now remember what he told me. I now have the same problem with grass textures for an airport and need to fix it in the required 10 minutes. Instead of chasing up Holger and bothering him I thought I would ask on here.

Thanks for that hgschnell, it is now working!

Anyone downloaded the Russian IL-76 and then tried it with Stan Sanchez textures for his AI version? It does not work for me, maybe because Stan states a TD model is required and it comes only with a MD model? His email address appears to be defunct.

OK, I will ask: what "brake message" is that, which I do not see when I start FS9?

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......

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.

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?

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.

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.

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.

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.

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.