SHP Forums

So having found, what may be an oversight in the Dagger of Amon Ra, and having messed with the AGI editor (to some degree) for machinima purposes, I thought it'd be fun to look at the SCI code for Dagger of Amon Ra. So I went to SHP - and found this:

http://sci.sierrahelp.com/Tools/SCITools.html

Which has 3 different versions of the SCI Studio (3, 4, and 150?)

Doing some googles, I found this:
http://sciprogramming.com/scitools.php?id=9

Which says: Last Updated: Mar 05, 2003 - which seems like a long time ago, when digging around resulted in this:

http://sourceforge.net/projects/scistudio/

Which shows: Last Update: 2013-05-02

So... figured I'd ask (I know several people have poked at the SCI Studio) - if I wanted to mess around with the Dagger of Amon Ra, which one should I use? (The one that has the easiest interface, even if it's less powerful, will be ideal for someone like myself, whose not touched the SCI Studio stuff before!)

SCI Studio and SCI Companion only work with SCI0. LB2 is SCI1.1. The latest stable version of Studio was 3.0. Brain was working on a version of Studio that would work with SCI1 (the first VGA games), but it is incomplete. MI was playing around with it and got it to compile, but it still needs so much to be done. Enrico Rolfi's TraduSCI can do SCI1.1 to SCI2, but us limited to message, view and pic resources. Its aim is for game translation. Aftertaste is plugging away at porting the SCI tools to C#, which opens up a number of intriguing possibilities. There are a number of things going on behind the scenes.

Put simply, even if SCI Studio support SCI1.1 games right now you couldn't mess with much besides art and sound (the latter to a much lesser degree). However, I myself have been trying to create a modification of SQ1VGA to alter the visual style to more closely resemble the original SQ1, but lack of tools makes it difficult. I'm restricted to editing VIEWs only, and even then I'm stuck between using two different view editors, each with their own problems which has stopped what little progress I could make in that area as well. For instance, one view editor has problems with saving the palette properly, while the other one resets the origin point to 0 all the time with no way to fix it without using the other VIEW editor and messing up the palette again.