Is there a way, or a hack, or a workaround, or a planned future enhancement, or whatever, that will allow one to import WED (.WMP) architecture that has textures applied to it, into MED as a model, and RETAIN all the textures and texture-mapping?

Because:
I'm finding that my current project is too big and too complex for 3DGS to handle. Maybe that reflects on me as a designer, maybe it reflects on the software, maybe a bit of both, but I've rebuilt the architecture in my level several times now, re-textured it, re-organized it (grouped it, ungrouped it, split it into chunks to try to speed up compiling, etc etc), and nothing is working. The nature of my project dictates that the entire level be loaded at once--it's based on a real building with lots of windows and open space, so fooling the user with multiple levels and billboards, etc, is not going to be effective. I'm on the verge of abandoning this project that I've been working on in 3DGS for two years and trying other software solutions. If I can get the architecture/model import/export to work with MED and .WMP's as described above, however, I may still be able to get this to work.

Thanks in advance.

No, you cannot export a .WMP to med with textures, though its not hard to re-texture in MED...

Oh, and I should mention that my level would compile and load in version 6.3 with no problem--slow, yes, but it would do it. In 6.4 and above, the level freezes while loading and all I get is black space and a few scattered entities showing.

This my dire need to get around this, and if I can export my level architecture to a model and retain all the texture info, then this could work.

When I view the level in preview mode, I do get a red wireframe around my level architecture (and blue around the models). When I look at it in build mode, I get a red wireframe around the entities that do show up (but most of my level isn't showing). Oddly, I cannot seem to move around in either mode, though previously in 6.4 (I'm in 6.5 now) I could at least move/fly-through in preview mode.

Preview = in wed and build = compiled and running in the actual engine?
I'm sure this is a texture problem then, if you can see the red wireframe. Are you using .tga textures?

Galen, You will have to wait for next upgrade, this has been implemented in ver6.53 and is available to beta testers. It might be available is next release. Wed can export/import level geometry with textures intact, read the beta page for some detail.
Bye,
MSL.

Oh my Gosh, I hope that comes through then!! That would save me, I kid you not.

Here are some screencaps showing my problem (actually, showing my level's problems--my own problems wouldn't fit on this page! aha ha)

Level Preview:
http://mysite.verizon.net/vze3f978/level-preview.jpg

Level Build (engine running):
http://mysite.verizon.net/vze3f978/level-build.jpg

I'm actually using .bmp's on level architecture, and .tga's for models and sprites. Like I said, this would all compile and work in 6.3... And I realize it's taking up a lot of memory. Thus my thinking that if I could compile the architecture as models, I could reduce the nexus a bit.

Believe me, I *really* appreciate you folks taking the time to help me with this! I honestly don't want to give up on this, but after 2 years of plugging away at this, I'm at the point of having to decide to keep going or cut my losses.

Also, does it matter if I use both .bmp's and .tga's in the same level?