290 replies to this topic

[Binx]

Yes, that's already done. The bombs/arrows physically leave the subscreen for some reason. Setting the counters to 99 every frame and the bomb/arrow item to true doesn't do anything either.

Easiest fix, in my opinion, is to place an unselectable dummy item that doesn't do anything in the same spot on your subscreen, then use a simple item bundle script to give you the dummy item as well as the real item. Then, any time you run out of MP, the real item disappears, but the dummy item stays, and the players wouldn't be able to tell the difference. this also gives you the freedom to "grey out", that is, alter the dummy sprite so that it appears faded and unselectable, items that can't currently be used.

[Moosh]

I just encountered a ZQuest crashing bug. Man, I thought those went extinct! I believe the cause of the crash is something pretty dumb too. Sometimes I give my scripts really long names just for the fun of it. In this case it was:

"ThisIsntRocketScienceButYouKnowWhatIs____ComboCycling"

 

Apparently I hit some sort of character limit for script names, because although it compiled just fine, as soon as I placed the script down on a screen, ZQuest crashed. I repeated loading and placing the script as a test. Same result.

 

Edit: Had a minor heart attack when overwriting the script because ZQuest hung a bit as if it was about to crash again. That'd be the dumbest thing possible to brick my quest with.

Edited by Moosh, 29 January 2016 - 09:45 AM.

[Saffith]

Is that something you can reproduce in another quest? I'm not seeing problems with it, but it may be a platform-specific thing.

[Timelord]

I just encountered a ZQuest crashing bug. Man, I thought those went extinct! I believe the cause of the crash is something pretty dumb too. Sometimes I give my scripts really long names just for the fun of it. In this case it was:

"ThisIsntRocketScienceButYouKnowWhatIs____ComboCycling"

 

Apparently I hit some sort of character limit for script names, because although it compiled just fine, as soon as I placed the script down on a screen, ZQuest crashed. I repeated loading and placing the script as a test. Same result.

 

Edit: Had a minor heart attack when overwriting the script because ZQuest hung a bit as if it was about to crash again. That'd be the dumbest thing possible to brick my quest with.

 

It'd probably be good to post the script itself, in the event that it isn't the script name that is causing it. That name is 53 chars long, and that doesn;t seem like a specific limit that would have been hardcoded.

 

Giiven that it has to do with combos, by any chance, does it do anything with LayerMap() , or any function that uses it? I know that setting LayerComboS() can cause crashes in 2.50.2, and that bug was already addressed for the next build.

 

@Saffith: It occurs to me that I never documented the char limit for ZScript names (script, variable, and otherwise). Do you know offhand what size is preallocated for this, maybe 255 chars, as a rule? I don;t even think there is a specific hard limit, but I could be wrong. I know the initial buffer for printLine[] is a size of 100, but charTemp[] is 512.

Edited by ZoriaRPG, 09 February 2016 - 08:37 AM.

[Moosh]

Is that something you can reproduce in another quest? I'm not seeing problems with it, but it may be a platform-specific thing.

Sorry for the late response. I didn't notice your reply until Zoria quoted me.

 

I just created a new FFC script, completely blank, just the name and void run() in a fresh new quest created in 2.50.2. It still crashes. This is tested on Windows 7, so maybe it's something like that bug where placing an item would crash ZQuest in Windows 8 except for once 8 fixed something?

 

It'd probably be good to post the script itself, in the event that it isn't the script name that is causing it. That name is 53 chars long, and that doesn;t seem like a specific limit that would have been hardcoded.

I'm 100% certain it's the name that's causing it because:

• This is a ZQuest crash, not a ZC one. ZQuest only has reason to look at the contents of the script during compilation, right? The crash occurs only after setting an FFC to use the script and closing the FFC editor window. All it should be reading there is the name, and then printing it to the screen in the upper left.
• After I shortened the script's name and changed nothing else, the crash stopped happening.
• I created a new script with the same name as the old one, just the name and the run function, and it crashed the exact same way as before.

