Howdy,well, I'm very delighted to see that someone has taken on the task of putting the Geobase data into FS format - thanks for that, Joel!!!However, I'm very disappointed that your read-me files don't even mention the person who wrote the complex freeware (!) tool to convert these kinds of data. I assume you used Luis Sa's SBuilder? Once again, the utility developers are the "unsung heroes" and the people that use them don't even say thanks... not nice!Cheers, Holger

Holger,I had a talk with Luis about this issue and I apologize to himProper credit will be done in the next release.Joel

I'm running a somewhat "borderline" PC for FS9. Can anyone tell me what kind of framerate hit this add-on makes? I'm currently running USA Roads without any noticeable hit to frame rates. Would this software be similar?

Hi Bill, framerate hits are highly machine-dependent as you know. I found a drop of about 30-40% over Montreal, with thousands of streets AND flattening on (which is probably induced by American Data roads). Easiest thing to do is to download Quebec and try it out. I'd be intrested in your results.Jon

Thanks for responding. I don't know if I can afford a 30% hit on my frame rates. I'm currently locked at 16 (getting 15+). The sim runs pretty nice and smooth, but I'm afraid if I lost 30%, it would be too much like a "slide show". Thankfully, USA Roads didn't make any noticeable difference on my system. I guess, for now, I'll just stick to flying "stateside".

Bill,Here's my data over a test area flying for 2 minutes. This is over a densely populated area of Montr

WOW!! I did a quick trip out of CYOO and was able to actually find the road intersection by my house. The only downside I've seen so far is a lot of the roads are so close together that autogen can't place anything around them.

The challenge now is how does this release mesh (did I say that?) with the commerical US road products (USA Roads and American Data Roads). Joel has suggested disabling a bunch of .bgls to ensure no overlap with the default FS2004 roads. But it is challenging at the US/Canada border as the .BGLs do not know international boundaries. So I believe what happens is that Joel's BGLs will correctly place Canadian roads, but near the border you may get overlap from either default or commercial BGLs that have both US and Canadian roads.For example. RD926160.BGL covers much of southwestern Ontario and little pieces of NY state, and some of the south shore of the northwest section of Lake Erie. Therefore it seems that you will still get default major roads in South Western Ontario. The option is to disable that BGL, lose bits of the US and have no duplication in Ontario.Now, am I out to lunch? Or do these two products already exclude Canadian .BGLs so all will work ok? I do recall that both products had a side effect of eliminating Canadian default roads near the border.I have switched so many times between USA Roads and American Data that something may have got tangled. Jon