I made a simple testlevel, a hollow cube with a position in it.

A verry simple scriptfile and the logfile;
Code:

---

// test-screen.wdl

var video_mode=8; //1024 * 768 screen resolution
var video_depth=32; //D3D mode
var video_screen=1; //1=full screen, 2=window

string start_level=<test-screen.wmb>;

// the main function is started at game start
//-------------------------------------------
function main()
{
	//set warninglevel
	warn_level = 2;	// announce bad texture sizes and bad wdl code
	
	//starting mouse mode (0, 1, or 2)
	mouse_pointer=0;
	mouse_mode=0;
	
	//now load the level
	level_load(start_level);

	wait(5);	//let level load
}


/*
log file
-dialog test-screen.$$M -pal palette.pcx -writelog -noportals -preview -threads 2
-gamma 1.50 -jitter 8  -lmambient 50  -sizeshaded 236 -bound 56000  -fat 64  48  8
-narrow 32  32  0  
WMP to WMB Compiler V7.01 (WMB6 BSP) [CPUs: 2]
  
Building fat hull ... ok 
Building narrow hull ... ok 
Building BSP tree ... ok 
Tesselating surfaces ... ok
Checking midpoints ... ok 
Placing 2 objects ..... ok 
Generating lightmaps .... ok 
Level size 610 units 
42 vertices 
40 visible surfaces 
1 textures 
Texture	space 43 Kb 
2 regions
Writing WMB file ... ok
 
Time:   1.0 sec
*/

---

What I found out is, when I run the level from WED the vars keep there default values and when I make a testrun from SED then it works perfect.
Next what I see in the logfile; Compiler V7.01
I have updated to 7.03, so I wonder, is this the right version or has the compiler a different number then WED?
Please help.

No, that's not a log file. If you have a screen size problem, I need a log for that problem, not messages from compiling some map. See "-diag" in the manual. The file you need to post is "acklog.txt".

Sorry, my fault.
I only can create a logfile in SED and make a test run, but then ofcource all is just fine;

LOGFILE acklog.txt
Log of A7 Engine 7.03 run at Tue Jun 26 08:53:01 2007
********* on Windows NT/2000/XP version 5.1 Build 2600
Options test-screen.wdl -eq -diag -te

App C:\Program Files\GStudio7\acknex.exe in C:\Program Files\GStudio7\testlevel_screen\
MM mixer opened
DSOUND device opened
DI interface opened
Start Window opened
© Conitec . Dieburg . San Diego . www.conitec.net
A7 Engine - Commercial Edition V7.03 - May 24 2007
Development version
Registered to: ***********

Mouse found
SB Audigy 2 ZS Audio [BCC0] opened
NVIDIA GeForce 7800 GTX pure T&L device 1ff9 detected
D3D device NVIDIA GeForce 7800 GTX 1ff9 selected
Compiling TEST-SCREEN.WDL - [Esc] to abort....
Running TEST-SCREEN.WDL
2 objects
D3D_Init Screen: 1024x768x32 -> Screen: 1x1024x768x32
Video memory found: 514 MB
Main started
Main loop.....
Level(test-screen.wmb)...cmap,0 ents,42 verts,0 lmaps,4 texs,40 faces,hull
Physics restarted...ok....ok
1st frame - 526336K... ok
Normal exit
Close level,DLL,objects
Free input,funcs,panels,defs,syns,views,strings,vars..ok
Free sounds,bmaps,fonts,hash,defs1,script..ok
Close dx,multimedia,D3D,engine,physics,nexus..ok
A7 Engine - Commercial Edition V7.03 - May 24 2007
© Conitec . Dieburg . San Diego . www.conitec.net
Registered to: **********
Close window

When I set -diag in WED (in the Map compiler --> Command-line options) it won't build and shows the following message;

Usage: MAPFILE -pal PALFILE[OPTIONS]
MAPFILE: filename $$M
PALFILE: filename. <PCX,RAW,BMP,LBM, or LMP>
OPTIONS:
-dialog: displays a dialog window for configuring options

?????????

Yes, according to the log everything's fine on your system.

I think your problem was that you were confusing the map compiler with the engine. The map compiler is the program that comes up when you click on "Build" if you want to compile a map. The engine is the program that comes up when you click on "Run" if you want to start your application. The map compiler window indeed has always the same resolution.

