Game Development Community

Adding a DIF in the editor crashes TGEA

by Dubai Coder · in Torque Game Engine Advanced · 09/29/2008 (6:56 pm) · 9 replies

I created a simple box with the latest constructor and when ever I add the dif to a scence TGEA crashed.
The log isn't helpful and Im not sure why this is happening. Any help?

I wanted to add that I'm using map2dif plus tgea.

#1
10/03/2008 (12:25 pm)
Is your texture for the box included in the export? What error are you getting?
#2
10/03/2008 (12:35 pm)
Use the regular export to dif from constructor instead of map2dif plus
#3
01/04/2009 (2:12 pm)
Export to Legacy TGEA, normal dif export doesn't work on TGEA. Well, for me it doesn't :)
#4
01/04/2009 (2:21 pm)
@Julian - "export as dif" should work for TGEA. There are only a few differences, the "legacy" mode just doesn't export the embedded dts models. What sort of error are you seeing?
#5
01/04/2009 (2:24 pm)
@Jaimi - can't remember exactly, but I get an exception error before the mission loads completely, with a click ok box, then TGEA closes. I don't have any dts models in the constructor model. I'll give it another go.
#6
01/04/2009 (2:26 pm)
Odd thing that, I've found that regular export from Constructor to DIF works flawlessly in TGE (1.5.2) and TGEa (1.7, 1.7.1), it's the map2dif (& plus) that routinely fails for me. I don't even use MAP files anymore -- Constructor and it's native CSX format only.

edit: corrected version #'s
#7
01/04/2009 (2:39 pm)
Oh by the way this is in stock TGEA 1.8 using direct x sdk (November 2008), without a re-compile, so not sure if this is the cause. I'll try a few things, see what comes up. Judging by the odd collision or lightmap crash I get in stock TGEA on the strong hold mission, mainly on jumping into the water, it may need a recompile.
#8
01/04/2009 (3:01 pm)
@Julian: There is a known rendering (shader failure) bug, especially noticeable with Interiors, with the Nov 08 DirectX SDK and TGEa (1.7, 1.7.1, & 1.8), but I wouldn't think that would cause your crash problem.
#9
01/04/2009 (3:08 pm)
@Michael - thanks for that. I knew I was taking a risk using Nov 08, normally use May or June. But recently wiped my machines after backing everything up, and decided to go full out on up to date everything. I'll do some testing, switch back to a previous release - and update you, just for good measure.