DeleD Community Edition

holger53

Just "installed" the map inporter.

But it is not shown under "plugins"

Unzipped with folder option

Mr.Fletcher · Posted: Tue Jun 12, 2007 6:28 pm Post subject:

I don't have any problems with that. Are you sure your DeleD version is new enough?
_________________
Behold! The DeleD Wiki! Please help us expanding it Smile

DeleD on IRC

Jeroen · Posted: Tue Jun 12, 2007 6:29 pm Post subject:

Also, the plugin DLL file needs to be in the Plugins directory. Is that the case?

holger53 · Posted: Tue Jun 12, 2007 8:41 pm Post subject:

ok, I was very stupid - updated the wrong program - had installed DeleD

twice on the computer without knowing.

I can now see the plugin

But the pluging chrashed when I tried to import some buildings of a torque content pack.

Paul-Jan · Posted: Wed Jun 13, 2007 8:35 am Post subject:

The .map importer is still in beta, I'll release a new version soon (as in: this week).

That said, torque .map files are one of the few file types it was sort of thoroughly tested with, so the fact that it crashes on you comes as a surprise. Do you think you could send me (paul [at] delgine [dot] com) one of these map files so I can debug it, or would the license not allow that?

I have a huge shortage of .map files to test things with. Which is the main reason why the importer is still in beta.

dr_boom · Member Joined: 02 Jun 2006 Posts: 5

I noticed the map importer does not work with quake 4 maps.

Paul-Jan · Posted: Mon Aug 20, 2007 7:30 pm Post subject:

Thanks for making that explicit, I'll see if I can find some files to test with and add support.

yanchiko · DeleD PRO user Joined: 09 Dec 2006 Posts: 49

When will ".map importer/exporter" be available?.

Paul-Jan · Posted: Wed Sep 19, 2007 11:24 am Post subject:

I'm affraid that will probably take a while. We don't have anything like that planned at the moment, for the following reasons:

1. While .map importing is rather trivial, exporting is not. Converting from polygon geometry to brushes is complex (sometimes impossible) and hard to get robust. Our Torque exporter takes this route, and it took us a a lot effort to get it where it is now (and it still isn't perfect).

2. Not a lot of people are interested in just exporting .maps, most want a ready-to-use solution for their particular engine, requiring custom entities and support for custom tools to postprocess the .map . We could try to build this support in a very generic way so users can plug-and-play their own entity definitions and tools into the exporter, but frankly... other tools exist that do precisely this, and the end-result is hardly userfriendly. It is much more likely that we'll be adding specific support for a particular engine (like we did with Torque), than such generic .MAP exporting behaviour.