Yes, I understand that, but the problem still remains;
When I use Run in WED the screen keeps its default values.
When I use Testrun in SED the screen acts on the vars.

So, the problem still exists.
When I build the level I see in the build logfile; Compiler V7.01
In the acknex logfile is it V7.03
Maybe there is a problem?

The map compiler and the engine are two different programs and have different version numbers.

The engine won't care whether you start it from SED, from WED, with the left hand, or with the right hand. When you're having different results, you're starting different scripts. Check what you're starting from WED.

I think we can now leave it at that, as the problem is obviously not related to the software.

Like I said in earlyer posts, I made a complete fresh level in A7 WED and add a simple script in A7 SED;
Code:

---

// test-screen.wdl
var video_mode=8; //1024 * 768 screen resolution
var video_depth=32; //D3D mode
var video_screen=1; //1=full screen, 2=window

string start_level=<test-screen.wmb>;

// the main function is started at game start
//-------------------------------------------
function main()
{
	//set warninglevel
	warn_level = 2;	// announce bad texture sizes and bad wdl code	//starting mouse mode (0, 1, or 2)
	mouse_pointer=0;
	mouse_mode=0;
	//now load the level
	level_load(start_level);
	wait(5);	//let level load
}

---

So, when I start with WED or SED, I use the same script and I have nothing changed in the command lines.

How on earth can I and up with different results when I run the level in WED or SED?

EDIT; The acknex logfile is only generated when I start the level in SED and NOT when I start in WED.
Is this normal or should it be generated in WED also?


EDIT2: In Run level in WED now I see the Command-line options;
test-screen.wdl -nx30 -wnd -d hires
I thought maybe the acknex. txt file is not generated because it has no order to do so. So I inserted -diag, with a result;

Log of A7 Engine 7.03 run at Tue Jun 26 11:42:13 2007
********* on Windows NT/2000/XP version 5.1 Build 2600
Options test-screen.wdl -nx 30 -wnd -d hires -diag

App C:\Program Files\GStudio7\acknex.exe in C:\Program Files\GStudio7\testlevel_screen\
MM mixer opened
DSOUND device opened
DI interface opened
Start Window opened
© Conitec . Dieburg . San Diego . www.conitec.net
A7 Engine - Commercial Edition V7.03 - May 24 2007
Development version
Registered to: *********

Mouse found
SB Audigy 2 ZS Audio [BCC0] opened
NVIDIA GeForce 7800 GTX pure T&L device 1ff9 detected
D3D device NVIDIA GeForce 7800 GTX 1ff9 selected
Compiling TEST-SCREEN.WDL - [Esc] to abort....
Running TEST-SCREEN.WDL
2 objects
D3D_Init Window: 1024x768x32 -> 1024x746 failed
D3D_Init Window: 800x600x32 -> Window: 1x800x600x32
Video memory found: 516 MB
Main started
Main loop.....
Level(test-screen.wmb)...cmap,0 ents,42 verts,0 lmaps,4 texs,40 faces,hull
Physics restarted...ok....ok
1st frame - 528384K... ok
Normal exit
Close level,DLL,objects
Free input,funcs,panels,defs,syns,views,strings,vars..ok
Free sounds,bmaps,fonts,hash,defs1,script..ok
Close dx,multimedia,D3D,engine,physics,nexus..ok
A7 Engine - Commercial Edition V7.03 - May 24 2007
© Conitec . Dieburg . San Diego . www.conitec.net
Registered to: *********
Close window

1024x746 failed.
Why does it fail when I run in WED and it does not fail when I run in SED, strange?

EDIT3; I made some pictures of the command-line options;
Commandline in WED

Shot at 2007-06-26

Commanline in SED

Shot at 2007-06-26

If this is the commandline for the engine why don't they show the same options?
And what does -eq mean, I can't find it in the manual?

You answer your own question, but why do you enter different options? With -wnd you start in Window mode and your window can not be bigger than the desktop. Its garbage in, garbage out.

How did I answer my own question? I did not enter different options, the only option I entered is -diag, the rest of the options are already there.

Ergo, my question remains; so there are two option fields that effect the engine, why don't they have the same contents?
Now you can run the level with different options set in WED and SED, verry confusing.

Command line options are there since many years and you can learn everything about them in the manual under "Command line options".

Generally, I think it's a good idea when you make yourself a little more familiar with Gamestudio and its components. This would avoid such problems in the future and would save not only for me, but also for yourself a lot of time.