Where did you put your macro? If you can select it there shouldn't be a problem. If it's in a different location to the others you might need to set the path to the folder from FSSC Tools/Preferences/Locations.

It's possible there's a bug with the macro itself.

There might well be a bug with your macro. I suggest not being too ambitious to start with. It's a complete waste of time & effort creating complex macros if they don't work. Create a simple untextured cube with EOD & try that as a test piece first. If this works the problem is with your original macro.

Try it first & see if that explains it. I'll be happy to check out your macro but if there's a bug I can't guarantee to fix it. For the last 5 years I've made it my business to check out most FS design programs & utilities to find out how to use them. I know enough about them to get people started & sort out the most common problems but that's usually as far as it goes.

I'm a great believer in taking things slowly. This usually turns out quicker in the long run. Start off with simple test pieces so you understand how it all works & gradually move up to the more complex projects. There's a lot to learn & Rome wasn't built in a day.

OK. It seems you're getting somewhere. For the textures to display they can either be in the FS9 main Texture folder or the Texture subfolder of your scenery. Except for the common texture libraries (Airport, VOD etc) I prefer the latter.

I don't have the latest version of FSSC. My version seems to have a bug with the texture export feature in the Export Wizard. As usual (belt & braces) check that the textures were actually exported & the files are where they should be. If not, check the list on the Wizard & paste them in manually.

PS. Quote:

Assuming the BGL files are in TTF\Scenery the textures should be in TTF\Texture.

Hmm. That looks fine to me providing those are the textures you used. I'm wondering if you activated the TTF folder from the FS9 Scenery Library or if it's still reading the original BGL you exported to the Addon Scenery\scenery folder. You might like to check that it's not still in there or you could well have a conflict. This is always a danger when you first start experimenting.

If all else fails mail me the files.

With all programs & utilities I find that spending a little time setting the preferences pays dividends. From EOD/Project Options/Paths set the FS Texture Path to FS9\Texture. I suggest you direct the Default Project Texture Path to FSSC\Texture. Double-click on the path to change it. Now exit EOD & restart it for the changes to take effect.

To texture an object select the Texture tab in the bottom left window. I suggest using default textures to avoid having to export them but this is your decision. Click whichever Texture Path you wish to use from the bottom radio buttons. The default option is All. Browse throught the list of textures & select one. Any one will do for a test. Once selected the textures are assigned separately to each side, top & bottom of your object. You can use different parts of the same texture if you wish. Select an option from the list along the top & check the "Paint this side" box. Another window will open showing the selected texture with various options. Drag the box to define the part of the texture you wish to use. Click OK. Repeat this procedure for all sides you wish to texture.

PS. After writing all this out in my own words I found it's explained properly in EOD Help.
http://www.echos.ch/eod/help/texture.htm

Please slow down a little & RTFM.............!

Quote:

It's no problem. As I told you I like messing around.
However. It does help to read the manual first.

Yes, you can use default scenery objects but not with the conventional design programs. Download RollerBall's (Roger Mole) "FS2004 User Friendly Scenery Design Package" here. http://www.simviation.com/fsdesign_scenery8.htm

I haven't tried it but I think it involves writing "simple" code.

Interesting reading this thread is. Hi Doug and atotti.  I just had to jump in with my 2 cents about Rogers neat package, I have been using it and it is great for somethings, however when it comes to the buildings I have found that most are coded to an area, ie... those nice hangers at LAX will not work elsewhere. I find that using the M$ Compiling Scenery SDK will get you alot more for your time spent learning how to use the compilier. But thats just me.

he forgets to mention that he should be a techer in this.
In the other topic ive started, possible called open hangers??, i have posted what i have mnaged thus far. not alot but still something.  8)