[Zolias]

I don't know if anyone else is having this problem, but when I start up ZC, it flickers and has a thinner, dual image to the left.  I'm using Windows 8.1 x64, and I've tried many attempts to fix it, even going to compatibility for Windows 7, the color display, making it run as administrator, disabling high DPI... nothing worked.  I don't have a lot of time, especially to browse this thread, so if anyone has an answer to fix this, I'd highly appreciate it.  Thanks.

[Timelord]

I don't know if anyone else is having this problem, but when I start up ZC, it flickers and has a thinner, dual image to the left.  I'm using Windows 8.1 x64, and I've tried many attempts to fix it, even going to compatibility for Windows 7, the color display, making it run as administrator, disabling high DPI... nothing worked.  I don't have a lot of time, especially to browse this thread, so if anyone has an answer to fix this, I'd highly appreciate it.  Thanks.

 

I'm pointing Dimentio to this, as he had issues with 8.1. The latest Windows release that I run is 7.

 

I pretty much always suggest running a VM with XP when you can. It resolves a large number of problems.

Edited by ZoriaRPG, 16 February 2016 - 01:37 AM.

[Moosh]

I'm experiencing some very odd issues with high numbered palettes in ZQuest, in this particular case palette 111. Sometimes it bugs out and thinks it's palette 011 in the preview instead. Cycling to palettes with shift + , or . will cycle to palettes relative to palette 011. Toggling light will make it visually display as palette 011 instead. Palette cycling data does not appear to get saved at all when I close ZQuest. This seems to happen for any palette 100 and up.

[Mister Snooze]

I do not know if I am placing this question in the proper place, but I have a question about Windows 10. I cannot play any games in this computer. Is a fix for this problem coming or am I the only one

[Timelord]

I do not know if I am placing this question in the proper place, but I have a question about Windows 10. I cannot play any games in this computer. Is a fix for this problem coming or am I the only one

Do you mean that you can't load any ZC quests, or do you mean any other software?

[Mister Snooze]

Do you mean that you can't load any ZC quests, or do you mean any other software?

Can;t load any ZC quests, at least not so that they are able to be viewed properly. When I start up ZC, it flickers and has a thinner, dual image to the left.

Edited by Mister Snooze, 17 February 2016 - 05:38 PM.

[Norzan]

I do not know if I am placing this question in the proper place, but I have a question about Windows 10. I cannot play any games in this computer. Is a fix for this problem coming or am I the only one

Are you loading them from the right directory? You can change the quest directory in Misc->Quest Directory.

 

Also yeah, that strobe light effect happens when you play in Windows 10 with fullscreen. That annoying effect goes away in window mode. 

[Mister Snooze]

Also yeah, that strobe light effect happens when you play in Windows 10 with fullscreen. That annoying effect goes away in window mode. 

Windows mode is much to small to play on, even full screen does not open fully in Windows 10 like it did in Windows 7

[coolgamer012345]

Windows mode is much to small to play on, even full screen does not open fully in Windows 10 like it did in Windows 7

Have you tried making the resolution of ZC larger (when it's set to be in windowed mode)? You can set it from within the ZC launcher (and I think ag.cfg, if the launcher doesn't work for some reason; I'm guessing "resx" and "resy" under "[zeldadx]" are the values you'd need to set, but I didn't try it)

[Mister Snooze]

Have you tried making the resolution of ZC larger (when it's set to be in windowed mode)? You can set it from within the ZC launcher (and I think ag.cfg, if the launcher doesn't work for some reason; I'm guessing "resx" and "resy" under "[zeldadx]" are the values you'd need to set, but I didn't try it)

Pardon my ignorance but I am not sure how to make ZC larger in window mode, the only thing I see in ZCLauncher is screen resolution. It seems like setting the window mode to a larger size would be my solution as the game does play in window mode. Thank you for your help