Crash of engine on start

Gamestudio Links

Zorro Links

Data from CSV not parsed correctly
by dr_panther. 05/06/24 18:50

Help with plotting multiple ZigZag
by degenerate_762. 04/30/24 23:23

M1 Oversampling
by 11honza11. 04/30/24 08:16

AUM Magazine

Latest Screens

0 registered members (), 1,119 guests, and 0 spiders.

Key: Admin, Global Mod, Mod

Newest Members

Print Thread

Rate Thread

Crash of engine on start #376704 07/05/11 23:35 07/05/11 23:35
M Malice Unregistered
Malice Unregistered M	A teammate of mine is using a laptop with 2 displays at different resolutions. One the primary display and the other a TV display. Upon opening a small test program I wrote, he gets the standard windows dialog "This program has encountered a problem and need to close" but no engine error is reported and no error code is given. The program is running fine on PC's other then this laptop. Please tell me steps to resolve this problem. My teammate requires the second display do to vision problems. Thank you for your time Malice

Re: Crash of engine on start [Re: ] #376712 07/06/11 02:36 07/06/11 02:36
Joined: Nov 2007 Posts: 1,143 United Kingdom DJBMASTER Serious User
DJBMASTER Serious User Joined: Nov 2007 Posts: 1,143 United Kingdom	It may be a missing DLL. Try updating to the latest DirectX version.

Re: Crash of engine on start [Re: DJBMASTER] #376734 07/06/11 07:25 07/06/11 07:25
Joined: Jul 2000 Posts: 27,986 Frankfurt jcl Chief Engineer
jcl Chief Engineer Joined: Jul 2000 Posts: 27,986 Frankfurt	It's probably not the engine that crashed. Your team mate should install Gamestudio and run the script of your test program with -diag. This way you'll find the script line that crashes. If the crash happens in a video or audio DLL, the acklog gives details of the problem.

Re: Crash of engine on start [Re: jcl] #377258 07/11/11 14:21 07/11/11 14:21
M Malice Unregistered
Malice Unregistered M	JCL here is the log txt... If I read this right the problem is me teammate doesn't have a direct x 9 vid card . Right? But the log seems to show that the engine starts anyway. So why the crash? Quote: Log of A8 Engine 8.20.1 run at Mon Jul 11 09:55:49 2011 Jay on Windows NT/2000/XP version 5.0 Build 2195 Options -diag App: D:\DVDs in the making\movies\frame_rate_test.cd\frame_rate_test.exe in D:\DVDs in the making\movies\frame_rate_test.cd\ Author: Jay Young MM mixer opened DSOUND device opened DI interface opened Start Window opened(c) Conitec - www.3dgamestudio.com A8 Engine - Commercial Edition V8.20.1 - May 12 2011 Linking D:\DVDs in the making\movies\frame_rate_test.cd\frame_rate_test.exe... Mouse found USB Headphone Set opened Mobile Intel(R) 965 Express Chipset Family old device 13f9 detected 3D Device is not DirectX 9 compatible! D3D device Mobile Intel(R) 965 Express Chipset Family 13f9 selected........ Running FRAME_RATE_TEST.EXE. Main started at 1.105 fStraing_Filler_startup started fMouse_startup started fPanel_Placer_startup started fPanel_Scaler_startup started fCam_startup started D3D_Init Window: 800x600 -> Window: 1x800x600x32 Video memory found: 302 MB Main loop at 1.164.... 1st frame with 302 MB at 1.167 LevelInit at 5.068 1 entities 1 cameras 0 lights 0 sounds 0 paths 0 lmaps 0 textures...ok LevelReady at 5.102

Re: Crash of engine on start [Re: ] #377355 07/12/11 14:36 07/12/11 14:36
Joined: Jul 2000 Posts: 27,986 Frankfurt jcl Chief Engineer
jcl Chief Engineer Joined: Jul 2000 Posts: 27,986 Frankfurt	This is likely a DirectX crash. Your frame rate test will probably not work on that notebook anyway, but simple games, such as some of the samples, also work with old 3D cards. The crash is either caused by an issue with the DirectX installation or driver, or it's simply a memory problem. DirectX usually crashes when memory runs low. Your teammate should check if he can run some of the samples, and he should reinstall DirectX and his video driver, to be on the safe side.

Re: Crash of engine on start [Re: jcl] #377368 07/12/11 15:33 07/12/11 15:33
M Malice Unregistered
Malice Unregistered M	Thanks JCL I will try those steps. I think it's a memory problem because at the time of the crash the tester is loading 100 ents via ent_create and using the ent_terrain_place function for level.c.

Moderated by old_bill, Tobias