strange... only since 1182 has this icon changed in all my versions
(the romview icon)
Acting weird in other ways too since I moved up to 1182.
It flashes my desktop several times and it takes the icons a while to come back.
has crashed a couple of times on exit.
turns my windows explorer screen black.
saves very slowly with a manual save, but the auto saves seem pretty quick.
seems like it was compiled with a different compiler from past experiences.
In the player the screens seem pretty jerky scrolling from one to the other.
Looks like your Icon cache got corrupted (does happen from time to time). A google search should help you erase your icon cache so a new one is created thus fixing all icon problems in Windows.
well.... ZC done it ;O)
1154 was a much better acting version, I'm sorry I upgraded
more....
the allegro log
ZQuest v2.11 Beta (Build 18)
Allocating tunes buffer (16.00k/16.00k)... OK
Allocating map buffer (1.11M/1.12M)... OK
Allocating combo buffer (5.98k/1.13M)... OK
Allocating string buffer (10.62M/11.76M)... OK
Allocating door combo buffer (159.50k/11.91M)... OK
Allocating dmap buffer (234.00k/12.14M)... OK
Allocating combo buffer (1.62M/13.76M)... OK
Allocating color data buffer (314.11k/14.07M)... OK
Allocating tile buffer (511.88k/22.56M)... OK
Allocating tile grab buffer (511.88k/31.06M)... OK
Allocating trash buffer (97.66k/31.16M)... OK
Allocating item buffer (31.00k/31.19M)... OK
Allocating weapon buffer (2.50k/31.19M)... OK
Allocating guy buffer (28.00k/31.22M)... OK
Allocating combo class buffer (32.17k/31.25M)... OK
Allocating combo undo buffer (1.62M/32.87M)... OK
Allocating new undo tile buffer (511.88k/33.37M)... OK
Resetting new tile buffer...OK
Allocating file path buffers (14.00k/33.38M)... OK
Initializing Allegro... OK
Loading data files:
Fonts.Dat...OK
ZQuest.Dat...OK
QST.Dat...OK
SFX.Dat...OK
OK
Initializing sound driver... OK
gfx mode set at -1 8bpp 800 x 600
Loading Quest...Decrypting...okay.
Opening...okay.
Reading Header...okay.
Made in ZQuest 211 Beta 18
Reading Rules...okay.
Reading Strings...okay.
Reading Doors...okay.
Reading DMaps...okay.
Reading Misc. Data...okay.
Reading Misc. Colors...okay.
Reading Game Icons...okay.
Reading Items...okay.
Reading Weapons...okay.
Reading Maps...okay.
Reading Combos...okay.
Reading Combo Aliases...okay.
Reading Color Data...okay.
Reading Tiles...okay.
Reading Tunes...okay.
Reading Cheat Codes...okay.
Reading Init. Data...okay.
Reading Custom Guy Data...okay.
Reading Custom Link Sprite Data...okay.
Reading Custom Subscreen Data...okay.
Reading FF Script Data...okay.
Reading SFX Data...okay.
Reading Item Drop Sets...okay.
Done.
Loading Quest...
Decrypting...okay.
Opening...okay.
Reading Header...okay.
Made in ZQuest 211 Beta 18
Reading Rules...okay.
Reading Strings...okay.
Reading Doors...okay.
Reading DMaps...okay.
Reading Misc. Data...okay.
Reading Misc. Colors...okay.
Reading Game Icons...okay.
Reading Items...okay.
Reading Weapons...okay.
Reading Maps...okay.
Reading Combos...okay.
Reading Combo Aliases...okay.
Reading Color Data...okay.
Reading Tiles...okay.
Reading Tunes...okay.
Reading Cheat Codes...okay.
Reading Init. Data...okay.
Reading Custom Guy Data...okay.
Reading Custom Link Sprite Data...okay.
Reading Custom Subscreen Data...okay.
Reading FF Script Data...okay.
Reading SFX Data...okay.
Reading Item Drop Sets...okay.
Done.
Saving Quest...
Writing Header...okay.
Writing Rules...okay.
Writing Strings...okay.
Writing Doors...okay.
Writing DMaps...okay.
Writing Misc. Data...okay.
Writing Misc. Colors...okay.
Writing Game Icons...okay.
Writing Items...okay.
Writing Weapons...okay.
Writing Maps...okay.
Writing Combos...okay.
Writing Combo Aliases...okay.
Writing Color Data...okay.
Writing Tiles...okay.
Writing MIDIs...okay.
Writing Cheat Codes...okay.
Writing Init. Data...okay.
Writing Custom Guy Data...okay.
Writing Custom Link Sprite Data...okay.
Writing Custom Subscreen Data...okay.
Writing FF Script Data...okay.
Writing SFX Data...okay.
Writing Item Drop Sets...okay.
Encrypting...okay.
Removing timers.
Cleaning aliases.
Cleaning subscreens.
Cleaning sfx.
Cleaning script buffer.
Cleaning qst buffers.
Cleaning maps.
Cleaning tile buffers.
Cleaning misc.
Cleaning midis.
Cleaning undotilebuf.
Cleaning datafiles.
Cleaning bitmaps...... OK.
Well I did do a lot of testing in zc and it seems to run much better now, and also much faster for large scripts. ZQuest is having some problems at the moment, I haven't figured them out yet. I don't mind switching back to g++ if the problem is out of my control (I'd still like to fix the underlying problem instead of just sweep it under the rug) or these issues don't get resolved by the next build.
The crash once again is credited to allegro though, and if there were no other bugs I'd actually like to take a look at it and see if it's fixable without breaking allegro. It's just not very high priority right now considering it might be a fools errand and that time is better spent with more pressing issues. I've noticed that the allegro hang doesn't happen to everyone. I myself have never gotten it.
...What do you mean jerky?
Presumably stutter as though he is running at something other then 60hz display and has vsync on.
Gleeok wrote:Well I did do a lot of testing in zc and it seems to run much better now, and also much faster for large scripts. ZQuest is having some problems at the moment, I haven't figured them out yet. I don't mind switching back to g++ if the problem is out of my control (I'd still like to fix the underlying problem instead of just sweep it under the rug) or these issues don't get resolved by the next build. The crash once again is credited to allegro though, and if there were no other bugs I'd actually like to take a look at it and see if it's fixable without breaking allegro. It's just not very high priority right now considering it might be a fools errand and that time is better spent with more pressing issues. I've noticed that the allegro hang doesn't happen to everyone. I myself have never gotten it.
...What do you mean jerky?
jerky... like it's consuming a lot of resources
this wasn't crashing like this on me until 1182
it crashed zquest 4 times yesterday and the player once
the player crashed just as I chose the quest to play. and zquest on exit every time.
this build is acting worse for me then any since I've returned.
If you're on XP please follow the instructions in this post the next time you suffer a crash and I'll see what exactly is causing it.
It crashes several times a day now
that color thing that used to whack out the colors once in a while is now a daily thing too.
this version is just bad news.
I'll try what you ask.
ok Jman, sending an addy in your PM
Gleeok,
you put me in the position here now that made me quit before, changing that DLL was a BAD idea.
Now I can't go forward and and can't go back.
I have very little to go to finish this quest and I'm stuck in lalashit again.
the 1154 was 100% better than the 1182, but I have completed too much to start back there and redo it all.
Let me know when you get something half way stable and maybe I'll try to finish this up, right now it's more irritating than it's worth.
Yeah, it seems the Allegro DLL is being screwy as was said.
I'm going to release a new build using mingw and the old DLL and see if that restores some stability and fixes some of these problems we've been having. We'll have to examine the problem with the new DLLs internally.
EDIT - Just noticed Gleeok may have fixed it. I can't be sure alone, so tell me if those issues continue to manifest and if so, I'll restore the old DLL like I said.
Freedom wrote:
Gleeok,
you put me in the position here now that made me quit before, changing that DLL was a BAD idea.
Now I can't go forward and and can't go back.
I have very little to go to finish this quest and I'm stuck in lalashit again.the 1154 was 100% better than the 1182, but I have completed too much to start back there and redo it all.
Let me know when you get something half way stable and maybe I'll try to finish this up, right now it's more irritating than it's worth.
Freedom: What do you think Dark Dragon used when he was putting out builds? Please do me a favor and just put 1182 in the trash and try the *hopefully* fixed build. If 1182 is crashing for you DO NOT USE IT. I'm not trying to play a practical joke "haha zc crash lol" here. I'm simply trying to get zc to the point (eventually...) where we won't even see much of these threads on how zc and zquest crashed 20 ways 'till sunday. I'd honestly like to get this thing stable, and apparently the road to the finish line is not straight, but more of a twisting wacky obstacle course.
..Honestly, If only I could put on some magic glasses and look inside ZC, I'd probably see a leprechaun screwing a dodo riding a unicorn over a rainbow.
[edit] OK, I've been messing with zquest for a bit now and all the menus appear to be working correctly and the only odd issue I was getting which was the gui mouse from 1182 is gone also. I'm guessing that whatever bytes that were corrupted before aren't any longer. Let me know if there are any problems.
yea well that one was so bad it had me worried it was going to not just screw my quest up but my computer as well, it wasn't just the crashing.
Ah.. I think I was editing that post when you replied.
It shouldn't be possible for that to happen. Maybe on windows 95 it might want to do a reboot :P ..But XP is a pretty solid OS. Even if you do something stupid (True story XD) like try to consume all of it's memory at once it'll just do a dump and reboot. The chances of zc crashing your computer I would have to say is a fat zero.
yea well.... I do stupid shit all the time, ask anybody that knows me.
;O)
both the 1188 and the 1190 seem much better