It amazes me, right now 2/3 of my client base is having me program in c-script still, not only does this take more time (costs them more) but limits a lot of there capabilities.

I understand that if you own a6 then it might be a money constraint, but a lot of people just would rather program in c-script than lite-c and im not really sure why.

Any insights?

maybe because of projects are started before lite-c existed... i dont see any logical reason besides having a6 or project was started years ago.

nope, all of them either im starting the basic frame work, or at least I know they've started withing the last 2 months.

We are still using C-Script for our upcoming project, and will likely stick with that through to the end of the year. This is because about 80% of our 3DGS-related code is in C-Script, and we have expertise there.

I'm hoping that Conitec will continue to support the language for as long as possible, as a transition away from that is likely to be a painful one for us. However, I realize that progress is inevitable.

Once C-Script is no longer viable, we'll have a decision to make between 3DGS/Lite-C, Unity3D/Boo/C#/JavaScript, and so forth.

Hey Ichiro. You guys need any more help over there yet?

back on topic: so for you its just an issue of a reusable code base that you already have?

shameless plug:
http://www.opserver.de/ubb7/ubbthreads.php?ubb=showflat&Number=270067#Post270067
you could also take a look at my python wrapper.

> Hey Ichiro. You guys need any more help over there yet?

We should be set presently (we have a pair of fantastic interns working away -- woo hoo!), but will let you know if we need more.

> so for you its just an issue of a reusable code base that you already have?

Assuming we're thinking the same way as your clients are, it's a combination of that and the fact that we have a good chunk of expertise invested in C-Script. Take this coming week, for example. We have a choice between:

* Learning Lite-C, converting tens of thousands of stable C-Script code into Lite-C, making possible modifications to our C++ code to work with that, setting a team up to debug it, creating workarounds for processes that need to be handled differently in Lite-C...
- or -
* ...or we could concentrate on completing the exclusive IGN/FilePlanet/GameSpy/D2D beta to reach their 3 million users.

We may eventually switch to Lite-C, but my team would murder me if we didn't focus on the latter for now. I'm guessing your clients are under the same constraints. That'll eventually change.

Ooh, and Ventilator's Python wrapper. That's hot stuff!

cool, well that helps a little, although most of the clients right now arent even near a release date, but I can definitely see the issue you have.

Lite-C is actually very easy and very similar to c-script. But I can understand if you don't need the features Lite-C offers, switching a large project takes time(about a month). This is using conversion tools, like BKreplacem. But if you were to start a new one, I would definitely use Lite-C.