Whenever I search the Avsim library for aircraft, I get page after page after page of repaints and textures for that aircraft, but but not the aircraft itself. It seems I have to have the exact file name in order to find an aircraft.I have tried boolean searches that should exclude textures and repaints but they don't seem to work.Suggestions?Thanks!Dewey

Yes. Don't look through the Repaints area of the library, but confine your search to FS2004 Aircraft...To do that, click on "Advanced Search" so you can select that single area of the library... ;)

>Whenever I search the Avsim library for aircraft, I get page>after page after page of repaints and textures for that>aircraft, but but not the aircraft itself. It seems I have to>have the exact file name in order to find an aircraft.>>I have tried boolean searches that should exclude textures and>repaints but they don't seem to work.>>Suggestions?>>Thanks!>>DeweyThe AVSIM file library search ability stinks if you ask me. Boolean searches and wild cards don't work as they should, if at all. If there was ONE part of AVSIM, I would like to see improved, that would definately be it.Matt

I like the library here and have no problem finding anything, just got to get familiar with the functions.Regards, MichaelKDFWhttp://www.calvirair.com/mcpics/mcdcvabanner.jpgCalVirAir International

>I like the library here and have no problem finding anything,>just got to get familiar with the functions.>>Regards, Michael>KDFWTry finding a FSPainter texture for American Airlines. Or just try searching for American Airlines. Or US Airways. Unless I'm missing something, it's impossible. Need to be able to do basic searches such as:+FSP +"American Airline"Matt

Generally I have to agree - I'm better at it now but finding precisely what I need is still not a particularly intuitive or even logical process at times.regards,MarkXPHomeSP2/FS9.1/3.2HT/1024mb/X700pro256

In fact, I have found that just a slight change in the search will give different results, even though the results of either search should be the same, or the one that is not working should be even more expansive.For instance, if I search for mtrl9* or mtrl9*.*, it only finds mtrl9_2.zip. If I search for mtrl9*.zip, it finds more files. So far, nobody has come up with an answer for me why this is so. If I knew why it worked this way, searches would be much easier.How many files am I missing because I can't search for them.I'm not complaining, what we have here is amazing, but I would like to see this work better. But I imagine there is some complex technical reason.Thomas[a href=http://www.flyingscool.com/FC_StartJava.html] http://www.flyingscool.com/images/Signature.jpg [/a]I like using VC's :-)

>Try finding a FSPainter texture for American Airlines. Orhttp://library.avsim.net/search.php?Search...4acrp&Go=Search>just try searching for American Airlines. Or US Airways. Yea, a term search via "" would be nice.>Need to be able to do basic searches such as:>>+FSP +"American Airline"Well, the logical ands are standard behaviour.Regards,http://www.bremmekamp.com/img/misc/avsim.jpg

I much prefer Avsim's file library to the one at "the other place." Try finding an original aircraft there. Say I want to find one of David Copley's P-38 models, for example. On Avsim, I can narrow my search to "original aircraft" and get it done quickly. Flightsim.com groups all files together by the type of aircraft they represent, whether they're a full model or merely a repaint, so I have to wade through repaints to find the original model.

>>Well, the logical ands are standard behaviour.Yes, somethings are standard behavior, and some things are not. For example. Why does a search for *A319* return 739 results, a search for *319*, returns 75 results, a search for A319 returns 627 results and a search for 319 returns 46 results??? I'm sure there is some logical explanation that an expert in search engine phraseology would be able to understand. But what about the rest of us or first time user??Also, using your example of searching for +fspainter +american +airlines would have missed this file fsp_a300_american.zip, because the uploader used "FSP" instead of "FSPainter" in the description. Sure you could change search to FSP*, instead of FSPainter, but if you change your search to +*FSP* +American +Airlines, watch out because you get a bunch of junk in the results??? Bottome line is that even if the searcher does happen to luck out and enter the search phrase exactly correct (which is unlikely), they will still end up missing things or having a lot of junk in the results. Of course, that is a problem with all search engines, but much more so with AVSIM.Also, while we're on the subject, am I the only one that wishes there was a way to set the default view of the results to sort by date instead of name?Anyway, sorry about the rant, I still think AVSIM is great :)Matt

I agree. I find flightsim's library search much more difficult to use than Avsim's.

>For example. Why does a search for *A319* return 739 results,>a search for *319*, returns 75 results, a search for A319>returns 627 results and a search for 319 returns 46 results???Why *319* yields much less results than *A319* I couldn't say. It's not obviously logical, though there sure is some obscure reason.Why A319 yields less than *A319* and 319 yields less than *319* should be obvious though. No wildcards.>Also, using your example of searching for +fspainter +american>+airlines would have missed this file fsp_a300_american.zip,>because the uploader used "FSP" instead of "FSPainter" in the>description. Sure you could change search to FSP*, instead of>FSPainter, but if you change your search to +*FSP* +American>+Airlines, watch out because you get a bunch of junk in the>results??? A bunch? 3 at the most. I think that's bearable.>Bottome line is that even if the searcher does happen to luck>out and enter the search phrase exactly correct (which is>unlikely), they will still end up missing things or having a>lot of junk in the results. Of course, that is a problem with>all search engines, but much more so with AVSIM.I don't agree, AVSIM's may not be top notch, but it could be MUCH worse (flightsim.com is a good negative example).>Also, while we're on the subject, am I the only one that>wishes there was a way to set the default view of the results>to sort by date instead of name?Well, I'm with you on this one. ;) Also a better measured "popularity" sort option than "number of downloads" would be great.Oh, and while we're in "wishful thinking" land I'd like the option to search title and description separately.>Anyway, sorry about the rant, I still think AVSIM is great :)Undoubtedly. Don't worry about the rant, personally I think it's well put even if I don't agree on all points.Regards,http://www.bremmekamp.com/img/misc/avsim.jpg

But you must admit that as noted above mtrl9* and mtrl9*.* should yield at least as many if not more than mtrl9*.zip, which for some reason is not the case. ???? I don't want to belabor the point, but I must admit confusion.Thomas[a href=http://www.flyingscool.com/FC_StartJava.html] http://www.flyingscool.com/images/Signature.jpg [/a]I like using VC's :-)

>>FSPainter, but if you change your search to +*FSP* +American>>+Airlines, watch out because you get a bunch of junk in the>>results??? >>A bunch? 3 at the most. I think that's bearable.>Actually, +*FSP* +American returns over 1,400 results. +FSP* +American returns 42 results. Why? Because the +*FSP* +American will return any file with FSP OR American in it. Where as +FSP* +American returns only those with FSP AND American in them????? That makes no sense at all. Wildcard searches are totally screwed up.I'm not saying the search is terrible. Just that there is a lot of room for improvement.Matt

>Actually, +*FSP* +American returns over 1,400 results. +FSP*>+American returns 42 results. Why? Because the +*FSP*>+American will return any file with FSP OR American in it. >Where as +FSP* +American returns only those with FSP AND>American in them????? That makes no sense at all.True.>Wildcard>searches are totally screwed up.Here I still disagree. Actually I'm surprised that the search does not just ignore wildcards as first characters of search terms, as many search engines (e.g. Google) would do, since these searches are causing much higher CPU loads than wildcards at the end of terms.Just because the search acts up when this (IMO quite special) kind of wildcard searching is done, doesn't mean wildcard searches are totally screwed up. The standard ones aren't.But you're absolutely right, would be nice if this were fixed.Regards,http://www.bremmekamp.com/img/misc/avsim.jpg