A7 to A8

Posted By: Truth

A7 to A8 - 05/30/12 16:39

Hi, i am trying to move my project from A7 to A8 but i have started using WDL C-Script and can't change to Lite-C so i am having a few problems;

1. str_cpy seems to not work anymore, im not sure if it's abandoned but what is the new alternative?

2. I think it's caused by the first problem but when i try to run my game i get 'script_crash in main: level_load(level_str)'

3. I know the old physics system 'phent' has been replaced by physix, but to use it i have to include <ackphysx.h> which is lite-c is there anyway to use this with C-Script?

Thanks
Posted By: Wjbender

Re: A7 to A8 - 05/30/12 17:02

1 + 2 = if we were to see some code we(meaning community)
could perhaps help with ease

3= i have no idea even what c-script is but if its a a7 version only i think you could not use physx with a7 (not sure as i dont know a7/c-script) but from my point of view
i dont think so..
Posted By: FoxHound

Re: A7 to A8 - 06/06/12 18:49

C-script is A6 and older but could work with A7. However it would be faster to start the code from scratch than to try to sort each change as there are so many differences and so much to learn when going in Lite-c. I took a game and changed it bit by bit to work with lite-c and just wasted my time.

Str_cpy works just fine in lite c. If your level doesn't load correctly something may be wrong with the level itself or the string name you gave it to load.
Posted By: Error014

Re: A7 to A8 - 06/07/12 21:58

Oh man. Okay, so str_cpy still works. But! Lite-c is case sensitive. Perhaps you wrote "Str_cpy", or "str_Cpy", or any such things? Basically, make sure that "str_cpy" is all small letters.

Possible other thing: If you use the string of a text-object ("mytext.string", that kinda stuff), then please note that the structure of texts changed when we went from C-Script to Lite-C, and you'd have to replace that with "(mytext.pstring)[0]".

Or perhaps it's something entirely different!
But this is as far as we can help you given the rather cryptic original post. "seems to not work" is, sadly, rather difficult to pin down. What's the error message, and what's your code?



I'll just assume that your assumption is true and 2) will solve itself after we took care of 1). As far as 3) is concerned, I cannot help - haven't used the physics engines.
© 2023 lite-C Forums