Questions about Lite-C

1: Lite-C can use OpenGL. Can I use my Game Programming Gems books based on OpenGL?
2: Will Lite-C replace C-Script in the near future?
3: Is it better to start learning Lite-C now instead of C-Scripting or do I need both?
4: Can I do everything with Lite-C language I can do with my A6 Commercial edition?
5: Are A5/A6 plugins suported with Lite-C?
6: How many physics objects are available in Lite-C?
7: How many players may connect in multiplayer with Lite-C?

On the forum I read people talk about with the Lite-C language you are able to create -small- games/app with the Lite-C language. What does it mean? You can't create big games at least as big as one can do with A6?

Do I really need Lite-C if in the future i'll upgrade to A7 commercial? Or is it just a handy tool to extend my current possibilities with A6 and upcomming A7!?

Thank you.

can I use my Game Programming Gems books based on OpenGL?

It depends on the code you want to write. OOP features arent supported except overloading.

Will Lite-C replace C-Script in the near future?

CScript will be supported in the future but will be abandoned in some time. I would suggest to start with liteC as soon as you can.

Is it better to start learning Lite-C now instead of C-Scripting or do I need both?

Start learning liteC. Or even better: learn liteC and C side by side. They are somehow identically (somehow! not 100%).

Can I do everything with Lite-C language I can do with my A6 Commercial edition?

Yes. ... if you own the commercial edition. If you own a lower version (or pro), its different

Are A5/A6 plugins suported with Lite-C?

Yes. Though, you should take care of "old" instruction interfaces to those DLLs. LiteC has a lot of implicite casts but in some case I could imagine that the variable types of arguments and you liteC code could be incompatible. So you should learn about casting before you use extensively plugins. In theory, though, there should be no problems at all.

Btw: DLL plugin development is now much easier than with CScript!

How many physics objects are available in Lite-C?

LiteC doesnt change engine edition limitations. If you own the commercial edition, you have to remain on 1 physics object.

How many players may connect in multiplayer with Lite-C?

See previous question.

On the forum I read people talk about with the Lite-C language you are able to create -small- games/app with the Lite-C language. What does it mean? You can't create big games at least as big as one can do with A6?

LiteC isnt limitating how big your game is (how do you determine how "big" a game is? I heared people saying Max Payne is a small game because its only 10 hours of play ). LiteC is *just* a new programming language and vice-versa it makes it possible to create even bigger games than before with CScript, so to say.

Do I really need Lite-C if in the future i'll upgrade to A7 commercial?

No, you can rely on CScript if you like.

Or is it just a handy tool to extend my current possibilities with A6 and upcomming A7!?

It is no tool. It is a programming language. But if you like to call it a tool, yes, indeed, it extends your possibilities

Will there be a new SDK to use with Lite-C?

HeelX thank you for taking the time to answer all my questions.

All the best,

Dusty

standalone lite-c does support full physics no multiplayer, however, so if u hav an edition that can do better than that, u can use lite-c in conjunction with it i think.

julz

So lite-C allow full access to render to texture also ?
Any limitations , caus it's simply a language wrapper to 3D things like TrueVision3D !

Another question... In the C-Lite ebook...
What exactly means "Classes & methods" = "partially"?

Quote:

---

caus it's simply a language wrapper to 3D things like TrueVision3D

---

I'm not entirely sure how you're drawing that conclusion. It's neither a wrapper, nor is it like TrueVision3D.

lite-C is practically it's own language. The DX9, and OGL, capability is programmed *using* lite-C (see opengl.h, and d3d9.h inside the include folder).

hack-panther:
It means that *some* classes and methods from other systems (d3d, ogl, etc) can be used through overloading. I think there's a lite-C workshop that discusses overloading using D3D as an example.

FixxeR