290 replies to this topic

[TheLegend_njf]

Apparently, I dunno if this is a known thing, you can break a quest by selecting the Allow Ladder Anywhere flag. If you select this flag out of curiousity, it seems to from my experience to make the situation permanent even if you uncheck it. Once checked for the first time, I dunno if this is true or not, but your quest will be doomed to be stuck in "perma allow ladder" which means every screen that has such a combo will trigger ladder permanently.

 

Can somebody test this to confirm it to be true?

 

Update: Nevermind, I pointed the cause to something else. 

Edited by NewJourneysFire, 25 July 2016 - 09:21 PM.

[Rambly]

Geez, Norton won't let me says it is a dangerous website, ugh

Apparently that file is part of the Visual C++ Redistributable package, which you can download and install from a slightly less skeevy source (Microsoft themselves) here.
 

Apparently, I dunno if this is a known thing, you can break a quest by selecting the Allow Ladder Anywhere flag. If you select this flag out of curiousity, it seems to from my experience to make the situation permanent even if you uncheck it. Once checked for the first time, I dunno if this is true or not, but your quest will be doomed to be stuck in "perma allow ladder" which means every screen that has such a combo will trigger ladder permanently.
 
Can somebody test this to confirm it to be true?

Just tried it; unchecking it seems to work fine for me. You're probably already aware that Dungeon-type DMaps (and caves, I think, but don't quote me on that) always have ladders allowed even if the "Use Ladder" screen flag isn't checked, but if you weren't aware, there you go.

[Gleeok]

Geez, Norton won't let me says it is a dangerous website, ugh

After you download msvcp12.dll it'll ask you for msvc12.dll and whatever else thanks to a fine Micro$oft product line of tools and people that know why they use them.

You can just get the entire redist here:
https://www.microsof...s.aspx?id=30679

EDIT: I should try reading all the posts next time.. >_>

[SyrianBallaS]

