assertion errors
#1
Posted 05 January 2010 - 05:48 PM
#2
Posted 05 January 2010 - 07:32 PM
Also, try opening a timed auto-save.
Edited by AgentLym, 05 January 2010 - 07:33 PM.
#3
Posted 05 January 2010 - 07:43 PM
Program:....
File:zsys.cpp
Line:217
Expression: Low<=high
For information on how your program can cuase an assertion
failer, see the Visual C + + documentation on asserts
(Press Retry to debug the application-JIT must be enabled) and when i go to hit retry zquest crashes.
what do i do. and the same thing comes up when i try to load auto time saved files of the same quest
confusing it confuses me to
Edited by DarkKing2, 05 January 2010 - 07:47 PM.
#4
Posted 05 January 2010 - 07:50 PM
Unfortunately, that's all the help I can offer! I've never had that problem before...
Are you running Vista?
#5
Posted 05 January 2010 - 07:57 PM
There must be a setting that must've been accidentally switched if it happens to timed saves and things... try the back-ups as well, just in case.
Unfortunately, that's all the help I can offer! I've never had that problem before...
Are you running Vista?
I never made backups i never had this problem eather
yes im running vista
#6
Posted 06 January 2010 - 04:14 AM
#7
Posted 06 January 2010 - 04:28 AM
#8
Posted 06 January 2010 - 02:22 PM
Edited by DarkKing2, 06 January 2010 - 02:23 PM.
#9
Posted 06 January 2010 - 02:48 PM
#11
Posted 07 January 2010 - 03:18 AM
http://www.shardstorm.com
Edited by Gleeok, 07 January 2010 - 03:19 AM.
#12
Posted 07 January 2010 - 02:17 PM
Download the latest version of zc and see if you still have any problems. (for windows that is 1121)
http://www.shardstorm.com
will that deleat my other quests?
#13
Posted 07 January 2010 - 03:28 PM
Edited by AgentLym, 07 January 2010 - 03:29 PM.
#14
Posted 07 January 2010 - 03:59 PM
#15
Posted 07 January 2010 - 04:28 PM
'Cause if ZQuest didn't work itself, then... there's definitely something wrong (or you're running Vista and need to disable Desktop Composition or something). If the quest still didn't work, then... I don't know what to say, except maybe one of the Devs around here will be able to manually hack into your quest file to fix the problem.
0 user(s) are reading this topic
0 members, 0 guests, 0 anonymous users