BladeDragon
|
Ok, this is kinda vexing to me, like V1, I just assumed WinV2 was a pure executable that ran any V2 game/code/program in Windows, however, after finally doing some V2 programming, I get nothing but a blank screen and a fade. After adding a global int I now get a WinV2 error that says "Error glbalint: glbalint()" or something. Is WinV2 requiring a completely seperate compilation with new System.VC commands, and such? Or is it that WinV2 is actually meant for V2.5 or V2.6 or something? Thanks all.
Posted on 2002-04-18 01:37:14
|
TheGerf
|
I think it compiles under V2.5. The only new command coming from V2 you really need to know would be autoexec()
Here's a quick intro:
http://www.vergesource.com/articles/view/8/
And here's the complete (to my knowledge) V2.5 vc reference:
http://www.vergesource.com/articles/view/29/
Of course, there's a couple changes in the WinV2 readme.
TheGerf, not just any gerf.
Posted on 2002-04-18 12:11:47
|
Omni
|
Well, I thought for myself that Winv2 would run any V2 game, and I was wrong. Also, for globalint, I know that in one version of verge, I think V2.5 beta 6 or something, one was required to put the terms "global" and "function" in front of declaractions. Maybe that is the problem, as I don't think Winv2 supports that. Maybe it doesn't register a problem, but that was what it reminded me of.
Also, most V2 games require that they be recompiled using the vcc that came with Winv2 before they will work under it, I believe, as V2 uses system.idx, V2.5 uses system.vcs, and Winv2 uses system.xvc for its compiled output. I don't think Winv2 supports system.idx or system.vcs, so I always recompile with the Winv2 VCC. But I could be wrong.
It is not wrong to not understand, for we are all ignorant, but neither is understanding pointless.
Posted on 2002-04-18 15:23:13
|
