DeleD Community Edition

[dirkk]

Hi,

information about the newly developed .map exporter goes here.

I think that especially the Torque community is in need of a good level editor, but I guess, other engines will benefit from this, too.

I start the round by posting two references to the .map format:

- www.rustycode.com/matt/MAPFiles.pdf.zip
(thanks to Matthew Fairfax)

- www.gamers.org/dEngine/quake/QuakeEd/map_example.html

[cmoibenlepro]

I don't know if it helps you, but in the other thread someone said that making a .map import plugin would be difficult because you need to make a .wad importer for textures, I just wanted to say that it is not needed.

wad texture files were used only to compile quake 2 maps.

in quake3 maps, you can also use loose tga or jpeg files if they are placed in the texture folder in the baseq3 folder.

hope it helps you

[smoothblur]

If you are planning on creating a .map exporter for use with the Torque Engine even though Torque uses the Valve220 .map format, there is no need to create a .wad file for the textures because map2dif looks for the textures files in the same directory as the .map or in a texture directory you set using a commandline switch.

Also if anyone needed a .wad file for any reason there are many freely available .wad compilers so creating a new one would be probably a waste of time.
_________________
Matt Summers
Dark Industries
http://www.darkindustries.com

[cmoibenlepro]

here is other .map specifications that could be useful:

http://www.planetquake.com/qref/wcs/

http://www.gamers.org/dEngine/quake/#QDP

http://www.gamers.org/dEngine/quake/QDP/qmapspec.html

I would like to help (because I would like to import my q3 maps made with quark into DeleD) but it's too advanced for me...

[dirkk]

Your help is greatly appreciated. For the time being, we will implement the exporter first. But indeed it might be a good idea to subsequently implement an importer after we have some experience with a working exporter.

[Jeroen]

That seems like a very good order of things. First an exporter, then an importer.

[cmoibenlepro]

I agree that both exporter and importer would be very useful

it seems a good order to start with a working exporter, but don't forget the importer

[cmoibenlepro]

any progress?

[dirkk]

Yes, there is some progress, and I am currently working on it. But there's no screenshots or anything else yet, unfortunately. But I am at it.

[granada]

Take your time dirk ,we can wait

dave
_________________
AMD Phenom(tm)IIx6 1090t Processor 3.20 GHS
8.00 GB memory
Windows 7 64 bit
Nvida Geforce GTX 580

[Il Buzzo]

Hi All,
I'm really sorry but owing to a fu**ed PCI 2.0 USB port my system crashed almost everyday, so I've not written anything in C++ for this plugin.
I think I'll start to work at it from 4th October cause this week-end I'll leave Italy for a week (I'm going on holiday ).
So I think I'll start everything from that week just as my landscape plugin (some ideas to add? look at the advanced landscape plugin thread).
Bye

[dirkk]

Hi,

I managed to do my first Torque import whith a DeleD object. Just a single texture and the UVs are messed up, but it's clearly the right geometry. Look here:





So, as you can see - I am at it .

- Dirk

[Jeroen]

So you can now export to a .map file? Great, it looks very promising! Keep up posted here!

[dirkk]

Yes, I forgot to mention: the exporter indeed exports to a map file first, which can then be fed to the (in)famous map2dif.exe which is part of the Torque Engine.

On a sidenote, you can see (sort of) from the screenshot, lighting is done completely in TGE on startup.

[granada]

Nice one dirk

dave
_________________
AMD Phenom(tm)IIx6 1090t Processor 3.20 GHS
8.00 GB memory
Windows 7 64 bit
Nvida Geforce GTX 580