Contents
English (United Kingdom)French (Fr)Deutsch (DE-CH-AT)
Random Thumbnail
monsat06.jpg
Search
Login
Navigation
Home Descent 3 Descent 3 construction Getting Dallas to work with MS VC++ 6.0
Most Recent
Featured Articles
Joomla 1.5 Featured Articles
Navigation
Home Descent 3 Descent 3 construction Getting Dallas to work with MS VC++ 6.0
Who Is Online?
We have 58 guests online
English (United Kingdom)French (Fr)Deutsch (DE-CH-AT)
Getting Dallas to work with MS VC++ 6.0 E-mail
User Rating: / 3
PoorBest 
Descent 3 - Descent 3 construction
Written by Thomas   
Wednesday, 15 October 2008 18:32

 

This article is about getting Dallas (the scripting engine) to work. It doesn't want to compete with pages like http://www.planetdescent.com/kyouryuu/tut-scripting.html because it actually encourages you to not use the EGCS compiler. Instead, it suggests Microsoft Visual Studio 6.0.

Descent 3 was originally developed in Visual Studio 6, of course with lots of bits written in Assembler. MS Visual Studio 6 isn't that great when it comes to compact and fast code, at least not compared to newer compiler generations. It does, however, beat the EGCS compiler by factors.

The prerequsite for scripting your levels is still the D3 SDK. You can get it from http://www.descent3.com/4_downloads.html or, via direct link, at http://www.descent3.com/files/sdk/d3-sdk14.zip. I have to say that you should not download the editor (D3Edit) from there because the one you get from that page is totally outdated.

Then, try to get a cheap copy of Microsoft Visual Studio 6.0. The software is not free but you can get it on eBay as a second-hand product almost for free.

The D3 SDK's readme.txt file (it's in the doc directory) tells you then what to do. You should read through it at least once (Here's the file: D3SDKreadme.txt). It refers you to a file called vcvars32.bat which has been installed together with Visual Studio.

Copy the file vcvars32.bat from MS VC's bin directory into the directoy where you installed the Descent 3 editor and rename it to something which makes more sense (maybe StartD3Edit.cmd). Now edit the file and add a line to the end of this file which starts the editor. This way, the batch script sets all required environment variables for MS Visual Studio first and then invokes D3Edit.

Easy, wasn't it?

 

Last Updated on Wednesday, 03 March 2010 23:50
 
You need to login or register to post comments.
Discuss this item on the forums. (0 posts)
Discuss (0 posts)