Problem when running

hi im using Ireng's acount to ask


the thing is when i run the map (after compiling)it closes automatically every time.....

i have win me, direct x 9c, geforece 2 mx (latest drivers)........


thanks

Run it with -diag, and post the acklog.txt.

Log of A6 Engine 6.60 run at Sun Sep 15 11:44:33 2002
Windows 95/98/ME version 4.90 Build 3000
Options -diag

App C:\WINDOWS\ESCRITORIO\STAGE1C[1].CD\STAGE1C.CD\STAGE1C.EXE in C:\WINDOWS\Escritorio\Stage1C[1].cd\Stage1C.cd\
MM mixer opened
DSOUND device opened
DI interface opened
Start Window opened
© Conitec . Dieburg . San Diego . www.conitec.net
A6 Engine - Commercial Edition V6.60 - May 20 2007

Mouse found
VIA Audio (WAVE) opened
NVIDIA GeForce2 MX/MX 400 pure T&L device 1ff9 detected
D3D device NVIDIA GeForce2 MX/MX 400 1ff9 selected
Compiling STAGE1C.WDL - [Esc] to abort.................
Running STAGE1C.WDL
15 objects
D3D_Init Screen: 1024x768x32 -> Screen: 1x1024x768x32
Video memory found: 111 MB
Main started
is_ai_Starter started
CameraFree01_Init started
CameraSelect_Init started
CameraTarget_Init started
Display00_Init started
Main loop..
WDL-Loaded:cameraFree01.wdl
WDL-Loaded:cameraSelect.wdl
WDL-Loaded:cameraTarget.wdl
WDL-Loaded:display00.wdl...
Level(demo.wmb)...cmap,24 ents,250 verts,2 lmaps,26 texs,212 faces,pvs,hull
Physics restarted...ok....ok
1st frame - 113664K.... ok

This looks as if your DirectX driver crashes when rendering the first frame. You have a very old hardware / software combination, but that's not the main reason for your problem - Win ME and Geforce 2 are still supported by A6 and A7.

Run the C-Script workshops and check out which one of them crash. Maybe it's a certain texture format that triggers a bug in your Geforce driver.

this is the link to the stage, maybe you can check it

http://rapidshare.com/files/55540289/Stage1C_1_.cd.zip.html


thanks

We don't need your level at the moment - we won't be able to reproduce your PC problem here unless you send us your PC .

It could be a driver or a hardware problem. But it would be interesting to learn at which point it happens. This was the reason why I suggested to run the workshops. They start with simple things like panels. If it's the mere amount of polygons that lets your driver crash, a hardware problem could be the reason - like a fault in a capacitor or memory chip.