Here is my solution to the windows 10 problem - create a virtual window (free) and install windows 7 (about $100 for DVD's)

 

Well there's three custom quests I've been able to play without problems so far (full screen seems to have the same bug for anything above 8-bit color even if it's selected), Legend of Lana DX, Umbral Cloud, and Tower of Courage. All the "n" quests work as well. It seems that scripted cutscenes at the beginning of a quest seems to crash upon registration. 

 

Two quest that crash instantly on me are Quest for the Hookshot 2 and Passage Through Time.

 

I think the biggest problem is that Windows 10 doesn't use the Win32 API by default.

Edited by SyrianBallaS, 26 July 2016 - 11:32 PM.

[ywkls]

Two quest that crash instantly on me are Quest for the Hookshot 2 and Passage Through Time.

 

 

Why, Windows 10? Why? I am happier than ever that I've yet to switch over to that, because apparently it hates ZC.

[Saffith]

I set up a Windows 10 virtual machine to try it on. I don't know if the same solution will work for real machines, but I did find a way to make it playable. In the [zeldadx] section of ag.cfg, set use_dwm_flush = 1 and throttlefps = 0, then run the game at 640x480. It's slightly slow, though - about 55 FPS. I don't know if that can realistically be fixed, but I'll look into it.

[Timelord]

I set up a Windows 10 virtual machine to try it on. I don't know if the same solution will work for real machines, but I did find a way to make it playable. In the [zeldadx] section of ag.cfg, set use_dwm_flush = 1 and throttlefps = 0, then run the game at 640x480. It's slightly slow, though - about 55 FPS. I don't know if that can realistically be fixed, but I'll look into it.

Even ag5 has had problems on Win 10. The changes are just too dramatic, compared to prior progressions of the Windows OS APIs.

I think the only sure fix, would be to make a custom, modified ag4 implementation.

( I neither expect, nor volunteer to make, that kind of radical overhaul. )

The speed issue may have been due to your VM though, so we'll need to wait for users with Win 10 to verify the findings.

Edited by ZoriaRPG, 29 July 2016 - 03:17 AM.

[Saffith]

The frame rate is an issue with how ZC uses DwmFlush(). I'm hoping it would be fixed by running it in a separate thread, which shouldn't be too hard to do.

The doublebuffer setting seems to work better that use_dwm_flush. triplebuffer would probably be better still, but the VM can't handle it.

Edit: Here's an experimental build that runs DwmFlush in a separate thread. Doesn't seem to work too well for me, but could I get a few people to try it out?
(Edit: Deleted)

It always uses DwmFlush, ignoring the ag.cfg setting, but the vsync setting under [zeldadx] may make a difference. Also, on 7 and Vista, I'd be interested in how it performs both with Aero enabled and disabled.

Another thing: when ZC is fullscreen and flickery, does the flickering stop when the menu is open or a dialog is up? Also on the AGN logo with the fire in the background?

[Saffith]

This is the only thing I'm waiting on for 2.50.3, so I'd really like answers as soon as possible.
To reiterate: do any of the following settings in the [zeldadx] section of ag.cfg make a difference when running fullscreen on Windows 10?
use_dwm_flush
vsync
doublebuffer
triplebuffer (may not be available even if enabled)
throttlefps (same as pressing F1)

Running at 640x480 may also be necessary.

Does the Armageddon Games look right? Does it flicker when the menu is open? Those both work right on my VM, but I have no idea if it would be the same on a real machine.

Does this modified build do any better or worse?
(Edit: Deleted)

[CSD]

The insane blue flicker I've been experiencing in full screen on normal 2.50.2 goes away with doublebuffer = 1 (F1 also does the trick, but it's not exactly playable). The Armageddon Logo or the menu open has never flickered. With the frame limit off I get 100fps in full screen where I would normally get 250fps windowed, regardless of doublebuffer -- that's probably just my computer being bad. I didn't notice any differences with the build you posted.

 

(I dunno but it sounded to me like other users were having worse problems than insane blue flicker on Win 10? Personally I've never had problems actually running the game or anything. One guy said Quest 4 Hookshot 2 crashes for him, but I played through that quest no problems...?)

Edited by CSD, 31 July 2016 - 08:06 PM.

[Gleeok]

Ah yes, the hardware buffering thing again. I remember now I was going to force enable double-buffering by default in the config options a while back but I just forgot about it. It used to be that up until windows 7 triple buffering mostly only worked in full-screen, but now that might be busted as well -- auto-detect is obviously becoming worse and worse with every new Microsoft release, and judging by the awful performance I wouldn't be surprised if they are just emulating old DirectX functionality at this point.


Also, just curious, but how does setting the color depth to 32 work out on win10?

[SyrianBallaS]

Done on Windows 10

Using the settings Saffith used allowed me to use full screen w/o flickering and no lag. It also starts up faster, before it would take a while for ZC to load.

use_dwm_flush = 1

doublebuffer = 1

 

Edit: This was not on the test-build

Edit2: Still like I said before some quests crash during name registration here's the error.

I got VC++ 05 to 15 (x86 and x64) redistributables so I don't know what's the problem.

 

@Gleeok

32-bit color looks the same on Windows 10 as it did on Windows 7. Really bad, the screen splits into four, all the menus are opaque blue, nonstop flickering.

Edited by SyrianBallaS, 01 August 2016 - 12:14 AM.

[Saffith]

Wait, during name entry? Do you mean when you're selecting the quest? At what point exactly is it that it crashes?


Maybe I'll enable double buffering by default on Windows. Anyone object? I say only on Windows because it seems to hurt performance on my system, and I suspect that has to do with the fact that software rendering is used on Linux.

[Timelord]

Wait, during name entry? Do you mean when you're selecting the quest? At what point exactly is it that it crashes?Maybe I'll enable double buffering by default on Windows. Anyone object? I say only on Windows because it seems to hurt performance on my system, and I suspect that has to do with the fact that software rendering is used on Linux.

Do you feel up to adding it to the launcher as a tickbox? How about reading the OS version, and doing it for 8 and above?

I also have a minor fix to roll into this update, that I'll get to you in the next few days. I'll send it to you by PM here, if you prefer that, or I'll just post it to the thread here.

Edited by ZoriaRPG, 01 August 2016 - 10:52 AM.

[CSD]

So I'm leaving the double buffer on from now on I guess. I didn't notice a performance hit.

 

I tried the colordepth=32 thing, and much of it is solid blue, but when you can see, there are 4 copies of everything. No nonstop flickering on my end (perhaps b/c of doublebuffer). Not sure how it's supposed to look, but probably not like that.