Moosh suggested I upgrade to 2.53.1_Win_Beta_51. It has crashed 4 times, something that has never happened to me in previous versions. He told me I best report it, here I am reporting it.
2.53.1_Win_Beta_51 Not Responding; Crashes
#1
Posted 06 June 2020 - 10:18 PM
#2
Posted 06 June 2020 - 10:18 PM
Edited by Magi_Hero, 06 June 2020 - 10:19 PM.
#3
Posted 06 June 2020 - 10:25 PM
#4
Posted 06 June 2020 - 10:34 PM
Is this both player and creator?
#5
Posted 06 June 2020 - 11:17 PM
Moosh suggested I upgrade to 2.53.1_Win_Beta_51. It has crashed 4 times, something that has never happened to me in previous versions. He told me I best report it, here I am reporting it.
Which programme is crashing: zelda.exe, or zquest.exe ?
Does any specific action precipitateit?
#6
Posted 07 June 2020 - 06:48 AM
Moosh suggested I upgrade to 2.53.1_Win_Beta_51. It has crashed 4 times, something that has never happened to me in previous versions. He told me I best report it, here I am reporting it.
Adding a quoted response here, in case you didn't see the above. I don't have enough information to proceed at all, although I can certainly provide more builds.
Basically, I need to know if ZQuest Editor crashes, if ZC Player crashes, or both; and if they do so immediately on opening a quest, or if they do so at a specific point, or on a specific action. From what I can see in the partial logfile, you opened ZQ Editor and loaded a quest. I see no data from ZC Player, and I do not know if that logfile is incomplete.
Should you feel up to it, you can log into openzc.org and attach any files that you need to posts there. The physical limit on file size is very large for the bug report forum, and they remain inline with the posts.
If only one quest causes this, then it'd help to have the file so that I can debug the programme. If you feel the need to send it in private, we will keep it in confidence.
If there is any additional software interfacing during the crashes, such as video capture, then I need to know what they are; and last, it is possible that it is a configuration file issue, or that you have mixed files.
As such, I need to know if you used the base, unzipped 2.53.1 distro, or if you copied files to a path with an older set of base files. If the latter, I need to know what version you were previously using. e.g. If you copied only zelda.exe, and zquest.exe, to an old 2.53.1 installation, then it could very well crash at start-up because it requires the newer zelda.dat file.
The older versions use a run-length-encoded (RLE) sprite for the splash screen, while the new builds use a bitmap sprite; and if you use a .dat file with the RLE, when trying to load a RLE and display as it as a bitmap, ZC will segfault.
I would like to resolve this, and document anything that I learn during the process, should it occur for anyone else.
If you need a specific version to resume work in the interim, we keep an archive of all older builds.
#7
Posted 07 June 2020 - 09:23 PM
PC specs could also be helpful I imagine. From what NJF described to me this was a frequent, seemingly random crash, possibly tied to tabbing out of the program window. I'm unsure if it was ZC or ZQuest that crashed. It started happening after I encouraged him to do a full update, so this is a fresh install of the latest build. I have not yet encountered any similar problems, worrying me that it could be an issue specific to his hardware, but I also haven't done as much work in TRIFORCE specifically. It might be a good idea to send a copy of TRIFORCE in private just to see if anything crashes while idling. It's a pretty big quest.
Edited by Moosh, 07 June 2020 - 09:25 PM.
#8
Posted 07 June 2020 - 10:29 PM
It's ZC, and usually when I leave the window to click on something else.
My hardware should be fine? What specifically in the hardware are you referring to?
Those are a lot of things to check, so I'll have to tackle them one at a time, it might take a few posts.
#9
Posted 07 June 2020 - 10:57 PM
This sounds exactly like what I experience. Are you using the GDI driver, or DirectDraw?It's ZC, and usually when I leave the window to click on something else.
#10
Posted 07 June 2020 - 11:36 PM
This sounds exactly like what I experience. Are you using the GDI driver, or DirectDraw?
How do I find out?
#11
Posted 08 June 2020 - 01:13 AM
How do I find out?
Take a screenshot of the ZCL, Drivers tab.
First thing to do, though, is edit zc.cfg, and set zc_win_proc_fix = 1 , then tell me if that fixes it. If it was already set to 1, then try it set to = 0.
#12
Posted 08 June 2020 - 10:39 AM
It was defaulted to avgddriverw. I'll try another one.
Update: It doesn't matter which one I pick, it seems as soon as I click out of the window, to work on zquest or something, it freezes because as soon as I return to ZC, it's already not responding. First sign being the music stops playing as soon as I click on zquest, which is an indicator that ZC has stopped responding because usually the music keeps playing.
#13
Posted 08 June 2020 - 11:45 PM
So I think I might have figured out something.
Moosh broke it.
Jk
Though it might be true, when I upgraded from 2.53 to 2.53.1, Moosh recommended I just copy over the cfg files from 2.53 to keep my own settings. I'm not sure how related this is, but I scrapped the old 2.53 upgrade and started again fresh with a backup of my TRIFORCE file (because sfx and everything seemed like it was starting to break).
Moral of the story.
Moosh broke it?
Too early to tell yet.
#14
Posted 09 June 2020 - 08:32 AM
So I think I might have figured out something.
Moosh broke it.
Jk
Though it might be true, when I upgraded from 2.53 to 2.53.1, Moosh recommended I just copy over the cfg files from 2.53 to keep my own settings. I'm not sure how related this is, but I scrapped the old 2.53 upgrade and started again fresh with a backup of my TRIFORCE file (because sfx and everything seemed like it was starting to break).
Moral of the story.
Moosh broke it?
Too early to tell yet.
So, out of the box, unzipped, it works fine?
Did you try toggling zc_win_proc_fix?
#15
Posted 09 June 2020 - 10:09 AM
I'll try it if it crashes again, it seems so far maybe that downloading with it's installed cfg files might have done the trick, copying over the cfg files from 2.53 might have broke it the last time, which if you think about, that would probably make sense of the cfg files are specifically designed to only work in the correct version. I haven't had problems since redownloading 2.53.1.
0 user(s) are reading this topic
0 members, 0 guests, 0 anonymous users