NS2 Decoda Work Directory
SparkyMcSparks
Join Date: 2010-04-12 Member: 71347Members
Join Date: 2010-04-12 Member: 71347Members
Prior to using the free version of Decoda with NS2, I was able to define in Settings command line argument:
/game myMod
That doesn't seem to work anymore.
Someone said because Decoda is setting the working directory to the mod folder.
Is there a fix to this?
<b>Edit</b>: A work around is to just go back to Launcher and set the game to (none) and debug your mod in Decoda with the command line.
A small inconvenience I guess. But if anyone is having trouble, that's the solution for now.
/game myMod
That doesn't seem to work anymore.
Someone said because Decoda is setting the working directory to the mod folder.
Is there a fix to this?
<b>Edit</b>: A work around is to just go back to Launcher and set the game to (none) and debug your mod in Decoda with the command line.
A small inconvenience I guess. But if anyone is having trouble, that's the solution for now.
Comments
The "NS2" link in the launcher works perfectly, however.
Thanks for the quick reply.
<center><object width="450" height="356"><param name="movie" value="http://www.youtube.com/v/hZMdfl1pthE"></param><embed src="http://www.youtube.com/v/hZMdfl1pthE" type="application/x-shockwave-flash" width="450" height="356"></embed></object></center>
edit: by the way, the work around in the original post works for me as well.
When I run a game, it just says "Error initializing game at D:\Games\Steam\steamapps\common\natural"
I guess it's because of the space in the directory name "natural selection 2".
The workaround still works though (with -game instead of /game).
BUT Decoda DOES NOT SAVE THE COMMAND LINE SETTINGS IN THE deproj FILE.