DIF Problem

#1 I'm betting you're really having the problem in TGE, too. You just haven't noticed it since it is not uniform across the same brushes. Download the patch to fix the collision issues.

#2 The strange thing is that when I fire the crossbow at it it explodes on contact...

#3 I never tried seeing if projectile collision worked rather than player collision. Did the patch fix the problems?

#4 Which Export Option should I be using for TGE or TGEA?

1)Export as Dif
2)Export as Legacy DIF
3)Export as Legacy TGEA DIF
4)Export-->Torque Game Engine(map2dif plus)
4)Export-->Torque Game Engine Advanced(map2dif plus TGEA)

I applied the patch, just making sure how I should export

#5 I use export as Dif.

#6 You need to use export as DIF, its the most compatible one at the moment but sadly it does not support portals at the moment as well

#7 Thanks for the fast replies...I'll see if the patch works

#8 Looks good...now I'm just bummed about portals

#9 You know I had collision problems just like that, but if i made the model...saved it, and then opened it back up before i exported it, then it worked fine:)

#10 That's why they were inconsistent. The new patch fixes those issues.

#11 It is posible to get portals working you need to recompile map2dif_plus after altering a line in the source code, this worked for me, all you need to do is change the line recompile map2dif_plus, copy the execuatable over to constructor folder, change the line back and recompile just to make sure the value is back to normal for the rest of the engine.

U32 Interior::smFileVersion = 14;

to

U32 Interior::smFileVersion = 0;

Its explained in detail in this forum post.

Hope this helps some people with portals not working.

#12 I have two questions:

1. Do I still need to get the patch? That post is from the end of September and I would assume that GG updated the one on their product page.

2. How do I tell if my new map2dif_plus works?

#13 1. Yes you still need to get it. Constructor is still 1.0.3, no new version

2. Change the export simply. You can configure it and tell it to use a different exe

#14 Thanks for the quick reply,

2. Oh, what I meant is how I know if it actually worked. I replaced the export .exe in the Constructor folder with the newly compiled one. But I can't really tell any difference on the .dif produced. Now I only exported a block to try it out so I assume I wouldn't notice anything. But how do I make sure that it works properly (i.e. exports portals properly).

I got TGEA last week so I don't know how it worked in prior versions.

#15 Using a debug compile of the engine, load your DIF and go into the console. Type setInteriorRenderMode(7); It will show you your portals. Check out Desmond Fletcher's holodeck tutorials for more information on render modes in debug.

#16 Oh wow, more quick replies. After looking through these forums I saw that most replies usually took a day or so. Now I'm really impressed :)

Thanks for the information. After looking through those pages and browsing around I thought I had to download the resource and integrate it. But apparently it was already integrated to begin with :) The setInteriorRnderMode(n); that is.

#17 With TGEA use the "export as legacy TGEA dif" if you will be using portals (with the new patch/exe dropped into your constructor folder) The setInteriorRnderMode(7) will show you in WE your portals by way of different colored areas for each portaled area(hitting I think F9 will also inact the same). If the area is white, a portal is not functioning appropriately. The setInteriorRnderMode(n) functions will only work when your using the debug.exe .

Portals will stop a given area from being rendered if that area is not in line of sight. If you need help on how to make portals, say so and I will walk you through them.

#18 Ah yes, I had forgotten that. I was testing in TGE, not TGEA. Thanks, Andrew.

#19 I got it all working.

F9 button worked like wonders and my areas are separated as they should be with the portals.

Now I ran into a few more problems:

1. The terrain doesn't show up inside the interior, which is good.. but the player still collides with the terrain. Is it possible to turn off terrain collision inside an interior? It'd be horrible have to edit the terrain map to flatten out the area it was annoying enough to export it to atlas format.
2. Oh.. and what if I want the terrain to actually show up inside (I guess that could be useful).

Thanks for all the good replies :)

Now I'll just experiment with the lighting and the trigger thing I found in Constructor. Seems nice to actually be able to place these without having to be in that clumsy world editor.