Wheres map2dif gone?

#1 You're best bet is to use Constructor and just do "Export As DIF...":

Constructor
Constructor 1.0.4 patch

There is a map2dif_plus_tse.exe in the root folder of Constructor if you are really set on using that instead.

#2 Thanks for the reply Matt.

I've tried Constructor 1.0.4 exporting but upon adding my interior + materials too stock TGEA (I used the T3D demo) I got a crash, I assumed the map2dif was out-of-date.

Does this mean a debugging session? :(

#3 @abydos:

I have not found any incompatibilities yet with 1.04 and TGEA 1.7 (that's what I am using now also). If you would like, I can look at your map and see what is causing the crash.

#4 Thanks Jaimi
I doesn't crash in TGEA 1.0.3 so id guess its an incompatibility thing (edit: maybe with something specific to my map)
When I have time to sort this, ill debug and see what I find.

#5

Quote:
Thanks for the reply Matt.

I've tried Constructor 1.0.4 exporting but upon adding my interior + materials too stock TGEA (I used the T3D demo) I got a crash, I assumed the map2dif was out-of-date.

How exactly (which of the export options) did you do this?

#6 Ive tried File->ExportToDif and File->ExportAsLegacyTGEA using default constructor 1.0.4 settings.

#7 Matt,

I know you've put a lot of work into Constructor. I'm just very comfortable with QuArK, after using it for seven or eight years now.

I know this is less than what you intended, but is there any chance that Constructor could be used as a command line replacement for map2DIF?

#8 Eric,
I've thought about abstracting the map compilation code from Constructor into a new map2dif but it just hasn't reached a high enough priority to be done (my time is unfortunately limited and what I am working on right now and for the next few months will be of *far* more value than a shiny new map2dif).

Internally, a lot of our efforts are focused on replacing DIF altogether with a better and easier solution which would be a win for everyone involved so it doesn't make sense to spend a lot of time fixing something we will be chucking out anyway. We are still in a highly fluctauting research phase on this so we aren't ready to start talking about it in *any* detail.

#9 I fully understand that Matt.
Thanks for the info.

#10 I finally had the chance too debug, this is what I found:
"Error alloc too large, increase frame size!"

Which I guess comes from
void* FrameAllocator::alloc(const U32 allocSize)
in frameAllocator.h

Found this
#define TORQUE_FRAME_SIZE 6 << 20

How do we know what to set it too?