Crash On Exit + Request.

Problems with the Windows version of Darwinia

Moderators: jelco, bert_the_turtle, Chris, andy, John

User avatar
Totallyout2lunch
level2
level2
Posts: 179
Joined: Tue Oct 29, 2002 5:33 pm
Location: Dorset, UK.

Crash On Exit + Request.

Postby Totallyout2lunch » Tue Sep 07, 2004 9:20 pm

The game crashed on ESC key, producing a black box. Im posting it here, as I do not think its to important to post on class B/A.

Also I am testing this on a Laptop, I do not have a mouse wheel, so would request a a key to skip the help, thus cycle to next point. I have extra mouse buttons for reading text so these could be used for the mouse wheel type input, or to add a key combo to scroll up and down.

-------------------

=========================
DARWINIA BLACK BOX REPORT
=========================

VERSION : win32-demo-beta2
ERROR : 'Darwinia has been forced to shutdown.
Please post your 'blackbox' file to the Darwinia forums,with a description of the error you encountered'

=========================
===== SYSTEM REPORT =====
=========================

SysInfoGenVersion: 2
CpuVendor: GenuineIntel
CpuModel: x86 Family 6 Model 9 Stepping 5
Num Processors: 1
Country: United Kingdom
Language: English
Num sound devices: 2
Primary sound device: VIA AC'97 Audio (WAVE)
Graphics Card: Intel(R) 82852/82855 GM/GME Graphics Controller
Operating System: Windows XP
Computer Name: ALIENWEAR



=========================
====== USER DATA ========
=========================

USERNAME : Totallyout2lunch
EMAIL : Totallyout2lunch@hotmail.com

=========================
====== PREFERENCES ======
=========================

ServerAddress = 127.0.0.1
BypassNetwork = 1
SinglePlayer = 1
IAmAServer = 1
TextLanguage = english
TextSpeed = 15
HelpEnabled = 1
SoundLibrary = dsound
SoundDriver = -1
SoundMixFreq = 44100
SoundMasterVolume = 255
SoundChannels = 16
SoundHW3D = 0
SoundSwapStereo = 1
ScreenWidth = 1024
ScreenHeight = 768
Windowed = 1
RenderLandscapeLighting = 0
RenderLandscapeOverlay = 1
RenderLandscapeDetail = 1
RenderWater = 1
RenderWaterDetail = 1
RenderClouds = 1
RenderNegative = 0
RenderPixelShader = 0
RenderSmoothLines = 0
RenderHighDetailVirii = 0
RecordDemo = 0
DemoFrameRate = 25
StartMap = mine
TestHarness = 0
ShowIntro = 0

=========================
====== STACKTRACE =======
=========================

retAddress = 00410729
retAddress = 0045D555
retAddress = 0041475F
retAddress = 0046AED2
retAddress = 7C816D4F
retAddress = 00000000
Check me out!!!
Windows Leads to anger, Anger leads to Hate, Hate Leads to Linux...
Andcarne
level4
level4
Posts: 675
Joined: Mon May 26, 2003 1:44 am

Postby Andcarne » Wed Sep 08, 2004 2:01 am

If it's a crash, it should go in Class A.
User avatar
Soulkeeper
level3
level3
Posts: 457
Joined: Sun Jun 27, 2004 3:04 pm
Location: Dorset, UK
Contact:

Postby Soulkeeper » Wed Sep 08, 2004 10:48 am

Also, this is Class A bug, any form of crash goes there. Also, you will find that this bug is well documented in the Class A forums.
- I see your destiny, I control your fate. I am the Guardian Soulkeeper. -
rob_quill
level1
level1
Posts: 69
Joined: Fri Apr 16, 2004 7:41 pm

Postby rob_quill » Wed Sep 08, 2004 12:37 pm

Also, in class B there is a thread about not having a mouse wheel, if you wanna make any suggestions there.

Rob
User avatar
Totallyout2lunch
level2
level2
Posts: 179
Joined: Tue Oct 29, 2002 5:33 pm
Location: Dorset, UK.

Postby Totallyout2lunch » Wed Sep 08, 2004 5:38 pm

Thanks guys.

Have posted and diagnosed the bug on the thread on the class a forum, I can replicate it anytime.

IV should be able to replicate it and fix it now.
Last edited by Totallyout2lunch on Thu Sep 09, 2004 5:22 pm, edited 2 times in total.
Check me out!!!
Windows Leads to anger, Anger leads to Hate, Hate Leads to Linux...
User avatar
Phydaux
level5
level5
Posts: 1615
Joined: Tue Feb 26, 2002 3:00 am
Location: Cardiff, UK
Contact:

Postby Phydaux » Wed Sep 08, 2004 7:47 pm

FYI

The classes of bugs are for the types of bug, not the severity (or importance) of the bug. On the forum index it tells you of the different types of bugs that go into each class.

Beta Class A Bugs: Crashes, hangs, fatal errors
Beta Class B Bugs: Incomplete levels, logical errors
Beta Class C Bugs: Graphical Glitches, Typos

Also the IV team requested that each bug have a seperate topic, so that when a bug is fixed, the topic can be closed. Having multiple bugs in the same topic can create a bit of a problem. ;)

If you can't find a topic about a bug you've found, create a new one. It's better to have multiple threads, than everyone being too shy, and leaving loads of bugs unchecked. (remember there are stick post at the top of each forum, and the ever useful search function.)

Return to “Windows Issues”

Who is online

Users browsing this forum: No registered users and 6 guests