Game Development Community

Dif Map ist very slow without portals

by Alex Anderson · in Constructor · 05/01/2007 (9:17 am) · 12 replies

Hi,

i had import my optimized q3 keep map ( hideportals, detailbrushes, caulktextures) in the constructor.
Then i change the q3 portals to torque protals.
But after the compiling into the tgea dif format, the map is very slow without all protals.

Where is the problem with portals?
There is no leak in the map, but even if, the constructor hasn't tools to find a leak?
To the tgea engine for our project, we use the demo.
Is there a wireframe modus aviable?

Many Thanks

Alex

#1
05/01/2007 (10:28 am)
I have only found ONE map2dif exporter that have working portals- but the map2dif with working portals dont do so well with exporting geometry.
Its one of the things they advertise when any customer is considering purchase, matter of fact they advertise allot of things that just plain dont work, or do not work as stated.

Anyhow, the most you can get out of a portal and map2dif is making sure you only use ONE zone portal (basically only one opening in your Dif), unless its a very very very basic Dif- nothing but square rooms. Make sure the spot you put your portal have SQUARE walls, portal will not work on any angled brush faces. Also make sure the portal do not touch or get near any DETAIL brush, i guess they hate each other, and the portal will go out drinking instead of zoning your map.


EDIT:
More in depth testing proves me wrong, this(old 2005 map2dif_plus) seems to export for TGE with working portals, as long as I use thick walls, and dont touch the portal to any DETAIL brush. Also the fewer brush the PORTAL is in contact with the better, so its still best to place PORTALS in areas of very simple geometry.
#2
05/01/2007 (11:09 am)
Hi Caylo,

can you give me an example ( map ) how the portals works in torque?
#3
05/01/2007 (11:20 am)
First, you DO know that Constructors "Export as Dif" and "Export as Legacy" both do not have portal support yet?

As far as an example;
Make a big cube, 20 tall 40x40 wide and deep.
Make it hollow with 3 units wide walls.
Subtract a 10x10x10 cube from one of the walls, to make the 'door way'.
Now add a 11 tall 11 wide 1 deep brush into the doorway, in the middle- make this brush your portal.
Now export with MAP2DIF.
#4
05/01/2007 (11:25 am)
Oh, i can not use the menuparts to compile.
In the constructor dir can i see 2 converter. (map2div_plus.exe, map2div_plus_tse.exe)
What is the right version to compile?

EDIT: I tested both versions and none works with the tgea engine. :(
#5
05/01/2007 (11:35 am)
I could be wrong but I thought they haven't released the tgea update that supports constructor dif's yet?
#6
05/01/2007 (11:43 am)
From the Constructor "FILE" menu one may use the EXPORT option and use any version of MAP2DIF they wish.
#7
05/03/2007 (7:02 am)
Please upload me an little example map with working portals in tgea.

Many Thanks

Alex
#8
05/03/2007 (10:46 am)
Please send me much money!

Many Thanks

ok, im just kidding a little.. Truly now, if you can move your mouse you should have no troubles making your own silly example map with working portals. As far as what version of Torque you wish it to be in, thats upto the export process- and im not about to go into what exporters support what functions, take some of your own time and learn a little.
#9
05/03/2007 (1:03 pm)
Here you go. This have Constructor and QUARK and .map and a TGE .dif.
#10
05/03/2007 (2:18 pm)
Hi Caylo,

many thanks for your help. Now i can see the size/cut of portals.
#11
05/27/2007 (12:05 am)
Mb is right. Your example "testall" crashes TGEA 1.0.1. Sorry... can't wait for that to change.
#12
05/27/2007 (3:10 am)
If you wish to use this with TGEA 1.0.1 you will need to export for TGEA 1.0.1 just the same way you already export your TGEA 1.0.1 DIF. If TGEA 1.0.1 do not yet have working portals then i guess it sucks to be stuck building a project with a yet- unfinished SDK. You will need to wait on portals until that part of TGEA 1.0.1 is working, so in the mean time you can practice your texture alignments....