Source code for v0.4.3?

[Gullible Jones]

Hi all - not sure if this is the right place to ask, but I'm wondering how/if I can procure the sources for Vega Strike 0.4.3?

I'm thinking of starting an updated fork of this version, as I prefer its "old school" feel and lower resource consumption to what I've seen in more recent versions.

Thanks...

[ezee]

Hello !
I've found that for you :
https://sourceforge.net/p/vegastrike/co ... ike_0_4_3/

Just checkout with the commit version 13682 .
Edit : don't believe that, see below
That should (not ) work .

[gonzo]

Hello!

I'm going to be a bit more verbose...

Hi all - not sure if this is the right place to ask, but I'm wondering how/if I can procure the sources for Vega Strike 0.4.3?

I've never done this in subversion before (I use git more) but I'm trying it out now. Basically you just check out the code as usual but add the specific revision for your version.
In your case r9266:
https://sourceforge.net/p/vegastrike/co ... ike_0_4_3/


So, modifying the instructions in the Wiki to check out the code:
http://wiki.vega-strike.org/HowTo:Checkout_SVN

...you end up with running the commands:

Code: Select all

svn co -r 9266 https://svn.code.sf.net/p/vegastrike/code/trunk/vegastrike

Code: Select all

svn co -r 9266 https://svn.code.sf.net/p/vegastrike/code/trunk/data

Or if you're on the latest revision you can try out this:
http://stackoverflow.com/questions/1429 ... mmand-lineI haven't tried this though...


Edit: changed revision number... I'm still not 100% sure on which is the correct one!

[gonzo]

Just checkout with the commit version 13682 .

I got a bit confused here. 13682 is the latest as of today. The correct revision would be the one I'm quoting above, no?

[ezee]

ah ah ah ... let me try so with TortoiseSvn .
Back in ten ... nine ..

you are right , my version is wrong ( HEAD ) .

9266 is the good number here yeah , thx supa gonzo !

[Gullible Jones]

Cool, thanks!

(Now I just have to figure out where the heck to store all this stuff... Gitlab won't do for the data, too many binary files!)

[gonzo]

Gitlab won't do for the data, too many binary files!)

They have rules against it or they're not good at it?

[Gullible Jones]

Err. Hmm. Maybe not. I had thought Git was no good with binary files, but it looks like it may be no worse than SVN.

In any case, this stuff is rather hard to compile. Lots of C++ syntax errors, missing header files for obscure OSes, stuff like that...

Edit: have to ask, what's the deal with the seemingly random occurrences of ClassName::Method (instead of just Method) inside header files?

[gonzo]

Err. Hmm. Maybe not. I had thought Git was no good with binary files, but it looks like it may be no worse than SVN.

The reason I asked is I've heard other comments like that here so I got curious. I started a repository on GitHub with VegaStrike and binary content was no issure there.

In any case, this stuff is rather hard to compile. Lots of C++ syntax errors, missing header files for obscure OSes, stuff like that...

I had a no luck compiling it but the stuff is ten years old.

I didn't try VegaStrike until much later. What about 4.3 is it that you're after? Have you checked out any of the mods?

[ezee]

Edit: have to ask, what's the deal with the seemingly random occurrences of ClassName::Method (instead of just Method) inside header files?

Can you paste an exemple please ?

[Gullible Jones]

From what I recall playing it a while ago, it was friendlier to low-spec PCs, and had a more Wing-Commander-like feel. No beam weapons, for instance.

This is all kind of on a whim though to be honest. I figured I could sharpen my C++ skills on this; didn't realize it'd be so difficult to even get working.

Edit: @ezee - I managed to lose all my changes by accident, and will probably give up on 0.4.3 for now. (Wish the data files for these games were not so huge.) Here is an example though, from src/cmd/nebula_basic.h:

Code: Select all

class Nebula: public Unit {
protected:
        static void Nebula::beginElement (void * Userdata,const XML_Char * name, const XML_Char ** atts);
...
        void beginElem(const std::string&,const AttributeList&);
...

Having "Nebula::" there prevents it from compiling.

(Hmm. I think maybe someone did this for all static methods?)

[loki1950]

Welcome aboard Gullible Jones you will have a real pain getting 0.4.3 to compile with any newer version of gcc or even VS Windows side lots of the constructs in the old code just will not work as C++ is a moving target BTW there are beam weapons in 0.4.3 just not available in the stating system the latest release works well on the second machine mentioned in my sig block better on Linux than Windows(less OS overhead)

Enjoy the Choice

[ezee]

Very strange yeah ...
The code for version 0.5.1 is different :

class Nebula : public Unit
6 {
7 protected:
8 static void beginElement( void *Userdata, const XML_Char *name, const XML_Char **atts );

and this declaration has been mooved in nebula_generic.h :
http://vegastrikevo.sourceforge.net/veg ... ource.html

The version i'm working on is the 0.5.1 rc1 because it's the one that works good ( out of the box ) for windows . You could try it ( and help me to fix the source if needed ) at
vegaevo site : https://sourceforge.net/p/vegastrikevo/ ... _0_5_1_r1/

But i don't know in other os than windows wich files to checkout .
For windows , i checkout Data , win32 , vegastrike , vega-vc9

Perhaps "vegastrike" + "data" would be enough for you ?

[gonzo]

From what I recall playing it a while ago, it was friendlier to low-spec PCs, and had a more Wing-Commander-like feel. No beam weapons, for instance.

Have you played around with the settings? If you run vssetup (./build/setup/vssetup ) you tweek the the shaders for a more low-spec feel.