When you get error messages, examine in which files they happen. This gives you hints for the reason of the problem - like missing or outdated files in your installation. I have not enough information to help you here, but you should be able to fix this, at least by re-installing 6.40 and re-updating to 6.60.

If you can't get it to run, describe your problem in "Ask Conitec" - I'll help you then. This thread is about A7 and your C-Script problems are probably unrelated.

For system variable like video_mode, video_depth : put
them inside a function and without the keyword "var".

For user define "global" variables like var myVar, yourVar... etc. put
them outside any functions just like usual. See an exammple from liteC
Workshop->Workdshop 23->script23.c.

I hope I can help to make it clear.

No no, I will explain it once more;
- I made a level in A6 (ofcource with C-Script).

Part of C-Script:
var video_mode=8; //1024 * 768 screen resolution
var video_depth=32; //D3D mode
var video_screen=1; //1=full screen, 2=window

- I copied that level to A7.
- I did not change anything in C-Script.
- I did not change the script into Lite_C.
- I build the level with A7.

When run, the part of C-Script (see above) does not affect the screen.
video_mode keeps default (6)
video_screen keeps default (2)

Now that is the problem, In A6 it works perfect and in A7 it does not.
Please help.

Frits: I understood your problem, but I don't have a ready solution because I have not enough information. When you use C-Script, there is no difference between A7 and A6.60. A7.03 just uses the very same A6 engine version as A6.60. Video_mode just works as before, as you can easily see when you start any C-Script project with A7. Almost all projects use video_mode.

You had reported script errors, so I think something's wrong with your installation anyway - see my answer above. Or it's a strange A7 error that no one else except you has experienced so far.

I'll be away next week, so I can't help you in the next days. But after my return - if your problem has then not meanwhile fixed itself - we'll walk through your installation process and have a closer look at your error messages. I think we'll find out what's wrong.

Thanks jcl, but the errors I have mentioned are not in my level but in the Techdemo.
But I will design a new level under A7, maybe something goes wrong when you copy an A6 level.

EDIT
I have made a brand new level in A7 and add some C-Script for the screen and a player.
Even now the screen keeps its default values and will not change to my desired screen resolution and to full screen.
I have no clue at all why this is not working in A7, I have no problem with this in A6.

frits, are you sure you started the right sed? if you use winXP and the recent used programs, it could be you started the wrong sed and thus not the right engine, just because the icons change.

it just happened to me, i got a black window , no errormessage.
maybe thats what is happening to you?

Yes, I use the right SED and I don't have the problem you described.

hi
i have a question about a7. ist the A7 engine going to be faster then tha A6 engine??
sam

Hi jcl, your back I see.
As a follow up for my problem I made a hollow cube in A7, put in a position and made a simple script in C-Script;
var video_mode=8; //1024 * 768 screen resolution
var video_depth=32; //D3D mode
var video_screen=1; //1=full screen, 2=window

When I build and run this the video_mode keeps its default value = 6 and the video_screen also keeps its default value = 2.

So my A7 does not react att all at the vars.
Can you shed any light on this, is it me or is it A7?

I don't know - I admit that your problem doesn't make any sense to me.

No one else had any problems with video modes so far, but on the other hand I can't see how someone can make a mistake with simply setting a video mode. Maybe it's a bug that for some reason only occurs in your configuration.

I suggest that you follow my first advice and check whether the problem only happens with your own scripts, or also with normal projects like techdemo. If so, please post about it on "Ask Conitec" or the bug forum and include your complete script and the acklog. That could give us a hint what's happening. I think we'll get this sorted out quite soon.