We do not do this because we don't want something so important to be untrustworthy. When the client unfreezes, your savestate is complete. The hitching is a purposeful signal that it is safe to proceed.
From my understanding of it, most of the hitch is caused while the savestate file is written on disk. Is there a quick solution for this issue?
Why not uploading it to YT?
EDIT: Maybe it also works with a switch that uses a variable which is set when timer_control is changed.Language: cpublic void timer_control_AND_3_is_1() {state = divider_reg & 0b0000001000;} public void timer_control_AND_3_is_2() {state = divider_reg & 0b0000100000;} public void timer_control_AND_3_is_3() {state = divider_reg & 0b0010000000;} public void timer_control_AND_3_is_0() {state = divider_reg & 0b1000000000;} public void timer_control_has_been_set() inline; // or just put these lines to where timer_control is set { // pointer array of 4 pointers StateOperation = StateOperations[timer_control & 3]; state_c = timer_control & 0x4; } public void tick_2() { divider_reg += 1; // call StateOperation here // this procedure allows several glitchy timer ticks, since it only measures falling edge of the state // so things like turning the timer off and resetting the divider will tick the timer // if ((state == 0 || state_c == 0) && (old_state > 0 && old_state_c > 0)) { if (((state & state_c) == 0) && ((old_state | old_state_c) != 0)) { timer_old = timer; timer += 1; // if overflow, set the interrupt flag and reload the timer (4 clocks later) if (timer < timer_old) { pending_reload = 4; reload_block = false; } } old_state = state; old_state_c = state_c; }
Language: cpublic void tick_2() { divider_reg += 1; // pick a bit to test based on the current value of timer control // switch (timer_control & 3) { // case 1: state = divider_reg & 0b0000001000; break; // case 2: state = divider_reg & 0b0000100000; break; // case 3: state = divider_reg & 0b0010000000; break; // case 0: state = divider_reg & 0b1000000000; break; // } int i = timer_control & 3; i = (i - 1) & 3; i = 0b0000001000 << (i * 2); state = divider_reg & i; // AND it with the state of the timer on/off bit state_c = timer_control & 0x4; // this procedure allows several glitchy timer ticks, since it only measures falling edge of the state // so things like turning the timer off and resetting the divider will tick the timer // if ((state == 0 || state_c == 0) && (old_state > 0 && old_state_c > 0)) { if (((state & state_c) == 0) && ((old_state | old_state_c) != 0)) { timer_old = timer; timer += 1; // if overflow, set the interrupt flag and reload the timer (4 clocks later) if (timer < timer_old) { pending_reload = 4; reload_block = false; } } old_state = state; old_state_c = state_c; }
Though I do provide a bad (but not absolutely horrible I guess) temporary encode, I VERY HIGHLY RECOMMEND you watch this on an emulator. There are a few things that are hard to see on the YouTube video. For instance, when Sabrina takes damage she does NOT turn invisible like it looks sometimes; she blinks every other frame. PLEASE just watch it on an emulator, but I uploaded it for those of you who absolutely insist not to, or those who want to watch it sooner and don't have an emulator on-hand.
About macros, while they do tend to improve performance, this is usually because they are the equivalent of inlining the whole code (instead of making potentially costly function calls). They are a pain to debug though (and sometimes understand), so I tend to avoid them whenever possible. Normally in C++, you can use __forceInline (or similar, depends on compiler) to force the compiler to inline functions. You can also do something similar in C# (as of .NET 4.5) by adding this attribute to a function: [MethodImpl(MethodImplOptions.AggressiveInlining)]. This is not exactly the same, but it will allow the compiler to inline the function in most cases, no matter the size of the function. Without this attribute, only very small functions will be inlined. Whether inlining will make it faster or not, though, really depends on the scenario - only testing will tell.
I'm not a programmer in real life
Those YouTube video ads
(Note that all methods except #3 don't modify the size of the picture.) Result: http://imgur.com/a/IpX59 It removes the mesh, but keeps the text more readable by strengthening vertical structures. It also works vertically (so there's also a bit of vertical blurring). I don't like how it makes the text a bit darker even when it shouldn't be, but that's for another day. EDIT: Unfortunately it's not suited for dithering that consists of columns only, which can be seen in the very first post in the bottom left corner.Language: Avisynthf = "castlevaniasotn-tas-maria-arandomgametaser.mkv" DSS2(f, pixel_type="RGB32") v0 = Method_0.Subtitle("original" , text_color=$FFFFFF) v1 = Method_1.Subtitle("add left neighbor at 50% intensity", text_color=$FFFFFF) v2 = Method_2.Subtitle("convolution" , text_color=$FFFFFF) v3 = Method_3.Subtitle("bilinear resize" , text_color=$FFFFFF) Interleave(v0, v1, v2, v3) function Method_0(clip c) { c PointResize(Width * 3, Height * 3) } function Method_1(clip c) { c.Layer(c, level=128, x=1) PointResize(Width * 3, Height * 3) } function Method_2(clip c) { c GeneralConvolution(0, " 0 1 0 1 0 1 0 1 0") c.Layer(last, level=128) PointResize(Width * 3, Height * 3) } function Method_3(clip c) { c BilinearResize(Width * 3, Height * 3) }
Comment/uncomment the 5 to see the different outcomes.Language: Avisynthtmp = Test s = defined(tmp) ? "yes" : "no" BlankClip.Subtitle(s) function Test { # 5 }
